Vista and 7.3 Display driver atikmdag stopped responding error

xeav

7.10 fixes the problem?

Satja

Not for me.

Pentium Core2Due 4300
2 GB RAM Geil
Gigabyte GA-965B-S3
Sapphire Radeon X1950Pro
Vista Bussines x86

Black screens after 10-15 mins playing NWN2, Oblivion or X3. Tried all the solutions mentioned in this thread. None works. Back to the XP future

anonimuz

Same here. Nothing worked for me. I tried every single solution I can find on google, but I had no luck at all. In fact, as I write this message i get the atikmdag.sys death message (stopped resonding error). Addition to that, I thought I got rid of the BSOD after I updated my mobo bios. But for some weird reason, I just had the BSOD after my screen started blinking and crazily gettin the atikmdag.sys death message. Now the BSOD was all BLANKED BLUE SCREEN and i saw it for only 2 second the rebooted automatically.

Now, I have X1050 ATI Radeon AGP and running Vista Ultimate 32-bit. ~1.5gb of ram. ~2.0ghz cpu. My graphic card doesnt have a fan, but i have an internal fan just for it.

And whenever I play World in Conflict, I always get the same death message. However the game doesnt crash but it just waiting for resource blah blah then back again.

I ran out of any clue other than going back to XP. But I have another problem with XP. These problems just piles up. Whenever I play World in Conflict in XP, game always crashes after 10-15min. sometiems even when the game just started it crashes back to desktop with no error message at all. the game just completely exits. So i don't know what causes it. I assume soemthin about the graphic driver.

If anyone can give me an advice to solve this problem, either to get vista working smoothly or running world in conflict in xp perfectly, I would appreciate it.

EDIT: I Reformatted my computer to vista again, still having the atikmdag error.

Th3_VVr41th

I'm pleased to say that with the 7.10's, my fan problem seems to have vanished.

The rpm is still lower at idle than normal, but, the speed increases as it should as the temp of the gpu increases!
I have no idea what was done differently in this release, but ATI seems to have finally fixed my one and only problem!

P.S. I did also revert back to Bios 2004 on my P5W DH (due to issues with the on-board sound not disabling, yet again) So maybe this may have been the fix as well, (although I have a vague memory of having the issue with the 2004 bios as well) I didn't think to test before dropping the old bios back in, just figured i'd mention this.

__________________

vf-

You're brave with a BETA BIOS. It's one thing to use BETA drivers, its another ball game when its a BETA BIOS

You don't know what gremlins could be in that.

At least it's sorted now, one hopes!

Th3_VVr41th

The 2206 bios is an official bios for my board. Even so, you are correct, obviously something is wrong within that
bios since the on-board sound refused to stay disabled.

I reloaded it, (2206, had to know for sure) running it now in fact, and my card isn't exhibiting any issues with the fan, it still works!
(so it wasn't my bios change, but i'll be going back to the 2004 bios, to keep the onboard disabled as it should be).
ATI apparently changed something, or its a fluke, either way, so far, so good!

__________________

anonimuz

I checked the event viewer and found this :

[COLOR=#455b64]Log Name: System
Source: atikmdag
Date: 10/13/2007 7:33:00 PM
Event ID: 45062
Task Category: CRT
Level: Error
Keywords: Classic
User: N/A
Computer: PC
Description:
CRT invalid display type
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="atikmdag" />
<EventID Qualifiers="49152">45062</EventID>
<Level>2</Level>
<Task>44</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2007-10-14T02:33:00.543Z" />
<EventRecordID>1684</EventRecordID>
<Channel>System</Channel>
<Computer>yan-PC</Computer>
<Security />
</System>
<EventData>
<Data>
</Data>
<Binary>00000000010000002C00000006B000C00000000000 00000000000000000000000000000000000000</Binary>
</EventData>
</Event>[/COLOR]



[COLOR=black]Now, i dont know if these tells me anything but, i'm hoping that someone could find a solution for this... I been tryin to find a solution for this... and it's drivin me ...[/COLOR]

CATALYSTCATCHER

We are experiencing issues with AGP and the past few driver releases. They seem as wide spread and senseless as the TDR conditions in this thread. The AGP problems, when they occur, are usually pretty nasty.
I suggest you stick with Cat 7.6 unless you already know that the TDR is occuring with that as well.

Even though you get different message in Vista than XP it would seem that the problem is similar in both OS. It is likely that Vista knows something is wrong and restarts the display driver, but XP is unaware and the game just dies without any error.

Try different game settings and look for game patches that may apply.

Glad to see that your FAN issue is solved. I am not aware of any changes made to the driver that relate to this, but if 7.10 fixes the problem then obviously something has changed.

thirtyandover

Just curious, but does it do any difference, if we use just the driver without catalyst?
At the moment I'm using the 7.9 driver but only 7.3 catalyst(not really using it, but it's installed).

CATALYSTCATCHER

Well, if that combination actually works for you then it's fine. However, you may end up missing features that are supported in the driver, but CCC, being older, is not updated to handle. (That's why we suggest keeping CCC and the driver in sync.)

In any case, if you have a problem of any kind we are always interested to know if the problem occurs because of a bug in the display driver, or in CCC or is due to both from a specific version. From the user side..........whatever works on your system is the best choice.

Th3_VVr41th

It is definitely something different in the drivers. I loaded up a fresh install of vista and dropped the 7.9's in, and the fan again wasn't doing anything, and I got the ATIKMDAG errors.

I installed the 7.10's and the fan works fine, errors are gone. I'll be stress testing them out soon enough. I figured I'd install bioshock and stranglehold (newest games I have ATM, although I may keep Bioshock off the system due to the bullshit DRM/SecuRcrap/limitations) along with all of my favorites. I'll see how it goes, but so far it looks good.

Something was changed, and I'm not complaining.

__________________

CATALYSTCATCHER

I'll see what I can find out about the change that seems to have cured the problem. Hopefully it was made intentionally and will show in the change log, otherwise it (the fix) could vanish as quickly as it appeared and that wouldn't be good.

I hope your testing goes well.

Th3_VVr41th

So far so good, since my last post I've been cycling the GPU to full load, then back to idle, and the fan ups it's speed, no problems. I can do the "auto clock" function in the overdrive section, again, no driver errors, and the fan spins up in direct relation to the GPU temp. (the GPU and MEM clocks now max out as well, no glitches or problems, nice)

It used to crash all the time just with that alone. I installed Stranglehold, and have it running now, no glitches, no errors, nothing. This is the way it was meant to be played, heh heh.

I have a slight renewed faith in ATI, maybe I might pick up one of the newer cards soon, but my x1900xtx is running everything I can throw at it fine, so, I'm in no rush. I'll wait for dx10 cards to mature and get all the bugs out first.

P.S. the thought that this may not be a documented fix, and that it may just be a fluke really sucks! I hope it was something that can be tracked down, I really like not having to use another piece of software on my system just to keep my videocard from crashing & burning.

__________________

CATALYSTCATCHER

I agree with you completely. I hate a mystery and would really like to uncover a definitive link between a change in the driver and the fan issue. BTW, we don't publish a change log, because there usually a 1000 or more entries on a month to month basis. Many of these are administrative rather than bug fix changes and the manual effort is simply to great to complete on a regular schedule. But I will look.

Satja

Same problems on XP, but the games (Oblivion, NWN2) just freeze here for me to.

stained_green

I'm still getting the ATIKMDAG errors regardless of what I try ...

HD 2400 PRO (Various driver versions)
Vista 64
Asus s2n4 sli board
AMD 64 x2 4200+

HL2 seems to run ok (only ever crashed once) but bioshock, second life etc. all cause the error. Only games cause this for me.
As with others, the system ran fine for some time, then just started with the errors.

I normaly just sit it out and wait for the fix to be released, but this has gone on now for so long it's just getting tiresome. I personaly dont have the cash to spend on a new card, which it seems might not even guarantee a solution, and felt compelled to add my voice of frustration to the others here.

XianMaiPian

The same to me as stained_green.

Brand new HP 8510P

Vista 64
Adapter Type ATI Radeon Graphics Processor (0x9581), ATI Technologies Inc. compatible
Adapter Description ATI Mobility Radeon HD 2600
Driver Version 7.01.01.646
ATI Catalyst™ 7.10 Display

The "ATIKMDAG stopped responding" problem keep pop up and end up in crash. If I change the theme from Vista to Classic, it will not happen in most situation. But it will crash in WOW, even in the 3D properties of ATI Catalyst. It happen from the first day I bough this notebook.

Will anyone give me some suggestion? Will Vista 32 work more stable with ATI driver? Thanks!

biliskner

I've got same sort of problems.. however I seem to be experiencing them on both Vista 32 and XP SP2..

Everyone else seems to not have a problem with XP..

System:
Asus P5KC
Asus EAH2600XT with 256MB GDDR3
Sapphire 2600XT with 256MB GDDR3
in Crossfire

Display hang occurs both in crossfire mode and single (the asus card is primary) with balanced settings and heavy load.

It also happens when i'm doing non-intensive stuff like surfing the net.. clicking on a menu button.. clicking on a link etc..

I'm pretty sure it's not a mobo issue since i got that replaced first..
My gfx cards are about 2-3 weeks old.. and i've been getting this problem since I first plugged em in.. randomly.. could go for hours without any hiccups then 6 in a row.

I've tried with 7.9, 7.10 and "7.10 rc4"
Rc4 seemed to be the most stable for me.. but decided to join the crowd and crash as well..

I'll be trying 7.7 and 7.6 soon.. but not getting my hopes up -_-

adambu1988

Hi there I too have the problem Ahh! DAM ATI ! But i was looking at my Graphics card which is a AGP x1950 (its the HIS one but it should still be the same) and I noticed that the ice cooler fan was attatched to the card by 3 wires but when I unpluged it I noticed there was only 2 pins there the red and black ones where connected but not the white one . Can anyone elese check to see if your cards have 3 pins or not Thanks!

magicuyr

i had to respond here, spend my life reading this hoping for something.

motherboard: TA690G
gfx: onboard x1250

i have used vista 32 ultimate and got the atimdag errors constently no matter what, where when or how, hell i would get them even if the computer was doing nothing.

so have rolled back to x pro, thinking stuff vista! :-( yeah right 15 mins into watching numb3rs and bam it goes no error, no log just a black screen, it comes back eventually but there seems to be no sound going through the HDMI cable anymore.

whats going on here lol, well there is my rant yep its crap, its all crap instead of forward with hardware, we are now returning to windows ME days when crashes was the norm.

ARGGGGGHHHHHHH

full spec:

TA690G all drivers and bios to date
amd 6000 + (not overclocked YET)
2 gig ocz ram at 800mhz

thats it, runs at a core temp of about 30 degrees, and case is 30 degrees.
i dont get the 100% cpu, and no rise in memory either. as for ATI man, there is no scenario to duplicate computer can be sat there, doing nothing and the driver will fail in Vista and XP and that is with screen saver, power saving etc all disabled.

hope this helps

biliskner

Tried 7.6, 7.7, 7.9, 7.10
All random hangs.. win xp and vista..
should i be looking to return my card?
I mean seriously.. if it was crashing in a game i could say damn maybe it's a driver error.. but in windows? firefox?? while playing freecell???

CATALYSTCATCHER

Most of the reports in this thread point to system specific hardware problems. What makes things so difficult is that we have one message (stopped responding) from Vista but different scenarios for each case.

If you have any components that can be returned, particularly suspect components lieke the graphics card, I would certainly bite the bullet and take the card back for exchange. At the very least if the Vista message continues, you can think about some other cause of the problems. If you have read this thread, you will note that there are many things that have cleared the issue for individuals.

There is also a huge thread regarding NV cards suffering the same problem. The thread makes an interesting read, because it shows the truley random nature of the occurence of this issue.

Keep us posted.

Skeetz

Alright seriously- what am I supposed to do, not be able to play any games until this mysterious issue is fixed?

When I looked at my card's box, it had a shiny sticker reading "Vista Ready!". That means I expect it to work with Vista. And when I say work, I mean work properly.

I payed for the card, I expect it to work. I honestly don't know what to do. I've had the card for about six months now, and no fix means I can't use my PC for the number one reason I own one-to play games. I personally don't feel like waiting until ATi fixes their drivers, when that could be months.

ATI should be seeing what the people who do have this problem, like me, are doing/not doing, and what people who do not, are doing/not doing.

I can play Flash games and older games like Myth without problem- but anything new, such as the Orange Box, which I just spent $50 on, but can't play, because ATi seems to fix everything but this. Playing any modern game for more than 10-15 minuets gives me the driver failure message.

Seriously, when can we expect to see this issue resolved? I've tried waiting patiently, and that's not working.

magicuyr

okay update on scanario:

have played games on xp today, not many but have had no pops
but have once again tried to watch dvd and bam its off.

using the onboard HDMI as my secondary screen, this is defo not an issue with windows vista or XP, this is no argument down to ATI been unable to write decent drivers anymore.

this is probably due to out sourceing there programming to schools, so they can make more money, and as they wont pay for good programmers, everybody twiddles there thumbs, whilst chips and cards get pumped out by there thousands with supposible support from ATI. if your on XP then nvidea but i here that vista has problems with nvidea so not much choice really.

CATALYSTCATCHER are you saying that the drivers are fine, and everyone should return there motherboards and graphics cards, can i have this as official.... or are you saying that the drivers are so screwed in so many ways that you dont know how and where it actually is???? lol

CATALYSTCATCHER

I am saying that most of these weird issues are generally resolved by fixing some hardware. System memory is common, particularly when overclocked. Sometimes the graphics card, sometimes the PSU and numerous other HW issues.

As far as our drivers go, we do test with current popular games and we are not seeing the TDR issue.

Unfortunately these two quoted posts are excellent examples of "how not to be helpful ".

You didn't even mention which card you might have.

magicuyr

hi as you advice read the post

i mentioned that i had a biostar TA690G with onboard x1250 chip
this has the ability to have vga and HDMI with sound at once with sound too.

chip again is an AMD 600+ not overclocked

memory is OCZ OCZ2SOE8001G

windows xp pro SP2.

ram is not overclocked, but runs at 800mhz

power supply is Buy 430W CoolerMaster eXtreme Power*RS-430-PCAR from CCL - Online Retailer of the Year 2006

temp is at 46 degrees running dvd through it now.

no additional hardware has been added and bios is latest bios from biostar

to duplcate install windows xp pro sp2 and vlc player

plug in LCD monitor into vga run 1280 x 1024 resolution

connect HDMI tele through HDMI cable into HDMI slot, run HDMI at 1360 x 768

you will then play DVD in vlc player, push over to second screen ( runnning in the dual screen not clone mode) then right click and choose full screen..... leave this and POP 10 - 15 mins and you will get joy, if you dont, leave machine running for 24 hrs then play without re-boot.

you will have no recorded system message in XP dont know why but you will have no sound once HDMI content returns.

this should help yes?

magicuyr

one more note i would try this setup on vista ultimate also

Veridian3

Just wanted to pop in and say thanks to CatalystCatcher for all the hard work on this on. I appreciate that there is no solution yet but the effort is appreciated.

Dyre Straits

I'll second that! Well-deserved.

__________________

CATALYSTCATCHER

Thank you and I apologize for not remembering your system details. ( It would be really nice if everyone would add the basic details to their signature.)

Assuming a single problem, the other symptoms are likely due to the fall out of the graphics driver restart. For example, the loss of HDMI audio after the graphics driver is restarted.

At a glance nothing appears suspect in your system details. But I must admit I will need to look into the integrated graphics as most issues occur with the add-in graphics boards.

Driver details would also be helpful, but I assume you are running Catalyst 7.10 and have probably tried earlier versions with no apparent change in this issue.

I must re-iterate, that randomly occurring problems are usually hardware created, while driver bugs can usually be repeated without a lot of difficulty.

Your scenario seems quite random and occurs in both XP and Vista which is another reason to suspect a hardware issue.

Has there ever been a time when your system was reliable? Or have you always experienced this problem?