After 6 month without a problem - everyday BSOD 0x00000116 - help needed

Hi,

I had 0 issues with my M17x R3 for the last 6 months. Until last week. since that, it started with BSOD 0x00000116 every day, during playing BF3. The behaviour is, it runs flawlesly for random period of time. then sudently, there is a "lag" lets say, the screen stops working for 1 second, then it moves forward for next 1 second, and then immediatelly BSOD 0x00000116.

See the 3 minidumps included.

I really need help. I didnt changed anything in last month.

I also try to reload the image, i created 6 months ago (acronis true image home) , but the behaviour is the same, on that image also......

 

what are your 580m temps like during gaming? Have HWINFO64 on while you game
Have you installed any custom bios?


STOP 0x00000116: VIDEO_TDR_ERROR
Usual causes: Video driver, overheating, bad video card, ?BIOS, ?Power to card (see Significant Posts section below)

Bug Check 0x116: VIDEO_TDR_ERROR (Windows Debuggers)

 

no custom bios, default I think A08.

all clockes are default. The system run without any errors for 6 months. Can someone please investigate the minidumps ?

Thank you.

Regarding temperatures i dont know, didnt read them yet, but will do and post it here ASAP.

 

Hi Tigress,

Looks like Slick investigated already and looks to be a heat issue. Definitely post the temps you are getting.

 

so here is a scan of 30 minutes of Playing BF3, all at Ultra settings.
As from what i see the max tempeture 580m goes is 69 degree Celsius, which is ok, it didnt reach 78 degrees (throttling). So it looks like its not heat issue.....
weird is, sometimes, it goes (BSOD) after 5 minutes of gaming, sometimes after 5 hours......

EDIT: hmmm. now i started the game after a while again, and it falls BSOD during first 2 minutes....
again BSOD 0x00000116, the temperature cant go so high in first 2 minutes..... , i think its definetly not issue with Temperature...

 

ok, the next thing to do on the debugging path is to reinstall your driver. Don't use a beta.

Use driver sweeper to clean out the previous nvidia driver first

 

you know, i only installed the driver 285.62 (official) 6 months ago. didnt changed it yet . so do you think this is a good idea ?
it was working fine for whole 6 months.

 

Bro, things get corrupted sometimes. Reinstallation of the driver is a very good idea. Do that next. We are just eliminating what could be causing your problems ina systematic order

 

fine men, fine. Im ok with that, just asking....
So now im going to reinstall the drivers... 285.62 with the cleaning option.

Then ill test it again, and let you know.

EDIT: Before i made the new test, 1 remark. From 10 logons into windows , 1/10 it will fall into "not aero" environment. when rebooted, then is ok again, AERO on. This is happening since day 1, but i wouldnt call it an issue..... dont know if this could have some connection...

EDIT2: drivers reinstalled with cleaning, now performing test BF3 again.........

 

install 296.10 WHQL (don't install 285, install this one, there are a ton of optimizations going on in both sides, nvidia and bf3, maybe they somehow screwed up the path of one library and it is causing backwards compatibility errors), as Slick says, computer is a weird thing, everything you install goes into registry, as registry gets crowded your computer can start to throw errors at you, just do a reinstall of drivers, but WHQL, not betas

for the aero issue install the following

R315150.exe

from dell website

 

thank you very much. Right now, i have re installed 285.62. for 2 hours of BF3 no BSOD, but ill test it also within next days. When it occures again, ill try the new 296.10 drivers, and let you know, right when new BSOD appears.

 

good to hear Tigress, keep playing!

 

did you check your CPU temps too?

 

checked ur minidumps and i found this

Code:

crash dump file: C:\Windows\Minidump\041412-22198-01.dmp
This was probably caused by the following module: nvkflt.sys (nvkflt+0x1AF14) 
Bugcheck code: 0x116 (0xFFFFFA800FC02430, 0xFFFFF880031C3F14, 0xFFFFFFFFC000009A, 0x4)
Error: VIDEO_TDR_ERROR
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed. 
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvkflt.sys . 
Google query: nvkflt.sys VIDEO_TDR_ERROR

seems like your driver may have become corrupted. also could be conflicting video codecs which use hardware accel but since you got BSOD while just running BF3 i'd say it's the former.

 

thank you very much to all of you.

Today another 3 hours of playing, still no BSOD.
Ill test it lets say another 20 hours. I keep you informed. I pray, the driver was really corrupted. (im glad its not the 78 degree throtling issue).



But can someone explain me this:
6 month ago, i created TIB file, (acronis true image home) of my whole C: drive (full backup). The drivers was working fine for whole 6 months. after ive got 7 reboots during last week, i reload the image from october 2011. And now: How is possible that the driver was also corupted in this image (The BSOD continue after reloading the image) ? Or the registry isnt copied from TIB file ? I really dont understand this.

 

ack!
acronis oh no.

funnily enough i had data corruption due to using acronis, i have since avoided that software like the plague. now resorted to using windows backup... yes that desperate, but it works... without my precious files being destroyed in the process.

 

I've been using Acronis for years and have several (dozen +) restores and haven't had a problem. That being said, I'm sure others have had issues such as yourself xeroxide. I've never had a corruption issue that wasn't fixed with a restore, so not certain why your image would have the driver corrupted.

Glad that you were able to get it running with the reinstall though.

 

so... another 4 hours of play BF3, still no BSOD. looks promising.

Thank you very much to all...

 

grrrrr, after 10 days of normal playing, another BSOD. see dump

 

Try instaling the latest non beta drivers and stop using that old one the new one is 296.10: Drivers - GeForce

 

That sucks. If I were you, I'd probably just wipe out the hard drive and start from a clean install of everything.

 

Good call as long as she uses the latest drivers. I think if she keeps putting the old drivers back in she will continue to have issues.

 

ok, ill try the latest drivers.

 

Please let us know how it works out for you.