BSOD after computer is idle

[jhickey]

Windows 7 64bit laptop. Has BSOD twice in the last 30 days. DM Zip file attached. Thanks for any assistance.

 

[essenbe]

Hello, hickey. I can try to help you. You have had one dump file within the last 4 months. That file lists

[COLOR=red]DRIVER_POWER_STATE_FAILURE (9f)[/COLOR]
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa801943ca10, Physical Device Object of the stack
Arg3: fffff80004ba03d8, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: fffffa801e8c9e10, The blocked IRP

The dump file lists

fffff800`04ba0668  fffff880`066bd976Unable to load image \SystemRoot\system32\DRIVERS\rtwlane.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for rtwlane.sys
*** [COLOR=red]ERROR: Module load completed but symbols could not be loaded for rtwlane.sys[/COLOR]
 rtwlane+0x12976

Which is the Realtek PCI-E Wireless LAN NIC NDIS Driver

fffff800`04ba0618  fffff880`04f94127Unable to load image \SystemRoot\system32\DRIVERS\igdkmd64.sys, Win32 error 0n2
*** [COLOR=red]WARNING: Unable to verify timestamp for igdkmd64.sys[/COLOR]
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
 igdkmd64+0x174127

Which is the Intel Graphics Driver

and

fffff800`04ba0520  fffff880`06239ea0Unable to load image \SystemRoot\system32\drivers\dlkmd.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dlkmd.sys
*** ERROR: Module load completed but symbols could not be loaded for dlkmd.sys
 dlkmd+0x2eea0

Which is the WDDM KMD Loader - DisplayLink Core Software driver may be able to be downloaded from DisplayLink Support other parts from the OEM.

Please update the listed drivers from your computer's web site. Also

Please fill out your System Specs​

   Information

Your System Specs will help us to help you, and doing it in this manner will make them available to all helpers in every post and keep us from hunting for them. We ask that you fill them out in as much detail as possible including Desktop or Laptop, Model number if it is an OEM computer and all components with the Manufacturer and Model number if possible.

If you will go to your last post and click the 'System Specs' in the bottom left of the post, you will find a link to update your system specs. Please fill those out in as much detail as possible, making sure to click save at the bottom of the page. If you would like to know what we would like, you can click 'My System Specs' at the bottom left of this post to see mine. If you do not know what your components are, this will help you accomplish this task. http://www.sevenforums.com/tutorials/180324-system-info-see-your-system-specs.html​

 

[essenbe]

Also, please
open an elevated command prompt ( click start, type cmd in the search box, right click on the cmd entryand select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.

 

[jhickey]

Unable to repair after three reboots. I have attached a the cbs.log. Any help appreciated.

 

[essenbe]

I'll see if I can get someone to read them for you.

 

[jhickey]

Thanks for all your advice!

 

[essenbe]

You aren't getting rid of me that easy. I'll still be here.

 

[NoelDP]

Ms have updated their advice on these particular errors - which until now we have attempted to fix (and succeeded, only for them to revert later)

 Line 36437: 2015-05-26 15:35:46, Info                  CSI    0000035a [SR] Repairing 1 components
 Line 36438: 2015-05-26 15:35:46, Info                  CSI    0000035b [SR] Beginning Verify and Repair transaction
 Line 36441: 2015-05-26 15:35:46, Info                  CSI    0000035d [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18839, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 36444: 2015-05-26 15:35:46, Info                  CSI    0000035f [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18839, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

They are from KB3022345.
It now appears that it's a detection problem rather than a real one, and the errors can be ignored - MS will update the logic in a later patch (which may well be in June's updates)
There are no other problems in the SFC, so carry on!