All games crash after a short period of gameplay

Akagi

Akagi

Akagi

Caporegime
Joined
29 Jul 2011
Posts
37,077
Location
In acme's chair.
Hi guys, pretty much every game I play crashes after 10 - 15 minutes of gameplay. (it freezes and I have to tab out when I am informed that it has crashed)

GPU is stock and i'm running a stable CPU overclock. I also did two short memtest passes, but will do several extended ones when I sleep tonight, I also did a fresh graphics driver install having completely removed every last trace of the old ones. Nothing has made a difference. The system is completely stable doing everything apart from gaming. Watching HD video is fine, folding is fine, Kombuster, Furmark, IBT, Prime95, all fine.

My specs are as in my sig, the drive my games are installed on is a 1TB Samsung SpinPoint F3. There is a D:\Program Files (x86) directory in there.
Here are a couple of game crash logs:

Metro 2033:
Problem signature
Problem Event Name: APPCRASH
Application Name: Metro2033.exe
Application Version: 1.0.0.1
Application Timestamp: 4c7775b7
Fault Module Name: nvwgf2um.dll
Fault Module Version: 9.18.13.2049
Fault Module Timestamp: 51c4104b
Exception Code: c0000005
Exception Offset: 00726317
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 2057
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

Extra information about the problem
Bucket ID: 3671778791

Crysis 3:
Description
Faulting Application Path: D:\Program Files (x86)\Origin\Origin Games\Crysis 3\Bin32\Crysis3.exe

Problem signature
Problem Event Name: APPCRASH
Application Name: crysis3.exe
Application Version: 1.3.0.0
Application Timestamp: 02f3b040
Fault Module Name: crysis3.exe
Fault Module Version: 1.3.0.0
Fault Module Timestamp: 02f3b040
Exception Code: c0000005
Exception Offset: 00cc0c63
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 2057
Additional Information 1: e110
Additional Information 2: e110ba26e624d11dafb9207fbbaa95ab
Additional Information 3: 239c
Additional Information 4: 239ca5941e7e2f1aef3027c1451bc754

Borderlands 2:
Description
Faulting Application Path: D:\Program Files (x86)\Steam\steamapps\common\Borderlands 2\Binaries\Win32\Borderlands2.exe

Problem signature
Problem Event Name: APPCRASH
Application Name: Borderlands2.exe
Application Version: 1.0.10.24011
Application Timestamp: 51cb7785
Fault Module Name: ntdll.dll
Fault Module Version: 6.1.7601.17725
Fault Module Timestamp: 4ec49b8f
Exception Code: c0000005
Exception Offset: 00022353
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 2057
Additional Information 1: 79f0
Additional Information 2: 79f00ca709e9e46a95c902827f16d9ae
Additional Information 3: 5979
Additional Information 4: 59793ce2388da256252ca53d45ffffa4

And these are the video hardware error logs that I get alongside the crashes:
Description
A problem with your video hardware caused Windows to stop working correctly.

Problem signature
Problem Event Name: LiveKernelEvent
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 2057

Extra information about the problem
BCCode: 117
BCP1: FFFFFA8010A01010
BCP2: FFFFF88004A16E30
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1
Bucket ID: X64_0x117_Tdr:2_IMAGE_nvlddmkm.sys
Server information: d7d5b7e4-7387-488a-816a-82fe5980b473
Any help would be greatly appreciated, I need to get this sorted before i49! :(

There is a possibility that this only started after I installed more RAM, but i'm not 100% certain. I will try with 8GB of RAM removed after I have run memtest tonight.
I can also shove another GPU in and see if the issue subsides (a 570 DCUII), but I don't understand how the GPU can be at fault when it appears healthy, can fold 24/7 without a snag, and is Kombuster stable with temps staying below 65 at all times.

Cheers guys.
 
Last edited:
Idleman said:
Are you using an Nvidia card by any chance?
Click to expand...

I am indeed, as in my sig. A GTX660 (MSI Twin Frozr III OC)

Never had any issues before this starting up quite recently. (I say recently, it must be a couple of months give or take)

I don't like where this is going :(
 
take a look at howmuch vccio or vccsa voltage is used

whatever one is at stock 1.05v try with 1.10v to start with and see if its any better

8gb is usually ok on 1.05v but 16gb usually needs a bit more
 
wazza300 said:
take a look at howmuch vccio or vccsa voltage is used

whatever one is at stock 1.05v try with 1.10v to start with and see if its any better

8gb is usually ok on 1.05v but 16gb usually needs a bit more
Click to expand...

I've put it on my list of things to tweak after I next restart, thanks for the input. :)
 
acme15 said:
I am indeed, as in my sig. A GTX660 (MSI Twin Frozr III OC)

Never had any issues before this starting up quite recently. (I say recently, it must be a couple of months give or take)

I don't like where this is going :(
Click to expand...

The nvwgf2um.dll is associated with Nvidia drivers, as is Bucket ID: X64_0x117_Tdr:2_IMAGE_nvlddmkm.sys, you may want to update your Nvidia drivers or roll back, if you already have.
Have you also tried repairing your Crysis installation?, via the Origin app.
 
Idleman said:
The nvwgf2um.dll is associated with Nvidia drivers, as is Bucket ID: X64_0x117_Tdr:2_IMAGE_nvlddmkm.sys, you may want to update your Nvidia drivers or roll back, if you already have.
Have you also tried repairing your Crysis installation?, via the Origin app.
Click to expand...

Drivers are the latest, I think this happened with the previous version too. (there was an update quite recently IIRC)

Stupid question, but is there any way to roll back the driver version? Or do I just have to track down an old download? I'm guessing there is an archive on the NVIDIA download site? (never had to do it before, can you tell? Haha :p)
 
acme15 said:
Drivers are the latest, I think this happened with the previous version too. (there was an update quite recently IIRC)

Stupid question, but is there any way to roll back the driver version? Or do I just have to track down an old download? I'm guessing there is an archive on the NVIDIA download site? (never had to do it before, can you tell? Haha :p)
Click to expand...

You can try some of these. Use the Nvidia installer, this will completely remove the present driver.

http://www.nvidia.co.uk/Download/Find.aspx?lang=en-uk
 
For me, the best way to test a stability of an overclock is to actually play games. Have you tried down clocking to see if it stops?
 
WuMyster said:
For me, the best way to test a stability of an overclock is to actually play games. Have you tried down clocking to see if it stops?
Click to expand...

It was fine with my 4.7GHz overclock a while back, and then it stopped being okay (whether that be because of drivers of adding extra RAM or something else) but at the moment I am using my 4.6GHz overclock settings (same volts as 4.7) which has been my go-to 100% stable overclock ever since I bought the 2500K just after release.
 
you didnt install those nvidia drivers that were killing the cards did you? that was roughly a month back, then they quickly released a revised version.

Edit: I think it was 320.18
 
acme15 said:
It was fine with my 4.7GHz overclock a while back, and then it stopped being okay (whether that be because of drivers of adding extra RAM or something else) but at the moment I am using my 4.6GHz overclock settings (same volts as 4.7) which has been my go-to 100% stable overclock ever since I bought the 2500K just after release.
Click to expand...

I was actually talking about the GPU, have you tried down clocking on that?
 
Whenever a game crashes for me on an overclocked GPU its 99% always the overclock but if you're running CPU overclock too it could be either but more likely GPU.

It can be fine for 20 minutes or an hour and then BAM, down it goes.

I dial down the overclock, problem goes away. GPU freezing usually makes the screen go haywire/bizaare patterns onscreen and freezes the machine for me, CPU lockup usually freezes the machine completely keeping screen intact or BSOD's.

As pointed out above hardware degrades over time. Theres no such thing as a fixed stable overclock . If it worked when it was new doesn't mean it'll still work several years later. Two choices in that case, dial down the overclock or increase the voltage.

"A problem with your video hardware caused Windows to stop working correctly." - probably a clue there.
 
Last edited:
Upped the VCCIO to 1.1v, giving it another try now. And if only Windows error messages were that accurate or helpful Davy. :p
 
The game seemed to play better than previously, and I believe that I got a lot more gameplay in before the freeze. Have put the VCCIO on 1.125v now, giving it yet another try. Will report back. If this doesnt work, i'll try with 8GB of RAM only, if that works, i'll try 16GB of different RAM. If that doesnt work, i'll up the VCCIO a tad more.

If fiddling with the RAM makes no difference i'll switch out the GPU, if that works i'll RMA my 660, if it doesn't work, by that point im probably crying in a corner somewhere. :rolleyes:
 
Hit F5 and then F10 in BIOS, play some games to see if it crash's, at least that way you will know if it's related to a bad overclock.
 
Yeah i'll do that first actually. Cheers.
Crashed after 37 minutes, must remember to put the VCCIO back to default.
 
You must log in or register to reply here.
Back
Top Bottom