Display driver amdkmdap stopped responding and has successfully recovered.

[nilo]

Display driver amdkmdap stopped responding and has successfully recovered.

I'm getting this error several times.
I'm on the Windows Desktop and screen goes black and the only thing I can see is the mouse pointer that does not move. Solution: reboot by clicking the reset button.

I'm running 12.3 whql drivers on 7 64bits.
I've already install a lot of drivers, using driversweeper, atiman.

And still same error: Display driver amdkmdap stopped responding and has successfully recovered. Black screen.

It only happens when I am using my PC, for instance surfing the net.

I leave my PC on during the day at home and when I come back from work, PC is running smoothly. When I start using it, black screen.

What is causing this? My graphic card? My PSU?

Some help would be appreciated, please.

[thatguy91]

I believe there is a GPU use issue regarding using a web browser... (not the browsers fault, its a driver bug). I notice if I am playing a video in mpc-hc and using Firefox on 8.960, the system freezes. If I just do one of the other, no issues (even if the video is paused). 12.4 should be out shortly.

[Laserbeast]

Just registered to let you know that I'm having the same exact issue on my new 2 week old PC. According to my event log, it's happened four times since April 10th. I thought it was a hardware fault, but after seeing this post and others, I believe it's a driver problem.

This happened to me while loading up a website in Chrome, and a couple times in BF3. But, I get exceptional game performance and no BSOD or random reboots. It has to be driver related.

My theory: 2D clocks are set to 100 Mhz Core, and 150 Mhz Memory and are making the driver crash under sudden loads. I'm trying to diagnose that as the problem, but I haven't had the issue when editing the profile XML to 300 Core, 800 Memory.

Hopefully 12.4 is out soon and this issue will go away. If anyone has any other fixes, please let us know.

[rflair]

You could try raising the default 2D voltage slightly.

This type of error is sometimes hard to diagnose though so try and keep track of what is happening at the moment it occurs, whats programs are running and such things.

[nilo]

so it's a driver fault?
where is the file profile to define settings?

what ati drivers are u using?

[linyanti]

I have two 5870's in Crossfire on an X58 with Vista 64. I have not been able to use any driver above 12.1 with or without the CAP's without the same problem you have.

Also, none of the newer drivers will uninstall for me. I have to use drive sweeper to get rid of them.

Since 12.1 without a CAP works great for me, I am just sticking with it.

I also have to underclock my videocards by ten percent using CCC Overdrive.

You could try those two things if nothing else fixes it.

[nilo]

i've installed 12.1 drvs.

let's see how this is running.

until now, no black screens.

[Saekerhett]

The last couple of days I had the same problem. Using 12.3 WHQL for my HD6850. But I never used Driver Sweeper to install new drivers and I believe over time some files may have gone corrupted. Now I used Driver Sweeper, went back to 12.2 (which is listed as 12.3 in CCC because they came out early march instead of february) and so far so good.

I'll keep an eye out.

[psyside]

12.1 is what you all need, regarding this issue! they are the most stable drivers if you want to avoid this problem, i tried 12.2/12.3/12.4 and none of them worked.....12.1 is the best option.

[nilo]

so far, so good. no black screens. no bsods.
12.1 drvs rule out.

[Saekerhett]

Hmm, yesterday I had the amdkmdap error again with 12.2 (early march). Now I have the new 8.97 April 18 drivers installed, but it's too early to tell if it helped. If it doesn't, I'm gonna reinstall Windows 7 and use 12.1. If that doesn't work either, I'm throwing that piece of **** out and buy a GTX 560 Ti.

Can't be my RAM (Corsair Vengeance CML8GX3M2A1600C9 Low Profile), tested it with memtest, 0 errors.
Can't be my PSU (OCZ ModXStream Pro 600 Watt), more than enough.

I think it's those piece of crap drivers, let's hope they come with a fix.

[Clouseau]

Do not solely count on memtest. All memtest is good for is letting you know if the ram stick is defective or not; only half the battle. If truly wanting to rule out bios settings as well, Prime95 needs to be run for a minimum of 24hrs without erroring out. Just becuase memtest said the ram was ok, does not mean the ram does not have issue when being stressed in combination with the cpu at the setting it is desired to be run at.

[Saekerhett]

Originally Posted by Clouseau

Do not solely count on memtest. All memtest is good for is letting you know if the ram stick is defective or not; only half the battle. If truly wanting to rule out bios settings as well, Prime95 needs to be run for a minimum of 24hrs without erroring out. Just becuase memtest said the ram was ok, does not mean the ram does not have issue when being stressed in combination with the cpu at the setting it is desired to be run at.

Maybe, but why did I keep getting those errors even when the pc is completely idle? And I now have the new april betas and it's fine so far.

[nilo]

at this time, i'm not doing any kind of OC.

just running Windows 7 x64 and 12.1 ati drvs.

until now, no black screens or bsods.

there is no need to reinstall 7.

[nilo]

Regarding this issue, anyone tried 12.4 drvs?

[psyside]

Originally Posted by nilo

Regarding this issue, anyone tried 12.4 drvs?

Yes its the same.

[onemoar]

disable powerplay/ULPS

[The Mac]

also if available, make sure wake by PCI/PCIe is enabled in the bios.

[Saekerhett]

I didn't see this error in over a month... Did a clean install of the 12.4 drivers and afterwards a complete reinstall of Windows because I bought an SSD, never saw this error again.