Go Back   DisplayLink Forum > DisplayLink Graphics Technology > Windows Software

 
 
Thread Tools Search this Thread Display Modes
Prev Previous Post   Next Post Next
Old 05-30-2012, 07:40 AM   #4
Garion
Junior Member
 
Join Date: May 2012
Posts: 9
Default 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
Attached Files
File Type: zip DRASNIA_20120530_002325.zip (722.9 KB, 0 views)
Garion is offline   Reply With Quote
 

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:09 AM.


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