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\DMP\011511-21481-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`03008000 PsLoadedModuleList = 0xfffff800`03245e50
Debug session time: Sat Jan 15 17:29:48.020 2011 (UTC - 5:00)
System Uptime: 0 days 0:27:40.784
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {ffffe4801d3fef62, 1, fffff8000307ba67, 7}
Could not read faulting driver name
Probably caused by : hardware ( nt!InterlockedPushListSList+17 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ffffe4801d3fef62, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff8000307ba67, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000007, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800032b00e0
ffffe4801d3fef62
FAULTING_IP:
nt!InterlockedPushListSList+17
fffff800`0307ba67 c14c8bd241 ror dword ptr [rbx+rcx*4-2Eh],41h
MM_INTERNAL_CODE: 7
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: System
CURRENT_IRQL: 0
TRAP_FRAME: fffff88005fd1a00 -- (.trap 0xfffff88005fd1a00)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa8005d997e0
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000307ba67 rsp=fffff88005fd1b98 rbp=0000000000000000
r8=fffff88005fd1b60 r9=0000000000000000 r10=fffffffffffffffb
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!InterlockedPushListSList+0x17:
fffff800`0307ba67 c14c8bd241 ror dword ptr [rbx+rcx*4-2Eh],41h ds:3000:ffffea00`17665f52=????????
Resetting default scope
MISALIGNED_IP:
nt!InterlockedPushListSList+17
fffff800`0307ba67 c14c8bd241 ror dword ptr [rbx+rcx*4-2Eh],41h
LAST_CONTROL_TRANSFER: from fffff800030f7849 to fffff80003078740
STACK_TEXT:
fffff880`05fd1898 fffff800`030f7849 : 00000000`00000050 ffffe480`1d3fef62 00000000`00000001 fffff880`05fd1a00 : nt!KeBugCheckEx
fffff880`05fd18a0 fffff800`0307682e : 00000000`00000001 fffffa80`05d99010 00000000`0032d500 fffffa80`05da5000 : nt! ?? ::FNODOBFM::`string'+0x40e0b
fffff880`05fd1a00 fffff800`0307ba67 : fffff880`03f04437 fffffa80`05d99010 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`05fd1b98 fffffa80`05d99010 : 00000000`00000000 00000000`00000000 fffff880`03f2fc0d fffffa80`05d99958 : nt!InterlockedPushListSList+0x17
fffff880`05fd1ba8 00000000`00000000 : 00000000`00000000 fffff880`03f2fc0d fffffa80`05d99958 fffff880`05fd1c00 : 0xfffffa80`05d99010
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!InterlockedPushListSList+17
fffff800`0307ba67 c14c8bd241 ror dword ptr [rbx+rcx*4-2Eh],41h
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!InterlockedPushListSList+17
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
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\DMP\011511-20498-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`03009000 PsLoadedModuleList = 0xfffff800`03246e50
Debug session time: Sat Jan 15 17:00:55.321 2011 (UTC - 5:00)
System Uptime: 0 days 2:57:22.695
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {ffffffffffffffff, 0, 1, fffff80003096db9}
Probably caused by : hardware ( nt!MiResolveDemandZeroFault+69 )
Followup: MachineOwner
---------
2: 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: ffffffffffffffff, memory referenced
Arg2: 0000000000000000, IRQL
Arg3: 0000000000000001, 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: fffff80003096db9, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800032b10e0
ffffffffffffffff
CURRENT_IRQL: 0
FAULTING_IP:
nt!MiResolveDemandZeroFault+69
fffff800`03096db9 000f add byte ptr [rdi],cl
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: firefox.exe
TRAP_FRAME: fffff88009ff8840 -- (.trap 0xfffff88009ff8840)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8003be72a0 rbx=0000000000000000 rcx=4cdff70001080000
rdx=000000000e780000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003096db9 rsp=fffff88009ff89d0 rbp=fffff88009ff8a40
r8=fffff88009ff8c20 r9=fffff68000073c00 r10=0000000000000000
r11=fffff88009ff8c20 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!MiResolveDemandZeroFault+0x69:
fffff800`03096db9 000f add byte ptr [rdi],cl ds:b66c:00000000`00000000=??
Resetting default scope
MISALIGNED_IP:
nt!MiResolveDemandZeroFault+69
fffff800`03096db9 000f add byte ptr [rdi],cl
LAST_CONTROL_TRANSFER: from fffff80003078ca9 to fffff80003079740
STACK_TEXT:
fffff880`09ff86f8 fffff800`03078ca9 : 00000000`0000000a ffffffff`ffffffff 00000000`00000000 00000000`00000001 : nt!KeBugCheckEx
fffff880`09ff8700 fffff800`03077920 : 00000000`00000001 00000000`00000000 ffffffff`ffffff00 fffffa80`0165c900 : nt!KiBugCheckDispatch+0x69
fffff880`09ff8840 fffff800`03096db9 : 80000000`2468f867 fffff880`09ff8a40 fffffa80`03be7638 fffffa80`03be7638 : nt!KiPageFault+0x260
fffff880`09ff89d0 fffff800`030939c6 : 00000000`00000000 00000000`0e780000 fffff880`09ff8c20 fffff680`00073c00 : nt!MiResolveDemandZeroFault+0x69
fffff880`09ff8ac0 fffff800`0307782e : 00000000`00000000 00000000`00437b00 00000000`09c80601 00000000`00000020 : nt!MmAccessFault+0x5c6
fffff880`09ff8c20 00000000`7125f936 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`00436f80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7125f936
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiResolveDemandZeroFault+69
fffff800`03096db9 000f add byte ptr [rdi],cl
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!MiResolveDemandZeroFault+69
FOLLOWUP_NAME: MachineOwner
DEBUG_FLR_IMAGE_TIMESTAMP: 0
IMAGE_NAME: hardware
MODULE_NAME: hardware
FAILURE_BUCKET_ID: X64_IP_MISALIGNED
BUCKET_ID: X64_IP_MISALIGNED
Followup: MachineOwner
---------
