Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [E:\BSODDmpFiles\nexpb\020912-35412-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03213000 PsLoadedModuleList = 0xfffff800`03458670
Debug session time: Thu Feb 9 12:54:00.795 2012 (GMT-7)
System Uptime: 0 days 0:08:45.028
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {411, fffff6fc50059108, 83b00000b2e4c882, fffff6fc50059129}
Probably caused by : dxgkrnl.sys ( dxgkrnl!DxgkLock+f7 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000000411, The subtype of the bugcheck.
Arg2: fffff6fc50059108
Arg3: 83b00000b2e4c882
Arg4: fffff6fc50059129
Debugging Details:
------------------
BUGCHECK_STR: 0x1a_411
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: javaw.exe
CURRENT_IRQL: 2
TRAP_FRAME: fffff880029f0f90 -- (.trap 0xfffff880029f0f90)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000000000a rbx=0000000000000000 rcx=0000000000000005
rdx=fffff8a00b221000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800536b53b rsp=fffff880029f1120 rbp=fffff880029f12a0
r8=0000000000000001 r9=0000000000000000 r10=0000000000000000
r11=fffff880029f1168 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
dxgkrnl!DxgkLock+0xf7:
fffff880`0536b53b 448b4cc208 mov r9d,dword ptr [rdx+rax*8+8] ds:fffff8a0`0b221058=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff8000326c96d to fffff8000328fc40
STACK_TEXT:
fffff880`029f0c38 fffff800`0326c96d : 00000000`0000001a 00000000`00000411 fffff6fc`50059108 83b00000`b2e4c882 : nt!KeBugCheckEx
fffff880`029f0c40 fffff800`032c1001 : 83b00000`b2e4c882 fffff6fc`50059108 0000007f`fffffff8 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x6061
fffff880`029f0c90 fffff800`032ad7ef : 00000000`00000000 fffff800`034c5500 00000000`00000000 fffff800`034c55c0 : nt!MiResolveTransitionFault+0x381
fffff880`029f0d20 fffff800`0329d9db : 00000000`00000056 fffff880`00000040 83b00000`b2e4c882 00000000`00000002 : nt!MiDispatchFault+0x95f
fffff880`029f0e30 fffff800`0328dd6e : 00000000`00000000 fffff8a0`0b221058 fffff8a0`0a8f9600 fffff8a0`0a8f9660 : nt!MmAccessFault+0xe1b
fffff880`029f0f90 fffff880`0536b53b : fffff880`0536b444 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`029f1120 fffff960`001bf6f2 : 00000000`491ccfe0 ffffffff`00000200 00000000`000007db 00000000`7ef92000 : dxgkrnl!DxgkLock+0xf7
fffff880`029f11f0 fffff800`0328eed3 : fffffa80`0696bb60 00000000`000002b8 fffff880`029f11f8 fffffa80`07fb5550 : win32k!NtGdiDdDDILock+0x12
fffff880`029f1220 00000000`732a156a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`491ccfb8 fffff800`03287210 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x732a156a
fffff880`029f1600 fffff880`029f1db0 : fffff880`029f1600 fffffa80`0696bb60 00000000`00000000 00000000`00000000 : nt!KiCallUserMode
fffff880`029f1608 fffff880`029f1600 : fffffa80`0696bb60 00000000`00000000 00000000`00000000 fffff880`029f1db0 : 0xfffff880`029f1db0
fffff880`029f1610 fffffa80`0696bb60 : 00000000`00000000 00000000`00000000 fffff880`029f1db0 00000000`00000000 : 0xfffff880`029f1600
fffff880`029f1618 00000000`00000000 : 00000000`00000000 fffff880`029f1db0 00000000`00000000 00000000`00000000 : 0xfffffa80`0696bb60
STACK_COMMAND: kb
FOLLOWUP_IP:
dxgkrnl!DxgkLock+f7
fffff880`0536b53b 448b4cc208 mov r9d,dword ptr [rdx+rax*8+8]
SYMBOL_STACK_INDEX: 6
SYMBOL_NAME: dxgkrnl!DxgkLock+f7
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgkrnl
IMAGE_NAME: dxgkrnl.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce799fa
FAILURE_BUCKET_ID: X64_0x1a_411_dxgkrnl!DxgkLock+f7
BUCKET_ID: X64_0x1a_411_dxgkrnl!DxgkLock+f7
Followup: MachineOwner
---------
Caused by
DirectX, your graphics card, or your graphics card driver. Other possible causes are memory or drivers.
Still no crashes due to verifier...
Run your memory tests again. Sometimes errors do not show up the first few runs (7 passes each), but show up on a subsequent run. If memory is failing, it can be finicky and work fine some of the time but not all the time, which is why it is good to run the tests multiple times.
Disable Verifier. Follow the steps for
Diagnosing basic problems with DirectX. To re-install your display card drivers as outlined in the DirectX link, use the following steps.
- Download the latest drivers for your display card(s)
- Click Start Menu
- Right Click My Computer/Computer
- Click Manage
- Click Device Manager from the list on the left
- Expand Display adapters
- Do the following for each adapter (in case you have multiple display cards)
- Right click the adapter
- Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
- Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
- Restart your computer after uninstalling drivers for all display cards
- Install the latest driver for the display cards once Windows starts
Alternatively:
- Login as an adminstrative user
- Download the latest drivers for your display card(s)
- Click Start Menu
- Click Control Panel
- Click Hardware and Sound
- Click Device Manager (the last link under Devices and Printers)
- Expand Display adapters
- Do the following for each adapter (in case you have multiple display cards)
- Right click the adapter
- Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
- Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
- Restart your computer after uninstalling drivers for all display cards
- Install the latest driver for the display cards once Windows starts
Enable Verifier on all non-Microsoft drivers as before.
