05-28-2012, 09:53 PM | #1 |
Junior Member
Join Date: May 2012
Posts: 9
|
BSOD in Windows 7
Hi there,
I have two Plugable DisplayLink devices attached to my system. One is based on DL-195 and the other is based on DL-3000. The system functioned perfectly fine until I bought and connected the DL-3000 device on my USB3 bus. Now, whenever the system goes into display powersave I either get a BSOD or the system refuses to wake the displays. Other times, the system goes into display powersave and the directly connected monitors turn off, however the DisplayLink monitors stay powered on with the desktop visible, but the system is no longer responding. I have tried updating all drivers to the latest available. I have a Renesas USB3 controller on the motherboard, and the graphics display is an ATI 5870. I have attached debug output to this post. The BSODs alternate between: 0x3b (SYSTEM_SERVICE_EXCEPTION) 0x7e (SYSTEM_THREAD_EXCEPTION_NOT_HANDLED) Both are centred around the file atikmdag.sys |
05-28-2012, 09:57 PM | #2 |
Junior Member
Join Date: May 2012
Posts: 9
|
Additional info
fffff880`04c38000 fffff880`057eb000 atikmdag (no symbols)
Loaded symbol image file: atikmdag.sys Image path: atikmdag.sys Image name: atikmdag.sys Timestamp: Wed Apr 18 18:50:42 2012 (4F8F6F72) CheckSum: 00B68CB0 ImageSize: 00BB3000 File version: 8.1.1.1248 Product version: 8.1.1.1248 File flags: 8 (Mask 3F) Private File OS: 40004 NT Win32 File type: 3.4 Driver File date: 00000000.00000000 Translations: 0409.04b0 CompanyName: Advanced Micro Devices, Inc. ProductName: ATI Radeon Family InternalName: atikmdag.sys OriginalFilename: atikmdag.sys ProductVersion: 8.01.01.1248 FileVersion: 8.01.01.1248 FileDescription: ATI Radeon Kernel Mode Driver LegalCopyright: Copyright (C) 1998-2011 Advanced Micro Devices, Inc. |
05-29-2012, 12:45 PM | #3 |
Senior Member
Join Date: Feb 2009
Posts: 1,561
|
Hi
I assume you updated the DisplayLink software to v6.3 at the same time as adding the DL-3000 adapter? I've raised a bug for this so our engineers can analyse the blue screen information. Thanks Wim |
05-30-2012, 08:40 AM | #4 |
Junior Member
Join Date: May 2012
Posts: 9
|
Reinstalled Windows
Hi there,
I formatted my drive and completely reinstalled Windows. I also installed all necessary drivers, latest versions, including DisplayLink Core v6.3. I am still getting BSODs: 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: fffff880031b1d12, The address that the exception occurred at Arg3: fffff88002dd4e98, Exception Record Address Arg4: fffff88002dd46f0, Context Record Address STACK_TEXT: fffff880`02dd50d0 fffff880`031a977d : 00000000`00000000 fffff880`031e1110 00000000`0000001e 00000000`00000002 : dlkmd+0x19d12 fffff880`02dd5150 fffff880`046af5a8 : fffffa80`0a778600 fffff880`02dd52a0 fffff880`02dd52a0 fffffa80`00000002 : dlkmd+0x1177d fffff880`02dd5220 fffff880`0471f1de : fffff8a0`03181e00 fffff8a0`03181ec0 00000000`00000000 fffffa80`0b9ec000 : dxgkrnl!DXGADAPTER:diCommitVidPn+0x50 fffff880`02dd5250 fffff880`046a7282 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff8a0`00000000 : dxgkrnl!DmmCommitVidPn+0x926 fffff880`02dd5390 fffff880`046bf2a1 : fffff8a0`03131201 fffff8a0`01399800 fffff8a0`01f6b400 fffff8a0`080b5100 : dxgkrnl!DXGADAPTER::CommitVidPn+0x546 fffff880`02dd56a0 fffff960`00765d8d : ffffffff`fffd74f6 ffffffff`fffd74f6 00000000`00000000 00000000`00000006 : dxgkrnl!DxgkCddDisable+0x609 fffff880`02dd5870 fffff800`03165e6a : fffffa80`00000003 fffffa80`0bc34060 00000000`00000080 fffffa80`0ba17b30 : cdd!PresentWorkerThread+0xa21 fffff880`02dd5c00 fffff800`02ebff06 : fffff880`033d7180 fffffa80`0bc34060 fffff880`033e1fc0 00000000`00000001 : nt!PspSystemThreadStartup+0x5a fffff880`02dd5c40 00000000`00000000 : fffff880`02dd6000 fffff880`02dd0000 fffff880`02dd4fe0 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 0xfffff88002dd46f0 ; kb FAILURE_BUCKET_ID: X64_0x7E_dlkmd+19d12 BUCKET_ID: X64_0x7E_dlkmd+19d12 start end module name fffff880`03198000 fffff880`03200000 dlkmd (no symbols) Loaded symbol image file: dlkmd.sys Image path: \SystemRoot\system32\drivers\dlkmd.sys Image name: dlkmd.sys Timestamp: Tue May 15 20:16:30 2012 (4FB31C0E) CheckSum: 0005C302 ImageSize: 00068000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4 I have the MEMORY.DMP file located at http://www.aloria.net/transfer/MEMORY.zip |
05-30-2012, 04:48 PM | #5 |
Junior Member
Join Date: May 2012
Posts: 9
|
Additional Regression testing
I have additional information for you. I attempted to roll the drivers back to previous versions. v6.2 still produces BSOD, however the faulting driver is now back to atikmdag.sys:
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: fffff88004e9b165, The address that the exception occurred at Arg3: fffff88002dd9cc8, Exception Record Address Arg4: fffff88002dd9520, 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: atikmdag+252165 fffff880`04e9b165 8b81a8000000 mov eax,dword ptr [rcx+0A8h] STACK_TEXT: fffff880`02dd9f00 fffff880`04e92cd1 : fffffa80`0ba93020 fffffa80`076dbbc0 00000000`00000006 fffff880`04fcee50 : atikmdag+0x252165 fffff880`02dd9f10 fffff880`04c5490d : fffffa80`076dbbc0 fffffa80`076dbbc0 fffff880`02dda060 fffff880`02dda060 : atikmdag+0x249cd1 fffff880`02dd9f40 fffff880`04c53b10 : fffffa80`076dbbc0 fffff880`02dda060 fffff880`02dda110 00000000`00000000 : atikmdag+0xb90d fffff880`02dd9fb0 fffff880`04c57d9e : fffffa80`076dbbc0 00000000`00000001 fffff880`02dda060 fffff880`02dda060 : atikmdag+0xab10 fffff880`02dd9fe0 fffff880`0430389d : fffff880`02dda100 fffffa80`066e04c0 fffffa80`0a63d040 00000000`00000000 : atikmdag+0xed9e fffff880`02dda030 fffff880`04370ab4 : 00000000`401e0300 fffffa80`078c8000 00000000`4e506456 fffff880`00000798 : atikmpag+0x989d fffff880`02dda0f0 fffff880`04369966 : 00000000`00d1d104 00000000`00000000 00000000`00d1d100 fffff880`02dda2a0 : dlkmd+0x17ab4 fffff880`02dda150 fffff880`044ba5a8 : fffffa80`076dbbc0 fffff880`02dda2a0 fffff880`02dda2a0 fffffa80`00000002 : dlkmd+0x10966 fffff880`02dda220 fffff880`0452a1de : fffff8a0`025f8900 fffff8a0`025f8990 00000000`00000000 fffffa80`0bb93000 : dxgkrnl!DXGADAPTER::DdiCommitVidPn+0x50 fffff880`02dda250 fffff880`044b2282 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff8a0`00000000 : dxgkrnl!DmmCommitVidPn+0x926 fffff880`02dda390 fffff880`044ca2a1 : fffff8a0`0ebcac01 fffff8a0`00f41100 fffff8a0`017c2500 fffff8a0`03e8dc00 : dxgkrnl!DXGADAPTER::CommitVidPn+0x546 fffff880`02dda6a0 fffff960`00665d8d : ffffffff`00000004 ffffffff`fffd74f6 00000000`00000002 00000000`00000006 : dxgkrnl!DxgkCddDisable+0x609 fffff880`02dda870 fffff800`03169e6a : 00000000`00000000 fffffa80`0a40a400 00000000`00000080 fffffa80`0bbc8b30 : cdd!PresentWorkerThread+0xa21 fffff880`02ddac00 fffff800`02ec3f06 : fffff800`03045e80 fffffa80`0a40a400 fffff800`03053cc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`02ddac40 00000000`00000000 : fffff880`02ddb000 fffff880`02dd5000 fffff880`02dd9fe0 00000000`00000000 : nt!KiStartSystemThread+0x16 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: atikmdag+252165 FOLLOWUP_NAME: MachineOwner MODULE_NAME: atikmdag IMAGE_NAME: atikmdag.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4f8f6f72 STACK_COMMAND: .cxr 0xfffff88002dd9520 ; kb FAILURE_BUCKET_ID: X64_0x7E_atikmdag+252165 BUCKET_ID: X64_0x7E_atikmdag+252165 Downgrading to driver v6.1 has stopped BSOD from occurring, both in power save and when you tell the system to logoff. v6.2 and v6.3 BSODs occur during power save AND when you tell the system to logoff. Last edited by Garion; 05-30-2012 at 04:50 PM. |
06-07-2012, 12:44 PM | #6 |
Senior Member
Join Date: Feb 2009
Posts: 1,561
|
Thanks for the dmp files. We are aware of this new BSOD on v6.3 and intend to fix it in the next maintenance release.
Wim |
07-06-2012, 04:42 PM | #7 |
Junior Member
Join Date: Jul 2012
Posts: 1
|
I'm experiencing the same issue, blue screen in dlkmd.sys with a DisplayLink USB adapter and S/W version 6.3.38103.0.
Please have the corrected version available soon. Thanks in advance. horst ginseng |
07-08-2012, 07:00 PM | #8 |
Junior Member
Join Date: Jul 2012
Posts: 2
|
I have similar BSOD, only that my card is NVIDIA
|
07-12-2012, 04:58 PM | #9 |
Senior Member
Join Date: Feb 2009
Posts: 1,561
|
This BSOD should now be fixed in the v7.0 Beta available on our website here:
http://www.displaylink.com/support/downloads.php Wim |
07-13-2012, 05:34 AM | #10 |
Junior Member
Join Date: May 2012
Posts: 9
|
I have installed the beta, and we'll see how this works out.
|
Thread Tools | Search this Thread |
Display Modes | |
|
|