Code:
-
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\BSODDmpFiles\Zeeky\Windows_NT6_BSOD_jcgriff2\013112-29889-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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03061000 PsLoadedModuleList = 0xfffff800`032a6670
Debug session time: Mon Jan 30 21:59:00.117 2012 (GMT-7)
System Uptime: 0 days 0:08:26.601
Loading Kernel Symbols
...............................................................
................................................................
........................................
Loading User Symbols
Loading unloaded module list
....
Unable to load image \SystemRoot\system32\DRIVERS\atipmdag.sys, Win32 error 0n2
*** ERROR: Module load completed but symbols could not be loaded for atipmdag.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000094, fffff88004dfa0a9, fffff880085dbf38, fffff880085db790}
Probably caused by : atipmdag.sys ( atipmdag+3740a9 )
Followup: MachineOwner
---------
1: 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: ffffffffc0000094, The exception code that was not handled
Arg2: fffff88004dfa0a9, The address that the exception occurred at
Arg3: fffff880085dbf38, Exception Record Address
Arg4: fffff880085db790, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000094 - {EXCEPTION} Integer division by zero.
FAULTING_IP:
atipmdag+3740a9
fffff880`04dfa0a9 41f7f0 div eax,r8d
EXCEPTION_RECORD: fffff880085dbf38 -- (.exr 0xfffff880085dbf38)
ExceptionAddress: fffff88004dfa0a9 (atipmdag+0x00000000003740a9)
ExceptionCode: c0000094 (Integer divide-by-zero)
ExceptionFlags: 00000000
NumberParameters: 0
CONTEXT: fffff880085db790 -- (.cxr 0xfffff880085db790)
rax=0000000000000000 rbx=fffff880085dc1c0 rcx=0000000000000000
rdx=0000000000000000 rsi=fffffa8007394400 rdi=fffff88004a86000
rip=fffff88004dfa0a9 rsp=fffff880085dc170 rbp=0000000000000026
r8=0000000000000000 r9=000000000000fc2d r10=fffff880085dc1c0
r11=fffff88004fefb80 r12=0000000000000000 r13=00000000ffffffff
r14=00000000000009dd r15=00000000000009de
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
atipmdag+0x3740a9:
fffff880`04dfa0a9 41f7f0 div eax,r8d
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x7E
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000094 - {EXCEPTION} Integer division by zero.
LAST_CONTROL_TRANSFER: from fffffa80073be78e to fffff88004dfa0a9
STACK_TEXT:
fffff880`085dc170 fffffa80`073be78e : 00000000`00000002 fffff880`04e91658 fffff880`0389e000 fffff880`085dc250 : atipmdag+0x3740a9
fffff880`085dc178 00000000`00000002 : fffff880`04e91658 fffff880`0389e000 fffff880`085dc250 fffff880`04df91d1 : 0xfffffa80`073be78e
fffff880`085dc180 fffff880`04e91658 : fffff880`0389e000 fffff880`085dc250 fffff880`04df91d1 00000000`00000027 : 0x2
fffff880`085dc188 fffff880`0389e000 : fffff880`085dc250 fffff880`04df91d1 00000000`00000027 fffff880`bebe0031 : atipmdag+0x40b658
fffff880`085dc190 fffff880`085dc250 : fffff880`04df91d1 00000000`00000027 fffff880`bebe0031 fffffa80`03c58000 : 0xfffff880`0389e000
fffff880`085dc198 fffff880`04df91d1 : 00000000`00000027 fffff880`bebe0031 fffffa80`03c58000 fffffa80`073acd48 : 0xfffff880`085dc250
fffff880`085dc1a0 00000000`00000027 : fffff880`bebe0031 fffffa80`03c58000 fffffa80`073acd48 fffff880`085dc250 : atipmdag+0x3731d1
fffff880`085dc1a8 fffff880`bebe0031 : fffffa80`03c58000 fffffa80`073acd48 fffff880`085dc250 fffffa80`07394400 : 0x27
fffff880`085dc1b0 fffffa80`03c58000 : fffffa80`073acd48 fffff880`085dc250 fffffa80`07394400 00000000`00000000 : 0xfffff880`bebe0031
fffff880`085dc1b8 fffffa80`073acd48 : fffff880`085dc250 fffffa80`07394400 00000000`00000000 0000fc0d`00000000 : 0xfffffa80`03c58000
fffff880`085dc1c0 fffff880`085dc250 : fffffa80`07394400 00000000`00000000 0000fc0d`00000000 00000000`00000000 : 0xfffffa80`073acd48
fffff880`085dc1c8 fffffa80`07394400 : 00000000`00000000 0000fc0d`00000000 00000000`00000000 fc2d0000`04dc03f6 : 0xfffff880`085dc250
fffff880`085dc1d0 00000000`00000000 : 0000fc0d`00000000 00000000`00000000 fc2d0000`04dc03f6 fa80073b`f3d40081 : 0xfffffa80`07394400
FOLLOWUP_IP:
atipmdag+3740a9
fffff880`04dfa0a9 41f7f0 div eax,r8d
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: atipmdag+3740a9
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: atipmdag
IMAGE_NAME: atipmdag.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a4a90cd
STACK_COMMAND: .cxr 0xfffff880085db790 ; kb
FAILURE_BUCKET_ID: X64_0x7E_atipmdag+3740a9
BUCKET_ID: X64_0x7E_atipmdag+3740a9
Followup: MachineOwner
---------
-
Loading Dump File [F:\BSODDmpFiles\Zeeky\Windows_NT6_BSOD_jcgriff2\011312-40669-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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0301b000 PsLoadedModuleList = 0xfffff800`03260670
Debug session time: Fri Jan 13 03:56:05.279 2012 (GMT-7)
System Uptime: 4 days 8:34:17.302
Loading Kernel Symbols
...............................................................
................................................................
........................................
Loading User Symbols
Loading unloaded module list
.................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa8005dc3038, f2000040, 800}
Probably caused by : hardware
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8005dc3038, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000f2000040, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000800, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
------------------
BUGCHECK_STR: 0x124_GenuineIntel
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: f
STACK_TEXT:
fffff880`009f09d8 fffff800`03616a3b : 00000000`00000124 00000000`00000000 fffffa80`05dc3038 00000000`f2000040 : nt!KeBugCheckEx
fffff880`009f09e0 fffff800`031a8513 : 00000000`00000001 fffffa80`05cc44e0 00000000`00000000 fffffa80`05cc4530 : hal!HalBugCheckSystem+0x1e3
fffff880`009f0a20 fffff800`03616700 : 00000000`00000728 fffffa80`05cc44e0 fffff880`009f0db0 fffff880`009f0d00 : nt!WheaReportHwError+0x263
fffff880`009f0a80 fffff800`03616052 : fffffa80`05cc44e0 fffff880`009f0db0 fffffa80`05cc44e0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`009f0bd0 fffff800`03615f0d : 00000000`00000002 00000000`00000001 fffff880`009f0e30 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`009f0c10 fffff800`03609e88 : fffffa80`0636c7e8 fffff880`009e8180 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`009f0c40 fffff800`0309652c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`009f0c70 fffff800`03096393 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`009f0db0 fffff800`0360eeea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`0331bc28 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpHpetQueryCount+0x1c
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: hardware
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_BUS
BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_BUS
Followup: MachineOwner
---------
-
Loading Dump File [F:\BSODDmpFiles\Zeeky\Windows_NT6_BSOD_jcgriff2\110511-35084-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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e02000 PsLoadedModuleList = 0xfffff800`03047670
Debug session time: Sat Nov 5 14:12:57.932 2011 (GMT-7)
System Uptime: 0 days 6:31:42.555
Loading Kernel Symbols
...............................................................
................................................................
........................................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {0, 2, 0, fffff800033ed477}
Unable to load image \SystemRoot\system32\DRIVERS\NETw5s64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for NETw5s64.sys
*** ERROR: Module load completed but symbols could not be loaded for NETw5s64.sys
Probably caused by : NETw5s64.sys ( NETw5s64+b76b )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800033ed477, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030b1100
0000000000000000
CURRENT_IRQL: 2
FAULTING_IP:
hal!HalpDmaNextContiguousPiece+103
fffff800`033ed477 448b08 mov r9d,dword ptr [rax]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: BitTorrent.exe
TRAP_FRAME: fffff880091f69b0 -- (.trap 0xfffff880091f69b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000044
rdx=0000000000000044 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800033ed477 rsp=fffff880091f6b48 rbp=0000000000000000
r8=0000000000000028 r9=0000000000000000 r10=00000000000fffff
r11=fffffa80069a19b0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz ac pe nc
hal!HalpDmaNextContiguousPiece+0x103:
fffff800`033ed477 448b08 mov r9d,dword ptr [rax] ds:0001:00000000`00000000=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002e7e1e9 to fffff80002e7ec40
STACK_TEXT:
fffff880`091f6868 fffff800`02e7e1e9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`091f6870 fffff800`02e7ce60 : fffffa80`0a1c47b0 fffff880`0682bc2e fffffa80`040bdac0 fffffa80`08590fd8 : nt!KiBugCheckDispatch+0x69
fffff880`091f69b0 fffff800`033ed477 : fffffa80`091533b0 fffffa80`0cd79fbc fffff800`033ed524 fffffa80`08590fd8 : nt!KiPageFault+0x260
fffff880`091f6b48 fffff800`033ed524 : fffffa80`08590fd8 fffffa80`069a19b0 fffffa80`069a17d0 00000000`00000000 : hal!HalpDmaNextContiguousPiece+0x103
fffff880`091f6b60 fffff800`033f04fb : fffffa80`08590fd8 fffffa80`069a19b0 fffffa80`091533b0 fffffa80`0b03ffd8 : hal!HalpDmaMapScatterTransfer+0x34
fffff880`091f6bb0 fffff800`033f0472 : fffffa80`08590fd8 fffffa80`08590fd0 00000000`00000028 00000000`00000000 : hal!HalpMapTransfer+0x7b
fffff880`091f6c40 fffff800`033ef94f : 00000000`00000000 fffff800`033ecfb9 00000000`00000000 00000000`00000003 : hal!IoMapTransfer+0x8e
fffff880`091f6c80 fffff800`033efafd : fffffa80`0637d050 fffffa80`069a19b0 00000000`00000001 fffffa80`000003b4 : hal!HalpAllocateAdapterCallback+0xc7
fffff880`091f6d20 fffff800`033f0156 : fffffa80`069a19b0 00000000`00000000 fffffa80`069a1900 00000000`00000003 : hal!IoFreeAdapterChannel+0x109
fffff880`091f6d50 fffff800`033ef71f : fffffa80`0b0ee9d0 00000000`00000050 fffffa80`069a19b0 fffffa80`0a875330 : hal!HalAllocateAdapterChannel+0x11a
fffff880`091f6d90 fffff880`018b6750 : fffffa80`08acc260 fffffa80`069a1620 fffffa80`000000a0 fffff880`06a78c40 : hal!HalBuildScatterGatherList+0x2f3
fffff880`091f6e00 fffff880`0683476b : fffffa80`0637d1a0 00000000`00000000 fffffa80`0aa6a5b0 fffff880`069d9aa0 : ndis!NdisMAllocateNetBufferSGList+0x110
fffff880`091f6ea0 fffffa80`0637d1a0 : 00000000`00000000 fffffa80`0aa6a5b0 fffff880`069d9aa0 00000000`00000000 : NETw5s64+0xb76b
fffff880`091f6ea8 00000000`00000000 : fffffa80`0aa6a5b0 fffff880`069d9aa0 00000000`00000000 00000050`00000100 : 0xfffffa80`0637d1a0
STACK_COMMAND: kb
FOLLOWUP_IP:
NETw5s64+b76b
fffff880`0683476b ?? ???
SYMBOL_STACK_INDEX: c
SYMBOL_NAME: NETw5s64+b76b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: NETw5s64
IMAGE_NAME: NETw5s64.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4aafedb7
FAILURE_BUCKET_ID: X64_0xA_NETw5s64+b76b
BUCKET_ID: X64_0xA_NETw5s64+b76b
Followup: MachineOwner
---------