Go Back   DisplayLink Forum > Alpha, Beta Software Testing Programs > Closed Alpha and Beta Programs > CLOSED: Windows 8 Software

 
 
Thread Tools Search this Thread Display Modes
Old 07-09-2012, 03:56 AM   #1
AnthonyB
Junior Member
 
Join Date: Jul 2012
Posts: 11
Default Stop 0x7e crash, Win8 RTM, v6.3 drivers and v7.0 beta 1 drivers

Hi,

My Lenovo W500 Thinkpad suffered a Stop 0x7e with the v6.3 DisplayLink drivers, running Win8 Release Preview (Build 8400).

Debug details below and DL Support Tool logs attached.

************************************************** *****************************
* *
* 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: fffff880015a4d12, The address that the exception occurred at
Arg3: fffff88002e49d68, Exception Record Address
Arg4: fffff88002e495a0, Context Record Address

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

Page 10924d not present in the dump file. Type ".hh dbgerr004" for details

MARKER_MODULE_NAME: IBM_ibmpmdrv

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`015a4d12 48833f00 cmp qword ptr [rdi],0

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

CONTEXT: fffff88002e495a0 -- (.cxr 0xfffff88002e495a0)
rax=0000000000000001 rbx=fffffa8006f1b000 rcx=6bb01ebc38dd0000
rdx=00000000000000a0 rsi=fffffa8006f1b000 rdi=0000000000000000
rip=fffff880015a4d12 rsp=fffff88002e49fa0 rbp=0000000000000001
r8=0000000000000065 r9=0000000000000000 r10=00000000fffffffd
r11=0000000000000000 r12=0000000000000000 r13=fffff880015df9a0
r14=fffff880015d4110 r15=fffff880015df8c0
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
dlkmd+0x19d12:
fffff880`015a4d12 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`015a4d12 48833f00 cmp qword ptr [rdi],0

BUGCHECK_STR: AV

LAST_CONTROL_TRANSFER: from fffff8800159c77d to fffff880015a4d12

STACK_TEXT:
fffff880`02e49fa0 fffff880`0159c77d : 00000000`00000000 fffff880`015d4110 00000000`00000003 fffff8a0`00000002 : dlkmd+0x19d12
fffff880`02e4a020 fffff880`0330e96d : fffffa80`06e49b00 fffff880`02e4a160 fffff8a0`00000001 fffffa80`00000002 : dlkmd+0x1177d
fffff880`02e4a0f0 fffff880`0330e64b : 00000000`00000001 fffff880`02e4a1e1 fffff8a0`09a966a0 00000000`00000001 : dxgkrnl!ADAPTER_DISPLAY:diCommitVidPn+0x4d
fffff880`02e4a120 fffff880`0330cc5a : fffff8a0`09a966a0 fffff8a0`16083350 fffffa80`08929f80 fffff803`00000001 : dxgkrnl!DmmCommitVidPn+0x3c3
fffff880`02e4a230 fffff880`0330be1f : fffff8a0`016dab80 fffff880`032e2c01 fffff8a0`09a966a0 fffff880`032e2c14 : dxgkrnl!ADAPTER_DISPLAY::CommitVidPn+0x262
fffff880`02e4a540 fffff880`032e21cc : fffff8a0`164c6000 fffff8a0`00f49480 fffff8a0`16083350 fffff8a0`016dab80 : dxgkrnl!CommitVidPn+0x93
fffff880`02e4a610 fffff960`00b35c57 : fffff901`000c8010 fffff901`000c9020 00000000`00000000 00000000`00000000 : dxgkrnl!DxgkCddEnable+0xb84
fffff880`02e4aa20 fffff960`00b34ec1 : ffffffff`fffd7477 fffff901`000c9560 fffff880`02e4abd0 00000000`00000007 : cdd!CreateAndEnableDevice+0x20b
fffff880`02e4aad0 fffff803`0cc3eec9 : fffff880`009c7180 fffffa80`0ad4d100 fffff901`000c9020 fffff880`009d2dc0 : cdd!PresentWorkerThread+0x8d9
fffff880`02e4ad10 fffff803`0cc41386 : fffff880`009c7180 fffffa80`0ad4d100 fffff880`009d2dc0 fffffa80`0a9db740 : nt!PspSystemThreadStartup+0x59
fffff880`02e4ad60 00000000`00000000 : fffff880`02e4b000 fffff880`02e45000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: dlkmd+19d12

MODULE_NAME: dlkmd

IMAGE_NAME: dlkmd.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4fb31c0e

STACK_COMMAND: .cxr 0xfffff88002e495a0 ; kb

FAILURE_BUCKET_ID: AV_dlkmd+19d12

BUCKET_ID: AV_dlkmd+19d12
Attached Files
File Type: zip ANTHOBENWIN8_20120709_124136.zip (440.5 KB, 1118 views)

Last edited by AnthonyB; 08-28-2012 at 12:27 AM. Reason: changing title to for accuracy
AnthonyB is offline  
Old 07-09-2012, 07:10 AM   #2
mlukaszek
Senior Member
 
mlukaszek's Avatar
 
Join Date: Feb 2010
Posts: 386
Default

Thanks for the report, this looks like something we've fixed already and the fix is queued for the upcoming release.
mlukaszek is offline  
Old 07-09-2012, 08:46 AM   #3
AnthonyB
Junior Member
 
Join Date: Jul 2012
Posts: 11
Default

Quote:
Originally Posted by mlukaszek View Post
Thanks for the report, this looks like something we've fixed already and the fix is queued for the upcoming release.
Great to hear!
Thanks for the confirmation
AnthonyB is offline  
Old 07-12-2012, 04:20 PM   #4
Wim
Senior Member
 
Join Date: Feb 2009
Posts: 1,561
Default

The release (v7.0 Beta 1) is now available from our website:

http://www.displaylink.com/support/downloads.php

Wim
Wim is offline  
Old 07-13-2012, 02:12 AM   #5
pcreehan
Junior Member
 
Join Date: Jun 2012
Posts: 4
Default new 7.0b drivers still don't work

The beta drivers still don't work for me - I used to have the black screen problem with 6.3 and that no longer happens, but now it says that my LT1421wide can't find any drivers. When I plug in the USB cable, it makes the "ding" but then nothing happens after that and the monitor device has the yellow exclamation point in Device Manager.

I have a Lenovo w510 running Win8 RP (8400).
pcreehan is offline  
Old 07-29-2012, 01:01 PM   #6
AnthonyB
Junior Member
 
Join Date: Jul 2012
Posts: 11
Default

Quote:
Originally Posted by Wim View Post
The release (v7.0 Beta 1) is now available from our website:

http://www.displaylink.com/support/downloads.php

Wim
Just a note that I'm running the 7.0 beta 1 drivers and again encountered Stop 0x7E crashes today. The only difference being that I wasn't connected to the DynaDock and the ATI driver appears to be the last module faulting, however right below it in the stack trace is dlkmd
AnthonyB is offline  
Old 07-30-2012, 07:27 AM   #7
mlukaszek
Senior Member
 
mlukaszek's Avatar
 
Join Date: Feb 2010
Posts: 386
Default

Can you post logs please? Thanks.
mlukaszek is offline  
Old 08-04-2012, 06:02 AM   #8
AnthonyB
Junior Member
 
Join Date: Jul 2012
Posts: 11
Default

Quote:
Originally Posted by mlukaszek View Post
Can you post logs please? Thanks.
Logs attached (note: I don't have the Display Dock connected as I'm not in my office. Then again, these bluescreens are occurring when I'm not connected to the Display Dock)

Some feedback I've had from AMD who have analysed the memory dump that may help - "It appears the DisplayLink driver is corrupting the DXGKARG_SETVIDPN parameter passed to our driver."

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: fffff8800494e165, The address that the exception occurred at
Arg3: fffff8800a259b18, Exception Record Address
Arg4: fffff8800a259350, Context Record Address

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


MARKER_MODULE_NAME: IBM_ibmpmdrv

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

FAULTING_IP:
atikmdag!KDBuffer::TilingMode+5
fffff880`0494e165 8b81a8000000 mov eax,dword ptr [rcx+0A8h]

EXCEPTION_RECORD: fffff8800a259b18 -- (.exr 0xfffff8800a259b18)
ExceptionAddress: fffff8800494e165 (atikmdag!KDBuffer::TilingMode+0x0000000000000005)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 00000000000000a8
Attempt to read from address 00000000000000a8

CONTEXT: fffff8800a259350 -- (.cxr 0xfffff8800a259350)
rax=0000000000000000 rbx=fffffa800a656020 rcx=0000000000000000
rdx=0000000000000000 rsi=00000000c000000d rdi=fffffa8006e1d040
rip=fffff8800494e165 rsp=fffff8800a259d50 rbp=fffff8800a259d50
r8=fffff88004a7ced0 r9=fffff880015daf00 r10=0000000000000000
r11=fffff88004a7ced0 r12=fffff8a000737020 r13=fffff8800a259e80
r14=fffff8800a259eb0 r15=fffffa8006e1c700
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
atikmdag!KDBuffer::TilingMode+0x5:
fffff880`0494e165 8b81a8000000 mov eax,dword ptr [rcx+0A8h] ds:002b:00000000`000000a8=????????
Resetting default scope

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: 00000000000000a8

READ_ADDRESS: 00000000000000a8

FOLLOWUP_IP:
atikmdag!KDBuffer::TilingMode+5
fffff880`0494e165 8b81a8000000 mov eax,dword ptr [rcx+0A8h]

BUGCHECK_STR: AV

DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER: from fffff88004945cd1 to fffff8800494e165

STACK_TEXT:
fffff880`0a259d50 fffff880`04945cd1 : fffffa80`0a656020 fffffa80`06e1c700 00000000`00000006 00000000`00000001 : atikmdag!KDBuffer::TilingMode+0x5
fffff880`0a259d60 fffff880`0470790d : fffffa80`06e1c700 fffffa80`06e1c700 fffff880`0a259eb0 fffff880`0a259eb0 : atikmdag!KDVidAdapter::IsTilingLinear+0x61
fffff880`0a259d90 fffff880`04706b10 : fffffa80`06e1c700 fffff880`0a259eb0 fffff880`0a259f70 00000000`00000000 : atikmdag!DISPATCHER:MMCommitVidPn+0xcd
fffff880`0a259e00 fffff880`0470ad9e : fffffa80`06e1c700 00000000`00000001 fffff880`0a259eb0 fffff880`0a259eb0 : atikmdag!DISPATCHER::CommitVidPn+0x120
fffff880`0a259e30 fffff880`035a789d : fffff880`00000700 fffffa80`06eb7740 fffffa80`06e19040 00000000`000007ff : atikmdag!Dispatch_CommitVidPn+0xae
fffff880`0a259e80 fffff880`0158e2e5 : fffffa80`06f60000 fffffa80`06f60000 fffff880`00000798 00000000`00000190 : atikmpag!ProxyCommitVidPn+0x2e9
fffff880`0a259f40 fffff880`015854d0 : fffffa80`06e1c700 fffffa80`06f622d4 fffffa80`06f622d4 00000000`00000002 : dlkmd+0x1a2e5
fffff880`0a259fc0 fffff880`015859df : fffffa80`06f60000 00000000`00000000 00000000`ffffffff fffff8a0`16622740 : dlkmd+0x114d0
fffff880`0a25a020 fffff880`02cfa96d : fffffa80`06e1c700 fffff880`0a25a160 fffff8a0`00000000 fffffa80`00000002 : dlkmd+0x119df
fffff880`0a25a0f0 fffff880`02cfa64b : 00000000`00000000 fffff880`0a25a1e1 fffff8a0`0e885b50 fffff880`02cbc0a0 : dxgkrnl!ADAPTER_DISPLAY:diCommitVidPn+0x4d
fffff880`0a25a120 fffff880`02cf8c5a : fffff8a0`0e885b50 fffff8a0`15def990 fffffa80`06e47b80 fffff803`00000000 : dxgkrnl!DmmCommitVidPn+0x3c3
fffff880`0a25a230 fffff880`02cf7e1f : fffff8a0`00b98cf0 fffff880`02ccec01 fffff8a0`0e885b50 fffff880`02ccec14 : dxgkrnl!ADAPTER_DISPLAY::CommitVidPn+0x262
fffff880`0a25a540 fffff880`02cce1cc : fffff8a0`1106f000 fffff8a0`0574ce70 fffff8a0`15def990 fffff8a0`00b98cf0 : dxgkrnl!CommitVidPn+0x93
fffff880`0a25a610 fffff960`00950c57 : fffff901`04647270 fffff901`04930020 00000000`00000000 fffff880`009c7180 : dxgkrnl!DxgkCddEnable+0xb84
fffff880`0a25aa20 fffff960`0094fec1 : ffffffff`fffd74f6 fffff901`04930560 fffff880`0a25abd0 00000000`00000007 : cdd!CreateAndEnableDevice+0x20b
fffff880`0a25aad0 fffff803`62247ec9 : 00000000`00000100 fffffa80`0ee9e900 fffff901`04930020 fffffa80`0e56b900 : cdd!PresentWorkerThread+0x8d9
fffff880`0a25ad10 fffff803`6224a386 : fffff880`009c7180 fffffa80`0ee9e900 fffffa80`0e56b900 fffffa80`0edcf940 : nt!PspSystemThreadStartup+0x59
fffff880`0a25ad60 00000000`00000000 : fffff880`0a25b000 fffff880`0a255000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: atikmdag!KDBuffer::TilingMode+5

MODULE_NAME: atikmdag

IMAGE_NAME: atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4f9aec32

STACK_COMMAND: .cxr 0xfffff8800a259350 ; kb

BUCKET_ID_FUNC_OFFSET: 5

FAILURE_BUCKET_ID: AV_atikmdag!KDBuffer::TilingMode

BUCKET_ID: AV_atikmdag!KDBuffer::TilingMode
Attached Files
File Type: zip ANTHOBENWIN8_20120804_145649.zip (415.4 KB, 986 views)
AnthonyB is offline  
Old 08-28-2012, 12:26 AM   #9
AnthonyB
Junior Member
 
Join Date: Jul 2012
Posts: 11
Default

Is there any ETA on an updated driver to fix this issue?

I experience the exact same crash, almost always when I un-sleep my PC, about once per week.
AnthonyB is offline  
Old 08-30-2012, 09:28 AM   #10
mlukaszek
Senior Member
 
mlukaszek's Avatar
 
Join Date: Feb 2010
Posts: 386
Default

Quote:
Originally Posted by AnthonyB View Post
Is there any ETA on an updated driver to fix this issue?

I experience the exact same crash, almost always when I un-sleep my PC, about once per week.
Does the same problem reproduce with Win8 RTM and DisplayLink's 7.0 beta? Thanks.
mlukaszek is offline  
 

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 06:00 PM.


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