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`02a64000 PsLoadedModuleList = 0xfffff800`02ca1e50
Debug session time: Tue Jan 25 21:36:22.993 2011 (GMT-5)
System Uptime: 0 days 1:23:56.304
Loading Kernel Symbols
...............................................................
................................................................
........................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc000001d, fffff8800480af73, fffff880064b5958, fffff880064b51c0}
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiSwitchContextWithCheck+123 )
Followup: MachineOwner
---------
4: 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: ffffffffc000001d, The exception code that was not handled
Arg2: fffff8800480af73, The address that the exception occurred at
Arg3: fffff880064b5958, Exception Record Address
Arg4: fffff880064b51c0, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.
FAULTING_IP:
dxgmms1!VidSchiSwitchContextWithCheck+123
fffff880`0480af73 7432 je dxgmms1!VidSchiSwitchContextWithCheck+0x157 (fffff880`0480afa7)
EXCEPTION_RECORD: fffff880064b5958 -- (.exr 0xfffff880064b5958)
ExceptionAddress: fffff8800480af73 (dxgmms1!VidSchiSwitchContextWithCheck+0x0000000000000123)
ExceptionCode: c000001d (Illegal instruction)
ExceptionFlags: 00000000
NumberParameters: 0
CONTEXT: fffff880064b51c0 -- (.cxr 0xfffff880064b51c0)
rax=0000000000000000 rbx=fffffa800de15090 rcx=0000000000000000
rdx=fffffa800cd99de0 rsi=fffffa800f412010 rdi=0000000000000001
rip=fffff8800480af73 rsp=fffff880064b5b90 rbp=fffffa800f461000
r8=0000000000000002 r9=0000000000000000 r10=fffffa800f4127e0
r11=fffff880064b5b70 r12=000000000de15090 r13=fffff880064b5d00
r14=0000000000000000 r15=0000000000000001
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
dxgmms1!VidSchiSwitchContextWithCheck+0x123:
fffff880`0480af73 7432 je dxgmms1!VidSchiSwitchContextWithCheck+0x157 (fffff880`0480afa7) [br=1]
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x7E
PROCESS_NAME: System
CURRENT_IRQL: 2
ERROR_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.
LAST_CONTROL_TRANSFER: from fffff8800480b193 to fffff8800480af73
FAILED_INSTRUCTION_ADDRESS:
dxgmms1!VidSchiSwitchContextWithCheck+123
fffff880`0480af73 7432 je dxgmms1!VidSchiSwitchContextWithCheck+0x157 (fffff880`0480afa7)
STACK_TEXT:
fffff880`064b5b90 fffff880`0480b193 : fffffa80`0f412010 fffffa80`0de15090 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiSwitchContextWithCheck+0x123
fffff880`064b5bf0 fffff880`04837e7a : 00000000`00000000 fffffa80`0de15090 00000000`00000080 fffffa80`0f412010 : dxgmms1!VidSchiScheduleCommandToRun+0xa7
fffff880`064b5d00 fffff800`02d78c06 : 00000000`04d48178 fffffa80`0f3bf060 fffffa80`0ca7c9e0 fffffa80`0f3bf060 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`064b5d40 fffff800`02ab2c26 : fffff800`02c4ee80 fffffa80`0f3bf060 fffff800`02c5cc40 fffff880`01224a90 : nt!PspSystemThreadStartup+0x5a
fffff880`064b5d80 00000000`00000000 : fffff880`064b6000 fffff880`064b0000 fffff880`064b5690 00000000`00000000 : nt!KxStartSystemThread+0x16
FOLLOWUP_IP:
dxgmms1!VidSchiSwitchContextWithCheck+123
fffff880`0480af73 7432 je dxgmms1!VidSchiSwitchContextWithCheck+0x157 (fffff880`0480afa7)
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: dxgmms1!VidSchiSwitchContextWithCheck+123
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc578
STACK_COMMAND: .cxr 0xfffff880064b51c0 ; kb
FAILURE_BUCKET_ID: X64_0x7E_BAD_IP_dxgmms1!VidSchiSwitchContextWithCheck+123
BUCKET_ID: X64_0x7E_BAD_IP_dxgmms1!VidSchiSwitchContextWithCheck+123
Followup: MachineOwner
---------
Debug session time: Tue Jan 25 22:00:38.723 2011 (GMT-5)
System Uptime: 0 days 0:18:32.034
Loading Kernel Symbols
...............................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {38802674, 2, 0, fffff80002a86d7d}
Probably caused by : ntkrnlmp.exe ( nt!KiProcessExpiredTimerList+6d )
Followup: MachineOwner
---------
4: 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: 0000000038802674, 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: fffff80002a86d7d, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cb30e0
0000000038802674
CURRENT_IRQL: 2
FAULTING_IP:
nt!KiProcessExpiredTimerList+6d
fffff800`02a86d7d 4885c0 test rax,rax
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
TRAP_FRAME: fffff88003046680 -- (.trap 0xfffff88003046680)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa800f329100
rdx=0000000000000102 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002a86d7d rsp=fffff88003046810 rbp=0000000000011673
r8=fffff880009b4301 r9=0000000000000006 r10=0000000000000073
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
nt!KiProcessExpiredTimerList+0x6d:
fffff800`02a86d7d 4885c0 test rax,rax
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002a7aca9 to fffff80002a7b740
STACK_TEXT:
fffff880`03046538 fffff800`02a7aca9 : 00000000`0000000a 00000000`38802674 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`03046540 fffff800`02a79920 : 00000000`00000000 fffffa80`0f329120 fffff880`03046740 fffffa80`0e65ca30 : nt!KiBugCheckDispatch+0x69
fffff880`03046680 fffff800`02a86d7d : fffffa80`0f329120 fffffa80`0eda3478 fffffa80`0eda3478 00000000`00000102 : nt!KiPageFault+0x260
fffff880`03046810 fffff800`02a874be : 00000002`96d3086f fffff880`03046e88 00000000`00011673 fffff880`009b53e8 : nt!KiProcessExpiredTimerList+0x6d
fffff880`03046e60 fffff800`02a86cb7 : fffff880`009b21c5 fffffa80`00011673 fffffa80`0dce3d38 00000000`00000073 : nt!KiTimerExpiration+0x1be
fffff880`03046f00 fffff800`02a81865 : 00000000`00000000 fffffa80`0f281210 00000000`00000000 fffff880`0526f588 : nt!KiRetireDpcList+0x277
fffff880`03046fb0 fffff800`02a8167c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
fffff880`064fb6e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiProcessExpiredTimerList+6d
fffff800`02a86d7d 4885c0 test rax,rax
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!KiProcessExpiredTimerList+6d
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
FAILURE_BUCKET_ID: X64_0xA_nt!KiProcessExpiredTimerList+6d
BUCKET_ID: X64_0xA_nt!KiProcessExpiredTimerList+6d
Followup: MachineOwner
---------