Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\042211-8689-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0x82c0e000 PsLoadedModuleList = 0x82d58850
Debug session time: Fri Apr 22 04:01:45.694 2011 (GMT-4)
System Uptime: 0 days 5:26:12.675
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {cccccccc, 2, 1, 82c87a23}
Unable to load image \SystemRoot\system32\DRIVERS\igdkmd32.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for igdkmd32.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd32.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiProcessDpcCompletedPacket+3d6 )
Followup: MachineOwner
---------
0: 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: cccccccc, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, 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: 82c87a23, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82d78718
Unable to read MiSystemVaType memory at 82d581a0
cccccccc
CURRENT_IRQL: 2
FAULTING_IP:
nt!KiSignalSynchronizationObject+1c
82c87a23 8901 mov dword ptr [ecx],eax
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
TRAP_FRAME: 8078ac64 -- (.trap 0xffffffff8078ac64)
ErrCode = 00000002
eax=0004c25d ebx=b6e51b78 ecx=cccccccc edx=00000000 esi=0004c25d edi=909a32a7
eip=82c87a23 esp=8078acd8 ebp=8078ace8 iopl=0 nv up ei ng nz ac po cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010293
nt!KiSignalSynchronizationObject+0x1c:
82c87a23 8901 mov dword ptr [ecx],eax ds:0023:cccccccc=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from 82c87a23 to 82c4f5cb
STACK_TEXT:
8078ac64 82c87a23 badb0d00 00000000 8078ac84 nt!KiTrap0E+0x2cf
8078ace8 82c85553 82d39d20 b6e51b70 82609788 nt!KiSignalSynchronizationObject+0x1c
8078ad10 9099934e b6e51b70 00000000 00000000 nt!KeSetEvent+0x8e
8078ad5c 90999451 82609788 82607000 00000000 dxgmms1!VidSchiProcessDpcCompletedPacket+0x3d6
8078ad78 9099951e 82609788 879de000 82609788 dxgmms1!VidSchiProcessDpcDmaPacket+0xc5
8078ad90 90999832 879de000 00000001 85e995a0 dxgmms1!VidSchDdiNotifyDpcWorker+0xb2
8078adb4 92145f28 85f15518 8078add4 92145e88 dxgmms1!VidSchDdiNotifyDpc+0x78
8078adc0 92145e88 8598eec0 85f15518 92145e2b dxgkrnl!VIDSCH_EXPORT::VidSchDdiNotifyDpc+0x11
8078add4 918aceb4 85f15518 92145e2b 8078ae18 dxgkrnl!DxgNotifyDpcCB+0x5d
WARNING: Stack unwind information not available. Following frames may be wrong.
8078ade4 918acb0c 85f5b000 00000000 8807bbc4 igdkmd32+0x87eb4
8078ae18 9183960d 85f5b000 00000000 00000000 igdkmd32+0x87b0c
8078af28 92145b45 85f5b000 85f15908 84b91a24 igdkmd32+0x1460d
8078af48 82c861b5 85f15908 85f15518 00000000 dxgkrnl!DpiFdoDpcForIsr+0x28
8078afa4 82c86018 82d39d20 84b919a0 00000000 nt!KiExecuteAllDpcs+0xf9
8078aff4 82c857dc 80786bc8 00000000 00000000 nt!KiRetireDpcList+0xd5
8078aff8 80786bc8 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2c
82c857dc 00000000 0000001a 00d6850f bb830000 0x80786bc8
STACK_COMMAND: kb
FOLLOWUP_IP:
dxgmms1!VidSchiProcessDpcCompletedPacket+3d6
9099934e 807dff00 cmp byte ptr [ebp-1],0
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: dxgmms1!VidSchiProcessDpcCompletedPacket+3d6
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4d4a24c1
FAILURE_BUCKET_ID: 0xA_dxgmms1!VidSchiProcessDpcCompletedPacket+3d6
BUCKET_ID: 0xA_dxgmms1!VidSchiProcessDpcCompletedPacket+3d6
Followup: MachineOwner
---------