Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD dump archive attached


09 Jan 2012   #1

win7 home premium 64 bit
 
 
BSOD dump archive attached

Good morning....

Is Windows 7 . . .
- x64
- the original installed OS on the system? Original
- an OEM or full retail version? OEM

- What is the age of system (hardware)? Purchased Spring, 2011
- What is the age of OS installation (have you re-installed the OS?) New hard drive, OS installed 1/2/12

My System SpecsSystem Spec
.

09 Jan 2012   #2

win7 home premium 64 bit
 
 

I believe the issue has to do with my video, as each BSOD occurred while either gaming or streaming video. If anyone could take a look and see if each BSOD has the same root cause I'd be grateful! Thanks!
My System SpecsSystem Spec
10 Jan 2012   #3

win7 home premium 64 bit
 
 

After reading through a few cases, I decided to remove NAV and go with the Windows one, so far that appears to have helped. It would be great if someone could check my dump to confirm if the BSOD appear to be random and possibly from NAV, or if it is something more specific. Thanks again!
My System SpecsSystem Spec
.


10 Jan 2012   #4

Windows 7 Home Premium 64 Bit
 
 

Code:
  1. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\sameoldufry\Windows_NT6_BSOD_jcgriff2\010312-35724-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (6 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`0304d000 PsLoadedModuleList = 0xfffff800`0328ae50 Debug session time: Tue Jan 3 13:00:24.355 2012 (UTC - 7:00) System Uptime: 0 days 5:38:47.716 Loading Kernel Symbols ............................................................... ................................................................ ......................................... Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1E, {0, 0, 0, 0} Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e ) Followup: MachineOwner --------- 5: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KMODE_EXCEPTION_NOT_HANDLED (1e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Arguments: Arg1: 0000000000000000, The exception code that was not handled Arg2: 0000000000000000, The address that the exception occurred at Arg3: 0000000000000000, Parameter 0 of the exception Arg4: 0000000000000000, Parameter 1 of the exception Debugging Details: ------------------ EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully. FAULTING_IP: +3161373564613636 00000000`00000000 ?? ??? EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: 0000000000000000 ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0 BUGCHECK_STR: 0x1E_0 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: f EXCEPTION_RECORD: fffff880030cc318 -- (.exr 0xfffff880030cc318) ExceptionAddress: fffff800030a9751 (nt!KeInsertQueueDpc+0x0000000000000261) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: ffffffffffffffff Attempt to read from address ffffffffffffffff TRAP_FRAME: fffff880030cc3c0 -- (.trap 0xfffff880030cc3c0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=f7fff880030a6320 rbx=0000000000000000 rcx=fffff880030a8aa0 rdx=0000000054ab884e rsi=0000000000000000 rdi=0000000000000000 rip=fffff800030a9751 rsp=fffff880030cc550 rbp=fffff880030a8a98 r8=0000000001ccca52 r9=0000000000000000 r10=fffff8000304d000 r11=fffff880030a8a98 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc nt!KeInsertQueueDpc+0x261: fffff800`030a9751 48894808 mov qword ptr [rax+8],rcx ds:f7fff880`030a6328=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff800030b6c2e to fffff800030beed0 STACK_TEXT: fffff880`030cb3f8 fffff800`030b6c2e : 00000000`00000000 00000000`00000000 fffff880`030cbb70 fffff800`030ebe28 : nt!KeBugCheck fffff880`030cb400 fffff800`030e4bed : fffff800`032cbc24 fffff800`03204a3c fffff800`0304d000 fffff880`030cc318 : nt!KiKernelCalloutExceptionHandler+0xe fffff880`030cb430 fffff800`030ec250 : fffff800`0320cb5c fffff880`030cb4a8 fffff880`030cc318 fffff800`0304d000 : nt!RtlpExecuteHandlerForException+0xd fffff880`030cb460 fffff800`030f91b5 : fffff880`030cc318 fffff880`030cbb70 fffff880`00000000 fffff880`030a6320 : nt!RtlDispatchException+0x410 fffff880`030cbb40 fffff800`030be542 : fffff880`030cc318 fffff880`030a4180 fffff880`030cc3c0 fffff880`030a4180 : nt!KiDispatchException+0x135 fffff880`030cc1e0 fffff800`030bce4a : fffffa80`09cfa010 00000000`000000aa fffffa80`09cfa010 00000000`00000000 : nt!KiExceptionDispatch+0xc2 fffff880`030cc3c0 fffff800`030a9751 : 00000000`00000001 fffff800`030c8a9a ffffffff`f70f2e80 fffffa80`0726cb60 : nt!KiGeneralProtectionFault+0x10a fffff880`030cc550 fffff800`030ca3e6 : fffff880`030a8ad8 00000000`54ab884e 00000000`01ccca52 00000000`00000005 : nt!KeInsertQueueDpc+0x261 fffff880`030cc5e0 fffff800`030cae7e : 0000002f`5443591c fffff880`030ccc58 00000000`0013e20a fffff880`030a66c8 : nt!KiProcessExpiredTimerList+0x186 fffff880`030ccc30 fffff800`030ca697 : 0000000e`f35b7cc2 0000000e`0013e20a 0000000e`f35b7c17 00000000`0000000a : nt!KiTimerExpiration+0x1be fffff880`030cccd0 fffff800`030c76fa : fffff880`030a4180 fffff880`030af040 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277 fffff880`030ccd80 00000000`00000000 : fffff880`030cd000 fffff880`030c7000 fffff880`030ccd40 00000000`00000000 : nt!KiIdleLoop+0x5a STACK_COMMAND: kb FOLLOWUP_IP: nt!KiKernelCalloutExceptionHandler+e fffff800`030b6c2e 90 nop SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt!KiKernelCalloutExceptionHandler+e FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600 FAILURE_BUCKET_ID: X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e BUCKET_ID: X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e Followup: MachineOwner ---------
  2. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\sameoldufry\Windows_NT6_BSOD_jcgriff2\010312-28298-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (6 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`03052000 PsLoadedModuleList = 0xfffff800`0328fe50 Debug session time: Tue Jan 3 15:38:26.906 2012 (UTC - 7:00) System Uptime: 0 days 2:36:34.826 Loading Kernel Symbols ............................................................... ................................................................ ......................................... Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff800030a07ff, fffff8800a26e050, 0} Probably caused by : ntkrnlmp.exe ( nt!KiDeliverApc+a7 ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the bugcheck Arg2: fffff800030a07ff, Address of the instruction which caused the bugcheck Arg3: fffff8800a26e050, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: nt!KiDeliverApc+a7 fffff800`030a07ff 498b4a30 mov rcx,qword ptr [r10+30h] CONTEXT: fffff8800a26e050 -- (.cxr 0xfffff8800a26e050) rax=0000000000000002 rbx=fffffa800a76c060 rcx=0000000000000001 rdx=0000000000000000 rsi=fffffa800a76c0b0 rdi=fffffa800a76c060 rip=fffff800030a07ff rsp=fffff8800a26ea30 rbp=0000000000000000 r8=f7fffa800a76c0b0 r9=0000000000000000 r10=f7fffa800a76c0a0 r11=0000000000100003 r12=0000000000000001 r13=0000000000000500 r14=fffffa800a00f880 r15=fffff8800a26ec20 iopl=0 nv up ei ng nz na po cy cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010287 nt!KiDeliverApc+0xa7: fffff800`030a07ff 498b4a30 mov rcx,qword ptr [r10+30h] ds:002b:f7fffa80`0a76c0d0=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: Steam.exe CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from fffff80003075ba9 to fffff800030a07ff STACK_TEXT: fffff880`0a26ea30 fffff800`03075ba9 : 00000000`00000000 00000000`00000000 fffffa80`0a76c120 00000000`00000000 : nt!KiDeliverApc+0xa7 fffff880`0a26eab0 fffff800`033b58f6 : fffff780`00000008 fffff800`030cb052 fffffa80`0a76c060 fffffa80`0a76c060 : nt!KiCheckForKernelApcDelivery+0x25 fffff880`0a26eae0 fffff800`033bba69 : 00000000`755c2400 00000000`00100000 00000000`00000000 00000000`7eef1001 : nt!ObReferenceObjectByHandleWithTag+0x3b6 fffff880`0a26ebb0 fffff800`030c3153 : fffffa80`0a76c060 00000000`3029da04 00000000`00000000 fffffa80`0959e2a0 : nt!NtWaitForSingleObject+0x69 fffff880`0a26ec20 00000000`755c2dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`0b50f0f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x755c2dd9 FOLLOWUP_IP: nt!KiDeliverApc+a7 fffff800`030a07ff 498b4a30 mov rcx,qword ptr [r10+30h] SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!KiDeliverApc+a7 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600 STACK_COMMAND: .cxr 0xfffff8800a26e050 ; kb FAILURE_BUCKET_ID: X64_0x3B_nt!KiDeliverApc+a7 BUCKET_ID: X64_0x3B_nt!KiDeliverApc+a7 Followup: MachineOwner ---------
  3. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\sameoldufry\Windows_NT6_BSOD_jcgriff2\010412-35568-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (6 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`0301b000 PsLoadedModuleList = 0xfffff800`03258e50 Debug session time: Wed Jan 4 11:45:15.403 2012 (UTC - 7:00) System Uptime: 0 days 9:37:33.894 Loading Kernel Symbols ............................................................... ................................................................ ......................................... Loading User Symbols Loading unloaded module list ...................... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 116, {fffffa800abc34e0, fffff88007e078c8, 0, 2} Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for atikmpag.sys *** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys Probably caused by : atikmpag.sys ( atikmpag+78c8 ) 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: fffffa800abc34e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT). Arg2: fffff88007e078c8, 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: atikmpag+78c8 fffff880`07e078c8 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`05d99898 fffff880`04527cbc : 00000000`00000116 fffffa80`0abc34e0 fffff880`07e078c8 00000000`00000000 : nt!KeBugCheckEx fffff880`05d998a0 fffff880`045279c6 : fffff880`07e078c8 fffffa80`0abc34e0 fffffa80`142df010 fffffa80`0bea8410 : dxgkrnl!TdrBugcheckOnTimeout+0xec fffff880`05d998e0 fffff880`04facf07 : fffffa80`0abc34e0 00000000`00000000 fffffa80`142df010 fffffa80`0bea8410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2 fffff880`05d99910 fffff880`04fdad7e : 00000000`ffffffff 00000000`0021e232 fffff880`05d99a70 00000000`00000102 : dxgmms1!VidSchiReportHwHang+0x40b fffff880`05d999f0 fffff880`04fd66af : fffffa80`0bea8410 ffffffff`feced300 00000000`00000000 fffff8a0`0b1f1000 : dxgmms1!VidSchWaitForCompletionEvent+0x196 fffff880`05d99a30 fffff880`04fd5023 : fffffa80`0bea8410 00000000`00000002 fffff880`05d99b90 fffff880`05d99b80 : dxgmms1!VidSchiWaitForEmptyHwQueue+0x8f fffff880`05d99b20 fffff880`04fd52fe : 00000000`00000000 00000000`00000002 00000003`00000380 fffffa80`14826010 : dxgmms1!VidSchiHandleControlEvent+0x3b fffff880`05d99b50 fffff880`04fa82c6 : ffffffff`ff676980 fffffa80`0bea8410 00000000`00000080 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x23e fffff880`05d99bf0 fffff880`04fd4e7a : fffffa80`142df010 fffffa80`142df010 00000000`00000080 fffffa80`0bea8410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da fffff880`05d99d00 fffff800`03330166 : fffff880`0add0c40 fffffa80`14e49780 fffffa80`06a0b040 fffff800`03084d87 : dxgmms1!VidSchiWorkerThread+0xba fffff880`05d99d40 fffff800`0306b486 : fffff880`009e8180 fffffa80`14e49780 fffff880`009f3040 fffff880`01232a90 : nt!PspSystemThreadStartup+0x5a fffff880`05d99d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: .bugcheck ; kb FOLLOWUP_IP: atikmpag+78c8 fffff880`07e078c8 4883ec28 sub rsp,28h SYMBOL_NAME: atikmpag+78c8 FOLLOWUP_NAME: MachineOwner MODULE_NAME: atikmpag IMAGE_NAME: atikmpag.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4ebb331c FAILURE_BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys Followup: MachineOwner ---------
  4. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\sameoldufry\Windows_NT6_BSOD_jcgriff2\010412-32651-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (6 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`03000000 PsLoadedModuleList = 0xfffff800`0323de50 Debug session time: Wed Jan 4 11:54:31.772 2012 (UTC - 7:00) System Uptime: 0 days 0:07:31.068 Loading Kernel Symbols ............................................................... ................................................................ ...................................... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1E, {ffffffffc0000005, fffff8000307558a, 0, ffffffffffffffff} Probably caused by : ntkrnlmp.exe ( nt!KeWaitForMultipleObjects+2b0 ) Followup: MachineOwner --------- 5: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KMODE_EXCEPTION_NOT_HANDLED (1e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Arguments: Arg1: ffffffffc0000005, The exception code that was not handled Arg2: fffff8000307558a, The address that the exception occurred at Arg3: 0000000000000000, Parameter 0 of the exception Arg4: ffffffffffffffff, Parameter 1 of the exception Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: nt!KeWaitForMultipleObjects+2b0 fffff800`0307558a c3 ret EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: ffffffffffffffff READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032a80e0 ffffffffffffffff ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. BUGCHECK_STR: 0x1E_c0000005 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: iexplore.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff800030b1a17 to fffff80003071f00 STACK_TEXT: fffff880`06be3a68 fffff800`030b1a17 : 00000000`0000001e ffffffff`c0000005 fffff800`0307558a 00000000`00000000 : nt!KeBugCheckEx fffff880`06be3a70 fffff800`03071542 : fffff880`06be4248 00000000`00000001 fffff880`06be42f0 00000000`00000004 : nt! ?? ::FNODOBFM::`string'+0x460da fffff880`06be4110 fffff800`0306fe4a : 00000000`04aff20c fffff880`06be46a0 00000001`00000000 fffff800`0333c698 : nt!KiExceptionDispatch+0xc2 fffff880`06be42f0 fffff800`0307558a : fffff800`0336abcf 00000000`00000004 fffff880`06be4520 0000002b`00000001 : nt!KiGeneralProtectionFault+0x10a fffff880`06be4488 fffff800`0336abcf : 00000000`00000004 fffff880`06be4520 0000002b`00000001 00000000`00000006 : nt!KeWaitForMultipleObjects+0x2b0 fffff880`06be4490 fffff800`0339606d : 00000000`00000001 00000000`00000000 00000000`00000001 00000000`00000000 : nt!ObpWaitForMultipleObjects+0x294 fffff880`06be4960 fffff800`03071153 : ffffffff`ffffffff fffffa80`0717a770 00000000`04c7f920 0000007f`00000004 : nt!NtWaitForMultipleObjects32+0xec fffff880`06be4bb0 00000000`75392dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`04afedf8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x75392dd9 STACK_COMMAND: kb FOLLOWUP_IP: nt!KeWaitForMultipleObjects+2b0 fffff800`0307558a c3 ret SYMBOL_STACK_INDEX: 4 SYMBOL_NAME: nt!KeWaitForMultipleObjects+2b0 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600 FAILURE_BUCKET_ID: X64_0x1E_c0000005_nt!KeWaitForMultipleObjects+2b0 BUCKET_ID: X64_0x1E_c0000005_nt!KeWaitForMultipleObjects+2b0 Followup: MachineOwner ---------
  5. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\sameoldufry\Windows_NT6_BSOD_jcgriff2\010412-32229-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (6 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`03006000 PsLoadedModuleList = 0xfffff800`03243e50 Debug session time: Wed Jan 4 13:46:32.012 2012 (UTC - 7:00) System Uptime: 0 days 1:50:54.292 Loading Kernel Symbols ............................................................... ................................................................ ........................................... Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1E, {0, 0, 0, 0} Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e ) Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KMODE_EXCEPTION_NOT_HANDLED (1e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Arguments: Arg1: 0000000000000000, The exception code that was not handled Arg2: 0000000000000000, The address that the exception occurred at Arg3: 0000000000000000, Parameter 0 of the exception Arg4: 0000000000000000, Parameter 1 of the exception Debugging Details: ------------------ EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully. FAULTING_IP: +6637643738393465 00000000`00000000 ?? ??? EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: 0000000000000000 ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0 BUGCHECK_STR: 0x1E_0 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 2 EXCEPTION_RECORD: fffff88002ffd328 -- (.exr 0xfffff88002ffd328) ExceptionAddress: fffff80003081ab1 (nt!KiTimerWaitTest+0x0000000000000171) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: ffffffffffffffff Parameter[1]: 0000000000000000 Attempt to execute non-executable address 0000000000000000 TRAP_FRAME: fffff88002ffd3d0 -- (.trap 0xfffff88002ffd3d0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000008 rbx=0000000000000000 rcx=0000000000000000 rdx=fffffa8006dc4120 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80003081ab1 rsp=fffff88002ffd560 rbp=f7fffa8006dc41f8 r8=fffff88002fd7301 r9=0000000000000004 r10=000000000000003a r11=0000000000000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na pe cy nt!KiTimerWaitTest+0x171: fffff800`03081ab1 488b6d00 mov rbp,qword ptr [rbp] ss:0018:f7fffa80`06dc41f8=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff8000306fc2e to fffff80003077ed0 STACK_TEXT: fffff880`02ffc408 fffff800`0306fc2e : 00000000`00000000 00000000`00000000 fffff880`02ffcb80 fffff800`030a4e28 : nt!KeBugCheck fffff880`02ffc410 fffff800`0309dbed : fffff800`03284c24 fffff800`031bda3c fffff800`03006000 fffff880`02ffd328 : nt!KiKernelCalloutExceptionHandler+0xe fffff880`02ffc440 fffff800`030a5250 : fffff800`031c5b5c fffff880`02ffc4b8 fffff880`02ffd328 fffff800`03006000 : nt!RtlpExecuteHandlerForException+0xd fffff880`02ffc470 fffff800`030b21b5 : fffff880`02ffd328 fffff880`02ffcb80 fffff880`00000000 fffffa80`06dc4120 : nt!RtlDispatchException+0x410 fffff880`02ffcb50 fffff800`03077542 : fffff880`02ffd328 fffffa80`06dc4128 fffff880`02ffd3d0 00000000`00000000 : nt!KiDispatchException+0x135 fffff880`02ffd1f0 fffff800`03075d12 : fffffa80`ffffd9dd fffff880`02ffd510 00000000`00000000 fffff880`02ffd7a8 : nt!KiExceptionDispatch+0xc2 fffff880`02ffd3d0 fffff800`03081ab1 : fffff800`031f0e80 fffffa80`06c50b60 00000000`00073e85 fffff880`0561154a : nt!KiStackFault+0x112 fffff880`02ffd560 fffff800`030832cd : fffffa80`06dc4120 fffffa80`07bcab18 fffffa80`07bcab18 00000000`00000000 : nt!KiTimerWaitTest+0x171 fffff880`02ffd5e0 fffff800`03083e7e : 0000000f`7e447feb fffff880`02ffdc58 00000000`0006823a fffff880`02fd7cc8 : nt!KiProcessExpiredTimerList+0x6d fffff880`02ffdc30 fffff800`03083697 : 00000004`e2ff20c3 00000004`0006823a 00000004`e2ff20f2 00000000`0000003a : nt!KiTimerExpiration+0x1be fffff880`02ffdcd0 fffff800`030806fa : fffff880`02fd5180 fffff880`02fe0040 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277 fffff880`02ffdd80 00000000`00000000 : fffff880`02ffe000 fffff880`02ff8000 fffff880`02ffdd40 00000000`00000000 : nt!KiIdleLoop+0x5a STACK_COMMAND: kb FOLLOWUP_IP: nt!KiKernelCalloutExceptionHandler+e fffff800`0306fc2e 90 nop SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt!KiKernelCalloutExceptionHandler+e FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600 FAILURE_BUCKET_ID: X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e BUCKET_ID: X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e Followup: MachineOwner ---------
  6. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\sameoldufry\Windows_NT6_BSOD_jcgriff2\010512-26894-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (6 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16841.amd64fre.win7_gdr.110622-1503 Machine Name: Kernel base = 0xfffff800`0304e000 PsLoadedModuleList = 0xfffff800`0328be70 Debug session time: Thu Jan 5 06:44:22.187 2012 (UTC - 7:00) System Uptime: 0 days 5:02:03.467 Loading Kernel Symbols ............................................................... ................................................................ .......................................... Loading User Symbols Loading unloaded module list ........... Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for atikmdag.sys *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000007E, {ffffffffc0000005, fffff88004899d10, fffff880021ba378, fffff880021b9be0} Probably caused by : atikmdag.sys ( atikmdag+31d10 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Some common problems are exception code 0x80000003. This means a hard coded breakpoint or assertion was hit, but this system was booted /NODEBUG. This is not supposed to happen as developers should never have hardcoded breakpoints in retail code, but ... If this happens, make sure a debugger gets connected, and the system is booted /DEBUG. This will let us see why this breakpoint is happening. Arguments: Arg1: ffffffffc0000005, The exception code that was not handled Arg2: fffff88004899d10, The address that the exception occurred at Arg3: fffff880021ba378, Exception Record Address Arg4: fffff880021b9be0, Context Record Address Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: atikmdag+31d10 fffff880`04899d10 8b4108 mov eax,dword ptr [rcx+8] EXCEPTION_RECORD: fffff880021ba378 -- (.exr 0xfffff880021ba378) ExceptionAddress: fffff88004899d10 (atikmdag+0x0000000000031d10) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: ffffffffffffffff Attempt to read from address ffffffffffffffff CONTEXT: fffff880021b9be0 -- (.cxr 0xfffff880021b9be0) rax=fffff88004d98880 rbx=f7fff8a0156e5010 rcx=f7fff8a0156e5010 rdx=f7fff8a0156e5010 rsi=fffffa8009adf920 rdi=fffff880021ba870 rip=fffff88004899d10 rsp=fffff880021ba5b8 rbp=00000000ffffffff r8=0000000000000002 r9=0000000f1dc60000 r10=fffff8a014e53ca0 r11=fffff880021ba7d0 r12=0000000000000002 r13=fffffa8009e4da40 r14=fffffa8009ea6d70 r15=fffffa8009e4da40 iopl=0 nv up ei ng nz na pe nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282 atikmdag+0x31d10: fffff880`04899d10 8b4108 mov eax,dword ptr [rcx+8] ds:002b:f7fff8a0`156e5018=???????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 0 ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: ffffffffffffffff READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032f60e0 ffffffffffffffff FOLLOWUP_IP: atikmdag+31d10 fffff880`04899d10 8b4108 mov eax,dword ptr [rcx+8] BUGCHECK_STR: 0x7E LAST_CONTROL_TRANSFER: from fffff88004c16a13 to fffff88004899d10 STACK_TEXT: fffff880`021ba5b8 fffff880`04c16a13 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : atikmdag+0x31d10 fffff880`021ba5c0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000001 : atikmdag+0x3aea13 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: atikmdag+31d10 FOLLOWUP_NAME: MachineOwner MODULE_NAME: atikmdag IMAGE_NAME: atikmdag.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4ebb3c7e STACK_COMMAND: .cxr 0xfffff880021b9be0 ; kb FAILURE_BUCKET_ID: X64_0x7E_atikmdag+31d10 BUCKET_ID: X64_0x7E_atikmdag+31d10 Followup: MachineOwner ---------
  7. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\sameoldufry\Windows_NT6_BSOD_jcgriff2\010512-27034-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (6 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16841.amd64fre.win7_gdr.110622-1503 Machine Name: Kernel base = 0xfffff800`0301c000 PsLoadedModuleList = 0xfffff800`03259e70 Debug session time: Thu Jan 5 07:31:44.812 2012 (UTC - 7:00) System Uptime: 0 days 0:46:01.732 Loading Kernel Symbols ............................................................... ................................................................ ........................................... Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1E, {0, 0, 0, 0} Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KMODE_EXCEPTION_NOT_HANDLED (1e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Arguments: Arg1: 0000000000000000, The exception code that was not handled Arg2: 0000000000000000, The address that the exception occurred at Arg3: 0000000000000000, Parameter 0 of the exception Arg4: 0000000000000000, Parameter 1 of the exception Debugging Details: ------------------ EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully. FAULTING_IP: +3261643934663731 00000000`00000000 ?? ??? EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: 0000000000000000 ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0 BUGCHECK_STR: 0x1E_0 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: f EXCEPTION_RECORD: fffff88002f1b318 -- (.exr 0xfffff88002f1b318) ExceptionAddress: fffff80003076de1 (nt!KeInsertQueueDpc+0x0000000000000261) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: ffffffffffffffff Attempt to read from address ffffffffffffffff TRAP_FRAME: fffff88002f1b3c0 -- (.trap 0xfffff88002f1b3c0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=f7fff880009ea320 rbx=0000000000000000 rcx=fffff880009ecaa0 rdx=00000000bfbb844b rsi=0000000000000000 rdi=0000000000000000 rip=fffff80003076de1 rsp=fffff88002f1b550 rbp=fffff880009eca98 r8=0000000001cccbb6 r9=0000000000000000 r10=fffff8000301c000 r11=fffff880009eca98 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc nt!KeInsertQueueDpc+0x261: fffff800`03076de1 48894808 mov qword ptr [rax+8],rcx ds:2458:f7fff880`009ea328=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff800030842ee to fffff8000308c590 STACK_TEXT: fffff880`02f1a408 fffff800`030842ee : 00000000`00000000 00000000`00000000 fffff880`02f1ab80 fffff800`030b9524 : nt!KeBugCheck fffff880`02f1a410 fffff800`030b22dd : fffff800`0329ab7c fffff800`031d4e68 fffff800`0301c000 fffff880`02f1b318 : nt!KiKernelCalloutExceptionHandler+0xe fffff880`02f1a440 fffff800`030b9950 : fffff800`031dbb0c fffff880`02f1a4b8 fffff880`02f1b318 fffff800`0301c000 : nt!RtlpExecuteHandlerForException+0xd fffff880`02f1a470 fffff800`030c68cf : fffff880`02f1b318 fffff880`02f1ab80 fffff880`00000000 fffff880`009ea320 : nt!RtlDispatchException+0x410 fffff880`02f1ab50 fffff800`0308bc02 : fffff880`02f1b318 fffff880`009e8180 fffff880`02f1b3c0 fffff880`009e8180 : nt!KiDispatchException+0x16f fffff880`02f1b1e0 fffff800`0308a50a : 00000000`00000001 00000000`00000002 00000000`0000000a fffffa80`07a9f9c8 : nt!KiExceptionDispatch+0xc2 fffff880`02f1b3c0 fffff800`03076de1 : 00000000`00000001 fffff800`0309611a ffffffff`f70f2e80 fffffa80`06ce6660 : nt!KiGeneralProtectionFault+0x10a fffff880`02f1b550 fffff800`03097d36 : fffff880`009ecad8 00000000`bfbb844b 00000000`01cccbb6 00000000`00000001 : nt!KeInsertQueueDpc+0x261 fffff880`02f1b5e0 fffff800`0309834e : 00000006`6e1ee243 fffff880`02f1bc58 00000000`0002b388 fffff880`009eb688 : nt!KiProcessExpiredTimerList+0x186 fffff880`02f1bc30 fffff800`03097b57 : 00000002`091a85c1 00000002`0002b388 00000002`091a8500 00000000`00000088 : nt!KiTimerExpiration+0x1be fffff880`02f1bcd0 fffff800`03094d8a : fffff880`009e8180 fffff880`009f3040 00000000`00000001 fffff800`00000000 : nt!KiRetireDpcList+0x277 fffff880`02f1bd80 00000000`00000000 : fffff880`02f1c000 fffff880`02f16000 fffff880`02f1bd40 00000000`00000000 : nt!KiIdleLoop+0x5a STACK_COMMAND: kb FOLLOWUP_IP: nt!KiKernelCalloutExceptionHandler+e fffff800`030842ee 90 nop SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt!KiKernelCalloutExceptionHandler+e FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aa44 FAILURE_BUCKET_ID: X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e BUCKET_ID: X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e Followup: MachineOwner ---------
  8. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\sameoldufry\Windows_NT6_BSOD_jcgriff2\010512-25896-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (6 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16841.amd64fre.win7_gdr.110622-1503 Machine Name: Kernel base = 0xfffff800`03004000 PsLoadedModuleList = 0xfffff800`03241e70 Debug session time: Thu Jan 5 12:06:07.476 2012 (UTC - 7:00) System Uptime: 0 days 4:33:21.395 Loading Kernel Symbols ............................................................... ................................................................ ........................................... Loading User Symbols Loading unloaded module list .......... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1E, {0, 0, 0, 0} Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e ) Followup: MachineOwner --------- 4: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KMODE_EXCEPTION_NOT_HANDLED (1e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Arguments: Arg1: 0000000000000000, The exception code that was not handled Arg2: 0000000000000000, The address that the exception occurred at Arg3: 0000000000000000, Parameter 0 of the exception Arg4: 0000000000000000, Parameter 1 of the exception Debugging Details: ------------------ EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully. FAULTING_IP: +6236626431663963 00000000`00000000 ?? ??? EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: 0000000000000000 ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0 BUGCHECK_STR: 0x1E_0 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: chrome.exe CURRENT_IRQL: 2 EXCEPTION_RECORD: fffff88003062558 -- (.exr 0xfffff88003062558) ExceptionAddress: fffff8000307e131 (nt!KiTimerWaitTest+0x0000000000000171) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: ffffffffffffffff Parameter[1]: 0000000000000000 Attempt to execute non-executable address 0000000000000000 TRAP_FRAME: fffff88003062600 -- (.trap 0xfffff88003062600) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000008 rbx=0000000000000000 rcx=0000000000000000 rdx=fffffa8006df9c20 rsi=0000000000000000 rdi=0000000000000000 rip=fffff8000307e131 rsp=fffff88003062790 rbp=f7fffa8006df9cf8 r8=fffff880009b4301 r9=0000000000000002 r10=00000000000000e4 r11=0000000000000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na pe cy nt!KiTimerWaitTest+0x171: fffff800`0307e131 488b6d00 mov rbp,qword ptr [rbp] ss:f7fffa80`06df9cf8=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff8000306c2ee to fffff80003074590 STACK_TEXT: fffff880`03061648 fffff800`0306c2ee : 00000000`00000000 00000000`00000000 fffff880`03061dc0 fffff800`030a1524 : nt!KeBugCheck fffff880`03061650 fffff800`0309a2dd : fffff800`03282b7c fffff800`031bce68 fffff800`03004000 fffff880`03062558 : nt!KiKernelCalloutExceptionHandler+0xe fffff880`03061680 fffff800`030a1950 : fffff800`031c3a38 fffff880`030616f8 fffff880`03062558 fffff800`03004000 : nt!RtlpExecuteHandlerForException+0xd fffff880`030616b0 fffff800`030ae8cf : fffff880`03062558 fffff880`03061dc0 fffff880`00000000 fffffa80`06df9c20 : nt!RtlDispatchException+0x410 fffff880`03061d90 fffff800`03073c02 : fffff880`03062558 fffffa80`06df9c28 fffff880`03062600 00000000`00000000 : nt!KiDispatchException+0x16f fffff880`03062420 fffff800`030723d2 : fffffa80`093d36a0 fffff880`0566c23d 00000000`00010011 fffffa80`093d21a0 : nt!KiExceptionDispatch+0xc2 fffff880`03062600 fffff800`0307e131 : fffff880`030a4180 fffffa80`0a280060 fffffa80`093d3030 fffff880`0561d921 : nt!KiStackFault+0x112 fffff880`03062790 fffff800`0307fc1d : fffffa80`06df9c20 fffffa80`0a27f4b0 fffffa80`0a27f4b0 00000000`00000000 : nt!KiTimerWaitTest+0x171 fffff880`03062810 fffff800`0308034e : 00000026`2ffe63a0 fffff880`03062e88 00000000`00100ae4 fffff880`009b6208 : nt!KiProcessExpiredTimerList+0x6d fffff880`03062e60 fffff800`0307fb57 : fffff880`009b21c1 fffffa80`00100ae4 fffffa80`093d2d38 00000000`000000e4 : nt!KiTimerExpiration+0x1be fffff880`03062f00 fffff800`0307a705 : 00000538`00000000 fffffa80`0bb9cb60 00000000`00000000 fffff800`03194b00 : nt!KiRetireDpcList+0x277 fffff880`03062fb0 fffff800`0307a51c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KyRetireDpcList+0x5 fffff880`03ef3be0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue STACK_COMMAND: kb FOLLOWUP_IP: nt!KiKernelCalloutExceptionHandler+e fffff800`0306c2ee 90 nop SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt!KiKernelCalloutExceptionHandler+e FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aa44 FAILURE_BUCKET_ID: X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e BUCKET_ID: X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e Followup: MachineOwner ---------
  9. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\sameoldufry\Windows_NT6_BSOD_jcgriff2\010612-31075-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (6 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16841.amd64fre.win7_gdr.110622-1503 Machine Name: Kernel base = 0xfffff800`0300c000 PsLoadedModuleList = 0xfffff800`03249e70 Debug session time: Fri Jan 6 14:11:45.120 2012 (UTC - 7:00) System Uptime: 0 days 12:49:29.339 Loading Kernel Symbols ............................................................... ................................................................ ........................................... Loading User Symbols Loading unloaded module list ................... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff9600016bfc1, fffff8800a5b41d0, 0} Probably caused by : win32k.sys ( win32k!ValidateHwnd+f1 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the bugcheck Arg2: fffff9600016bfc1, Address of the instruction which caused the bugcheck Arg3: fffff8800a5b41d0, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: win32k!ValidateHwnd+f1 fffff960`0016bfc1 498b9058010000 mov rdx,qword ptr [r8+158h] CONTEXT: fffff8800a5b41d0 -- (.cxr 0xfffff8800a5b41d0) rax=fffff900c01e1410 rbx=fffff900c0405580 rcx=0000000000010390 rdx=fffffa8009d88a10 rsi=0000000000010390 rdi=fffff900c0641d40 rip=fffff9600016bfc1 rsp=fffff8800a5b4ba0 rbp=fffff8800a5b4ca0 r8=f7fff900c01e1410 r9=0000000077240dd3 r10=fffff9600013d54c r11=fffff900c01e1410 r12=000000007efdb000 r13=000000000008fd20 r14=000000000008ec70 r15=0000000075862450 iopl=0 nv up ei pl nz na pe nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202 win32k!ValidateHwnd+0xf1: fffff960`0016bfc1 498b9058010000 mov rdx,qword ptr [r8+158h] ds:002b:f7fff900`c01e1568=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: Steam.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff9600013d583 to fffff9600016bfc1 STACK_TEXT: fffff880`0a5b4ba0 fffff960`0013d583 : 00000000`00010390 00000000`00000000 fffff880`0a5b4ca0 00000000`00000000 : win32k!ValidateHwnd+0xf1 fffff880`0a5b4bd0 fffff800`0307b813 : fffffa80`088091f0 00000000`06324060 fffffa80`088091f0 00000000`00000cfc : win32k!NtUserShowWindow+0x37 fffff880`0a5b4c20 00000000`75862dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`0008ebf8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x75862dd9 FOLLOWUP_IP: win32k!ValidateHwnd+f1 fffff960`0016bfc1 498b9058010000 mov rdx,qword ptr [r8+158h] SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: win32k!ValidateHwnd+f1 FOLLOWUP_NAME: MachineOwner MODULE_NAME: win32k IMAGE_NAME: win32k.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4ecdcf5b STACK_COMMAND: .cxr 0xfffff8800a5b41d0 ; kb FAILURE_BUCKET_ID: X64_0x3B_win32k!ValidateHwnd+f1 BUCKET_ID: X64_0x3B_win32k!ValidateHwnd+f1 Followup: MachineOwner ---------
  10. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\sameoldufry\Windows_NT6_BSOD_jcgriff2\010812-31059-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (6 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16841.amd64fre.win7_gdr.110622-1503 Machine Name: Kernel base = 0xfffff800`03051000 PsLoadedModuleList = 0xfffff800`0328ee70 Debug session time: Sun Jan 8 13:00:31.814 2012 (UTC - 7:00) System Uptime: 1 days 11:42:30.094 Loading Kernel Symbols ............................................................... ................................................................ ................................................ Loading User Symbols Loading unloaded module list ................................. ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D1, {baebcd8, 2, 0, fffff8800417e65d} Unable to load image \??\C:\ProgramData\Norton\{0C55C096-0F1D-4F28-AAA2-85EF591126E7}\NAV_17.5.0.127\Definitions\IPSDefs\20120106.002\IDSvia64.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for IDSvia64.sys *** ERROR: Module load completed but symbols could not be loaded for IDSvia64.sys Probably caused by : IDSvia64.sys ( IDSvia64+1965d ) Followup: MachineOwner --------- 5: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If kernel debugger is available get stack backtrace. Arguments: Arg1: 000000000baebcd8, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, value 0 = read operation, 1 = write operation Arg4: fffff8800417e65d, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032f90e0 000000000baebcd8 CURRENT_IRQL: 2 FAULTING_IP: IDSvia64+1965d fffff880`0417e65d 2b4b48 sub ecx,dword ptr [rbx+48h] CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 PROCESS_NAME: System TRAP_FRAME: fffff8800baeb9e0 -- (.trap 0xfffff8800baeb9e0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=000000000f61f984 rbx=0000000000000000 rcx=0000000000000052 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff8800417e65d rsp=fffff8800baebb70 rbp=0000000000000000 r8=fffff8800baebc60 r9=0000000000000001 r10=fffff8800baebc90 r11=0000000000000001 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na pe nc IDSvia64+0x1965d: fffff880`0417e65d 2b4b48 sub ecx,dword ptr [rbx+48h] ds:2074:00000000`00000048=???????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff800030c0b29 to fffff800030c15c0 STACK_TEXT: fffff880`0baeb898 fffff800`030c0b29 : 00000000`0000000a 00000000`0baebcd8 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffff880`0baeb8a0 fffff800`030bf7a0 : fffffa80`0c667160 00000000`0baebc90 00000000`00000000 fffffa80`0e3bfad8 : nt!KiBugCheckDispatch+0x69 fffff880`0baeb9e0 fffff880`0417e65d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260 fffff880`0baebb70 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : IDSvia64+0x1965d STACK_COMMAND: kb FOLLOWUP_IP: IDSvia64+1965d fffff880`0417e65d 2b4b48 sub ecx,dword ptr [rbx+48h] SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: IDSvia64+1965d FOLLOWUP_NAME: MachineOwner MODULE_NAME: IDSvia64 IMAGE_NAME: IDSvia64.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4e26d5f2 FAILURE_BUCKET_ID: X64_0xD1_IDSvia64+1965d BUCKET_ID: X64_0xD1_IDSvia64+1965d Followup: MachineOwner ---------
  11. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\sameoldufry\Windows_NT6_BSOD_jcgriff2\010812-24273-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (6 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16841.amd64fre.win7_gdr.110622-1503 Machine Name: Kernel base = 0xfffff800`0304f000 PsLoadedModuleList = 0xfffff800`0328ce70 Debug session time: Sun Jan 8 13:34:38.890 2012 (UTC - 7:00) System Uptime: 0 days 0:32:44.651 Loading Kernel Symbols ............................................................... ................................................................ ............................................... Loading User Symbols Loading unloaded module list ....... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff880057210a4, fffff88008061810, 0} Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiInterlockedRemoveHeadListIfExist+30 ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the bugcheck Arg2: fffff880057210a4, Address of the instruction which caused the bugcheck Arg3: fffff88008061810, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: dxgmms1!VidSchiInterlockedRemoveHeadListIfExist+30 fffff880`057210a4 48897108 mov qword ptr [rcx+8],rsi CONTEXT: fffff88008061810 -- (.cxr 0xfffff88008061810) rax=0000000000000000 rbx=fffffa800a7c66a8 rcx=f7fffa800a7b5b28 rdx=0000000000000000 rsi=fffffa800a7c6698 rdi=fffffa800a7c7018 rip=fffff880057210a4 rsp=fffff880080621e0 rbp=fffffa800a7c64a0 r8=fffff88008062200 r9=0000000000000000 r10=0000000000000000 r11=fffff880018d9120 r12=fffffa800a7c64a0 r13=00000000ffffffff r14=0000000000000001 r15=fffffa800a18a010 iopl=0 nv up ei pl nz na pe nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202 dxgmms1!VidSchiInterlockedRemoveHeadListIfExist+0x30: fffff880`057210a4 48897108 mov qword ptr [rcx+8],rsi ds:002b:f7fffa80`0a7b5b30=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: dwm.exe CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff880057210a4 STACK_TEXT: fffff880`080621e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiInterlockedRemoveHeadListIfExist+0x30 FOLLOWUP_IP: dxgmms1!VidSchiInterlockedRemoveHeadListIfExist+30 fffff880`057210a4 48897108 mov qword ptr [rcx+8],rsi SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: dxgmms1!VidSchiInterlockedRemoveHeadListIfExist+30 FOLLOWUP_NAME: MachineOwner MODULE_NAME: dxgmms1 IMAGE_NAME: dxgmms1.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4d3fa174 STACK_COMMAND: .cxr 0xfffff88008061810 ; kb FAILURE_BUCKET_ID: X64_0x3B_dxgmms1!VidSchiInterlockedRemoveHeadListIfExist+30 BUCKET_ID: X64_0x3B_dxgmms1!VidSchiInterlockedRemoveHeadListIfExist+30 Followup: MachineOwner ---------
The problems for 1,2,4,5,7,8,9 blame system files. These could be due to lack of Windows Updates, lack of driver updates, system file corruption, hard drive corruption/bad sectors on the hard drive, viruses, bad RAM, bad RAM slots, and underlying driver incompatibilities.
  1. Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs.
  2. Run SFC /SCANNOW Command - System File Checker up to three times to fix all errors.
  3. Check for viruses.
    Download and install the free version of Malwarebytes : Free anti-malware, anti-virus and spyware removal download (do not start the trial) and make sure it is updated. Do not run a scan yet.
    Download VIPRE Rescue - VIPRE Computer Recovery Solution from Sunbelt Software but do not unzip it yet
    Download the Fakerean removal tool but do not run it yet.
    Start your computer in Safe Mode
    Unzip VIPRE Rescue and let it run.
    Run a full scan with Malwarebytes.
    Run the fakerean removal tool.
  4. Install all Windows Updates and update your device drivers (see Installing and updating drivers in 7, Driver Reference Table - sysnative.com - MVP and Drivers and Downloads for driver updating).
  5. Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete.
  6. An underlying driver that is incompatible with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:
    a. Backup your system and user files
    b. Create a system restore point
    c. If you do not have a Windows 7 DVD, Create a system repair disc
    d. Run Driver Verifier

    If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using System Restore OPTION TWO.

    Thanks to zigzag3143 for contributing to the Verifier steps.
    If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.


10 was caused by Norton, so we usually recommend uninstalling Norton using https://www-secure.symantec.com/nort...=1&pvid=f-home and replace it with Microsoft Security Essentials - Free Antivirus for Windows to run with the Windows Firewall.

3,6, and 11 are related to your display card driver; 3 and 6 require STOP 0x116: VIDEO_TDR_ERROR troubleshooting and 11 requires Diagnosing basic problems with DirectX
My System SpecsSystem Spec
10 Jan 2012   #5

Windows 7 Home Premium 64 Bit
 
 

And yes, it is quite possible all of these were related to Norton. Post back if you have further problems and need to follow the steps in my previous post. Good luck that it was just Norton!
My System SpecsSystem Spec
Reply

 BSOD dump archive attached




Thread Tools



Similar help and support threads for2: BSOD dump archive attached
Thread Forum
BSOD (dump attached) BSOD Help and Support
Daily BSOD (dump attached) BSOD Help and Support
BSOD, Mini Dump Attached. Help? BSOD Help and Support
BSOD problem - dump is attached BSOD Help and Support
BSOD 124 code please help DUmp attached BSOD Help and Support
New BSOD Dump file attached BSOD Help and Support
Bsod code 124 dump attached BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 01:42 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33