• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

Quick question - driver crashing

JamesM

JamesM

JamesM

Soldato
Joined
18 Oct 2002
Posts
7,639
Location
Sutton Coldfield, Birmingham
Would a faulty GPU (or GPUs) cause the AMD driver stopped responding error in windows?

Have tried Win 8 and 8.1, all drivers ranging from 13 to the latest 14 betas and it happens at random times at default GPU clocks.

Also would a GPU cause a system freeze on the desktop? Only really happens if the system is left for a period of time.

Event logger also reports this "Display driver amdkmdap stopped responding and has successfully recovered." at regular times.
 
Yep and have done a fresh install a number of times.

On system loadup it can sometimes take between 5-10 seconds for the desktop icons to show on the desktop too which I find odd as my AMD system shows them as soon as the desktop is up.
 
I've not had this with my 290, but when my GTX660 used to do this it turned out to be a faulty card.

Uninstall the drivers and use Driver Fusion and CCleaner to remove all traces of the AMD drivers, then re-install.
 
Is there anything I can do to put just the cards through their paces? Perhaps run heaven for a long period of time?

Thing is if I so much as look at a CPU overclock the system crashes/blue screens every time so that points to a CPU/motherboard/mem issue however i've swapped CPU and the problem still happens in regards to the desktop freezing? I'm at a loss really
 
JamesM said:
Would a faulty GPU (or GPUs) cause the AMD driver stopped responding error in windows?
Click to expand...

In answer to your question - YES it could!

You could try heaven or just try gaming with it, I know my 660 would crash the driver no matter which what I did.
 
Use OCCT James. That will test the core for instability/artifacts. If it produces errors at stock clocks/voltages RMA it.

LtMatt said:
Copy my settings. (ignore memory usage) This will sniff out a faulty or unstable gpu. If you get any errors at stock clock/voltage settings, then you know its faulty.

I7V7V05.jpg


OCCT detects tiny artifacts that would otherwise be hard to see whilst watching a short benchmark sequence or whist normal gaming. If it produces any errors, you know it's not fully stable.
Click to expand...
 
JamesM said:
Yep and have done a fresh install a number of times.

On system loadup it can sometimes take between 5-10 seconds for the desktop icons to show on the desktop too which I find odd as my AMD system shows them as soon as the desktop is up.
Click to expand...

In which case it may very well be a dodgy card. I'd try what LtMatt has suggested and see what results that comes up with.
 
I have been having the same problem as well ever since I got my 290, although it is very random, can happen during idle, games, youtube videos or even watching a film via MPC-HC, might happen within 10 min or could be ok for a few days, same with gaming, can play for 4 hours straight and nothing or it could crash within 10 min.

I have done DDU, reinstall of AMD drivers (various combinations i.e. no ccc or anything else except the driver)

Googled it and seems to be a pretty common problem and a few possible fixes:

http://www.tomshardware.co.uk/answers/id-1656824/atikmdag-sys-error-bsod-startup.html

And another thread on it:

http://www.overclock.net/t/1478456/bluescreen-error-0xa0000001-with-amd-290x

ATM I have only got the ATI driver installed and nothing else, no MSI afterburner etc. and have done that reg. fix for the atikmdag file. So far been fine but for all I know, it could crash again in a day, 5 days or whatever....
 
Running that.. it shows the voltages as follows

+3.3 = 1.99v
+5v = 3.36v
-12v = -7.05v
-5v = -6.57v

They look rather off don't they?
 
Cheers Nexus, glad it's not just me! Will look at those when OCCT has finished.

Is OCCT any good for CPU testing too?
 
Does it monitor the PSU side of things accurately?

This is a Seasonic which has only just been replaced as the original was faulty.

No errors found for 15 mins.
 
Last edited:
Just been running prime and system appears to have crashed/shutdown.

This is looking more and more likely to be a CPU/mobo/memory fault at the moment
 
Ok system had a CLOCK_WATCHDOG_TIMEOUT with everything at stock.

According to the might google this could indicate a hardware issue.

Have just run memtest and that found now errors so I guess this points towards motherboard or CPU now.

Cheers for the help guys, will keep investigating.
 
JamesM said:
Ok system had a CLOCK_WATCHDOG_TIMEOUT with everything at stock.

According to the might google this could indicate a hardware issue.

Have just run memtest and that found now errors so I guess this points towards motherboard or CPU now.

Cheers for the help guys, will keep investigating.
Click to expand...

Clock watchdog always means cpu vcore James. Up that mofo 2-3 notches.
 
Everything was at stock :s

Have rolled back to a previous BIOS and put 1.35v through it, will see what happens.
 
You must log in or register to reply here.
Back
Top Bottom