meridian
08-18-2012, 08:32 AM
Hi
I am using the latest stable driver 6.3M1 and getting a number of BSODs caused by the dlkmd driver.
The windbg !analyze -v is pasted below:
6: kd> !analyze -v
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff880154f3d12, The address that the exception occurred at
Arg3: fffff8800f771d28, Exception Record Address
Arg4: fffff8800f771590, Context Record Address
Debugging Details:
------------------
PEB is paged out (Peb.Ldr = 000007ff`fffd3018). Type ".hh dbgerr001" for detail
s
PEB is paged out (Peb.Ldr = 000007ff`fffd3018). Type ".hh dbgerr001" for detail
s
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced me
mory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
dlkmd+19d12
fffff880`154f3d12 48833f00 cmp qword ptr [rdi],0
EXCEPTION_RECORD: fffff8800f771d28 -- (.exr 0xfffff8800f771d28)
ExceptionAddress: fffff880154f3d12 (dlkmd+0x0000000000019d12)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000000
Attempt to read from address 0000000000000000
CONTEXT: fffff8800f771590 -- (.cxr 0xfffff8800f771590)
rax=0000000000000000 rbx=fffffa800a3bf000 rcx=2e6d671177960000
rdx=00000000000000a0 rsi=fffffa800a3bf000 rdi=0000000000000000
rip=fffff880154f3d12 rsp=fffff8800f771f60 rbp=0000000000000001
r8=0000000000000065 r9=0000000000000000 r10=0000000000000000
r11=fffff8800f771f50 r12=0000000000000000 r13=fffff8801552e9a0
r14=fffff88015523110 r15=fffff8801552e8c0
iopl=0 nv up ei ng nz ac pe cy
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010293
dlkmd+0x19d12:
fffff880`154f3d12 48833f00 cmp qword ptr [rdi],0 ds:002b:00000000`000
00000=????????????????
Resetting default scope
DEFAULT_BUCKET_ID: NULL_DEREFERENCE
PROCESS_NAME: csrss.exe
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory
at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000000
READ_ADDRESS: 0000000000000000
FOLLOWUP_IP:
dlkmd+19d12
fffff880`154f3d12 48833f00 cmp qword ptr [rdi],0
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff880154eb77d to fffff880154f3d12
STACK_TEXT:
fffff880`0f771f60 fffff880`154eb77d : 00000000`00000000 fffff880`15523110 000000
00`00000003 00000000`00000002 : dlkmd+0x19d12
fffff880`0f771fe0 fffff880`074ac494 : fffffa80`0c0db000 fffff880`0f772198 fffff8
80`00000001 00000000`00000002 : dlkmd+0x1177d
fffff880`0f7720b0 fffff880`0751be2e : 00000000`00000002 fffff8a0`0b88c860 000000
00`00000000 fffffa80`0c044000 : dxgkrnl!DXGADAPTER::DdiCommitVidPn+0x50
fffff880`0f7720e0 fffff880`074a4282 : 00000000`00000001 00000000`00000000 fffffa
80`0a675c90 fffff8a0`00000001 : dxgkrnl!DmmCommitVidPn+0x7ba
fffff880`0f772220 fffff880`074d13d4 : fffff8a0`0afb0101 fffff8a0`0afb3900 fffff8
a0`0af7f801 fffff8a0`00000000 : dxgkrnl!DXGADAPTER::CommitVidPn+0x546
fffff880`0f772530 fffff880`074bb67b : fffff8a0`02d09190 fffff8a0`0afb3340 000000
00`00000000 fffff8a0`0afb3950 : dxgkrnl!CommitVidPn+0x68
fffff880`0f7725d0 fffff960`0064682d : fffff900`c1ea9020 00000000`00000001 fffff8
80`0f772cd0 00000000`00000001 : dxgkrnl!DxgkCddEnable+0x166b
fffff880`0f772920 fffff960`00645ce1 : ffffffff`00000004 ffffffff`fffd7476 000000
00`00000002 00000000`00000000 : cdd!CreateAndEnableDevice+0x1e1
fffff880`0f7729b0 fffff800`039646ca : 00000000`00000000 fffffa80`0a3a7b60 000000
00`00000080 fffffa80`0c0eeb30 : cdd!PresentWorkerThread+0x975
fffff880`0f772d40 fffff800`036a2126 : fffff800`03840e80 fffffa80`0a3a7b60 fffff8
00`0384ecc0 00000000`00000246 : nt!PspSystemThreadStartup+0x5a
fffff880`0f772d80 00000000`00000000 : fffff880`0f773000 fffff880`0f76d000 fffff8
80`0f7716b0 00000000`00000000 : nt!KiStartSystemThread+0x16
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: dlkmd+19d12
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dlkmd
IMAGE_NAME: dlkmd.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4fb31c0e
STACK_COMMAND: .cxr 0xfffff8800f771590 ; kb
FAILURE_BUCKET_ID: X64_0x7E_dlkmd+19d12
BUCKET_ID: X64_0x7E_dlkmd+19d12
Followup: MachineOwner
---------
6: kd>
I am using the latest stable driver 6.3M1 and getting a number of BSODs caused by the dlkmd driver.
The windbg !analyze -v is pasted below:
6: kd> !analyze -v
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff880154f3d12, The address that the exception occurred at
Arg3: fffff8800f771d28, Exception Record Address
Arg4: fffff8800f771590, Context Record Address
Debugging Details:
------------------
PEB is paged out (Peb.Ldr = 000007ff`fffd3018). Type ".hh dbgerr001" for detail
s
PEB is paged out (Peb.Ldr = 000007ff`fffd3018). Type ".hh dbgerr001" for detail
s
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced me
mory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
dlkmd+19d12
fffff880`154f3d12 48833f00 cmp qword ptr [rdi],0
EXCEPTION_RECORD: fffff8800f771d28 -- (.exr 0xfffff8800f771d28)
ExceptionAddress: fffff880154f3d12 (dlkmd+0x0000000000019d12)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000000
Attempt to read from address 0000000000000000
CONTEXT: fffff8800f771590 -- (.cxr 0xfffff8800f771590)
rax=0000000000000000 rbx=fffffa800a3bf000 rcx=2e6d671177960000
rdx=00000000000000a0 rsi=fffffa800a3bf000 rdi=0000000000000000
rip=fffff880154f3d12 rsp=fffff8800f771f60 rbp=0000000000000001
r8=0000000000000065 r9=0000000000000000 r10=0000000000000000
r11=fffff8800f771f50 r12=0000000000000000 r13=fffff8801552e9a0
r14=fffff88015523110 r15=fffff8801552e8c0
iopl=0 nv up ei ng nz ac pe cy
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010293
dlkmd+0x19d12:
fffff880`154f3d12 48833f00 cmp qword ptr [rdi],0 ds:002b:00000000`000
00000=????????????????
Resetting default scope
DEFAULT_BUCKET_ID: NULL_DEREFERENCE
PROCESS_NAME: csrss.exe
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory
at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000000
READ_ADDRESS: 0000000000000000
FOLLOWUP_IP:
dlkmd+19d12
fffff880`154f3d12 48833f00 cmp qword ptr [rdi],0
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff880154eb77d to fffff880154f3d12
STACK_TEXT:
fffff880`0f771f60 fffff880`154eb77d : 00000000`00000000 fffff880`15523110 000000
00`00000003 00000000`00000002 : dlkmd+0x19d12
fffff880`0f771fe0 fffff880`074ac494 : fffffa80`0c0db000 fffff880`0f772198 fffff8
80`00000001 00000000`00000002 : dlkmd+0x1177d
fffff880`0f7720b0 fffff880`0751be2e : 00000000`00000002 fffff8a0`0b88c860 000000
00`00000000 fffffa80`0c044000 : dxgkrnl!DXGADAPTER::DdiCommitVidPn+0x50
fffff880`0f7720e0 fffff880`074a4282 : 00000000`00000001 00000000`00000000 fffffa
80`0a675c90 fffff8a0`00000001 : dxgkrnl!DmmCommitVidPn+0x7ba
fffff880`0f772220 fffff880`074d13d4 : fffff8a0`0afb0101 fffff8a0`0afb3900 fffff8
a0`0af7f801 fffff8a0`00000000 : dxgkrnl!DXGADAPTER::CommitVidPn+0x546
fffff880`0f772530 fffff880`074bb67b : fffff8a0`02d09190 fffff8a0`0afb3340 000000
00`00000000 fffff8a0`0afb3950 : dxgkrnl!CommitVidPn+0x68
fffff880`0f7725d0 fffff960`0064682d : fffff900`c1ea9020 00000000`00000001 fffff8
80`0f772cd0 00000000`00000001 : dxgkrnl!DxgkCddEnable+0x166b
fffff880`0f772920 fffff960`00645ce1 : ffffffff`00000004 ffffffff`fffd7476 000000
00`00000002 00000000`00000000 : cdd!CreateAndEnableDevice+0x1e1
fffff880`0f7729b0 fffff800`039646ca : 00000000`00000000 fffffa80`0a3a7b60 000000
00`00000080 fffffa80`0c0eeb30 : cdd!PresentWorkerThread+0x975
fffff880`0f772d40 fffff800`036a2126 : fffff800`03840e80 fffffa80`0a3a7b60 fffff8
00`0384ecc0 00000000`00000246 : nt!PspSystemThreadStartup+0x5a
fffff880`0f772d80 00000000`00000000 : fffff880`0f773000 fffff880`0f76d000 fffff8
80`0f7716b0 00000000`00000000 : nt!KiStartSystemThread+0x16
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: dlkmd+19d12
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dlkmd
IMAGE_NAME: dlkmd.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4fb31c0e
STACK_COMMAND: .cxr 0xfffff8800f771590 ; kb
FAILURE_BUCKET_ID: X64_0x7E_dlkmd+19d12
BUCKET_ID: X64_0x7E_dlkmd+19d12
Followup: MachineOwner
---------
6: kd>