How to fix 'Display driver has stopped responding'?
Tags:
-
Graphics Cards
- Games
- Displays
-
Graphics
Last response: in Graphics & Displays
xero99
June 7, 2014 9:07:13 AM
I get this while playing games and itll just freeze then a message saying 'The display driver has stopped responding and has successfully recovered' will pop up. I've tried reinstalling drivers, down clocking gpu and increasing tdr delay but nothing seems to work
More about : fix display driver stopped responding
-
Reply to xero99
What drivers are you installing?
Try this cleaning utility: http://www.guru3d.com/files_details/display_driver_unin...
Then re download the driver installer and try again.
Try this cleaning utility: http://www.guru3d.com/files_details/display_driver_unin...
Then re download the driver installer and try again.
-
Reply to Suztera
m
0
l
Related resources
- How to fix display driver stopped responding windows 7 - Forum
- How to fix this? Display Driver Stopped Responding and Has Recovered - Forum
- fhow to fix the display drivers stopped responding and recovered successfully - Forum
- Fix display driver stopped responding - Forum
- FIXED!!! GTX 780 Display driver stopped responding and has recovered - Forum
xero99
June 8, 2014 5:17:04 AM
damric here are my specs:
FX 8350
ASUS M5A97 R2.0 Motherboard
Gigabyte R9 270x
XFX Pro 550W
Everything is on stock clocks and the recommended PSU wattage for my GPU is 500W. My PSU is XFX which I think is re-branded sea sonic so it should be good enough quality. I will try using the cleaning utility Suztera mentioned and reinstalling my Catalyst drivers but i don't expect it to solve the problem as i have tried it many times before.
FX 8350
ASUS M5A97 R2.0 Motherboard
Gigabyte R9 270x
XFX Pro 550W
Everything is on stock clocks and the recommended PSU wattage for my GPU is 500W. My PSU is XFX which I think is re-branded sea sonic so it should be good enough quality. I will try using the cleaning utility Suztera mentioned and reinstalling my Catalyst drivers but i don't expect it to solve the problem as i have tried it many times before.
-
Reply to xero99
m
0
l
xero99
June 8, 2014 10:47:44 AM
If you already re-loaded the driver, then you have hardware instabilities. It could be caused from any of the follwoing:
- Unstable CPU
- Unstable RAM
- Unstable GPU
A PSU with a defective capacitor will not be filtering ripple and could cause any of the above to become unstable.
I would run a stress test on the CPU first, something like prime95 for a few hours, or 20 passes of linx, or IBT.
If that checks out fine I would try MEMTEST86+ for a couple passes.
If memory and CPU both pass without errors, then you have narrowed it down to your GPU or PSU. Even good quality PSUs can fail once in a while. Typically it's the PSU that causes a graphics card to become unstable. I would consider RMA for PSU and/or Graphics card.
- Unstable CPU
- Unstable RAM
- Unstable GPU
A PSU with a defective capacitor will not be filtering ripple and could cause any of the above to become unstable.
I would run a stress test on the CPU first, something like prime95 for a few hours, or 20 passes of linx, or IBT.
If that checks out fine I would try MEMTEST86+ for a couple passes.
If memory and CPU both pass without errors, then you have narrowed it down to your GPU or PSU. Even good quality PSUs can fail once in a while. Typically it's the PSU that causes a graphics card to become unstable. I would consider RMA for PSU and/or Graphics card.
-
Reply to damric
m
0
l
xero99
June 8, 2014 11:20:50 AM
A while ago I was getting BSODs that were caused by Atikmdag.sys so I ran a memtest and found that one of my ram sticks was faulty (I was also getting the display driver error at the time). Since then ive been using the good stick and have had no BSODs but still the occasional stopped responding message while gaming. I found out that Atikmdag also causes the 'display driver has stopped responding' error so they were maybe linked.
Although i said id reinstalled the drivers many times i have not used software to completely remove the drivers, just the AMD uninstaller. So maybe It was/is a driver issue and the bad stick of RAM combined with it caused the BSOD?
Although i said id reinstalled the drivers many times i have not used software to completely remove the drivers, just the AMD uninstaller. So maybe It was/is a driver issue and the bad stick of RAM combined with it caused the BSOD?
-
Reply to xero99
m
0
l
xero99 said:
A while ago I was getting BSODs that were caused by Atikmdag.sys so I ran a memtest and found that one of my ram sticks was faulty (I was also getting the display driver error at the time). Since then ive been using the good stick and have had no BSODs but still the occasional stopped responding message while gaming. I found out that Atikmdag also causes the 'display driver has stopped responding' error so they were maybe linked. Although i said id reinstalled the drivers many times i have not used software to completely remove the drivers, just the AMD uninstaller. So maybe It was/is a driver issue and the bad stick of RAM combined with it caused the BSOD?
It really sounds like you have instability, like your RAM timings/voltage not set up right. I would run some prime95 blend for a few hours to verify.
-
Reply to damric
m
0
l
xero99
June 8, 2014 11:59:59 AM
damric said:
xero99 said:
A while ago I was getting BSODs that were caused by Atikmdag.sys so I ran a memtest and found that one of my ram sticks was faulty (I was also getting the display driver error at the time). Since then ive been using the good stick and have had no BSODs but still the occasional stopped responding message while gaming. I found out that Atikmdag also causes the 'display driver has stopped responding' error so they were maybe linked. Although i said id reinstalled the drivers many times i have not used software to completely remove the drivers, just the AMD uninstaller. So maybe It was/is a driver issue and the bad stick of RAM combined with it caused the BSOD?
It really sounds like you have instability, like your RAM timings/voltage not set up right. I would run some prime95 blend for a few hours to verify.
I am running prime 95 blend right now. If I'm looking for errors to show the system in unstable does that literally mean a BSOD or crash/freeze or will a message in Prime 95 on one of the tests or main thread say there was an error?
-
Reply to xero99
m
0
l
xero99
June 8, 2014 12:30:27 PM
Worker #6 encountered an error:
[Jun 8 19:46] Worker starting
[Jun 8 19:46] Setting affinity to run worker on logical CPU #6
[Jun 8 19:46] Beginning a continuous self-test to check your computer.
[Jun 8 19:46] Please read stress.txt. Choose Test/Stop to end this test.
[Jun 8 19:46] Test 1, 26000 Lucas-Lehmer iterations of M12451841 using AMD K10 type-2 FFT length 640K, Pass1=640, Pass2=1K.
[Jun 8 19:59] Self-test 640K passed!
[Jun 8 19:59] Test 1, 3200000 Lucas-Lehmer iterations of M172031 using AMD K10 type-1 FFT length 8K, Pass1=32, Pass2=256.
[Jun 8 20:08] Self-test 8K passed!
[Jun 8 20:08] Test 1, 21000 Lucas-Lehmer iterations of M14155777 using AMD K10 type-2 FFT length 720K, Pass1=320, Pass2=2304.
[Jun 8 20:20] FATAL ERROR: Rounding was 0.48828125, expected less than 0.4
[Jun 8 20:20] Hardware failure detected, consult stress.txt file.
[Jun 8 20:20] Torture Test completed 2 tests in 33 minutes - 1 errors, 0 warnings.
[Jun 8 20:20] Worker stopped.
Could you please explain what I should do next? Thanks for the help so far.
[Jun 8 19:46] Worker starting
[Jun 8 19:46] Setting affinity to run worker on logical CPU #6
[Jun 8 19:46] Beginning a continuous self-test to check your computer.
[Jun 8 19:46] Please read stress.txt. Choose Test/Stop to end this test.
[Jun 8 19:46] Test 1, 26000 Lucas-Lehmer iterations of M12451841 using AMD K10 type-2 FFT length 640K, Pass1=640, Pass2=1K.
[Jun 8 19:59] Self-test 640K passed!
[Jun 8 19:59] Test 1, 3200000 Lucas-Lehmer iterations of M172031 using AMD K10 type-1 FFT length 8K, Pass1=32, Pass2=256.
[Jun 8 20:08] Self-test 8K passed!
[Jun 8 20:08] Test 1, 21000 Lucas-Lehmer iterations of M14155777 using AMD K10 type-2 FFT length 720K, Pass1=320, Pass2=2304.
[Jun 8 20:20] FATAL ERROR: Rounding was 0.48828125, expected less than 0.4
[Jun 8 20:20] Hardware failure detected, consult stress.txt file.
[Jun 8 20:20] Torture Test completed 2 tests in 33 minutes - 1 errors, 0 warnings.
[Jun 8 20:20] Worker stopped.
Could you please explain what I should do next? Thanks for the help so far.
-
Reply to xero99
m
0
l
xero99
June 8, 2014 1:54:04 PM
After doing a CMOS clear I ran the test again and there was another error:
[Mar 30 22:36] Worker starting
[Mar 30 22:36] Setting affinity to run worker on logical CPU #3
[Mar 30 22:36] Beginning a continuous self-test to check your computer.
[Mar 30 22:36] Please read stress.txt. Choose Test/Stop to end this test.
[Mar 30 22:36] Test 1, 26000 Lucas-Lehmer iterations of M12451841 using AMD K10 type-2 FFT length 640K, Pass1=640, Pass2=1K.
[Mar 30 22:50] Self-test 640K passed!
[Mar 30 22:50] Test 1, 3200000 Lucas-Lehmer iterations of M172031 using AMD K10 type-1 FFT length 8K, Pass1=32, Pass2=256.
[Mar 30 23:02] Self-test 8K passed!
[Mar 30 23:02] Test 1, 21000 Lucas-Lehmer iterations of M14155777 using AMD K10 type-2 FFT length 720K, Pass1=320, Pass2=2304.
[Jun 8 21:48] FATAL ERROR: Rounding was 0.5, expected less than 0.4
[Jun 8 21:48] Hardware failure detected, consult stress.txt file.
[Jun 8 21:48] Torture Test completed 2 tests in 1679 hours, 12 minutes - 1 errors, 0 warnings.
[Jun 8 21:48] Worker stopped.
Ignore the time, it was behind when I started the test due to the CMOS.
How much would you recommend I increase the CPU and RAM voltage by?
[Mar 30 22:36] Worker starting
[Mar 30 22:36] Setting affinity to run worker on logical CPU #3
[Mar 30 22:36] Beginning a continuous self-test to check your computer.
[Mar 30 22:36] Please read stress.txt. Choose Test/Stop to end this test.
[Mar 30 22:36] Test 1, 26000 Lucas-Lehmer iterations of M12451841 using AMD K10 type-2 FFT length 640K, Pass1=640, Pass2=1K.
[Mar 30 22:50] Self-test 640K passed!
[Mar 30 22:50] Test 1, 3200000 Lucas-Lehmer iterations of M172031 using AMD K10 type-1 FFT length 8K, Pass1=32, Pass2=256.
[Mar 30 23:02] Self-test 8K passed!
[Mar 30 23:02] Test 1, 21000 Lucas-Lehmer iterations of M14155777 using AMD K10 type-2 FFT length 720K, Pass1=320, Pass2=2304.
[Jun 8 21:48] FATAL ERROR: Rounding was 0.5, expected less than 0.4
[Jun 8 21:48] Hardware failure detected, consult stress.txt file.
[Jun 8 21:48] Torture Test completed 2 tests in 1679 hours, 12 minutes - 1 errors, 0 warnings.
[Jun 8 21:48] Worker stopped.
Ignore the time, it was behind when I started the test due to the CMOS.
How much would you recommend I increase the CPU and RAM voltage by?
-
Reply to xero99
m
0
l
xero99
June 9, 2014 8:59:34 AM
With the increased voltages, so far all workers have passed the 21000 Lucas-Lehmer iteration test which is the test that caused the errors both times before. I will keep it running for a few hours like you said in-case there is still an error.
What do you think are good temps? Before I increased CPU voltage from about 1.3 to 1.4V it would max at 55 degrees Celsius socket temp and the package was a lot lower. Now the max socket temp is 65 degrees and the package is 48 degrees. Are these still good temps?
IF it is now stable what should I do next? If CPU/RAM was working properly wouldn't it be stable on stock settings? Please correct me or explain as I am a noob. lol
What do you think are good temps? Before I increased CPU voltage from about 1.3 to 1.4V it would max at 55 degrees Celsius socket temp and the package was a lot lower. Now the max socket temp is 65 degrees and the package is 48 degrees. Are these still good temps?
IF it is now stable what should I do next? If CPU/RAM was working properly wouldn't it be stable on stock settings? Please correct me or explain as I am a noob. lol
-
Reply to xero99
m
0
l
xero99
June 9, 2014 9:28:17 AM
I've had an error. What now, should I increase voltages more or not?
[Jun 9 16:10] Worker starting
[Jun 9 16:10] Setting affinity to run worker on logical CPU #4
[Jun 9 16:10] Beginning a continuous self-test to check your computer.
[Jun 9 16:10] Please read stress.txt. Choose Test/Stop to end this test.
[Jun 9 16:10] Test 1, 26000 Lucas-Lehmer iterations of M12451841 using AMD K10 type-2 FFT length 640K, Pass1=640, Pass2=1K.
[Jun 9 16:24] Self-test 640K passed!
[Jun 9 16:24] Test 1, 3200000 Lucas-Lehmer iterations of M172031 using AMD K10 type-1 FFT length 8K, Pass1=32, Pass2=256.
[Jun 9 16:34] Self-test 8K passed!
[Jun 9 16:34] Test 1, 21000 Lucas-Lehmer iterations of M14155777 using AMD K10 type-2 FFT length 720K, Pass1=320, Pass2=2304.
[Jun 9 16:47] Self-test 720K passed!
[Jun 9 16:47] Test 1, 1800000 Lucas-Lehmer iterations of M250519 using AMD K10 type-0 FFT length 12K, Pass1=48, Pass2=256.
[Jun 9 16:56] Self-test 12K passed!
[Jun 9 16:56] Test 1, 18000 Lucas-Lehmer iterations of M15597569 using AMD K10 type-2 FFT length 800K, Pass1=640, Pass2=1280.
[Jun 9 17:08] Self-test 800K passed!
[Jun 9 17:08] Test 1, 1100000 Lucas-Lehmer iterations of M420217 using AMD K10 type-1 FFT length 20K, Pass1=80, Pass2=256.
[Jun 9 17:17] Self-test 20K passed!
[Jun 9 17:17] Test 1, 18000 Lucas-Lehmer iterations of M17432577 using AMD K10 type-2 FFT length 896K, Pass1=896, Pass2=1K.
[Jun 9 17:19] FATAL ERROR: Rounding was 0.5, expected less than 0.4
[Jun 9 17:19] Hardware failure detected, consult stress.txt file.
[Jun 9 17:19] Torture Test completed 6 tests in 1 hour, 9 minutes - 1 errors, 0 warnings.
[Jun 9 17:19] Worker stopped.
The default settings for my RAM in the bios are not what they should be. For example I have 1600Mhz CL9 Ram but it is set to 1333MHz and the timings are all wrong. I will look on the corsair website and run the test again once I have tried to set everything to what it should be, if that could maybe help?
[Jun 9 16:10] Worker starting
[Jun 9 16:10] Setting affinity to run worker on logical CPU #4
[Jun 9 16:10] Beginning a continuous self-test to check your computer.
[Jun 9 16:10] Please read stress.txt. Choose Test/Stop to end this test.
[Jun 9 16:10] Test 1, 26000 Lucas-Lehmer iterations of M12451841 using AMD K10 type-2 FFT length 640K, Pass1=640, Pass2=1K.
[Jun 9 16:24] Self-test 640K passed!
[Jun 9 16:24] Test 1, 3200000 Lucas-Lehmer iterations of M172031 using AMD K10 type-1 FFT length 8K, Pass1=32, Pass2=256.
[Jun 9 16:34] Self-test 8K passed!
[Jun 9 16:34] Test 1, 21000 Lucas-Lehmer iterations of M14155777 using AMD K10 type-2 FFT length 720K, Pass1=320, Pass2=2304.
[Jun 9 16:47] Self-test 720K passed!
[Jun 9 16:47] Test 1, 1800000 Lucas-Lehmer iterations of M250519 using AMD K10 type-0 FFT length 12K, Pass1=48, Pass2=256.
[Jun 9 16:56] Self-test 12K passed!
[Jun 9 16:56] Test 1, 18000 Lucas-Lehmer iterations of M15597569 using AMD K10 type-2 FFT length 800K, Pass1=640, Pass2=1280.
[Jun 9 17:08] Self-test 800K passed!
[Jun 9 17:08] Test 1, 1100000 Lucas-Lehmer iterations of M420217 using AMD K10 type-1 FFT length 20K, Pass1=80, Pass2=256.
[Jun 9 17:17] Self-test 20K passed!
[Jun 9 17:17] Test 1, 18000 Lucas-Lehmer iterations of M17432577 using AMD K10 type-2 FFT length 896K, Pass1=896, Pass2=1K.
[Jun 9 17:19] FATAL ERROR: Rounding was 0.5, expected less than 0.4
[Jun 9 17:19] Hardware failure detected, consult stress.txt file.
[Jun 9 17:19] Torture Test completed 6 tests in 1 hour, 9 minutes - 1 errors, 0 warnings.
[Jun 9 17:19] Worker stopped.
The default settings for my RAM in the bios are not what they should be. For example I have 1600Mhz CL9 Ram but it is set to 1333MHz and the timings are all wrong. I will look on the corsair website and run the test again once I have tried to set everything to what it should be, if that could maybe help?
-
Reply to xero99
m
0
l
If increasing voltages helps, then it would lead me to think that your PSU or motherboard is not filtering properly, meaning ripple is fluctuating such that it causes errors when the sine wave hits a valley. This is usually caused by a leaky capacitor.
Your RAM should work fine at 1333 at default settings. I would leave it at that until you have fully diagnosed your problem. I think the next step is to try a different PSU.
Your RAM should work fine at 1333 at default settings. I would leave it at that until you have fully diagnosed your problem. I think the next step is to try a different PSU.
-
Reply to damric
m
0
l
xero99
June 9, 2014 10:47:12 AM
xero99
June 9, 2014 10:51:26 AM
xero99
June 9, 2014 11:00:23 AM
Presler said:
It may be a dying gpu too. Mine died soon after this error was displayed. Try re-installing drivers as run as administrator. I don't know how it helps but it resolved mine. Also be prepared to rma your gpu.I have tried reinstalling drivers and it didn't help. At the moment I am more concerned about the prime 95 errors as that shows there is a hardware issue in something other than GPU and the same thing causing the prime 95 errors may be causing my 'display driver has stopped responding' errors? My GPU is less than 6 months old, and so is the rest of the system apart from the RAM which is two years old.
-
Reply to xero99
m
0
l
Related resources
- Solved[SOLVED] Display driver stopped responding. GTX 970 superclocked Forum
- SolvedDisplay driver stopped responding and has recovered Forum
- Solved''display driver has stopped responding and has recovered'' Forum
- SolvedDisplay driver nvlddmkm stopped responding and was recovered. Forum
- SolvedBSoD,Freezes,0xa000001,Display driver stopped responding Windows 8.1 Forum
- SolvedAMD display driver has stopped responding and has recovered Forum
- SolvedAMD vision Display driver stopped responding and has recovered Forum
- SolvedDisplay driver stopped responding and has recovered. Forum
- Solved"Display driver stopped responding and has recovered" Forum
- SolvedNvidia 331.93 display driver stopped responding and has recovered! Forum
- SolvedDisplay Driver Stopped Responding and has Recovered in Windows 8.1 Forum
- SolvedDisplay driver stopped responding and has recovered {nvlddmkm error] Forum
- SolvedDisplay Driver stopped responding, New GPU (Gigabyte GTX 780 Ghz) Forum
- SolvedBlue screens during gaming(Dota 2) and Display Driver has stopped responding Forum
- SolvedDisplay driver stopped responding and has recovered Forum
- More resources
Read discussions in other Graphics & Displays categories
!