Vista and 7.3 Display driver atikmdag stopped responding error

reggie14

Isn't this a deficiency in the driver? Presumably its difficult for Windows to provide much feedback on the cause of the TDRs. But, you'd think that the video card drivers could log information that would provide helpful information for debugging purposes. It doesn't sound like they do that (nvidia's drivers included).

CATALYSTCATCHER

Not really. Logging information takes time and just like the end user the drivers assume the hardware is perfect so they can get on with the task of being fast. Think about it... If you had to call home and tell the wife every time you made a turn in your car or changed lanes, you would never get anywhere. (Extreme but a reasonable analogy)


If the driver had to log every action that was going to happen next the overall performance would be cut in half. At least half. In most cases the drivers expect everything to happen properly so they don't log every action. That's why debug/trace code is turned off in a production driver. A diagnostic program will keep a log but the diagnostic is under no pressure to run fast. It only needs to be thurough and accurate. Actually a windows memory dump is an attempt to capture the machine state at roughly the time of the problem, But as I am sure everybody knows an average PC will have 100s of MB of code in memory at any given time And 100s of MB of data flying around on the memory bus and PCIE bus and 10s of MB of texture data and device commands being issued per second. So when 1 bit of data is corrupted in some manner and that leads to a code loop without any exit a TDR will occur.

The real wonder is how most computers actually run properly in the first place.

Sunrazor

Ok I tried 2 different motherboards and 2 different brands of memory in different configurations. My 2 3850TurboX seems to work fine and dandy in my gf:s computer. CPU is hardly broken and the PSU gives stable voltage. I am out of clues. This gives me a headache and costs too much time and money.

Ran some Corsair RAM on a Gigabyte GA-P35-DS4 with the same results. Driver stops responding after a while or at random. Gonna roll back to 7.12 and see what happens when I get home tomorrow.


Gear:

CPU: Intel Q6600 Quad Core @ stock settings.
MB: Asus Maximus Formula X38.
RAM: Ocz Reaper 2 x 2048 Mb PC6400 @ specified timings and voltage.
GPU: 2 x HIS Radeon 3850 TurboX Limited edition 512Mb in Crossfire
PSU: Corsair TX750W

BFsMarvinTM

Tried again and same result. did a full uninstall of everything and then just installed the videodrivers and not the ccc and after 5mins it happened again. so I have gone to the 7.2 for now.
Hope this helps.

speedway

Hi,

I don't play games and also get the atikmdag error, but only during the start up of Windows Vista. I know have disconnected my second monitor out since it seems to be related to having a second device connected.

speedway

Hi,

I don't play games and also get the atikmdag error, but only during the start up of Windows Vista. I know have disconnected my second monitor out since it seems to be related to having a second device connected.

Best regards,
Pete

psies

I thought i had some luck with disabling AA and AF and AI from ATI
But no.. with Need for speed prostreet, the game crashes every few minute orso..

I now lowered the default settings of my videocard, HIS IceQ 3 Turbo 3870.
With default runs at 850Mhz and mem: 2400mhz.
I underclockt it to 825mhz en 2300Mhz for the memory.
Played NFS and COD4 and so far had no problems.

Sunrazor

Could this be a collision of some sort with Intel MB chipset drivers and ATI drivers? Just speculating here. I see alot of Intel boards with this. I am/have one myself. I am on the edge of dumping my ATI cards for Nvidia just to give it a shot and see if it disappears. This is like a digital nightmare.

gfish

Hi,

Been getting this error only since purchasing a HD3870 card. No other system upgrades, including OS, were made. Previous card was an nVidia 7600GS. To fix the problem, I have tried Catalyst 8.1 and 8.2, and Vista x86 and x64, including SP1 RTM. The problem does not go away, except when I detach 1 monitor from my extended dual-screen setup. This is not a feasible 'fix', however, and should not be suggested as such.

Current specs:
Intel Core 2Duo E6600
Gigabyte 965P-DS3P (Rev 3.3)
4gig 667 DDR2 Kingston (4x1Gig)
HIS HD 3870 IceQ 3 512MB GDDR4 PCIe (non 'turbo' version, NOT overclocked)
Vista x64 (SP1) [note: same error occurring under x86 Vista]
Catalyst 8.2 [note: same error under catalyst 8.1]

PSU: 600W SuperFlower Modular PSU

I understand this is not solely limited to ATi; nVidia cards are receiving this problem. However, it seems nVidia are more proactive in trying to determine a solution. This is evident by looking at the nVidia forums- there are numerous threads and replies regarding an equivalent error. I say this only to make ATi aware that they are potentially going to alienate customers if they do not devote appropriate resources to fixing serious issues such as this. I am seriously considering purchasing an nVidia card if this error is not fixed soon.

Thankyou.

EDIT: I have also run Memtest86 for >24 hours with no errors.

Tlz

I just saw that the Catalyst 8.3 drivers are out so I'm going to take a chance and install them. I'll post again if something happens. Still no problems with the 7.12 drivers.

scegg

I have the same problem on my new PC.

CPU: AMD 5000+ (Black)
MB: ASUS M3A (now in use) / SUPoX AK780U (Both tried)
Mem: Kingston DDR2-800 512MB*4
Video: XFX 8600GTS / Sapphire 3870 Std (now in use) (Both tried)
Disp: Samsong 245B + 940BW
Audio: Creative Audigy2 ZS (MB Audio is disabled)
PSU: 400W(PFC)
HD: Hitachi 160G*2 SATA
Other: ASUS 16X DVD, SONY DVDMulti, Samsung 1.44MB
Video Driver: All (shipped with hardware, newest from manufactory, newest from ATi/NVidia, older version from ATi/NVidia) (ATi 8.1 8.2 8.3 included)
OS: Windows Server 2008 RC1 Enterprise / Windows Server 2008 Trial Enterprise / Windows Vista Utimate / Windows Vista SP1 Utimate (All x64)

In Windows Server: Go black and auto-restart computer
In Vista: Maybe 1: Go black for 2 secs and then display TDR message.
Or 2: Go black for 2 secs and then display TDR message and still go black for 2 secs and then display TDR and still... yes, a dead circle until you press any key -> halt.

__________________
Allen St.Clair

VoMeT

I too like most here have been having the same problem, with alot of trial and error and a few format and installs, I can finally create mine on demand.

PC specs:
XP Pro / Vista Ultimate 32bit
ASUS Maximus Formula SE
Intel E6750 C2D
2x1gb Crucial Ballistix PC8500/1066
2xWD2500ks-raid0
Ati HD3870
Enermax 565w PS
X-fi Plat
bios 907 - and have used every single bios update they have and do not have.
Radeon 8.3 drivers, and have used the rest from 7.8 on.

I do not know how to log the error, but in creating it is easy for me now. For me is just setting the memory to 1066mhz in bios can create the driver not responding TDR, it took a long time to figure it out, but for me underclocking the memory has corrected the error (just happened to leave all settings at auto in bios, loaded everything OS,apps,games, utility's) everything ran awesome , no errors until I went back into bios to set the memory to stock speeds, then all hell breaks loose, and i have used corsair and crucial memory and both do exactly the same thing, if someone knows how to log the error, i'm more then happy to re-produce the error. But for me my cure has been to run my memory at PC6400/800mhz, defeating the purpose of buying 1066 memory but a temp cure at the most.

CATALYSTCATCHER

Workaround for sure.

But I must ask how the graphics driver causes the problem? If everything is fine (well no TDR) when you underclock and you are only changing the the system memory clocks the most likely diagnosis is that data gets corrupted in system memory or on the bus when it is read or written. Because the graphics driver passes image data and GPU instructions thru system memory when a bad/corupt instruction reaches the GPU then things go bad. If only image data were corrupt you may see display corruption but can also experience nasty problems if the data is related to a coordinate on the display. Graphics drivers do not generally check the sanity of the instructions or data, because that slows performance. This is what causes most of the bad scenarios in AGP systems. Particularly AGP using early AGP chipsets.

BTW: I can also get TDRs quite regularly if I use Overdrive on the GPU. But in my case no problem at stock clocks, just when I OC.

In a case like yours, you have a good repro and a serious clue. That being system memory speed. What would make a very interesting test, if possible without spending money. That is to try a graphics card from a different vendor and see if you still experience problems at 1066 memory speed.

VoMeT

I have used 3 different cards all with the same results ATI X1900GT which has been replaced with the HD3870 that was in my wifes PC, but i have claimed the new card , Sapphire HD 2600XT which is in my wifes PC now, and the recent Chaintech HD3870 which i am using today.
As I said in my earlier post that this was a cure for me to run at lower settings, never stating that it was a driver issue, but being able to reproduce the problem is a start but going any further then that for me is beyond my ability.

CATALYSTCATCHER

Thanks for clarifying. :-) This thread is littered with people blaming the video driver, so I just assumed. Sorry.

What I meant by a different graphics card, was a competitor card rather than a different manufacturer of ATI.

But most people don't have that luxury.

Unfortunate you spent extra on the faster FSB and memory but you can't use it. On the other hand, stable and running beats really fast and crashing any day of the week. I hate a pc that crashes. Particularly on the home front. Too much abuse at work I guess. :-)

VoMeT

I'll see what I can do, I have a friend with Nvidia card so I might borrow it for the day and see if I can reproduce the "nvlddmkm has stopped responding" by setting bios back to 1066. It may be later in the week but I will post back with some info of what happens.

inexile

Just recently started getting the "Atikmdag" error. I have tried many of the work arounds/fixes with no luck. Though I can produce the error on command 100% of the time. (The button of death!)Sometimes it goes through a series of recovering 4 times then crashing and or no recovery and blue screen. Is there anyway to log the error?

Sunrazor

I have tried running on a single GPU and this causes the problem to be smaller. Only occationally get the error. Still I find this unacceptable. Considering the effort I have gone through I am today dumping my ATI cards for Nvidia. I find no other solution viable at the moment after 2 brands of memory, 2 motherboards, countles checks and "fixes" tried. I am tired and angry so this is it for my ATI history.

BFsMarvinTM

well I tried the 8.3 drivers and still no fix still getting the error.
gone back to the 7.2 and will keep trying.

gwhiz2k

I hope I don't jinx myself here, but my problem seems to be getting better on its own. Running the same software, no changes, except I underclocked the GPU a very minute amount down again (695 GPU, 829 memory). I haven't had a looping TDR + lockup since March 3rd. Before that it was Feb 27. I had a couple of TDRs since, but no lockup. Last non-crashing lockup was March 5. Looking at all the problem reports, the issue seems to be on a trend of slowing resolving itself. I'm stumped. Since I have a fairly stable machine again, I'm afraid to upgrade to 8.3.

Tokage

I get the popular "Atikmdag" error on vista 32 bit with an "Peak Radeon HD3870", (can't play any 3d game or see full screen video)... So i tried changing graphic card (Asus EAH2400Pro) and with a different OS (Linux Ubuntu 64 bit) on the same computer and each OS with the latest (8.3) driver from Ati :


Vista 32 bit + Peak HD3870 --> Atikmdag stopped responding...

Vista 32 bit + Asus EAH2400Pro --> Tested 3 days with NO problems.

Ubuntu 64 bit + Peak HD3870 -- > Unable to play any 3d game more than 5 minutes (system crash, no Atikmdag error message but need reboot)

Ubuntu 64 bit + Asus EAH2400Pro --> No problem (tested 3 days)


This is my hardware:

CPU: Intel Core 2 duo E6850 @ 3 Ghz
Motherboard: Asus P5E3 Deluxe
Memory : CORSAIR DDR3 PC3-10666 - 2 x 1 Gb (2 Gb) 1333 MHz - CAS 9 - Silver DHX
Power supply: Antec Phantom 500W
Single monitor (Res : 1280x1024)

I hope this can help and not confuse people more :P
...Sorry for my bad English.. ^^

Spyre

The fact that it does the same thing in Linux and Vista would indicate its a hardware issue since the Vista and Linux drivers are wildly different. It is most likely power supply related issue or a faulty 3870 card.

This would also be confimed by the 2400 working fine since it uses less power.

__________________
ATI Beta Tester
game.AMD.Moderator

gfish

I have been reading alot that there are no issues with Catalyst 7.2. Is this the general consensus? If so, I might give 7.2 a try (I have a 3870).

SypherNL

It felt like the 8.3 drivers were better, the yellow exclamation mark disappeared after showing the balloontip (which wasn't showing up before).

But today, I had two crashes. One of them was pretty severe, in which my "automatic disabling of secondary monitor"-tool couldn't help. I had to manually disconnect my HDMI cable in order to get it back in control.

Normally, the issue would occur once a WEEK, not twice a day! Bloody hell...

On a side note: My ticket is open for 6 months now. 6 freaking months.
And every time they release new drivers, there is a huge list of new features and gameplay enhancements (wow 2FPS more while playing game XYZ) but the list of known issues is growing and growing. Why on earth are they focussing on new things instead of fixing the old?

I am really disappointed in the whole business, the support is really bad (at least CATALYSTCATCHER is trying his best), and they keep on sending me answers and questions of things I've already tried and/or answered.

Because I thought it was a PSU issue, I've replaced my PSU with one that has twice the amount of 12v lines and is more stable. This was a waste of money, 100 euro's down the drain for what?

CATALYSTCATCHER

What we need is a problem that we can reproduce fairly easily. Not the typical TDR that occurs at an unpredictable time and only a few times a week or even a day.

It has been mentioned before, but I will say it again. When you are prompted to send an error report to MS then please do. They actively collect the information and when they can see a pattern (similar devices, similar region, you name it) they will work with whomever to resolve/workaround the scenario. But they are stumpped by random events just like us.

The TDR events are not great PR for any of the involved parties. In fact if we could cure all TDRs we would. It would be a wonderful PR move.

xengren

Hey all,
I have the same problem on my laptop with an ATI Xpress 1150. I have solved it by turning off the Vista theme and using the classic theme. It's some weird conflict with Aero I think. Someone should just let ATI use Visual Studios 2005 to remote debug their machine. This doesn't seem like it would easily be fixed with just reports to MS. It's probably some sort of race condition that is causing a deadlock.

K.P.

reggie14

I just replaced my old AthlonX2/nForce4 system with a Q6600/P35 system, and transfered over my 3850 video card. Over the last week I've gotten 4 TDRs. So far they've all happened over night, when the machine is on, but not doing much. I'm still running Vista 32-bit and I've had SP1 installed for a while now. SP1 actually seemed to help a little on my old system. It seemed to cut TDR events roughly in half, although this new system has been getting them more often. I'm still running dual monitors, which seems to exacerbate the problem.

CatalystCatcher, should I RMA the card, or is that a futile effort?

Avictory101

Hey Everyone I am new here and was glad to see a place dedicated to finding out this problem I just started getting after upgrading my computer.

Of course my issue is being experienced with the ATI HD 2600 Pro AGP 8X I had bought.

Now I wish to point out with me is that this experience only started happening after I recieved my new components for the new tower I was building.

I had this EXACT same card in my old system which was:
K7S5A Pro
512MB DDR X1
AMD Athlon 64 1800+
400W PSU
Windows Vista Home Premium 32bit

with this older system the card worked and not once did I get that error problem. I was able to play games and watch videos with ease *not counting the constant lag I would recieve for sometimes having such a slow system* with never a display error popping up for me and leaving it on over night it would never give me that problem.

Now when I got my new system I started getting the atikmdag problem out of no where! In my new system I currently have:
MoBo: MSI K9MMV
CPU: AMD Athlon 64 X2 +4200
RAM: Super Talent 1GB DDR2 pc6400 800Mhz x2
PSU: 400w
Same Windows Vista Home Premium 32bit

Now when I get my problems it ALWAYS occurs when I am launching a game, watching a movie or when say when I try to acces anything that pops up the User Access Control window to give permission to access the program (i.e. Installing a program, accessing Device Manager)

Maybe this has already been addressed or talked about but was hoping maybe this info would help out to you all.

I have yet to see it ask me to send this info to MS to help study this problem. I am fairly knowledgeable with my computers but not too in depth with resolving issues such as these! I rather stick to my Graphic Design

But if something like this has been addressed and fix please let me know but thanks for reading this everyone!

Art

axmt

I own a Custom Built Level 5 Computer and have Found a solution that while shorts the useability of "EXTRAS" with an ATI Graphics Card Does Work. You Can find this Information at this link
atikmdag error message/computer freeze. - Vista Forums
Which is at an Official Vista Forum. Also To the AMD Staff Member we tried With One Stick of Memory,, No problem Until We INSTALLED the CATALYST CONTROL PANEL SOFTWARE.
The Driver works beautifully BY ITSELF. But the CATALYST CONTROL PANEL Causes the Error.. The Problem is with ATIKMDAG.SV this file is the one that is causing the Headaches. Read teh Above linked Post to see How My System engineer and I came to this Conclusion.

SypherNL

Very nice find, and I am willing to try it out here seeing I have this problem lots of times.
I removed the installation of CCC 8.3 from my PC, and I will try it out and report back.