GTX 680 Driver Crash

Status
Not open for further replies.

tramik

Distinguished
Oct 15, 2010
76
0
18,660
So this is what I’ve been dealing with – issues with mt GTX 680.

A few hours ago I installed the new Tomb Raider game, great. The moment I go to launch it, it crashes and I get the error from the nVidia panel: “Display driver NVIDIA Windows Kernel Mode Driver, Version 314.07 stopped responding and has successfully recovered.”

Look into it, okay – the GPU drivers apparently don’t like the games tessellation settings. Fine. Disabled. Runs the game fine.

Shortly after playing, my screen goes black for a split second, and comes up with the same error. Alright, I gave it a reboot. Shortly after surfing around, it happens again.

Alright, something with the drivers must be pooched.

Uninstalled the software and the drivers, did a clean sweep with Driver Sweeper. Rebooted and all that jazz. Installed the 314.07 driver (since they are newest ones), rebooted. Still happening. Sometimes right away, sometimes every 5-10 minutes, sometimes I can go 20 minutes without it happening… but it’s still happening.

I don’t even need to be doing anything specific, just opening a web browser and putting a bit of pressure on the GPU seems to do it.

Okay, so I look at the event Viewer to see what exactly is going on.

================================
- System
- Provider
[ Name] Display

- EventID 4101
[ Qualifiers] 0

Level 3

Task 0

Keywords 0x80000000000000

- TimeCreated
[ SystemTime] 2013-03-08T01:35:03.000000000Z

EventRecordID 100737

Channel System

Computer Tramik-PC

Security

- EventData
nvlddmkm

=====================================

Alright, so nvlddmkm stops responding and that’s why my drivers are crashing. Wipe out the drivers again, this time install older version 310.x. Same thing happens… in fact it happens with the beta 314.14 ones as well.

Look up some more stuff online. Some people think these crashes can be cause by overheating. I monitor my GPU with HWMonitor and that’s not the case, everything is cool. That, and as said before, it crashes even when I’m browsing or just surfing my start menu.

So finally, I remove all the drivers, shut my PC down, and reseat my GPU – unplugged it and everything. Set my bios back to factory default (I never OC’d my gpu, just my CPU) just to be sure. Reinstalled the 314.07 drivers. Still happening.

All this started right after I installed that damn game.

I’ve already submitted a ticket to EVGA with similar information. Any ideas would be just frickin’ fantastic – I’m bloody exhausted and frustrated… and would really like to avoid a reformat.
 
The game is completely uninstalled and it's happening on a regular basis now, without the game running at all. Happens during any game or even web browsing on occasion.

EDIT: Man, it's almost unbearable. Sometimes it happens 2-3 times back to back. Tried all the drivers I can get my hands on, even manually deleting nvlddmkm.sys.

I have an 850W OCZ psu. I don't suspect this is the issue since I've been running this rig fine for the last 6 months with this card, never an issue.

Now I'm starting to think I can hear a frequency sound coming from the gpu.... but I'm just not sure if it's in my head or it's always been there. Arg.
 
I am having the EXACT same issue and just registered to let you know. GTX 670, 314.14 beta driver. It was working flawlessly in Tomb Raider for the past week or so, but as of today, I am getting that driver error every few minutes in Windows itself. Literally the only thing I have done today is browsed the web and installed the new DLC for Mass Effect 3. Reboots did not help. What the hell is going on?
 
I am having the same problem, and went through the exact same scenario as the OP, same hardware.

I'm not sure if it was some microsoft auto update patch that did it. I used system restore to go back a few days. I uninstalled and reinstalled drivers to no avail. I did notice it saying something about a DirectX install in that time period in system restore.

Next step is to try to reinstall DirectX when I get home.

In games it black screens but usually comes back up without too much trouble, playing videos though it goes black and beeps and reboots and that is more annoying and irritating.

Let's keep this thread going with whats been tried and not worked out or what EVGA,etc says and hopefully we can figure something out.
 


Not sure, but it's one of the recent installs..

For me it was latest Nvidia Beta Drivers, Tomb Raider early in the week. Everything worked fine. Start installing the neverwinter beta client and notice that the driver stops responding/recovered error with a blank screen. Check logs and it did it in the middle of the night twice before it consistently started happening on Thursday afternoon. Played Tera fine and it would be intermittent with the driver stopped responding/recovered but usually when just idling around and not during heavy play.

Ran the EVGA OC stress test included in Precision X.

95% stress, temps never went above 60 and 0 artifacts problems, does this for 5-10 minutes then the driver stops responding.

Last time this happened was a year ago and I vaguely remember blowing out the dust, reseating, reinstalling drivers and reinstalling directx. The only thing I did not do this time is reinstall directx.

The only other thing I can think of is the PSU but this is more than coincidence someone has the same issues. I'm not sure if this is due to some Microsoft patch perhaps that auto installed(devious plan to encourage Windows8 😛) or what. If it was a bad PSU I think I would get hard lock ups in games and other system issues but it seems pretty isolated to the video drivers/card.

I was thinking it is not impossible for cards to go bad but I would hate to RMA and have it sent back after working okay for 2 minutes on someone's bench as is always the case, and this is just too much coincidence, there has to be a link somewhere.
 
There were some people on the steam thread with AMD cards and issues with this game as well.

I haven't installed Tomb Raider and haven't had issues with other games after going to the beta drivers last week. I've played other games as recently as 17 hours ago without any issues. I will definitely steer clear of TR for the time being.
 


Thank you for the information. I try to keep the machine patched up to date and firewalled and never browse on it. The last thing I would have thought to look at, I will definitely check this out.

It's kind of funny that I'm hoping that my machine has malware lol.
 


Yup, I found it last night actually and came here to bring word. It wasn't being detected by either windows defender or AVG. I managed to find it by watching the resource monitor closely along side my precision X resources... and boom, tagged it.

Works fine now.
 
Status
Not open for further replies.