Blue Screen error comes suddenly--please help
roblem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033
Additional information about the problem:
BCCode: 116
BCP1: 81E06008
BCP2: 9B6119B0
BCP3: 00000000
BCP4: 0000000C
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1
Files that help describe the problem:
C:\Windows\Minidump\021712-19624-01.dmp
C:\Users\Administrator.TVPL\AppData\Local\Temp\WER-152646-0.sysdata.xml
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
February 17th, 2012 6:21am
if you have WinDbg, use that to debug your dump file: http://msdn.microsoft.com/en-us/windows/hardware/gg463009
otherwise, upload the dump file (from C:\Windows\memory.dmp) to SkyDrive and post it here for someone to look at.
Free Windows Admin Tool Kit Click here and download it now
February 17th, 2012 9:30am
STOP 0x00000116: VIDEO_TDR_ERROR
Usual causes: Video driver, overheating, bad video card, ?BIOS, ?Power to card (see Significant Posts section below)
Significant posts:
http://www.sevenforums.com/crashes-debugging/25912-bsod.html#post280172
"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 buildup and subsequently inadequate cooling." -
H2SO4
February 17th, 2012 4:36pm
Hello,
Bug Check Code 0x116: http://msdn.microsoft.com/en-us/library/windows/hardware/ff557263(v=vs.85).aspx
This indicates that an attempt to reset the display driver and recover from a timeout failed.
Please start by updating your graphic card driver and check results. If this does not help, please contact your manufacturer Technical Support for assistance.
You can also contact Microsoft CSS for assistance.
This
posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
Microsoft
Student Partner 2010 / 2011
Microsoft
Certified Professional
Microsoft
Certified Systems Administrator: Security
Microsoft
Certified Systems Engineer: Security
Microsoft
Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
Microsoft
Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
Microsoft
Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
Microsoft
Certified Technology Specialist: Windows 7, Configuring
Microsoft
Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations
Microsoft
Certified IT Professional: Enterprise Administrator
Microsoft Certified IT Professional: Server Administrator
Microsoft Certified Trainer
Free Windows Admin Tool Kit Click here and download it now
February 18th, 2012 6:28am