|
Problem description: After playing Crysis 3 on my system for about an hour this morning, I've been having constant graphics driver failure and recoveries. You know the one, the system suddenly loses video, only to recover in about 5 seconds, with the word balloon at the bottom saying that the driver failed, but was able to recover. Attempted fixes: I've uninstalled and reinstalled the video driver. I have reseated the video card. Recent changes: I updated the video driver over a week ago, and have played heavy graphics games like Assassin's Creed III and Crysis 3 since then. I'm going to try to downgrade my driver next, but I'm worried this is hardware, because of this:  I loaded up SpeedFan to keep an eye on the GPU temperature. The first two spikes occur while viewing a 720p video on YouTube. The third spike happened completely randomly, while I was making this thread. This seems strange to me. Why would an overheat spike happen completely out of nowhere? And it's only spiking up to 55C. I would've thought a video card could at least survive up to that. It's not optimal, sure. (After posting this graph, I went AFK for a few minutes, and the card steadily rose to 70C. When I came back and started typing, it crapped out, and lowered back down to 50 instead of 30-40. Looking more and more like hardware...) Oh, one other 'recent change', kind of: it's one of the coldest days of the year here in central Florida. Um... it's 50 outside right now. We don't have the heat running. -- Operating system: Win7 Pro 64bit System specs: Custom built machine. Gigabyte Z68AP-D3, i2500k quad code, 8GB RAM, GeForce 670 2GB, 750W power supply, SSD boot drive and two HDDs. Location: Florida I have Googled and read the FAQ: Yes
|
| # ? Mar 3, 2013 22:14 |
|
|
|
| # ? May 25, 2013 06:04 |
|
|
Watch temperatures using the sensors tab of GPU-Z, SpeedFan isn't reliable. The GTX 670 begins throttling at 70C, so ideally it wouldn't exceed 69C in normal (gaming) workloads.
|
| # ? Mar 4, 2013 02:11 |
|
|
I just put my old 460 card in, and... it just happened again. (And a second time while writing this post.) Which is... good. Guess that will rule out hardware, unless I have some weird-rear end motherboard issue. And after working phone tech support on Dell workstations, I know that weird-rear end motherboard issues happen. I saw there was a Microsoft Fix It tool for this issue. I suppose I can try it, as at work, half the time when a customer calls in with a DVD drive issue, the Fix It tool for registry filters will solve the issue. But the fact that I have to change something dealing with timeouts on the GPU makes me feel like there is something more going on. Oh well... Edit: Fix It didn't fix it. God, is the next step really reinstalling Windows? Groan. Edit 2: I can run through Assassin's Creed 3 just fine. (And at the higher specs for my 670, too, so it's bad FPS, but it still runs fine.) Then I quit, get back to Windows, and the moment I try to drag a window, it craps out. Hrm... Aero? But it was the Uplay window, which doesn't use Aero, but whatever. Time to load up msconfig. Edit 3: Went into full diagnostic mode. I have GPU-Z and Process Explorer running. It took some time, but after browsing through imgur, I got the failure. GPU-Z says I had a GPU Load spike of 99%, while Process Explorer says I didn't. But PE does say I had a sudden CPU spike at the time. Just around 30%. Research tells me I have a virus. Revol fucked around with this message at Mar 4, 2013 around 04:10 |
| # ? Mar 4, 2013 03:18 |
|
|
Have you tried this? http://www.raymond.cc/blog/fix-nvid...ped-responding/
|
| # ? Mar 5, 2013 06:13 |
|
|
I've had the exact same issue with my Asus Geforce GTX 680, which also started after installing Crysis 3. I ended up reformatting my computer last night, though I can't say for sure yet if it has helped.
|
| # ? Mar 5, 2013 07:17 |
|
|
Zogo posted:Have you tried this? It was a virus. A very simple one. Just deleted two files from a temp folder, and the issue is resolved.
|
| # ? Mar 6, 2013 15:49 |
|
|
How did you find the virus? I'm getting this exact same issue after installing Crysis 3.
|
| # ? Mar 11, 2013 03:36 |
|
|
It's probably the bitcoin miner being bundled in lots of new Don Lapre fucked around with this message at Apr 2, 2013 around 13:38 |
| # ? Apr 2, 2013 05:34 |
|
|
|
| # ? May 25, 2013 06:04 |
|
|
After years without getting that error it hit me a few times last night. I had updated to the latest Nvidia driver lately but I think the culprit was a game I installed. It would often switch resolution and flash both my monitors during the game. I rolled back the video driver but that didn't help. Went back to a restore point from 3 days ago and the error hasn't come up since. We'll see over the next few days, though.
|
| # ? Apr 3, 2013 23:39 |
|
