Go Back   DisplayLink Forum > DisplayLink Graphics Technology > Windows Software

Reply
 
Thread Tools Search this Thread Display Modes
Old 11-27-2013, 07:46 PM   #1
snowkoan
Junior Member
 
Join Date: Nov 2013
Posts: 3
Post dlkmd.sys BSOD - PAGE_FAULT_IN_NONPAGED_AREA

Hi,

I have a USB monitor and have installed the DisplayLink drivers. I am not currently using the monitor, but the DisplayLink driver still managed to bring down my system. For the last couple of days, I've had weird display artifacts on my screen. Today, during one of those artifacts, the system went down.

Can a DisplayLink dev take a look at this please?

I'm uploading the crash dump here (I'll leave it up for a couple of weeks or so): http://ottawagamelan.org/aa/MEMORY.7z

Here's the basic info. It appears that I have the latest driver installed (7.4.51572.0). I'm running on Windows 7 x64 SP1.

Thanks,
Alnoor

************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff880520e46f8, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff88004f636a5, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000005, (reserved)

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


WRITE_ADDRESS: fffff880520e46f8

FAULTING_IP:
dlkmd+66a5
fffff880`04f636a5 87748168 xchg esi,dword ptr [rcx+rax*4+68h]

MM_INTERNAL_CODE: 5

IMAGE_NAME: dlkmd.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 52528c3b

MODULE_NAME: dlkmd

FAULTING_MODULE: fffff88004f5d000 dlkmd

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: System

CURRENT_IRQL: 0

TRAP_FRAME: fffff88003726a30 -- (.trap 0xfffff88003726a30)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000134480c0 rbx=0000000000000000 rcx=fffff88004fc4390
rdx=00000000000000ba rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004f636a5 rsp=fffff88003726bc0 rbp=0000000000000080
r8=0000000000000065 r9=0000000000000000 r10=0000000000000000
r11=fffff88003726bb0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
dlkmd+0x66a5:
fffff880`04f636a5 87748168 xchg esi,dword ptr [rcx+rax*4+68h] ds:0010:fffff880`520e46f8=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff800033455b3 to fffff800032c8bc0

STACK_TEXT:
fffff880`037268c8 fffff800`033455b3 : 00000000`00000050 fffff880`520e46f8 00000000`00000001 fffff880`03726a30 : nt!KeBugCheckEx
fffff880`037268d0 fffff800`032c6cee : 00000000`00000001 fffff880`520e46f8 00000001`00000000 fffffa80`0f004000 : nt! ?? ::FNODOBFM::`string'+0x43801
fffff880`03726a30 fffff880`04f636a5 : fffffa80`0ea93000 fffffa80`0f004000 00000000`00000080 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`03726bc0 fffff800`035652ea : fffffa80`0d3e7470 fffffa80`0c72aae0 fffff880`03726c70 fffffa80`0d3e7470 : dlkmd+0x66a5
fffff880`03726c00 fffff800`032b98e6 : fffff880`031d7180 fffffa80`0d3e7470 fffff880`031e1fc0 00000000`00000001 : nt!PspSystemThreadStartup+0x5a
fffff880`03726c40 00000000`00000000 : fffff880`03727000 fffff880`03721000 fffff880`03726910 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
dlkmd+66a5
fffff880`04f636a5 87748168 xchg esi,dword ptr [rcx+rax*4+68h]

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: dlkmd+66a5

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: X64_0x50_dlkmd+66a5

BUCKET_ID: X64_0x50_dlkmd+66a5

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

0: kd> lm vm *dl*
start end module name
fffff880`01495000 fffff880`0149d000 dlkmdldr (deferred)
Image path: \SystemRoot\system32\drivers\dlkmdldr.sys
Image name: dlkmdldr.sys
Timestamp: Mon Oct 07 06:25:43 2013 (52528C27)
CheckSum: 00012FD3
ImageSize: 00008000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

fffff880`04f5d000 fffff880`04fe3000 dlkmd (no symbols)
Loaded symbol image file: dlkmd.sys
Image path: \SystemRoot\system32\drivers\dlkmd.sys
Image name: dlkmd.sys
Timestamp: Mon Oct 07 06:26:03 2013 (52528C3B)
CheckSum: 00068276
ImageSize: 00086000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
snowkoan is offline   Reply With Quote
Old 11-28-2013, 10:07 AM   #2
JamesH
Senior Member
 
JamesH's Avatar
 
Join Date: Jan 2012
Posts: 1,500
Default

Hi,

Thanks for the information.

Can you attach the files generated by this tool when you next see this issue?
http://www.displaylink.com/support/ticket.php?id=269

Thanks,
James
JamesH is offline   Reply With Quote
Old 11-28-2013, 12:53 PM   #3
snowkoan
Junior Member
 
Join Date: Nov 2013
Posts: 3
Default

Hi,

I'm attaching the requested diagnostics, password protected. I will send you a private message with the password.

My system is basically the same right now as it was after the BSOD yesterday. Again, I don't have a DisplayLink device connected but I do see the dlkmd.sys driver running.

Thanks for your help,
Alnoor
Attached Files
File Type: zip 20131128_083217.zip (420.7 KB, 1 views)
snowkoan is offline   Reply With Quote
Old 11-28-2013, 03:13 PM   #4
JamesH
Senior Member
 
JamesH's Avatar
 
Join Date: Jan 2012
Posts: 1,500
Default

Hi,

Thanks for the information.

Can you get an image / video of the artefacts?

Does this happen randomly or after a specific event?

Thanks,
James
JamesH is offline   Reply With Quote
Old 11-29-2013, 05:35 PM   #5
snowkoan
Junior Member
 
Join Date: Nov 2013
Posts: 3
Default

Hi James,

I see mostly static artifacts, generally on my second monitor. It is connected to the VGA port on my laptop. The primary monitor is connected via HDMI. I can't really pin down an event. I'll often being doing tasks in Visio or Powerpoint (scrolling, dragging etc..) when the artifacts appear. If I move the mouse around, they generally disappear after a few seconds.

I'm attaching an example pic. Often the artifact is just a portion of the screen.

It is possible that the artifacts are completely unrelated to the BSOD. Does this seem like something the DisplayLink drivers could be responsible for?

Thanks,
Alnoor
Attached Images
File Type: jpg 2013-11-29_13-28-18_941_Ottawa.jpg (99.1 KB, 8 views)
snowkoan is offline   Reply With Quote
Reply

Tags
bsod, dklmd.sys, driver

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT. The time now is 04:56 AM.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2019, vBulletin Solutions, Inc.