BSOD 9F - laptop screen won't turn on after sleep

[uncommonlich]

My Dell Latitute E7440 will frequently have a blank screen after going to sleep. When it happens, I can't use the laptop until I turn it off and on, losing all the programs I have open. Two days ago I got a BSOD 9F when trying to wake it up. I don't know that's wrong with the laptop, running WinDBG on the minidump tells me either ntkrnlmp.sys or igdkmd64.sys caused it but I don't have any detail beyond that. Need someone more knowledgeable than I to help me.

 

[Golden]

There appears to 2 independent issues here.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff88005cac2db, fffff88004308900, 0}

*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
Probably caused by : [B][COLOR="Red"]igdkmd64.sys [/COLOR][/B]( igdkmd64+1b22db )

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

0: kd> lmvm igdkmd64
start             end                 module name
fffff880`05afa000 fffff880`05f33fe0   igdkmd64 T (no symbols)           
    Loaded symbol image file: igdkmd64.sys
    Image path: igdkmd64.sys
    Image name: igdkmd64.sys
    Timestamp:        Wed May 08 09:45:19 [B][COLOR="red"]2013[/COLOR][/B] (51899917)
    CheckSum:         00442E25
    ImageSize:        00439FE0
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

The Intel video driver is outdated. See if an updated driver exists:
https://downloadcenter.intel.com/

The 0x9 is less clear, but I suspect the issue is the outdated Intel network driver.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {4, 258, fffffa80036c6040, fffff80000b9a3d0}

Implicit thread is now fffffa80`036c6040
Probably caused by : ntkrnlmp.exe ( nt!PnpBugcheckPowerTimeout+76 )

Followup: MachineOwner
---------
ffff800`00b9a628  fffffa80`0a868000
fffff800`00b9a630  00000014`00000000
fffff800`00b9a638  00000000`00000000
fffff800`00b9a640  fffffa80`07c01f50
fffff800`00b9a648  fffff880`06087787Unable to load image NETwsw02.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for NETwsw02.sys
*** ERROR: Module load completed but symbols could not be loaded for [B][COLOR="red"]NETwsw02.sys[/COLOR][/B]
 NETwsw02+0x4787
fffff800`00b9a650  fffffa80`0a47af60
fffff800`00b9a658  fffff880`061e80f8 NETwsw02+0x1650f8
fffff800`00b9a660  fffffa80`0a47af60
fffff800`00b9a668  fffffa80`07bf98b0
fffff800`00b9a670  00000000`00000000
fffff800`00b9a678  fffff880`06087550 NETwsw02+0x4550
fffff800`00b9a680  fffffa80`07bf98b0
fffff800`00b9a688  fffff880`06087787 NETwsw02+0x4787
fffff800`00b9a690  fffffa80`00000000
fffff800`00b9a698  00000000`00000000
fffff800`00b9a6a0  fffffa80`0a47adc0
fffff800`00b9a6a8  fffff880`0609c3a3 NETwsw02+0x193a3
fffff800`00b9a6b0  00000000`00000000
ffff880`06083000 fffff880`063ec000   NETwsw02 T (no symbols)           
    Loaded symbol image file: NETwsw02.sys
    Image path: NETwsw02.sys
    Image name: NETwsw02.sys
    Timestamp:        Fri Jun 28 05:44:36[B][COLOR="red"] 2013[/COLOR][/B] (51CC9D2C)
    CheckSum:         003582CF
    ImageSize:        00369000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Update the driver from the same site.

In fact, I strongly recommend updating all Intel based drivers from that location.

 

[uncommonlich]

Ok I'll get on updating these drivers, didn't realize they were this old.