Random BSOD, error 0x0000009f (DRIVER_POWER_STATE_FAILURE), Asus N76VZ

Page 3 of 6 FirstFirst 12345 ... LastLast

  1. Posts : 2
    Windows 7 Ultimate x64
       #21

    Welcome.

    I have exactly the same problem with the same error. For me, the error occurs once in about 2 weeks.


    DRIVER_POWER_STATE_FAILURE (9f) A driver has failed to complete a power IRP within a specific time (usually 10 minutes). Arguments: Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time Arg2: fffffa800aa62a10, Physical Device Object of the stack Arg3: fffff800044073d8, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack Arg4: fffffa80127a3600, The blocked IRP
    The solution to the BSOD does not occur is to disable Nvidia graphics card in Windows.

    I wonder if this error is not related to the fact that you and I have Windows 7 and the computer is installed as standard Windows 8.

    Maybe there is some incompatibility with Windows 7?

    Sorry for my English.
    Grzegorz
      My Computer


  2. Posts : 33
    Windows 7 Ultimate x64
    Thread Starter
       #22

    I did cross my mind, but I doubt it. All official drivers are provided for Windows 7. On the other hand, Asus is known to produce/provide very crappy drivers and idiotic bloatware.

    I'm curious about one thing? If I'm not mistaken, you also have Asus N76VZ? Did it also come without OS, or with LinuxDOS, or what it was called...?
      My Computer


  3. Posts : 2
    Windows 7 Ultimate x64
       #23

    Yes, I have N76VZ. It comes with Windows 8, but I reinstalled with Windows 7 (from MSDN)
      My Computer


  4. Posts : 1,735
    Windows 7 enterprise 64 bit, Windows 7 Pro 64 bit ,Windows 8 64bit
       #24

    malus said:
    I just got another BSOD. This means that nothing that I've tried suggested here fixed it. I suspected the SSD or RAM from the start. Is it now safe to exclude the gpu and drivers, even though the dump files blame the gpu?

    Is there any way to pinpoint the problem a bit more precise?

    If it is the problem with ssd or ram; is there a way to provoke the crash?

    I will try next with pulling out one ram module....


    PS Since the bsods are now comming daily, it seems that installing the newset nvidia drivers actually worsened it.
    There is not much we can do to cause it to BSOD because it has been so hard to pin down the actual cause of the problem, though I am beginning to suspect the SSD more so than the ram.I say this because OCZ SSD's have been show to cause all sorts of BSOD problems (atleast on this forum). Have you reseated the SSD as I asked?
      My Computer


  5. Posts : 33
    Windows 7 Ultimate x64
    Thread Starter
       #25

    Yes, I have heard also quite alot about OCZ causing BSODs, however I cannot find traces of it causing error 0x0000009f (DRIVER_POWER_STATE_FAILURE).
    Actually the SSD was suspect form the start. One of the first things I did when I first noticed BSODs was to unplug, check and replug the drives. I'm not sure now, but I think that I also exchanged the slot position of drives, because I suspected that this could've caused the bsods. It didn't help. Then I figured out that I'm using the drive with one of the first FWs. Then I flashed the newest FW, and that seemed to decrease the number of BSODs form 1 per day to 1 per week.

    So let's assume it's the SSD. Is there a way to try to cause the BSOD on prupose by doing some SSD test?

    It is essential that I at least find the cause for this. Even if it is some deeper HW problem.
      My Computer


  6. Posts : 1,735
    Windows 7 enterprise 64 bit, Windows 7 Pro 64 bit ,Windows 8 64bit
       #26

    malus said:
    Yes, I have heard also quite alot about OCZ causing BSODs, however I cannot find traces of it causing error 0x0000009f (DRIVER_POWER_STATE_FAILURE).
    Actually the SSD was suspect form the start. One of the first things I did when I first noticed BSODs was to unplug, check and replug the drives. I'm not sure now, but I think that I also exchanged the slot position of drives, because I suspected that this could've caused the bsods. It didn't help. Then I figured out that I'm using the drive with one of the first FWs. Then I flashed the newest FW, and that seemed to decrease the number of BSODs form 1 per day to 1 per week.

    So let's assume it's the SSD. Is there a way to try to cause the BSOD on prupose by doing some SSD test?

    It is essential that I at least find the cause for this. Even if it is some deeper HW problem.
    There in lies the problem, I do not know if there is such a stress test for an SSD, I am going to see if I can get other eyes on this to help solve the problem.
      My Computer


  7. Posts : 2,573
    Win7 Ultimate X64
       #27

    Havent checked your files but when updating FW for SSD its also good practise to check for bios update

    Also as a test you could take an image of your install remove ssd and load to other HDD to see what the situation is ?
      My Computer


  8. Posts : 33
    Windows 7 Ultimate x64
    Thread Starter
       #28

    I flashed the latest bios for my laptop.

    What application should I use to transfer my system from ssd to hdd?

    One more thing. Could it be that this is caused by default ahci driver?
      My Computer


  9. Posts : 33
    Windows 7 Ultimate x64
    Thread Starter
       #29

    I still didn't exchange the SSD/HDD as suggested. I'm keeping that for last.

    But I did something else.

    I went through all the drivers on Asus website, and googled each of them to find the newest versions not infected by Asus. Everything except for the latest NVIDIA drivers. Few were outdated, even though Asus specifically instructs to install those. One interesting package I found, called "Intel Rapid Storage" contained few drivers in inf format, including the Intel AHCI driver.

    Since I did that 3 days ago, I didn't get the BSOD. Hopefully it will last.
      My Computer


  10. Posts : 686
    Windows 7 x64 Ultimate SP1
       #30

    Dsprague said:
    Also try running through this tutorial: Fix: Nvlddmkm.sys Blue Screen BSOD Error in Windows 7

    With the help of some of our other members Iit was pointed out to me thta you have around 24K of this error:
    Code:
    Event[0]:
      Log Name: System
      Source: Disk
      Date: 2012-12-07T17:37:27.469
      Event ID: 51
      Task: N/A
      Level: Warning
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Malus-AsusN76
      Description: 
    An error was detected on device \Device\Harddisk2\DR24 during a paging operation.
    so please also run the following from an elevated command prompt:

    Code:
    chkdsk /f /r
    If the harddisk device has the letter R in the code (like here, DR 24) it is a removable drive (or recognized as such by Windows), and this is quite a normal error for removable drives. So there would be no need for a checkdisk scan.

    Malus, if you see another BSOD I'm afraid you will have to service your laptop. The NVIDIA graphics adapter transitions from D0 (fully online and functioning) to D3 (asleep, powered off) state often, and if it doesn't accomplish that succesfully, this kind of BSOD would be understandable and almost surely caused by faulty hardware, unfortunately.

    I hope that the cause is the one you found in your last post and that the problem is solved.
    Last edited by Teerex; 18 Mar 2013 at 16:40.
      My Computer


 
Page 3 of 6 FirstFirst 12345 ... LastLast

  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 01:11.
Find Us