• 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

Soldato
Joined
18 Oct 2002
Posts
7,640
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.
 
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
 
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.
 
Everything was at stock :s

Have rolled back to a previous BIOS and put 1.35v through it, will see what happens.
 
Back
Top Bottom