Problem devices:
Code:
High Definition Audio Controller PCI\VEN_10DE&DEV_0BE5&SUBSYS_14703842&REV_A1\4&2EB3824&0&0118 This device is disabled.
Possible outdated drivers... Those in red are known to cause issues with Windows 7 and should be removed; the red dates mean the driver needs to be updated ASAP:
Code:
ASACPI fffff880`0f211000 fffff880`0f219000 Sun Mar 27 20:30:36 2005 (42476c4c) 00003c77 ASACPI.sys
RTCore64 fffff880`0b33a000 fffff880`0b340000 Wed May 25 00:39:12 2005 (42941d90) 00004158 RTCore64.sys
PxHlpa64 fffff880`01095000 fffff880`010a0700 Wed Oct 17 12:25:02 2007 (4716537e) 00015810 PxHlpa64.sys
wdcsam64 fffff880`0402d000 fffff880`04030880 Wed Apr 16 02:39:08 2008 (4805bb2c) 0000d887 wdcsam64.sys
ALSysIO64 fffff880`08018000 fffff880`08020000 Sun Apr 19 13:41:04 2009 (49eb7e50) 0000bbad ALSysIO64.sys
ASACPI: See below...
RTCore64: RivaTuner/EVGA Precision/MSI Afterburner (known issues w/Win7)... Remove from the system.
PxHlpa64.sys
wdcsam64.sys
ALSysIO64.sys
Code:
-
Loading Dump File [D:\Kingston\BSODDmpFiles\Homeuser66\Windows_NT6_BSOD_jcgriff2\022912-17518-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`04576500?
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e4b000 PsLoadedModuleList = 0xfffff800`03090670
Debug session time: Wed Feb 29 09:55:08.101 2012 (UTC - 7:00)
System Uptime: 0 days 2:30:52.036
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, fffffa800a3b4050, fffff80004576518, fffffa800f0e6010}
*** WARNING: Unable to verify timestamp for iaStorV.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStorV.sys
Probably caused by : iaStorV.sys
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa800a3b4050, Physical Device Object of the stack
Arg3: fffff80004576518, Functional Device Object of the stack
Arg4: fffffa800f0e6010, The blocked IRP
Debugging Details:
------------------
DRVPOWERSTATE_SUBCODE: 3
IMAGE_NAME: iaStorV.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4c11875b
MODULE_NAME: iaStorV
FAULTING_MODULE: fffff880010b9000 iaStorV
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
STACK_TEXT:
fffff800`045764c8 fffff800`02f35cd2 : 00000000`0000009f 00000000`00000003 fffffa80`0a3b4050 fffff800`04576518 : nt!KeBugCheckEx
fffff800`045764d0 fffff800`02ed35fc : fffff800`04576600 fffff800`04576600 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x34a90
fffff800`04576570 fffff800`02ed3496 : fffffa80`0d7afc68 fffffa80`0d7afc68 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`045765e0 fffff800`02ed337e : 00000015`136f1f87 fffff800`04576c58 00000000`0008da9f fffff800`03041668 : nt!KiProcessExpiredTimerList+0xc6
fffff800`04576c30 fffff800`02ed3167 : 00000005`7ee647c5 00000005`0008da9f 00000005`7ee647fd 00000000`0000009f : nt!KiTimerExpiration+0x1be
fffff800`04576cd0 fffff800`02ebf96a : fffff800`0303de80 fffff800`0304bcc0 00000000`00000000 fffff880`0ffa4db0 : nt!KiRetireDpcList+0x277
fffff800`04576d80 00000000`00000000 : fffff800`04577000 fffff800`04571000 fffff800`04576d40 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: X64_0x9F_3_disk_IMAGE_iaStorV.sys
BUCKET_ID: X64_0x9F_3_disk_IMAGE_iaStorV.sys
Followup: MachineOwner
---------
-
Loading Dump File [D:\Kingston\BSODDmpFiles\Homeuser66\Windows_NT6_BSOD_jcgriff2\022212-32448-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e05000 PsLoadedModuleList = 0xfffff800`0304a670
Debug session time: Wed Feb 22 10:38:28.861 2012 (UTC - 7:00)
System Uptime: 0 days 0:00:48.923
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa800cdb9010, fffff8800fa0df10, 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
Probably caused by : nvlddmkm.sys ( nvlddmkm+801f10 )
Followup: MachineOwner
---------
5: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800cdb9010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800fa0df10, 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.
Debugging Details:
------------------
FAULTING_IP:
nvlddmkm+801f10
fffff880`0fa0df10 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`05306b88 fffff880`0ff1c000 : 00000000`00000116 fffffa80`0cdb9010 fffff880`0fa0df10 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`05306b90 fffff880`0feef867 : fffff880`0fa0df10 fffffa80`0c3d0000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`05306bd0 fffff880`0ff1be0f : 00000000`ffffd84d ffffffff`fffe7960 fffffa80`0cdb9010 00000000`0000000f : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`05306c80 fffff880`0ffeaec1 : fffffa80`0bf84580 00000000`00000080 00000000`00000000 fffffa80`0c3b5410 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`05306d00 fffff800`0311cfee : 00000000`01f2dbc9 fffffa80`0bf36b60 fffffa80`09d40040 fffffa80`0bf36b60 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`05306d40 fffff800`02e735e6 : fffff800`02ff7e80 fffffa80`0bf36b60 fffff800`03005cc0 fffff880`0126b384 : nt!PspSystemThreadStartup+0x5a
fffff880`05306d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
nvlddmkm+801f10
fffff880`0fa0df10 4883ec28 sub rsp,28h
SYMBOL_NAME: nvlddmkm+801f10
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4dd73a68
FAILURE_BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys
BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys
Followup: MachineOwner
---------
- This crash is due to the system sending a device driver the signal to turn itself off or turn itself on during a power cycle such as during sleep, hibernate, shut down, or startup. The device or device driver failed to respond to the signal and so the system crashed to force the power state. Could be caused by either the devices themselves or their drivers.
- This is a 0x116 TDR crash... see below.
For the first crash: - Older versions of ASACPI.SYS are a known BSOD problem on Windows 7. Update the driver by:
- Going to the Asus motherboard support site
When you reach the website: - Scroll down the page and click Utilities
- Hold Ctrl and press f (ctrl+f) to enter the browser's find feature
- Search for "ATK0110 driver for WindowsXP/Vista/Win7 32&64-bit" (without quotes)
- Download and install the driver.
- After installation is complete, verify that it installed correctly.
- Click Start Menu
- Click My Computer
- Go to C:\WIndows\System32\drivers\
- Verify that the ASACPI.SYS file is dated 2009 or newer (2010,etc.)
Thanks to JMH and zigzag3143 for the above information.
- Update all Intel drivers using the Intel® Driver Update Utility
For the second crash:
These are all stop 0x116 VIDEO_TDR_FAILURE conditions.
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.
The above quote was taken from https://www.sevenforums.com/crashes-d...tml#post280172, which is linked to in usasma's thread about this error. Closely follow the first three posts of usasma's thread outlining STOP 0x116: VIDEO_TDR_ERROR troubleshooting and proceed through each step. Let us know if you need further help.