Win 7 - Blue Screen - BCCode 116

Mr Bob

Golden Member
Sep 6, 2004
1,757
12
81
I just installed Windows 7 today and got all my programs installed, files transferred over, etc..

Tonight, I left the computer alone for 30 minutes, when I came back, it appears to have been in a standby mode.

After hitting the spacebar to come back from this mode, the monitors finally turned on, and then a blue screen popped up.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 116
BCP1: 84FE6008
BCP2: 8F2EEA30
BCP3: 00000000
BCP4: 00000002
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

I can't seem to find much on this one..
 

Mr Bob

Golden Member
Sep 6, 2004
1,757
12
81
Minidump points to display drivers, but I'm running the latest version, so dunno what else I can do...

Installed 'em fresh today.

Minidump:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\122809-28984-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82a42000 PsLoadedModuleList = 0x82b8a810
Debug session time: Mon Dec 28 23:15:49.466 2009 (GMT-7)
System Uptime: 0 days 1:25:52.216
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
...............................................................
................................................................
...................................................
Loading User Symbols
Loading unloaded module list
.......
3: kd> .sympath srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Expanded Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
3: kd> .reload
Loading Kernel Symbols
...............................................................
................................................................
...................................................
Loading User Symbols
Loading unloaded module list
.......
3: kd> !analyze -v
Unable to load image \SystemRoot\System32\drivers\dxgkrnl.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: 84fe6008, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: 8f2eea30, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 00000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 00000002, Optional internal context dependent data.

Debugging Details:
------------------

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

FAULTING_IP:
nvlddmkm+dea30
8f2eea30 55 push ebp

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT: 1

BUGCHECK_STR: 0x116

PROCESS_NAME: System

CURRENT_IRQL: 0

STACK_TEXT:
8cb4eb74 8fd98adb 00000116 84fe6008 8f2eea30 nt!KeBugCheckEx+0x1e
WARNING: Stack unwind information not available. Following frames may be wrong.
8cb4eb98 8fd998fa 8f2eea30 00000000 00000002 dxgkrnl+0x8cadb
8cb4ebbc 8fdc992c 00000000 00000102 86c95008 dxgkrnl+0x8d8fa
8cb4ec34 8fdf3a32 fffffcfb 000506b9 00000000 dxgmms1!VidSchiReportHwHang+0x3c0
8cb4ec5c 8fdf4153 00000000 00000000 00000000 dxgmms1!VidSchiCheckHwProgress+0x68
8cb4ec98 8fdd08f0 8cb4ec90 86c83008 86c8add0 dxgmms1!VidSchiWaitForSchedulerEvents+0x1b1
8cb4ed28 8fdf54b7 86c95008 82a7e3f1 86c95008 dxgmms1!VidSchiScheduleCommandToRun+0xaa
8cb4ed3c 8fdf5573 86c95008 00000000 86c98210 dxgmms1!VidSchiRun_PriorityTable+0xf
8cb4ed50 82c5066d 86c95008 ac2a0c7e 00000000 dxgmms1!VidSchiWorkerThread+0x7f
8cb4ed90 82b020d9 8fdf54f4 86c95008 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nvlddmkm+dea30
8f2eea30 55 push ebp

SYMBOL_NAME: nvlddmkm+dea30

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4b0764b5

FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys

BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys

Followup: MachineOwner
---------
 
Last edited:

RadiclDreamer

Diamond Member
Aug 8, 2004
8,622
40
91
Minidump points to display drivers, but I'm running the latest version, so dunno what else I can do...

Installed 'em fresh today.

Minidump:

Have you tried an older set? Its possible that this bug was introduced in this release, or possible the last few
 

railman

Member
Dec 22, 2009
82
0
0
Sounds like your video card might not support the sleep/standby state that Win 7 went into. You can check to see what power states your system supports from a command line with powercfg.exe /a. Check what is supported against what Win 7 has set as default and correct if necessary.
 

Mr Bob

Golden Member
Sep 6, 2004
1,757
12
81
Looks like it doesn't support "S2" - dunno what state Win 7 tried to go in.. is there a way to find out about that?

C:\Users\User>powercfg.exe /a
The following sleep states are available on this system: Standby ( S1 S3 ) Hibernate Hybrid Sleep
The following sleep states are not available on this system:
Standby (S2)
The system firmware does not support this standby state.

C:\Users\User>