Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\a\Minidump\D M P\122210-34554-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x8301f000 PsLoadedModuleList = 0x83167810
Debug session time: Wed Dec 22 06:57:57.435 2010 (UTC - 5:00)
System Uptime: 0 days 0:00:11.965
Loading Kernel Symbols
..................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, 86c558fc, 0, 0}
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: 00000000, Machine Check Exception
Arg2: 86c558fc, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000, High order 32-bits of the MCi_STATUS value.
Arg4: 00000000, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
------------------
BUGCHECK_STR: 0x124_AuthenticAMD
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
STACK_TEXT:
8e327cc4 830edfc5 86c558e0 83186c28 83186c20 nt!WheapCreateTriageDumpFromPreviousSession+0x32
8e327ce4 830eedef 83186c20 86c558e0 83186c50 nt!WheapProcessWorkQueueItem+0x56
8e327d00 8308cf3b 83186c20 00000000 85cc24c0 nt!WheapWorkQueueWorkerRoutine+0x1f
8e327d50 8322d6d3 00000001 ab5a0b4d 00000000 nt!ExpWorkerThread+0x10d
8e327d90 830df0f9 8308ce2e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: hardware
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: 0x124_AuthenticAMD_PROCESSOR_BUS_PRV
BUCKET_ID: 0x124_AuthenticAMD_PROCESSOR_BUS_PRV
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\a\Minidump\D M P\122210-14336-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*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
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e5f000 PsLoadedModuleList = 0xfffff800`0309ce50
Debug session time: Wed Dec 22 08:19:35.930 2010 (UTC - 5:00)
System Uptime: 0 days 2:01:37.226
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {0, c, 8, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
Followup: MachineOwner
---------
1: 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: 0000000000000000, memory referenced
Arg2: 000000000000000c, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: 0000000000000000, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800031070e0
0000000000000000
CURRENT_IRQL: c
FAULTING_IP:
+3538346362626361
00000000`00000000 ?? ???
PROCESS_NAME: svchost.exe
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
TRAP_FRAME: fffff8800679c570 -- (.trap 0xfffff8800679c570)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000003 rbx=0000000000000000 rcx=0000000000000003
rdx=f8800679c7a00006 rsi=0000000000000000 rdi=0000000000000000
rip=0000000000000000 rsp=fffff8800679c700 rbp=0000000000000000
r8=0000000000004cc0 r9=0000000000000000 r10=0000000000000030
r11=fffff88002fd5180 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
00000000`00000000 ?? ???
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002ececa9 to fffff80002ecf740
FAILED_INSTRUCTION_ADDRESS:
+3538346362626361
00000000`00000000 ?? ???
STACK_TEXT:
fffff880`0679c428 fffff800`02ececa9 : 00000000`0000000a 00000000`00000000 00000000`0000000c 00000000`00000008 : nt!KeBugCheckEx
fffff880`0679c430 fffff800`02ecd920 : 00000000`00000000 00000000`00000005 fffffa80`08214000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`0679c570 00000000`00000000 : 00000000`00040001 00000000`00000005 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiPageFault+260
fffff800`02ecd920 440f20c0 mov rax,cr8
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: nt!KiPageFault+260
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
FAILURE_BUCKET_ID: X64_0xD1_CODE_AV_NULL_IP_nt!KiPageFault+260
BUCKET_ID: X64_0xD1_CODE_AV_NULL_IP_nt!KiPageFault+260
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\a\Minidump\D M P\122210-14430-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*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
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e02000 PsLoadedModuleList = 0xfffff800`0303fe50
Debug session time: Tue Dec 21 17:11:47.130 2010 (UTC - 5:00)
System Uptime: 0 days 22:26:49.009
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7F, {8, 80050031, 6f8, fffff8800166b9b6}
Probably caused by : ndis.sys ( ndis!memcmp+6 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000006f8
Arg4: fffff8800166b9b6
Debugging Details:
------------------
BUGCHECK_STR: 0x7f_8
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff80002e71ca9 to fffff80002e72740
STACK_TEXT:
fffff880`009edd68 fffff800`02e71ca9 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff880`009edd70 fffff800`02e70172 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`009edeb0 fffff880`0166b9b6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
00000000`0a1d85e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!memcmp+0x6
STACK_COMMAND: kb
FOLLOWUP_IP:
ndis!memcmp+6
fffff880`0166b9b6 087222 or byte ptr [rdx+22h],dh
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: ndis!memcmp+6
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: ndis
IMAGE_NAME: ndis.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc184
FAILURE_BUCKET_ID: X64_0x7f_8_ndis!memcmp+6
BUCKET_ID: X64_0x7f_8_ndis!memcmp+6
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\a\Minidump\D M P\122210-19437-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*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
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e68000 PsLoadedModuleList = 0xfffff800`030a5e50
Debug session time: Wed Dec 22 08:27:40.405 2010 (UTC - 5:00)
System Uptime: 0 days 0:06:30.716
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff80002ed79e4, fffff88009d71250, 0}
Probably caused by : hardware ( nt!KiSystemServiceExit+49 )
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: fffff80002ed79e4, Address of the instruction which caused the bugcheck
Arg3: fffff88009d71250, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - <Unable to get error code text>
FAULTING_IP:
nt!KiSystemServiceExit+49
fffff800`02ed79e4 8801 mov byte ptr [rcx],al
CONTEXT: fffff88009d71250 -- (.cxr 0xfffff88009d71250)
rax=fffff880009e7180 rbx=0000000005365b90 rcx=0000000000000000
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ed79e4 rsp=fffff88009d71c20 rbp=fffff88009d71ca0
r8=0000000000000000 r9=0000000000000000 r10=fffffa8006a36570
r11=fffffa8006f4a060 r12=00000000053dadd0 r13=0000000000000000
r14=0000000000000001 r15=0000000000000001
iopl=0 nv up di pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010046
nt!KiSystemServiceExit+0x49:
fffff800`02ed79e4 8801 mov byte ptr [rcx],al ds:002b:00000000`00000000=??
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: vegas100.exe
CURRENT_IRQL: 0
MISALIGNED_IP:
nt!KiSystemServiceExit+49
fffff800`02ed79e4 8801 mov byte ptr [rcx],al
LAST_CONTROL_TRANSFER: from 0000000076f4ff5a to fffff80002ed79e4
STACK_TEXT:
fffff880`09d71c20 00000000`76f4ff5a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x49
00000000`0bc5fe48 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76f4ff5a
FOLLOWUP_IP:
nt!KiSystemServiceExit+49
fffff800`02ed79e4 8801 mov byte ptr [rcx],al
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!KiSystemServiceExit+49
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
STACK_COMMAND: .cxr 0xfffff88009d71250 ; kb
MODULE_NAME: hardware
FAILURE_BUCKET_ID: X64_IP_MISALIGNED
BUCKET_ID: X64_IP_MISALIGNED
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\a\Minidump\D M P\122210-14710-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*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
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e62000 PsLoadedModuleList = 0xfffff800`0309fe50
Debug session time: Wed Dec 22 09:11:26.345 2010 (UTC - 5:00)
System Uptime: 0 days 0:00:52.641
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff80002ed19e4, fffff8800bb17250, 0}
Probably caused by : hardware ( nt!KiSystemServiceExit+49 )
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: fffff80002ed19e4, Address of the instruction which caused the bugcheck
Arg3: fffff8800bb17250, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - <Unable to get error code text>
FAULTING_IP:
nt!KiSystemServiceExit+49
fffff800`02ed19e4 8801 mov byte ptr [rcx],al
CONTEXT: fffff8800bb17250 -- (.cxr 0xfffff8800bb17250)
rax=fffff880009e7180 rbx=0000000005398ee0 rcx=0000000000000000
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ed19e4 rsp=fffff8800bb17c20 rbp=fffff8800bb17ca0
r8=0000000000000000 r9=0000000000000000 r10=fffffa8006a1a570
r11=fffffa800a959060 r12=00000000056a6e50 r13=0000000000000000
r14=0000000000000001 r15=0000000000000001
iopl=0 nv up di pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010046
nt!KiSystemServiceExit+0x49:
fffff800`02ed19e4 8801 mov byte ptr [rcx],al ds:002b:00000000`00000000=??
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: vegas100.exe
CURRENT_IRQL: 0
MISALIGNED_IP:
nt!KiSystemServiceExit+49
fffff800`02ed19e4 8801 mov byte ptr [rcx],al
LAST_CONTROL_TRANSFER: from 00000000775cff5a to fffff80002ed19e4
STACK_TEXT:
fffff880`0bb17c20 00000000`775cff5a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x49
00000000`0bb1fe48 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x775cff5a
FOLLOWUP_IP:
nt!KiSystemServiceExit+49
fffff800`02ed19e4 8801 mov byte ptr [rcx],al
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!KiSystemServiceExit+49
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
STACK_COMMAND: .cxr 0xfffff8800bb17250 ; kb
MODULE_NAME: hardware
FAILURE_BUCKET_ID: X64_IP_MISALIGNED
BUCKET_ID: X64_IP_MISALIGNED
Followup: MachineOwner
---------