Windows has recovered from unexpected shutdown - Windows 7 64bit

#21
so Far so good. i got no errors.. i updated my mainboard bios and nvedia using the live update 5. i hope this resolves my problem. Thanks for the help Elmer :) and also to Trouble.. i will just post here if anything goes bad again :)
 


#22
I guess im back here.. my friend told me to reformat my PC.. to get rid of the error..ive already installed the latest from the latest drivers. including SP 1 and BIOS.. but i still got this error.. but it's locale ID is different from before
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033


Additional information about the problem:
BCCode: 116
BCP1: FFFFFA80053CA010
BCP2: FFFFF88010529AE4
BCP3: FFFFFFFFC000009A
BCP4: 0000000000000004
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1


Files that help describe the problem:
C:\Windows\Minidump\012112-20872-01.dmp
C:\Users\Cruz\AppData\Local\Temp\WER-37721-0.sysdata.xml


Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows


If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

here's the minidump. Thank you
View attachment 012112-20872-01.zip
 


Elmer

Extraordinary Member
#23
You're getting a Stop Error Code 116
(Link) "It's not a true crash, in the sense that the bluescreen was initiated only because the combination of video driver and video hardware was being unresponsive, and not because of any synchronous processing exception.

Since Vista, the "Timeout Detection and Recovery" (TDR) components of the OS video subsystem have been capable of doing some truly impressive things to try to recover from issues which would have caused earlier OSs like XP to crash. As a last resort, the TDR subsystem sends the video driver a "please restart yourself now!" command and waits a few seconds. If there's no response, the OS concludes that the video driver/hardware combo has truly collapsed in a heap, and it fires off that stop 0x116 BSOD.

If playing with video driver versions hasn't helped, make sure the box is not overheating. Try removing a side panel and aiming a big mains fan straight at the motherboard and GPU. Run it like that for a few hours or days - long enough to ascertain whether cooler temperatures make a difference. If so, it might be as simple as dust build up and subsequently inadequate cooling." - H2SO4
Ensure that none of the hardware is being over-clocked.
Ensure that the machine is adequately cooled. Chase out those dust bunnies!

A nasty dust bunny!
 


#24
Thanks for this info.. i dont know how to see if my hardware is over-clocked.. but my Mainboard has this special feature which is the MSI Global ? Mainboard - H61M-E23 (B3) ... but i already disabled it.. ill just try to open the case and blow up all dust bunnies..
thanks for this info.
 


Elmer

Extraordinary Member
#25
Let us know either way! (not just the bad ways!!). And give yourself a pat on the back for getting all your drivers / system up to date! Way to Go!!!

N.B. Did you get the latest bios from the 11th of this month? Addresses:
- Update CPU micro code.
- Update RAID option ROM.
- Improved memory compatibility.
 


#26
oh. i dindnt see that latest bios update. but im currently downloading it.. thanks :)
 


#27
hi.. i guess im back..
i have this latest dump file.... and i was wondering what is that sound means? coz everytime my PC hanged up or crashes .. it has this sound like i dont know how to explain.. but it sounds like theres something wrong.. anyway.
i guess it is still the error 116 but i have already updated my drivers .. including the latest BIOS.. i dont know what to do now :(..
 


Elmer

Extraordinary Member
#29
i guess it is still the error 116 but i have already updated my drivers .. including the latest BIOS.. i dont know what to do now :(..
Kaspersky can, on very rare occasions, contribute to BSOD's on some Windows 7 systems. I suggest, for experimental purposes, that you uninstall Kaspersky with the Removal tool for Kaspersky and download BSOD friendly Microsoft Security Essentials as its replacement. Make sure Windows firewall is enabled. Once your blue screen issues are resolved feel free to re-install an up to date Kaspersky set up.
 


Trouble

Noob Whisperer
#31
Michael:
You have a driver called
NTIOLib_X64.sys 10/20/2010 which I believe is associated with MSI Afterburner, a program which has known issues with Windows 7.
My suggestion at this point would be to consider uninstalling the program and afterward double check and confirm that NTIOLib_X64.sys is not present here C:\Windows\System32\Drivers (or anywhere else on your system for that matter) you may find it necessary to rename the file extension from NTIOLib_X64.sys to NTIOLib_X64.OLD to prevent it from loading. And of course if you were using that program to perform any CPU, Memory or Graphics Card overclocking return settings to default / normal / auto
See if that helps the issue at all.
Regards
Randy
 


#32
i made a search and i uninstall some MSI drivers that have the NTIOLib_X64.sys file ... i hope this will fix my problem.. Thank you so much
 


Trouble

Noob Whisperer
#33
Me too. Keep us posted and of course attach any new dump files if the problem persists.
 


#34
hi.. goodevening.. its been a week since the last time i opened my computer.. and lately i just received the error again. still the BBcode 116..

heres the dump file View attachment 020712-16645-01.zip
Thanks
 


Trouble

Noob Whisperer
#35
Hello Michael, sorry to hear things do not seem to be improving.
Code:
BugCheck 116, {fffffa8003e62390, fffff8800fcc6ae4, ffffffffc000009a, 4}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
[COLOR=#ff0000][U][B]Probably caused by : nvlddmkm.sys[/B][/U][/COLOR] ( nvlddmkm+c3bae4 )

[U][B]VIDEO_TDR_FAILURE (116)[/B][/U]
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8003e62390, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800fcc6ae4, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.

FAULTING_IP: 
nvlddmkm+c3bae4
fffff880`0fcc6ae4 4883ec28        sub     rsp,28h
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
CUSTOMER_CRASH_COUNT:  1
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
CURRENT_IRQL:  0
STACK_TEXT:  
fffff880`04dd6a48 fffff880`0fd61000 : 00000000`00000116 fffffa80`03e62390 fffff880`0fcc6ae4 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`04dd6a50 fffff880`0fd34867 : fffff880`0fcc6ae4 fffffa80`057c1000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`04dd6a90 fffff880`0fd60e0f : fffffa80`ffffd84d ffffffff`fffe7960 fffffa80`03e62390 00000000`0000000f : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`04dd6b40 fffff880`0f037ec1 : fffffa80`03a91aa0 00000000`00000080 00000000`00000000 fffffa80`05720300 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`04dd6bc0 fffff800`03361fee : 00000000`02548f9b fffffa80`05723060 fffffa80`036b49e0 fffffa80`05723060 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`04dd6c00 fffff800`030b85e6 : fffff880`02fd7180 fffffa80`05723060 fffff880`02fe1fc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`04dd6c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND:  .bugcheck ; kb
FOLLOWUP_IP: 
nvlddmkm+c3bae4
fffff880`0fcc6ae4 4883ec28        sub     rsp,28h
SYMBOL_NAME:  nvlddmkm+c3bae4
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME:  nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  4e99233b
FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
Followup: MachineOwner
I think that your focus should be on the TDR (Timeout Detection and Recovery) error. So take some time and read this article NVIDIA Statement on TDR Errors - NVIDIA Forums
Paying particular attention to the information regarding "Common issues that can cause a TDR" and "Things to check first" items.
Consider running FurMark (BURN-IN test, full screen, with whatever screen resolution you typically are using) watch your temps. Also consider overall system temperature issues as well as a possible problem with your PSU (Power Supply Unit) may be inadequate, failing and heating up itself or just unable to supply proper and consistent volts and amps required by your Nvidia card.
Regards
Randy
 


Last edited:
#36
Good day..I ran the Furmark software and while testing it.. i noticed that the temps. is raising higher than 60.. then all of a sudden restarted..
there might be some problem with my PSU, i dont know..
here's the dump file. View attachment 020812-38703-01.zip
 


#37
I guess i should upgrade my PSU unit.. since my PSU is buil-in from the casing... this is the only and last thing i need to do to fix my problem... Thanks :)
 


Trouble

Noob Whisperer
#38
Good day..I ran the Furmark software and while testing it.. i noticed that the temps. is raising higher than 60.. then all of a sudden restarted..
there might be some problem with my PSU, i dont know..
here's the dump file. View attachment 18536
Temperatures in the 60c range are not anything to be concerned about with your Nvidia GeForce GT 220, typically when running FurMark you'll likely see your temperature rise rather rapidly into the 60+ range but with a FurMark load of 99% or so you should see the temps level off somewhere near 68 to 69 degrees if the card is receiving proper cooling (fan functioning properly and free of accumulated dust, dirt and debris).
My concern is that your machine crashed, rebooted and produced another VIDEO TDR FAILURE (116).
Can you confirm that the card and the rest of your system is receiving proper cooling?
Do you have the option of trying another video card?
Regarding your PSU, I think that that is actually the problem. Looks like the specs for that unit is 18amps on +12Volts and I believe that particular card requires considerably more. Google your power supply and I think you will find other instances of issues with that particular unit being somewhat inferior regarding what it has available, it's 600 Watts but doesn't have the requisite muscle available in respect to amps.
Regards
Randy
 


This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.