Driver Power State Failure


  1. Posts : 5
    Windows 7 64 bit
       #1

    Driver Power State Failure


    Hey i have a problem with my toshiba satellite it does not boot up correctly when i start the computer it takes long time than usual and also after it starts the windows 7 wallpaper comes and normally there is a log in button to log into my pc but now theres no login button its only the normal windows 7 wallpaper.
    Well One night i was using the computer and i was using speed up my pc and playing games and it got very slow and it got a lot stuck so i had to force it down and after i start it up again it says the computer was unable to boot properly and stuff but after that i have tried few stuff and now no error comes up but it does not start correctly i have no way on going into my computer.
    The stuff i did was i tried sfc and it was not able to fix the problems it said check the cbs file or something for the logs of the errors and also before the errors come up but after i did all four of these no errors come it starts but no login button only windows 7 wallpaper this is what i tried doing
    type > bootrec /fixmbr
    type > bootrec /fixboot
    type > bootrec /scanos
    type > bootrec /rebuildbcd
    Those four i tried.

    Like i just told i tried all those four options of bootrec and it made the computer boot up but only the windows 7 wallpaper is there when it should be the windows 7 wallpaper and a log in button but the login button is not there i can post pictures if needed.

    Startup repair could not fix the problems.
    Sfc could not fix the problems.
    Bootrec changed the problems but not fixed.

    I see that the hard disk is fine i can view the files there and everything using my recovery disk.
    I can use cmd using my recovery disk.
    I also tried restore to an earlier time it kept working for more than 5 hours so i thought its not working then i forced it down and now it says no restore points.

    Please help me i do not know what the problems are so its hard to fix but hard disk works fine only problem is there is no log in button after the starting windows.

    I have recovery disk and also i can use cmd and check system files and folders using recovery disk but can not use the pc when trying to boot up the starting windows comes up with windows logo and takes longer than usual and also nothing happens after that i can only see the windows 7 wallpaper and nothing else comes up but sometimes the start up repair auto mantically starts but I left it for about 10 hours and still it did not finish so i don't think startup repair works.
      My Computer


  2. Posts : 5
    Windows 7 64 bit
    Thread Starter
       #2

    Driver Power State Failure


    I get a Driver_power_state_failure with a stop : 0x0000009F(0x00000004,0x00000258,0x8658F020,0x8397CB24)

    Yesterday i was working with my computer and i was running a game and fix my pc and it was very slow it got stuck and i forced it down and when i start the pc i get that error.

    I have tried sfc and bootrec and startup repair none of them can fix the problem it says unable to fix the problem.
    I also have the recovery disk and can view the hard disk files and also use cmd but i tried the startup repair and it could not fix the problem.

    Please help here is few pictures:



      My Computer


  3. Posts : 3,056
    Windows 10
       #3

    Welcome to SF nisva :) .

    The first thing I would do is to back up any files you can't afford to lose, you said you can access your files
    already which is good, you can also follow this tutorial to back them up if possible.




    Then follow these steps (where possible) to diagnose the state the HDD is in.


       Warning
    The Following Method Should NOT Be Performed On An SSD!


    Testing the HDD:



    1. Perform a Disk Check | Disk Check- Scroll down to OPTION TWO of the tutorial and use the /R switch in the CHKDSK command | chkdsk C: /R.
    2. Then Post the Disk Check results following | This Tutorial.
    3. Once back in Windows, download Crystal Disk Info and post a screenshot (multiple shots if you have more than one drive).
    4. Download SeaTools for DOS if you don't want to use a CD to test the HDD you can use YUMI – Multiboot USB Creator to create a bootable USB (instructions are found at the bottom of both pages).
    5. If SeaTools for DOS is unable to recognize your HDD:
    6. Visit HDDdiag and follow the instructions | Or follow the instructions below.

    If SeaTools For DOS does not recognize the drive;
    Boot into the BIOS using the *Fx key.
    Look for an entry called SATA Mode (or something similar), it should be set to IDE / AHCI.
    It's probably set to AHCI which is why SeaTools doesn't recognize them in the DOS environment.
    Set it to IDE then save and exit usually by pressing the F10 key.
    Now boot into SeaTools and it should detect the drives.
    Start the Long Test and let it run.
    Upon completion don't try to boot into Windows as it will only result in a BSOD, go back into the BIOS
    and change the SATA setting back to what it was in the first place.



    Arc said:
    Re-seat the sata and power.

    Let us know the results.
      My Computer


  4. Posts : 5
    Windows 7 64 bit
    Thread Starter
       #4

    Hey thanks for posting back since no one else did but you should know that i cannot boot up the pc the blue screen as above comes up but i can only view/run files using my recovery disk i can also use cmd and do the chkdsk c:/r but i cannot post the disk check result following your tutorial because i cannot boot up the pc to do this.

    Also can you let me know what the error codes mean:
    Driver_power_state_failure with a stop : 0x0000009F(0x00000004,0x00000258,0x8658F020,0x8397CB24)

    What does the codes mean what causes the problem if i find what causes the problem maybe i can reinstall/install or remove the software which causes this problem.

    Ill do your steps once i receive a reply.

    Thanks again so much for replying cause i really need the computer to work.
      My Computer


  5. Posts : 3,056
    Windows 10
       #5

    0x9F which is DRIVER POWER STATE FAILURE that happens in
    transitions between power states most commonly S0 (ON state) > S3 (Sleep state)
    or vice-verse. You can read more HERE.
    The most common cause is a device driver but sometimes it's the hardware itself
    that is at fault.
    Is this case the 1st parameter is 0x00000004 which means there is a PnP (plug and play)
    lock which is being held and not released in a timely fashion which causes a wait
    and a synchronization to fail.

    Did you try to logon into Safe Mode?
    What did the CHKDSK say?
    Did you try SeaTools yet?
    What peripherals are connected to the PC?
      My Computer


  6. Posts : 5
    Windows 7 64 bit
    Thread Starter
       #6

    Hey thanks for replying yes i tried safe mode it was loading and got stuck at classpnp.sys then i fixed that by making it to IDE then after that safe mode does not start after its done loading it goes into a black screen saying fix problems recommended and start windows normally i tried that and it does start up repair i kept it for around 8 hours or more it keeps at attempting repairs it does not go further .
    And no i have not tried seatools what must i do with it can it fix my problem?
    And if peripherals are like devices or something then no i have no usb or anything connected nothing.

    Here is what chkdsk said on c drive:


    I think that my windows is in the D not c so ill do a scan in D drive.
    The picture i posted up is the c drive.
    Last edited by nisva; 20 Dec 2013 at 14:11.
      My Computer


  7. Posts : 3,056
    Windows 10
       #7

    Sorry for the late reply.
    nisva said:
    Hey thanks for replying yes i tried safe mode it was loading and got stuck at classpnp.sys then i fixed that by making it to IDE then after that safe mode does not start after its done loading it goes into a black screen saying fix problems recommended and start windows normally i tried that and it does start up repair i kept it for around 8 hours or more it keeps at attempting repairs it does not go further .
    That is because you can't change the SATA mode after the fact without a proper preparation,
    doing so will only cause very fast BSOD's (because it can't access the DISK to generate a dump)
    which is what you're getting. Please set the SATA mode back to what is was before.

    nisva said:
    And no i have not tried seatools what must i do with it can it fix my problem?
    And if peripherals are like devices or something then no i have no usb or anything connected nothing.
    It won't fix your problem but it will give us better insight as to what the physical condition of the HDD is.

    nisva said:
    I think that my windows is in the D not c so ill do a scan in D drive.
    The picture i posted up is the c drive.
    The results look good.
    I don't think it is.

    Do you currently have data you can't afford to lose?
      My Computer


  8. Posts : 5
    Windows 7 64 bit
    Thread Starter
       #8

    I have many files i cant afford to lose.
    And my windows is installed in D.
      My Computer


  9. Posts : 3,056
    Windows 10
       #9

    I still find it hard to believe to be the case.

    Regardless I would go for a clean OEM (OEM that is if the system specs listed in your profile
    are true and up to date)
    install after backing up the needed data.

    1. Emergency Kit - save your files from a dead OS
    2. Clean Reinstall - Factory OEM Windows 7
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 07:10.
Find Us