New
#41
SF Diag...
Here is an excellent tutorial on actions that may help
Troubleshooting Windows 7 Failure to Boot
OK Thanks - I will follow this and let you know what happens. I reckon it will be a LONG NIGHT!
I just looked at your reports, it may be problems with your graphic card driver from Nividia.
Thanks to Z3r, you can get into safe mode.
See if you can update your graphics card driver in safe mode
Here is your report, I have bolded the driver in question
http://www.ehow.com/how_5841450_inst...safe-mode.htmlCode:Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Richard\AppData\Local\Temp\Temp1_BenB.zip\SF_01-09-2012\090112-28735-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030 Machine Name: Kernel base = 0xfffff800`03653000 PsLoadedModuleList = 0xfffff800`03897670 Debug session time: Sat Sep 1 16:50:25.424 2012 (GMT-4) System Uptime: 0 days 0:00:47.767 Loading Kernel Symbols ............................................................... ................................................................ ............... Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 116, {fffffa8008a15010, fffff8800f23c9c8, 0, 2} 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 *** WARNING: Unable to verify timestamp for win32k.sys *** ERROR: Module load completed but symbols could not be loaded for win32k.sys Probably caused by : nvlddmkm.sys ( nvlddmkm+1759c8 ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* VIDEO_TDR_FAILURE (116) Attempt to reset the display driver and recover from timeout failed. Arguments: Arg1: fffffa8008a15010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT). Arg2: fffff8800f23c9c8, The pointer into responsible device driver module (e.g. owner tag). Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation. Arg4: 0000000000000002, Optional internal context dependent data. Debugging Details: ------------------ FAULTING_IP: nvlddmkm+1759c8 fffff880`0f23c9c8 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`033ec9c8 fffff880`0407c000 : 00000000`00000116 fffffa80`08a15010 fffff880`0f23c9c8 00000000`00000000 : nt!KeBugCheckEx fffff880`033ec9d0 fffff880`0407bd0a : fffff880`0f23c9c8 fffffa80`08a15010 fffffa80`05a60d50 fffffa80`086ab410 : dxgkrnl!TdrBugcheckOnTimeout+0xec fffff880`033eca10 fffff880`04122f07 : fffffa80`08a15010 00000000`00000000 fffffa80`05a60d50 fffffa80`086ab410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2 fffff880`033eca40 fffff880`0414cb75 : 00000000`ffffffff 00000000`00000b03 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b fffff880`033ecb20 fffff880`0414b2bb : 00000000`00000102 00000000`00000000 00000000`00000b03 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71 fffff880`033ecb50 fffff880`0411e2c6 : ffffffff`ff676980 fffffa80`086ab410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb fffff880`033ecbf0 fffff880`0414ae7a : 00000000`00000000 00000000`0000000f 00000000`00000080 fffffa80`07a8e168 : dxgmms1!VidSchiScheduleCommandToRun+0x1da fffff880`033ecd00 fffff800`03968e6a : 00000000`0656577c fffffa80`0848d350 fffffa80`048d9040 fffffa80`0848d350 : dxgmms1!VidSchiWorkerThread+0xba fffff880`033ecd40 fffff800`036c2ec6 : fffff880`009e9180 fffffa80`0848d350 fffffa80`07a8e060 00000000`3e97f000 : nt!PspSystemThreadStartup+0x5a fffff880`033ecd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: .bugcheck ; kb FOLLOWUP_IP: nvlddmkm+1759c8 fffff880`0f23c9c8 4883ec28 sub rsp,28h SYMBOL_NAME: nvlddmkm+1759c8 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 ---------
Interesting....
I will update driver and see if it helps...
You actually gave us two reports, the first gave no information, it was corrupt.
The second indicated graphics. One report is almost never enought to fix the BSOD problem.