Display Driver Has Stopped Working and Has Recovered
  1 / 2    
I keep receiving the error in the title whenever I play World of Warcraft for over an hour or so. The screen goes black suddenly, WoW stops responding, and that message pops up. I have tried what Microsoft recommends (changing registry value for video timeout) and that has done nothing. Anyone have any ideas? Windows 7 64-bit Nvidia GTX 650 Ti with latest driver (as of 3/18/13) 8 GB DDR3 RAM AMD Athalon II X2 240 processor 850 W PSU
I keep receiving the error in the title whenever I play World of Warcraft for over an hour or so. The screen goes black suddenly, WoW stops responding, and that message pops up. I have tried what Microsoft recommends (changing registry value for video timeout) and that has done nothing. Anyone have any ideas?

Windows 7 64-bit
Nvidia GTX 650 Ti with latest driver (as of 3/18/13)
8 GB DDR3 RAM
AMD Athalon II X2 240 processor
850 W PSU

#1
Posted 03/18/2013 11:21 PM   
Start by going back to the [url=http://us.download.nvidia.com/Windows/306.23/306.23-desktop-win8-win7-winvista-64bit-english-whql.exe]306.23[/url] driver. Latest driver is BETA, previous one is BETA, I sure hope that is not the ones your complaining about. If that did not fix it, continue on down and give me all the information about your PSU to find it only. [url=http://www.piriform.com/speccy/download/standard]SPECCY[/url] run that and give the link as shown in the picture below please. [url=http://www.cpuid.com/downloads/hwmonitor/1.21-64bit.zip] CPUID HWMonitor [/url] Voltage / TEMP monitor / Logging program. [IMG]http://i307.photobucket.com/albums/nn286/Greybear1n2/Puvlish_Speccy.jpg[/IMG]
Start by going back to the 306.23 driver.

Latest driver is BETA, previous one is BETA, I sure hope that is not the ones your complaining about.

If that did not fix it, continue on down and give me all the information about your PSU to find it only.

SPECCY run that and give the link as shown in the picture below please.

CPUID HWMonitor Voltage / TEMP monitor / Logging program.



Image

My Opinion is no more important or right than yours. But if your using the LATEST drivers, go back to the prior set.

Piss Poor tech support blame all issues on drivers and assumes that your an idiot. Find a set that you know worked and see if the problem exists still.

""Don't f with it if it ain't broken!""

Constantly updating drivers is a good way to F'up the whole system.

#2
Posted 03/19/2013 01:27 AM   
When I said latest driver, I meant latest certified build, which in this case is 314.07. I tried going back to the 306.23 driver, but the installer gave an error saying there was no compatible hardware. Do you want the Speccy and CPUID stuff then? Or should I try going back to a driver version compatible with my card (i.e. 310.90, 306.97)?
When I said latest driver, I meant latest certified build, which in this case is 314.07. I tried going back to the 306.23 driver, but the installer gave an error saying there was no compatible hardware. Do you want the Speccy and CPUID stuff then? Or should I try going back to a driver version compatible with my card (i.e. 310.90, 306.97)?

#3
Posted 03/19/2013 03:16 PM   
Sorry about that, for all the 6xx series that the previous drivers covered, I am surprised the 650Ti was not in that version. [url=http://us.download.nvidia.com/Windows/306.97/306.97-desktop-win8-win7-winvista-64bit-english-whql.exe]306.97[/url] Yes on the other information please.
Sorry about that, for all the 6xx series that the previous drivers covered, I am surprised the 650Ti was not in that version.

306.97

Yes on the other information please.

My Opinion is no more important or right than yours. But if your using the LATEST drivers, go back to the prior set.

Piss Poor tech support blame all issues on drivers and assumes that your an idiot. Find a set that you know worked and see if the problem exists still.

""Don't f with it if it ain't broken!""

Constantly updating drivers is a good way to F'up the whole system.

#4
Posted 03/20/2013 12:17 AM   
Alright, I rolled back the driver to 306.97 Speccy: [url]http://speccy.piriform.com/results/LGaO5s4EZ2MwEOEAzjrLg50[/url] HW Monitor: [url]http://i.imgur.com/v2fiN0X.jpg[/url] And here is the PSU I have: http://www.newegg.com/Product/Product.aspx?Item=N82E16817153158&Tpk=thermaltake%20smart%20m850w&IsVirtualParent=1
Alright, I rolled back the driver to 306.97

Speccy: http://speccy.piriform.com/results/LGaO5s4EZ2MwEOEAzjrLg50

HW Monitor: http://i.imgur.com/v2fiN0X.jpg

And here is the PSU I have: http://www.newegg.com/Product/Product.aspx?Item=N82E16817153158&Tpk=thermaltake%20smart%20m850w&IsVirtualParent=1

#5
Posted 03/20/2013 01:11 AM   
Ok, Run the CPUID in the background and have it watch the voltage / Temps Right off the bat, if youll look at the 3.3v and the 12v, both CPUID and SPECCY show that the 3.3 is 3.0v and the 12c is pushing 13.3v Most will tell you not to believe a software monitoring program...but for me, if two are showing it, I would be looking at trying another PSU. Thats me. Also, it is showing that your RAM is underclocked at the wrong voltage and speed. Lets see how the Different drivers work for you. IF the Drivers make no Difference, Remove Half the RAM and try again.
Ok, Run the CPUID in the background and have it watch the voltage / Temps

Right off the bat, if youll look at the 3.3v and the 12v, both CPUID and SPECCY show that the 3.3 is 3.0v and the 12c is pushing 13.3v

Most will tell you not to believe a software monitoring program...but for me, if two are showing it, I would be looking at trying another PSU. Thats me.

Also, it is showing that your RAM is underclocked at the wrong voltage and speed.

Lets see how the Different drivers work for you.

IF the Drivers make no Difference, Remove Half the RAM and try again.

My Opinion is no more important or right than yours. But if your using the LATEST drivers, go back to the prior set.

Piss Poor tech support blame all issues on drivers and assumes that your an idiot. Find a set that you know worked and see if the problem exists still.

""Don't f with it if it ain't broken!""

Constantly updating drivers is a good way to F'up the whole system.

#6
Posted 03/20/2013 01:38 AM   
Alright, I'll let the CPUID run while I'm playing tomorrow and post back. In the meantime, What would cause my RAM to be at the wrong voltage and speed? The sticks are only a couple months old
Alright, I'll let the CPUID run while I'm playing tomorrow and post back. In the meantime, What would cause my RAM to be at the wrong voltage and speed? The sticks are only a couple months old

#7
Posted 03/20/2013 02:24 AM   
Well it is a DELL motherboard :) - voltages. That is where I am curious if reducing the amount of ram changes the issue, if so, it will prolley change the voltage as well. When enough voltage cannot be gotten, some items suffer and ram needs proper voltage to maintain data integrity. DDR2/DDR3 is generally on the 3.3v rail.
Well it is a DELL motherboard :) - voltages. That is where I am curious if reducing the amount of ram changes the issue, if so, it will prolley change the voltage as well.

When enough voltage cannot be gotten, some items suffer and ram needs proper voltage to maintain data integrity. DDR2/DDR3 is generally on the 3.3v rail.

My Opinion is no more important or right than yours. But if your using the LATEST drivers, go back to the prior set.

Piss Poor tech support blame all issues on drivers and assumes that your an idiot. Find a set that you know worked and see if the problem exists still.

""Don't f with it if it ain't broken!""

Constantly updating drivers is a good way to F'up the whole system.

#8
Posted 03/20/2013 02:45 AM   
Ok, this is after running WoW at medium graphics for about 2 hours with the new driver Speccy: [url]http://speccy.piriform.com/results/YSoNFz1A4BTRw0RHH8d213B[/url] CPUID: [url]http://i.imgur.com/Z46ZP6t.png[/url]
Ok, this is after running WoW at medium graphics for about 2 hours with the new driver

Speccy: http://speccy.piriform.com/results/YSoNFz1A4BTRw0RHH8d213B

CPUID: http://i.imgur.com/Z46ZP6t.png

#9
Posted 03/20/2013 09:09 PM   
You forgot to tell me if it crashed....Granted ""2 hours"" is ""over an hour or so"" but if it crashed, no real change.
You forgot to tell me if it crashed....Granted ""2 hours"" is ""over an hour or so"" but if it crashed, no real change.

My Opinion is no more important or right than yours. But if your using the LATEST drivers, go back to the prior set.

Piss Poor tech support blame all issues on drivers and assumes that your an idiot. Find a set that you know worked and see if the problem exists still.

""Don't f with it if it ain't broken!""

Constantly updating drivers is a good way to F'up the whole system.

#10
Posted 03/21/2013 12:42 AM   
Oops, sorry. It never crashed
Oops, sorry. It never crashed

#11
Posted 03/21/2013 02:42 AM   
I would call that good then. Make sure the Windows Updates are not set to install automatically optional updates. If it appears not to be fixed or the issue returns and the driver is still to the 306.97. try halving the memory.
I would call that good then.

Make sure the Windows Updates are not set to install automatically optional updates. If it appears not to be fixed or the issue returns and the driver is still to the 306.97. try halving the memory.

My Opinion is no more important or right than yours. But if your using the LATEST drivers, go back to the prior set.

Piss Poor tech support blame all issues on drivers and assumes that your an idiot. Find a set that you know worked and see if the problem exists still.

""Don't f with it if it ain't broken!""

Constantly updating drivers is a good way to F'up the whole system.

#12
Posted 03/21/2013 03:03 AM   
Alright, will do. Thanks a ton for the help
Alright, will do. Thanks a ton for the help

#13
Posted 03/21/2013 03:36 AM   
Welcome. Definitely keep us updated :)
Welcome. Definitely keep us updated :)

My Opinion is no more important or right than yours. But if your using the LATEST drivers, go back to the prior set.

Piss Poor tech support blame all issues on drivers and assumes that your an idiot. Find a set that you know worked and see if the problem exists still.

""Don't f with it if it ain't broken!""

Constantly updating drivers is a good way to F'up the whole system.

#14
Posted 03/21/2013 03:41 AM   
Alright, I got another crash again today while still using the 306.97 driver. I'll try take out half the RAM, as you suggested. What is the purpose of that? And should I be looking for something after I do that?
Alright, I got another crash again today while still using the 306.97 driver. I'll try take out half the RAM, as you suggested. What is the purpose of that? And should I be looking for something after I do that?

#15
Posted 03/26/2013 07:24 PM   
  1 / 2    
Scroll To Top