• This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.

Crash when trying to put a laptop to sleep (ntoskrnl.exe)


estroop

New Member
Posts
4
#1
Hello. I have an ASUS x552m laptop with Windows 8.1.

Over the past days, it crashes when I try put it into Sleep mode (maybe 1 out of 4 times). The screen turns off, but the little lights under the touchpad stay lit for a few minutes and then the computer shuts down. I get dump files every time and they are referring to ntoskrnl.exe+14e2a0 DRIVER_POWER_STATE_FAILURE.

I've read in the forums that many ASUS laptops have a similar issue. I uninstalled some of the preinstalled ASUS software and downloaded a new NVIDIA graphics driver after I started to get these crashes. I was thinking about restoring the system to the state when the crashes hadn't occurred yet, but I haven't done it yet.

No 3rd party antivirus, only Windows Defender

Any help welcome. View attachment 67289
 
Last edited:

My Computer

System One

  • OS
    Windows 8.1

lifetec

New Member
Power User
Posts
660
#2
The last 5 dumpfiles all blames Probably caused by : usbccgp.sys
Code:
  *******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, ffffe00032d8b8c0, fffff800f4c37aa0, ffffe00030df4990}
Probably caused by : usbccgp.sys
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
DRIVER_POWER_STATE_FAILURE (9f)
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: ffffe00032d8b8c0, Physical Device Object of the stack
Arg3: fffff800f4c37aa0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffe00030df4990, The blocked IRP
But this being a windows drivers this probably not the real culprit.
Analysing the blocked irp gives
Code:
   [       Unable to load image \SystemRoot\system32\DRIVERS\ewusbwwan.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ewusbwwan.sys
*** ERROR: Module load completed but symbols could not be loaded for ewusbwwan.sys
 \Driver\ewusbmbb nt!PopSystemIrpCompletion
   Args: 00014400 00000000 00000004 00000002
 [  0, 0]   0  0 00000000 00000000 00000000-ffffe00031a75010
It looks that the culprit is ewusbwwan.sys
Driver Description: Huawei Mobile Broadband USB NDIS Miniport Driver
Driver Update Site: ?Huawei Error? - Huawei Official Site or try the carrier that provided the modem
Looking at your systeminfo i found
[03]: HUAWEI Mobile Connect - 3G Network Card
Connection Name: Mobile broadband
Update to a windows 8.1 compatible driver or remove this device.
 

My Computer

System One

  • OS
    windows 8.1
    Computer type
    PC/Desktop
    System Manufacturer/Model Number
    self build
    CPU
    Intel(R) Core(TM) i5 CPU 750 @ 2.67GHz
    Motherboard
    Asrock P55 Pro
    Memory
    DDR3 Team--Elite-1333 8 gb
    Graphics Card(s)
    Sapphire R9 280x
    Sound Card
    Realtek Alc 855
    Monitor(s) Displays
    Acer V233H
    Screen Resolution
    1920 x 1020
    Hard Drives
    Samsung evo 850 SSd
    Seagate ST 320 gb
    Samsung HD 750 gb
    Seagate ST 3000gb
    PSU
    OCZ Stealth 600 watt
    Case
    Antec 300
    Mouse
    Speedlink Ledos and Nexus

estroop

New Member
Posts
4
#3
Huawei application actually caused crashes months ago. Then I downloaded a newer version and it worked fine until now. Today I downloaded the newest version but still seemed to crash. Maybe I should try to run in compatibility mode?
 

My Computer

System One

  • OS
    Windows 8.1

lifetec

New Member
Power User
Posts
660
#5
It could be.
But also use the DISM command
Note
If SFC could not fix something, then run the command again to see if it may beable to the next time. Sometimes it may take running the sfc /scannow
command 3 timesrestarting the PC after each time to completely fix everything that it's ableto.

If not, then run the
Dism /Online /Cleanup-Image/RestoreHealth command to repair any component store corruption, restart the PCafterwards, and try the sfc /scannowcommand again.

 

My Computer

System One

  • OS
    windows 8.1
    Computer type
    PC/Desktop
    System Manufacturer/Model Number
    self build
    CPU
    Intel(R) Core(TM) i5 CPU 750 @ 2.67GHz
    Motherboard
    Asrock P55 Pro
    Memory
    DDR3 Team--Elite-1333 8 gb
    Graphics Card(s)
    Sapphire R9 280x
    Sound Card
    Realtek Alc 855
    Monitor(s) Displays
    Acer V233H
    Screen Resolution
    1920 x 1020
    Hard Drives
    Samsung evo 850 SSd
    Seagate ST 320 gb
    Samsung HD 750 gb
    Seagate ST 3000gb
    PSU
    OCZ Stealth 600 watt
    Case
    Antec 300
    Mouse
    Speedlink Ledos and Nexus

cluberti

Cat herder
VIP Member
Pro User
Redmond

Posts
651
#7
It's not that different:
Code:
// Bugcheck is a 0x9f (DRIVER_POWER_STATE_FAILURE):
0: kd> .bugcheckBugcheck code 0000009F
Arguments 00000000`00000004 00000000`0000012c ffffe000`32cfd040 fffff803`45c37ac0

// The thread pending the IRP that caused the crash is param 3:
0: kd> !thread ffffe00032cfd040
GetPointerFromAddress: unable to read from fffff803445e8000
THREAD ffffe00032cfd040  Cid 0004.15d0  Teb: 0000000000000000 Win32Thread: 0000000000000000 WAIT: (DelayExecution) KernelMode Non-Alertable
    ffffffffffffffff  NotificationEvent
IRP List:
    ffffe00030427ab0: (0006,0550) Flags: 00000000  Mdl: 00000000
Not impersonating
GetUlongFromAddress: unable to read from fffff80344535b00
Owning Process            ffffe0002e4a08c0       Image:         System
Attached Process          N/A            Image:         N/A
fffff78000000000: Unable to get shared data
Wait Start TickCount      1044045      
Context Switch Count      106917         IdealProcessor: 2  NoStackSwap
ReadMemory error: Cannot get nt!KeMaximumIncrement value.
UserTime                  00:00:00.000
KernelTime                00:00:00.000
Win32 Start Address nt!ExpWorkerThread (0xfffff803442cc8d0)
Stack Init ffffd00022b24dd0 Current ffffd00022b23db0
Base ffffd00022b25000 Limit ffffd00022b1f000 Call 0
Priority 14 BasePriority 12 UnusualBoost 2 ForegroundBoost 0 IoPriority 2 PagePriority 5
Child-SP          RetAddr           : Args to Child                                                           : Call Site
ffffd000`22b23df0 fffff803`442d0a2e : ffffd001`5c9c0180 ffffe000`32cfd040 00000000`0000000a 00000000`fffffffe : nt!KiSwapContext+0x76
ffffd000`22b23f30 fffff803`442d04a9 : ffffe000`32cfd040 ffffe000`32cfd180 00000000`00097edb 00000000`00000000 : nt!KiSwapThread+0x14e
ffffd000`22b23fd0 fffff803`442c6904 : ffffd000`22b24120 00000000`00000002 fffff780`000000dc fffff801`c38a816c : nt!KiCommitThreadWait+0x129
ffffd000`22b24050 fffff801`c45f173b : ffffe000`2f29ec60 ffffe000`2f29ec60 ffffd000`22b24120 00000000`00000000 : nt!KeDelayExecutionThread+0xe14
ffffd000`22b240f0 ffffe000`2f29ec60 : ffffe000`2f29ec60 ffffd000`22b24120 00000000`00000000 ffffe000`300ae7a0 : nbdrv+0x473b
ffffd000`22b240f8 ffffe000`2f29ec60 : ffffd000`22b24120 00000000`00000000 ffffe000`300ae7a0 fffff801`c3939f03 : 0xffffe000`2f29ec60
ffffd000`22b24100 ffffd000`22b24120 : 00000000`00000000 ffffe000`300ae7a0 fffff801`c3939f03 ffffffff`fffb6c20 : 0xffffe000`2f29ec60
ffffd000`22b24108 00000000`00000000 : ffffe000`300ae7a0 fffff801`c3939f03 ffffffff`fffb6c20 ffffe000`2ef7f558 : 0xffffd000`22b24120

// Looking at the IRP we can see the driver that we're pending:
0: kd> !irp ffffe00030427ab0
Irp is active with 16 stacks 16 is current (= 0xffffe00030427fb8)
 No Mdl: No System Buffer: Thread ffffe00032cfd040:  Irp stack trace.  
     cmd  flg cl Device   File     Completion-Context
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    


            Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    


            Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    


            Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    


            Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    


            Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    


            Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    


            Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    


            Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    


            Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    


            Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    


            Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    


            Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    


            Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    


            Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    


            Args: 00000000 00000000 00000000 00000000
>[IRP_MJ_PNP(1b), IRP_MN_REMOVE_DEVICE - (2)]
            0  0 ffffe0002ef7e050 00000000 00000000-00000000
 \Driver\ewusbmbb
            Args: 00000000 00000000 00000000 00000000



0: kd> lmvm ewusbwwan
start             end                 module name
fffff801`c7ab2000 fffff801`c7b26000   ewusbwwan T (no symbols)           
    Loaded symbol image file: ewusbwwan.sys
    Image path: \SystemRoot\system32\DRIVERS\ewusbwwan.sys
    Image name: ewusbwwan.sys
    Timestamp:        Mon Sep 02 00:50:44 2013 (52244354)
    CheckSum:         0007185C
    ImageSize:        00074000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
Still the Huawei driver set. I'd remove it entirely if possible and see if the problem persists - if this is your only way to connect to the internet from this box, you might want to look into a more reliable modem.
 

My Computer

System One

  • OS
    Windows 8.1 x64
    Computer type
    PC/Desktop
    System Manufacturer/Model Number
    Custom
    CPU
    Intel Core i7 4790K @ 4.5GHz
    Motherboard
    Asus Maximus Hero VII
    Memory
    32GB DDR3
    Graphics Card(s)
    Nvidia GeForce GTX970
    Sound Card
    Realtek HD Audio
    Hard Drives
    1x Samsung 250GB SSD
    4x WD RE 2TB (RAIDZ)
    PSU
    Corsair AX760i
    Case
    Fractal Design Define R4
    Cooling
    Noctua NH-D15