Jibby Posted December 29, 2009 Share Posted December 29, 2009 (edited) I installed Windows 7 (now fully updated) this morning, setup all the programs/drivers for my hardware, and transferred the files from my previous computer over to this new install. The computer has been running all day just fine, many restarts, zero issues. I left the computer alone for 30 mintues, and it decided to go into a standby type mode (video card gets quiet, monitors turned off), I brought it back by tapping the spacebar (didn't hit the power button). When it comes back, I am immediately presented with a blue screen. 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 uploaded the zip of my minidump here: http://tiny.cc/XiqV6 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 ® Windows Debugger Version 6.11.0001.404 X86 Copyright © 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 --------- Edited December 29, 2009 by Jibby Link to post Share on other sites
IntelGuy Posted December 29, 2009 Share Posted December 29, 2009 I've been seeing a lot of Windows 7 driver issues that are always with Nvidia display drivers. Reminds me some of the Nvidia/Vista fiasco. I would suggest rolling back to the native win 7 display driver and see if the issue persists. Link to post Share on other sites
stormy13 Posted December 29, 2009 Share Posted December 29, 2009 Jibby have a good look around over here, http://www.sevenforums.com/crashes-debugging/ Quite a few threads dealing with BSOD's and Sleep. I've been seeing a lot of Windows 7 driver issues that are always with Nvidia display drivers. Reminds me some of the Nvidia/Vista fiasco. I experienced that one firsthand when Vista came out. Had a 7600GT at the time and the Nvidia drivers kept me on XP for about 6 months till they finally got decent Vista drivers out. Link to post Share on other sites
Jibby Posted December 29, 2009 Author Share Posted December 29, 2009 Jibby have a good look around over here, http://www.sevenforums.com/crashes-debugging/ Quite a few threads dealing with BSOD's and Sleep. I experienced that one firsthand when Vista came out. Had a 7600GT at the time and the Nvidia drivers kept me on XP for about 6 months till they finally got decent Vista drivers out. - Well I ended up just disabling the standby/hibernate commands. It doesn't look like my video card supports S2 . 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. We'll see how things go. Not sure if this may be related to the fact I'm hooked up to an HD Plasma - maybe that video connection is the one with the problem. If anyone else runs across this error, please post your monitors/video connections, maybe we'll see this is related to that. I'm running 2 Dell 1905FP, a ViewSonic VA2226w, and a Panasonic HD Plasma TH-42PZ77U Link to post Share on other sites
.png.9d4b89b15b2cd5e65edd93a0e6823dce.png)
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now