The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    Driver_power_state_failure bsod

    Discussion in 'Sager and Clevo' started by 4rm, Feb 10, 2013.

  1. 4rm

    4rm Notebook Enthusiast

    Reputations:
    0
    Messages:
    24
    Likes Received:
    0
    Trophy Points:
    5
    I've had my NP9150 for a few weeks now, and everything has been great until now. I closed the lid of my laptop and went away for a few hours, and when I came back the fans were very loud and a BSOD had appeared.
    W7K7HUd.jpg
    I looked up what caused this, and it seemed to mostly be an issue with the power options. I went through them but found nothing suspicious. I'm using default power settings, nothing is custom. I restarted my computer fine, and it has not blue-screened since.

    Here are the dumps from Who Crashed:

    Code:
    On Sat 2/9/2013 5:49:39 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\020913-8751-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0) 
    Bugcheck code: 0x9F (0x3, 0xFFFFFA800CC955B0, 0xFFFFF80000B9C3D8, 0xFFFFFA80116CD6A0)
    Error: DRIVER_POWER_STATE_FAILURE
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 
    
    
    
    On Sat 2/9/2013 5:49:39 PM GMT your computer crashed
    crash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) 
    Bugcheck code: 0x9F (0x3, 0xFFFFFA800CC955B0, 0xFFFFF80000B9C3D8, 0xFFFFFA80116CD6A0)
    Error: DRIVER_POWER_STATE_FAILURE
    Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 
    
    Somewhat related, I've been experiencing random shutdowns when I close my laptop lid. At the moment it's just set to go to sleep when the lid is closed, but it very often powers off. I suspect that somehow the hinge is pressing the power button (or maybe something gets caught between them) and turning it off.

    Has anyone else experienced this? Is it possible for the hinge to be pressing the power button?

    Thanks in advance.
     
  2. jaybee83

    jaybee83 Biotech-Doc

    Reputations:
    4,125
    Messages:
    11,571
    Likes Received:
    9,151
    Trophy Points:
    931
    do u have an ssd running in ur system? if so, go ahead and check if there is an updated firmware available for it, maybe the current one has issues with going to / returning from sleep state.
    also, u could try different power states (powersaver/balanced/high perf.) and see if that still shuts off ur machine or makes it bsod.

    Sent from my Galaxy Nexus using Tapatalk 2
     
  3. Srikar

    Srikar Notebook Evangelist

    Reputations:
    55
    Messages:
    398
    Likes Received:
    2
    Trophy Points:
    31
    Can't help you, but I have an unrelated (kinda) issue. Every now and then, my computer likes to go into sleep or hibernation on its own. It never happens more than once in 24 hours and usually happens mid-afternoon, although it hasn't done it in about a week..Sometimes I won't be there when it happens but most of the time I'm doing something, like typing on a forum, browsing the internet, or something else (hasn't happened in a game yet). It's really weird and I can't come up with any errors in the event viewer when it happens.
     
  4. 4rm

    4rm Notebook Enthusiast

    Reputations:
    0
    Messages:
    24
    Likes Received:
    0
    Trophy Points:
    5
    I do have an SSD, but how do I check for a firmware update? I tried going into Device Manager and selecting Update Driver, but I don't think that's right.
     
  5. jaybee83

    jaybee83 Biotech-Doc

    Reputations:
    4,125
    Messages:
    11,571
    Likes Received:
    9,151
    Trophy Points:
    931
    download crystaldiskinfo, it will tell u what ur current firmware is. then go to this link right here: Crucial.com Product Downloads - Firmware Updates

    choose ur ssd model (crucial m4 msata) and see if the offered firmware version is identical to the one u have. if its not, then id recommend updating it (update guide is given in that link as well). make sure to make a backup of ur data first, since some firmware upgrades can be destructive!

    cheers
     
  6. 4rm

    4rm Notebook Enthusiast

    Reputations:
    0
    Messages:
    24
    Likes Received:
    0
    Trophy Points:
    5
    It looks like I'm running the latest firmware.

    So far it seems like the power states make no difference.
     
  7. jaybee83

    jaybee83 Biotech-Doc

    Reputations:
    4,125
    Messages:
    11,571
    Likes Received:
    9,151
    Trophy Points:
    931
    hm too bad, back to square one then...

    Sent from my Galaxy Nexus using Tapatalk 2
     
  8. 4rm

    4rm Notebook Enthusiast

    Reputations:
    0
    Messages:
    24
    Likes Received:
    0
    Trophy Points:
    5
    My computer shut off when I closed the lid again, but it's very inconsistent, I can't pinpoint the cause. I was on battery saver mode and when I closed the lid for maybe 5-7 seconds, it shut off. I tried again four more times, but it just went to sleep. I tried only closing it enough to make the computer think it was closed (to make sure nothing was hitting the power button) and it went to sleep as normal. I also tried closing it all the way, but it just went to sleep. I switched to maximum performance and did the same, but it just went to sleep as planned. I checked the "Choose what closing the lid does" and every option was set to sleep for all power settings.

    Is there maybe a program to detect what caused the last shutdown? Who Crashed only tells me what caused the last BSOD.

    Edit: It looks like I can (sort of) detect the last shutdown with eventvwr. This was the cause of the last shutdown

    Code:
    - System
    
      - Provider
    
       [ Name]  EventLog
    
      - EventID 6008
    
       [ Qualifiers]  32768
    
       Level 2
    
       Task 0
    
       Keywords 0x80000000000000
    
      - TimeCreated
    
       [ SystemTime]  2013-02-10T19:09:13.000000000Z
    
       EventRecordID 21827
    
       Channel System
    
       Computer ███████-PC
    
       Security
    
    
    - EventData
    
       2:08:22 PM
       ‎2/‎10/‎2013
       
       
       9482
       
       
       DD07020000000A000E0008001600B900DD07020000000A00130008001600B900600900003C000000010000006009000000000000B00400000100000000000000
    
    
    --------------------------------------------------------------------------------
    
    Binary data:
    
    
    In Words
    
    0000: 000207DD 000A0000 0008000E 00B90016
    0008: 000207DD 000A0000 00080013 00B90016
    0010: 00000960 0000003C 00000001 00000960
    0018: 00000000 000004B0 00000001 00000000
    
    
    In Bytes
    
    0000: DD 07 02 00 00 00 0A 00   Ý.......
    0008: 0E 00 08 00 16 00 B9 00   ......¹.
    0010: DD 07 02 00 00 00 0A 00   Ý.......
    0018: 13 00 08 00 16 00 B9 00   ......¹.
    0020: 60 09 00 00 3C 00 00 00   `...<...
    0028: 01 00 00 00 60 09 00 00   ....`...
    0030: 00 00 00 00 B0 04 00 00   ....°...
    0038: 01 00 00 00 00 00 00 00   ........