BSOD's Again on Desktop

writhziden · Feb 19, 2013

Same problem. Disabling sleep would likely fix it since it is a 0x9F DRIVER_POWER_STATE_FAILURE crash. A 0x9F DRIVER_POWER_STATE_FAILURE crash means that the system tried to enter a sleep or hibernation state (or tried to resume from one), and the driver did not respond to the request for the device to enter a low-power or disabled state (or enter a normal or enabled state for resuming from sleep/hibernation). In this case, your Intel(R) PRO/1000 PCI Express Network Connection Driver is not responding to the system's signal to change power states.

The other time you may see these crashes is when the system is shutting down to power down or starting up after being powered down.

Amcgrap · Feb 19, 2013

Thanks for your response. I disabled the sleep mode, just to test this problem. Still, how can we solve this without having to "handicap" the system? I have never been so concerned about sleep mode on my desktops but that is a bit irresponsible! What do you suggest as next steps?

Thanks again.

writhziden said:
Same problem. Disabling sleep would likely fix it since it is a 0x9F DRIVER_POWER_STATE_FAILURE crash. A 0x9F DRIVER_POWER_STATE_FAILURE crash means that the system tried to enter a sleep or hibernation state (or tried to resume from one), and the driver did not respond to the request for the device to enter a low-power or disabled state (or enter a normal or enabled state for resuming from sleep/hibernation). In this case, your Intel(R) PRO/1000 PCI Express Network Connection Driver is not responding to the system's signal to change power states.

The other time you may see these crashes is when the system is shutting down to power down or starting up after being powered down.

jcgriff2 · Feb 21, 2013

I agree with writhziden - Intel Ethernet

Code:

0: kd> !irp fffffa8009eb5140
Irp is active with 4 stacks 3 is current (= 0xfffffa8009eb52a0)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
     cmd  flg cl Device   File     Completion-Context
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
>[ 16, 2]   0 e1 fffffa800870e050 00000000 fffff8000330f200-fffffa800b7c4580 Success Error Cancel pending
          Unable to load image \SystemRoot\system32\DRIVERS\e1e6232e.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for e1e6232e.sys
*** ERROR: Module load completed but symbols could not be loaded for e1e6232e.sys
 \Driver\e1express    nt!PopSystemIrpCompletion
            Args: 00015400 00000000 00000005 00000003
 [  0, 0]   0  0 00000000 00000000 00000000-fffffa800b7c4580    

            Args: 00000000 00000000 00000000 00000000

Doubtful, but check for updated driver -

Code:

0: kd> lmvm e1e6232e
start             end                 module name
fffff880`041b1000 fffff880`041fd000   e1e6232e   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\e1e6232e.sys
    Image name: e1e6232e.sys
    Timestamp:        Tue Oct 30 05:19:42 2012 (508F9BAE)

https://www.sysnative.com/drivers/driver.php?id=e1e6232e.sys

Regards. . .

jcgriff2

writhziden · Feb 21, 2013

You may also consider running Verifier to see if it finds whether a conflicting driver is behind these crashes.

Driver Verifier - BSOD related

Search

Search

BSOD's Again on Desktop

writhziden

Administrator, .NET/UWP Developer

Amcgrap

Well-known member

jcgriff2

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)

writhziden

Administrator, .NET/UWP Developer

BSOD's Again on Desktop

writhziden

Administrator, .NET/UWP Developer

Amcgrap

Well-known member

jcgriff2

Co-Founder / AdminBSOD Instructor/ExpertMicrosoft MVP (Ret.)

writhziden

Administrator, .NET/UWP Developer

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)