Windows 7 Forums


Windows 7: BSOD - Believe since GP push of screensaver/idle lockout - 1000007e

28 Nov 2012   #1

Virginia
 
 
BSOD - Believe since GP push of screensaver/idle lockout - 1000007e

Hey there,

Pushed a screensaver/idle lockout setting via GP to some users, and ever since, a few have been crashing, I think. Not sure its the screensaver. Mine crashed today, attached .dmp logs.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033

Additional information about the problem:
BCCode: 1000007e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF8800555CD12
BCP3: FFFFF8800DE94BE8
BCP4: FFFFF8800DE94440
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\112812-15054-01.dmp
C:\Users\jdoerflinger\AppData\Local\Temp\WER-73039-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\windows\system32\en-US\erofflps.txt


Any idea? Thanks!
Jim

My System SpecsSystem Spec

28 Nov 2012   #2

Virginia
 
 

Did I submit the right data? This forum moves fast! Thread on page 3 in 6 hours.

Jim
My System SpecsSystem Spec
28 Nov 2012   #3

Windows 7 Home Premium 64bit SP1
 
 

Welcome

Both your recent BSOD-s were caused by WDDM KMD Loader - DisplayLink Core Software

Recommend uninstalling this software and its drivers and see if the problem persists

Use the free version of Revo Uninstaller to uninstall. Uninstall using Advanced Mode

Code:
....
*** WARNING: Unable to verify timestamp for dlkmd.sys
*** ERROR: Module load completed but symbols could not be loaded for dlkmd.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff8800555cd12, fffff8800de94be8, fffff8800de94440}

Probably caused by : dlkmd.sys ( dlkmd+19d12 )

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

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8800555cd12, The address that the exception occurred at
Arg3: fffff8800de94be8, Exception Record Address
Arg4: fffff8800de94440, 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`0555cd12 48833f00        cmp     qword ptr [rdi],0

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

CONTEXT:  fffff8800de94440 -- (.cxr 0xfffff8800de94440)
rax=0000000000000000 rbx=fffffa800a0a4000 rcx=1e7247a8f6980000
rdx=00000000000000a0 rsi=fffffa800a0a4000 rdi=0000000000000000
rip=fffff8800555cd12 rsp=fffff8800de94e20 rbp=0000000000000001
 r8=0000000000000065  r9=0000000000000000 r10=0000000000000000
r11=fffff8800de94e10 r12=0000000000000000 r13=fffff880055979a0
r14=fffff8800558c110 r15=fffff880055978c0
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`0555cd12 48833f00        cmp     qword ptr [rdi],0 ds:002b:00000000`00000000=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

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: GetPointerFromAddress: unable to read from fffff800032c4100
GetUlongFromAddress: unable to read from fffff800032c41c0
 0000000000000000 Nonpaged pool

FOLLOWUP_IP: 
dlkmd+19d12
fffff880`0555cd12 48833f00        cmp     qword ptr [rdi],0

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffffa800a0a4000 to fffff8800555cd12

STACK_TEXT:  
fffff880`0de94e20 fffffa80`0a0a4000 : fffffa80`0a0a4000 00000000`00000001 fffffa80`0a0a4000 00000000`401e034c : dlkmd+0x19d12
fffff880`0de94e28 fffffa80`0a0a4000 : 00000000`00000001 fffffa80`0a0a4000 00000000`401e034c 00000000`00d1d100 : 0xfffffa80`0a0a4000
fffff880`0de94e30 00000000`00000001 : fffffa80`0a0a4000 00000000`401e034c 00000000`00d1d100 00000001`00000001 : 0xfffffa80`0a0a4000
fffff880`0de94e38 fffffa80`0a0a4000 : 00000000`401e034c 00000000`00d1d100 00000001`00000001 00000000`00000000 : 0x1
fffff880`0de94e40 00000000`401e034c : 00000000`00d1d100 00000001`00000001 00000000`00000000 00000000`00000002 : 0xfffffa80`0a0a4000
fffff880`0de94e48 00000000`00d1d100 : 00000001`00000001 00000000`00000000 00000000`00000002 fffff880`0555ce3a : 0x401e034c
fffff880`0de94e50 00000001`00000001 : 00000000`00000000 00000000`00000002 fffff880`0555ce3a fffffa80`0a36b000 : 0xd1d100
fffff880`0de94e58 00000000`00000000 : 00000000`00000002 fffff880`0555ce3a fffffa80`0a36b000 00000000`00000002 : 0x00000001`00000001


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 0xfffff8800de94440 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_dlkmd+19d12

BUCKET_ID:  X64_0x7E_dlkmd+19d12

Followup: MachineOwner
---------
Update the Intel Graphics Driver as well. Go to this link: Intel® Driver Update Utility Accept and run using Java. Update all outdated drivers

Please upload your msinfo32.nfo file. To get this: Start Menu -> Type msinfo32 into the Search programs and files box -> When it opens, go to File, Save -> Save as msinfo32.nfo and save in a place you will remember -> Let it finish the process of gathering and saving the system info -> Right click the .nfo file, click send to compressed (zipped) folder -> Upload the .zip file here.

Please upload your msinfo32.txt file. To get this: Start Menu -> Type msinfo32 into the Search programs and files box -> When it opens, go to File, Export -> Save as msinfo32.txt and save in a place you will remember -> Let it finish the process of gathering and saving the system info -> Right click the .txt file, click send to compressed (zipped) folder -> Upload the .zip file here.
My System SpecsSystem Spec
.


29 Nov 2012   #4

Virginia
 
 

Appreciate the help kat! Two questions if you don't mind:

- What software did you use to provide those quazi-user friendly results?
- What is benefit of using revo over add/remove programs? Edit: I think I know the answer to this. Read the driver is to help monitors work via USB (HP docking stations). Software won't generally uninstall without additional tools?

Thanks a ton!
Jim
My System SpecsSystem Spec
29 Nov 2012   #5

Windows 7 Home Premium 64bit SP1
 
 

  1. Debugging Tool for Windows (sdksetup.exe + .Net Framework Version 4.5)
  2. Yes it should. But Revo gives you the option to clean out remaining registries of the program for a clean uninstall of the program.
  3. BSOD Analysis - Getting Started
My System SpecsSystem Spec
29 Nov 2012   #6

Virginia
 
 

Attached requested files. Once problem identified, is there an easy way to fix this across 60 laptops, or is it going to be a manual process of uninstall/update on each?

Thanks!
Jim
My System SpecsSystem Spec
29 Nov 2012   #7

Windows 7 Home Premium 64bit SP1
 
 

Hopefully unistalling should be a fix.
My System SpecsSystem Spec
Reply

 BSOD - Believe since GP push of screensaver/idle lockout - 1000007e problems?



Thread Tools



Similar help and support threads for: BSOD - Believe since GP push of screensaver/idle lockout - 1000007e
Thread Forum
BSOD: 1000007e BSOD Help and Support
BSOD - Crashes while computer idle/not idle (Unpredictable) BSOD Help and Support
CM Hyper 212 Plus One(push) OR Two(push-pull) fans? Hardware & Devices
1000007e BSOD BSOD Help and Support
BSOD:1000007e BSOD Help and Support


All times are GMT -5. The time now is 12:43 PM.


Seven Forums Android App Seven Forums IOS App Follow us on Facebook

Windows 7 Forums is an independent web site and has not been authorized,
sponsored, or otherwise approved by Microsoft Corporation.
"Windows 7" and related materials are trademarks of Microsoft Corp.
© Designer Media Ltd
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32