Blue screen in dlkmd.sys (7E), crash / BSOD

lesha · 06-01-2012, 07:03 PM

I tried using the "Ask Question" tool, but that failed repeatedly (a blank page loaded after my submission, suggesting that the PHP had a fatal error). Can you file a bug for this too?

I have a SIIG JU-DV0112-S1 on a Windows 7 amd64 Acer Aspire One 722. I am using DisplayLink Core Software 6.3.38355.0.

This is pretty similar, but not quite the same as this crash report:

http://www.displaylink.org/forum/showthread.php?p=6682

In my case, it happens quite repeatably, and always when I'm away from the computer -- i.e. probably around the activation of various power saving settings.

I tried plugging in the SIIG device both directly into my laptop, and also through a USB hub. It crashes regardless.

Here is what I could get out of WinDbg:

Code:

Microsoft (R) Windows Debugger Version 6.2.8400.0 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

WARNING: Whitespace at start of path element
Symbol search path is: srv*c:\cache*http://msdl.microsoft.com/download/symbols;

Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Machine Name:
Kernel base = 0xfffff800`02c63000 PsLoadedModuleList = 0xfffff800`02ea7670
Debug session time: Wed May 30 13:25:53.096 2012 (UTC - 7:00)
System Uptime: 0 days 1:20:55.920
Loading Kernel Symbols
...............................................................
................................................................
.......................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000007ff`fffd9018).  Type ".hh dbgerr001" for details
Loading unloaded module list
...................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7E, {ffffffffc0000005, fffff88005354d12, fffff88003552d28, fffff88003552580}

*** ERROR: Module load completed but symbols could not be loaded for dlkmd.sys
Probably caused by : dlkmd.sys ( dlkmd+19d12 )

Followup: MachineOwner
---------

1: 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: fffff88005354d12, The address that the exception occurred at
Arg3: fffff88003552d28, Exception Record Address
Arg4: fffff88003552580, Context Record Address

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
dlkmd+19d12
fffff880`05354d12 48833f00        cmp     qword ptr [rdi],0

EXCEPTION_RECORD:  fffff88003552d28 -- (.exr 0xfffff88003552d28)
ExceptionAddress: fffff88005354d12 (dlkmd+0x0000000000019d12)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000000
Attempt to read from address 0000000000000000

CONTEXT:  fffff88003552580 -- (.cxr 0xfffff88003552580)
rax=0000000000000000 rbx=fffffa8004400000 rcx=19d20e9a7a7c0000
rdx=00000000000000a0 rsi=fffffa8004400000 rdi=0000000000000000
rip=fffff88005354d12 rsp=fffff88003552f60 rbp=0000000000000001
 r8=0000000000000065  r9=0000000000000000 r10=0000000000000000
r11=fffff88003552f50 r12=0000000000000000 r13=fffff8800538f9a0
r14=fffff88005384110 r15=fffff8800538f8c0
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`05354d12 48833f00        cmp     qword ptr [rdi],0 ds:002b:00000000`00000000=????????????????
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`05354d12 48833f00        cmp     qword ptr [rdi],0

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff8800534c77d to fffff88005354d12

STACK_TEXT:  
fffff880`03552f60 fffff880`0534c77d : 00000000`00000000 fffff880`05384110 00000000`00000007 00000000`00000002 : dlkmd+0x19d12
fffff880`03552fe0 fffff880`02ccd5a8 : fffffa80`047e6840 fffff880`03553198 fffff880`00000002 00000000`00000002 : dlkmd+0x1177d
fffff880`035530b0 fffff880`02d3d072 : 00000000`00000002 fffff8a0`09974010 00000000`00000000 fffffa80`04453000 : dxgkrnl!DXGADAPTER::DdiCommitVidPn+0x50
fffff880`035530e0 fffff880`02cc5282 : 00000000`00000002 00000000`00000000 fffffa80`05eef2c0 fffff8a0`00000002 : dxgkrnl!DmmCommitVidPn+0x7ba
fffff880`03553220 fffff880`02cf24dc : fffff8a0`07dc0101 fffff8a0`07dddf00 fffff8a0`00805001 fffff8a0`00000000 : dxgkrnl!DXGADAPTER::CommitVidPn+0x546
fffff880`03553530 fffff880`02cdc747 : fffff8a0`026cd040 fffff8a0`07d6c090 00000000`00000000 fffff8a0`07dddfc0 : dxgkrnl!CommitVidPn+0x68
fffff880`035535d0 fffff960`0064682d : fffff900`c07e7020 00000000`00000001 fffff880`03553cd0 00000000`00000002 : dxgkrnl!DxgkCddEnable+0x166b
fffff880`03553920 fffff960`00645ce1 : ffffffff`00000004 ffffffff`fffd74f6 00000000`00000002 00000000`00000000 : cdd!CreateAndEnableDevice+0x1e1
fffff880`035539b0 fffff800`02f78e6a : fffffa80`05b99c10 fffffa80`05bde910 00000000`00000080 fffffa80`051d5060 : cdd!PresentWorkerThread+0x975
fffff880`03553d40 fffff800`02cd2f06 : fffff880`009e8180 fffffa80`05bde910 fffffa80`05b4a760 00000000`16c40000 : nt!PspSystemThreadStartup+0x5a
fffff880`03553d80 00000000`00000000 : fffff880`03554000 fffff880`0354e000 fffff880`035526a0 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 0xfffff88003552580 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_dlkmd+19d12

BUCKET_ID:  X64_0x7E_dlkmd+19d12

Followup: MachineOwner
---------

mlukaszek · 06-06-2012, 11:15 AM

Quote:

Originally Posted by lesha

Here is what I could get out of WinDbg:

Hi, do you think you could archive the memory dump and upload it somewhere so we could inspect it? From the initial look it looks like an issue we have fixed already, and the fix will appear in next maintenance release.

Thanks,
Michal

scottbilas · 06-08-2012, 03:28 PM

I saw the same issue myself right after I upgraded to 6.3M0. BSOD's every 15 minutes, clearly an issue with power saving. Disabling power saving eliminates the blue screens.

I can't go back to the previous driver version I was on because I was getting crashes in our WPF/DirectX app while debugging in Visual Studio. Read somewhere that 6.3 fixed that. (I'd prefer no power saving over crashes in our app while debugging.)

Mlukaszek I PM'd you with a question about how I can get the dump files to you.

scottbilas · 06-08-2012, 05:06 PM

I am also getting this every time I log out. Right before it does a switch to the login screen, kaboom. Win7 x64.

psignoret · 06-14-2012, 02:27 AM

Quote:

Originally Posted by mlukaszek

From the initial look it looks like an issue we have fixed already, and the fix will appear in next maintenance release.

Do you know when this will be? I have the same problem. As soon as I step away from the computer, when I come back it will have BSOD'd. For now, I'm disabling power management options to try to avoid it, but in the long run, this is not a feasible option.

Thanks,
Philippe

lesha · 06-16-2012, 05:26 PM

For what it's worth, I've had 2 crash-free weeks after downgrading to 6.1, as suggested on the other thread. 6.2 still crashed on power save.

Michal, I'm also looking forward to the maintenance release! Please update the thread so that we can test your fix. I'll be PMing you about the crash dump.

06-08-2012, 03:28 PM	#3
scottbilas Junior Member Join Date: Dec 2011 Posts: 2	I saw the same issue myself right after I upgraded to 6.3M0. BSOD's every 15 minutes, clearly an issue with power saving. Disabling power saving eliminates the blue screens. I can't go back to the previous driver version I was on because I was getting crashes in our WPF/DirectX app while debugging in Visual Studio. Read somewhere that 6.3 fixed that. (I'd prefer no power saving over crashes in our app while debugging.) Mlukaszek I PM'd you with a question about how I can get the dump files to you.

06-08-2012, 05:06 PM	#4
scottbilas Junior Member Join Date: Dec 2011 Posts: 2	I am also getting this every time I log out. Right before it does a switch to the login screen, kaboom. Win7 x64.

06-16-2012, 05:26 PM	#6
lesha Junior Member Join Date: Jun 2012 Posts: 2	For what it's worth, I've had 2 crash-free weeks after downgrading to 6.1, as suggested on the other thread. 6.2 still crashed on power save. Michal, I'm also looking forward to the maintenance release! Please update the thread so that we can test your fix. I'll be PMing you about the crash dump.