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\030311-44600-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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`0325d000 PsLoadedModuleList = 0xfffff800`0349ae50
Debug session time: Thu Mar 3 20:50:02.810 2011 (UTC - 5:00)
System Uptime: 4 days 7:39:00.177
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
....................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {58, 2, 0, fffff8000338ba80}
Probably caused by : memory_corruption ( nt!MiReleaseConfirmedPageFileSpace+40 )
Followup: MachineOwner
---------
3: 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: 0000000000000058, 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: fffff8000338ba80, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800035050e0
0000000000000058
CURRENT_IRQL: 2
FAULTING_IP:
nt!MiReleaseConfirmedPageFileSpace+40
fffff800`0338ba80 4c8b6e58 mov r13,qword ptr [rsi+58h]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
TRAP_FRAME: fffff880043d2900 -- (.trap 0xfffff880043d2900)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff880043d2b08 rbx=0000000000000000 rcx=000000000000000c
rdx=fffff880043d2ac0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000338ba80 rsp=fffff880043d2a90 rbp=0000000005fd7448
r8=0000000000000114 r9=00000000000572a0 r10=000000000000be29
r11=fffff781c0000488 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!MiReleaseConfirmedPageFileSpace+0x40:
fffff800`0338ba80 4c8b6e58 mov r13,qword ptr [rsi+58h] ds:00000000`00000058=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800032ccca9 to fffff800032cd740
STACK_TEXT:
fffff880`043d27b8 fffff800`032ccca9 : 00000000`0000000a 00000000`00000058 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`043d27c0 fffff800`032cb920 : bad00000`23ddb921 fffffa80`0745fb18 00000000`00000000 00000087`696e1a4f : nt!KiBugCheckDispatch+0x69
fffff880`043d2900 fffff800`0338ba80 : 00000980`00000000 0000007f`fffffff8 00000000`00000001 00000000`00000000 : nt!KiPageFault+0x260
fffff880`043d2a90 fffff800`032b79da : 05fd7448`05dd2158 08ad0c22`b5fb7e7e fffffa80`0745fb18 05fd7448`05dd2158 : nt!MiReleaseConfirmedPageFileSpace+0x40
fffff880`043d2b10 fffff800`035bc30f : fffffa80`0745fa60 00000000`00000000 00000000`69536d4d fffffa80`000840a1 : nt!MiDeleteSegmentPages+0x316
fffff880`043d2bc0 fffff800`033f509b : fffffa80`0745fa68 00000000`00000001 00000000`00000000 00000000`00000631 : nt!MiSegmentDelete+0x7b
fffff880`043d2c00 fffff800`033f570d : 00000000`00000000 00000000`00000080 fffffa80`05501740 00000000`00000012 : nt!MiProcessDereferenceList+0x23b
fffff880`043d2cc0 fffff800`035707c6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiDereferenceSegmentThread+0x10d
fffff880`043d2d40 fffff800`032abc26 : fffff880`009b2180 fffffa80`0552db60 fffff880`009bd0c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`043d2d80 00000000`00000000 : fffff880`043d3000 fffff880`043cd000 fffff880`043d2550 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiReleaseConfirmedPageFileSpace+40
fffff800`0338ba80 4c8b6e58 mov r13,qword ptr [rsi+58h]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!MiReleaseConfirmedPageFileSpace+40
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4cc791bd
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0xA_nt!MiReleaseConfirmedPageFileSpace+40
BUCKET_ID: X64_0xA_nt!MiReleaseConfirmedPageFileSpace+40
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\030511-39499-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00b9c500?
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`03208000 PsLoadedModuleList = 0xfffff800`03445e50
Debug session time: Sat Mar 5 13:34:40.722 2011 (UTC - 5:00)
System Uptime: 1 days 3:56:18.940
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, fffffa80062b0a20, fffff80000b9c518, fffffa8005795560}
Probably caused by : pci.sys
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa80062b0a20, Physical Device Object of the stack
Arg3: fffff80000b9c518, Functional Device Object of the stack
Arg4: fffffa8005795560, The blocked IRP
Debugging Details:
------------------
DRVPOWERSTATE_SUBCODE: 3
IMAGE_NAME: pci.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc117
MODULE_NAME: pci
FAULTING_MODULE: fffff88000e0a000 pci
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
STACK_TEXT:
fffff800`00b9c4c8 fffff800`032e7273 : 00000000`0000009f 00000000`00000003 fffffa80`062b0a20 fffff800`00b9c518 : nt!KeBugCheckEx
fffff800`00b9c4d0 fffff800`0328429e : fffff800`00b9c600 fffff800`00b9c600 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x292b0
fffff800`00b9c570 fffff800`03283dd6 : fffffa80`0ca143a0 fffffa80`0ca143a0 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5e0 fffff800`032844be : 000000ea`2db84d90 fffff800`00b9cc58 00000000`006260de fffff800`033f6e48 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`03283cb7 : 00000024`8063e1c2 00000024`006260de 00000024`8063e17f 00000000`000000de : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`03280eea : fffff800`033f2e80 fffff800`03400c40 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: X64_0x9F_3_nvlddmkm_IMAGE_pci.sys
BUCKET_ID: X64_0x9F_3_nvlddmkm_IMAGE_pci.sys
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\030611-27939-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00b9c500?
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`0320c000 PsLoadedModuleList = 0xfffff800`03449e50
Debug session time: Sun Mar 6 18:13:57.590 2011 (UTC - 5:00)
System Uptime: 0 days 5:34:43.808
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, fffffa80062c1a20, fffff80000b9c518, fffffa800b1bbe10}
Probably caused by : pci.sys
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa80062c1a20, Physical Device Object of the stack
Arg3: fffff80000b9c518, Functional Device Object of the stack
Arg4: fffffa800b1bbe10, The blocked IRP
Debugging Details:
------------------
DRVPOWERSTATE_SUBCODE: 3
IMAGE_NAME: pci.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc117
MODULE_NAME: pci
FAULTING_MODULE: fffff88000d49000 pci
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
STACK_TEXT:
fffff800`00b9c4c8 fffff800`032eb273 : 00000000`0000009f 00000000`00000003 fffffa80`062c1a20 fffff800`00b9c518 : nt!KeBugCheckEx
fffff800`00b9c4d0 fffff800`0328829e : fffff800`00b9c600 fffff800`00b9c600 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x292b0
fffff800`00b9c570 fffff800`03287dd6 : fffff800`0342c700 00000000`0013a4f7 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5e0 fffff800`032884be : 0000002e`c2e1f074 fffff800`00b9cc58 00000000`0013a4f7 fffff800`033fb168 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`03287cb7 : 00000007`4a0650c1 00000007`0013a4f7 00000007`4a065010 00000000`000000f7 : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`03284eea : fffff800`033f6e80 fffff800`03404c40 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: X64_0x9F_3_nvlddmkm_IMAGE_pci.sys
BUCKET_ID: X64_0x9F_3_nvlddmkm_IMAGE_pci.sys
Followup: MachineOwner
---------