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

[gsawicki]

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

 

[malus]

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...?

 

[gsawicki]

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

 

[Dsprague]

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?

 

[malus]

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.

 

[Dsprague]

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.

 

[Pauly]

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 ?

 

[malus]

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?

 

[malus]

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.

 

[Teerex]

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:

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: 
[COLOR=Red]An error was detected on device \Device\Harddisk2\DR24 during a paging operation.[/COLOR]

so please also run the following from an elevated command prompt:

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.

 

[malus]

I'm not sure I understood you description of eventual problem. Especially the "if it doesn't accomplish that successfully" part. Who/what accomplishes what?

So if I get BSODed again you think it's the faulty NVIDIA GPU? Can I then assume that everything else is fine? (including the officially unsupported RAM and not so quality SSD).

You see, the trouble is that I foolishly got rid of the original 2+4GB RAM modules when I installed the 2 8GB modules. And knowing the reputation of the only local official service center, I'm sure that this will be reason enough for them not accept the warranty. Besides, they are known for extremely long waiting periods, and crappy service.

 

[Teerex]

The NVIDIA adapter accomplishing the change in power state. Every time that square GPU activity icon in the tray lights up (or gets rainbowy ), even for a second, the adapter goes from being asleep to fully online. Every time the icon goes dark, it gets back to sleep. It is awakened and put to sleep by its driver through PCI - that is how Optimus saves energy in a nutshell.

I was prompted to mention this by the dump pointing to that NVIDIA kernel driver. What the root cause of it could be, I really cannot say, we're getting into Gremlin territory. And I'm not a BSOD expert. I haven't even had a single one since I got this laptop (it is also an ASUS, it's N73SV and it has Optimus too).

The Microsoft documentation says this about your BSOD.
0x3

(Windows XP and later)
The physical device object (PDO) of the stack
The functional device object (FDO) of the stack. In Windows 7 and later, this parameter is reserved.
The blocked IRP
A device object has been blocking an IRP for too long a time.

What this meany exactly, I cannot say, but you'll recognize parameter 1 in your BSOD, it's 3.

Anyway, if it doesn't happen again, forget about what I wrote. And you can also relax about that disk error; I think (by the way, do you really attach removable drives that often (sticks, externals)?

 

[malus]

Yes. I use multiple USB sticks, external HDD drives, media devices, phones, tablets...regularly.

I didn't like that Optimus thing from the beginning. I had the first issues with it when it would reset display color calibration to default every time when Optimus would switch. Since the default color settings are abysmal, this was a big problem. I followed some instructions that I found somewhere on the net to disable some Asus or Intel bloatware. After I did it, it stopped resetting. I thought that was that, but now that you mentioned the Optimus, I think maybe this could have something to do with it. Though, I was getting the BSOD before I removed it.

I'm getting sick of it slowly and starting to regret saving some money for not going with Vaio S15.
Not only that Asus support is awful, but also drivers and non existent quality control.

 

[Teerex]

I, on the other hand, couldn't be more happier with mine, it works great for the second year running; & unlike Sony, ASUS actually allows you to install the freshest Nvidia Verde drivers. You got a bad apple, it happens to someone once in a while, that's why the RMA procedure exists.

I'm sorry about your display problems; although I envy you because you have keyboard backlight, subwoofer and a few more things I don't have (and a more powerful Nvidia), I heard that the matte screen looks grainy and that the color profile is bad. Mine is glossy, so outside in the open it suffers from reflections, but then again, who uses a 17'3 incher outside? I don't

!!!
Just thought of another thing - have you ever flashed your BIOS since you bought it? Are you using the newest version available for your model? A BIOS glitch could easily be responsible for a problem like this one.
And again, if you don't see the BSOD anymore, ignore the lines just above this one.

 

[malus]

No need to envy the backlit keyboard. I personally use the external keyboard most of the time. After watching it for fun few days, I switched it off and never used it again. It's nice to have it for like 5min in a week, but not really useful. Even less so the subwoofer. I use my laptop as a desktop replacement, but I do change my location every few days, so after some time I just didn't bother to carry the sub with me anymore. If I really need good sound I use real hi-fi equipment or headphones. Sub is not really that good anyway to be carried around. Although, even without the subwoofer these speakers are the best I've heard on laptop.

My screen is not grainy, although I heard about that. It's actually excellent for a TN display, and once the colors are set properly, it can even be used for some serious graphics work. I use it along with calibrated wide gamut PVA and IPS displays, so I can compare. The default colors are EXTREMELY wrong though. B&C are way too strong. Colors oversaturated and with EXTREME blue hue. I mean really extreme. Unusable. So much that not only no color work can be done, but the actual Windows UI looks wrong. I don't know what Asus was thinking with that. However, once set right, it's the best TN display I have seen on a laptop. Or even desktop TN display actually.

What do you think, could that thing with resetting display color settings (before removal) had something to do with eventually broken GPU?

Yes. I flashed the latest (213) BIOS the moment it got out. It seemed to act the same on all BIOS versions.

 

[Teerex]

We shouldn't be discussing this so much if you're not having the problem any more.

A possible elimination of all possible software causes would also be a little extreme - you would have to reinstall Windows from scratch, using a clean bloatwareless disc downloded from digitalriver, for example.

My screen is also fabulous, It's a ChiMei display (CMO1726); the viewing angles, the brightness and contrast are all outstanding for a TN display. And I do the same things you do, I carry it around from place to place, use an external keyboard and plug in a hi-fi for sound (where available ). Maybe after a while I would think the same about the extras as you.

Here is an educational read about that BSOD error code - while reading bear in mind the Nvidia adapter is going to sleep (D3) and back from sleep independently - the rest of the system stays awake.

You can check which power state the Nvidia adapter is in in Device Manager. Go to the details tab for Nvidia, click Property and scroll to Power Data. Look at the top of the Value frame. When you stop using Nvidia, the Current power state should be D3 - (instantly!), when you use it again for any application it should be D0, also instantly.

 

[malus]

Unfortunately, after 9 BSOD free days I got the same BSOD again. Same scenario. Happened while on, but idle and with screen off (on default High performance power settings). I thought I was finally BSOD free, after reinstalling all the drivers because this was the longest period without the BSOD even though I used my laptop extensively in this period...wrong...

I will now try use it without the one 8GB RAM module and see what happens then.

 

[malus]

I tried it with 8gb. It didn't help. Still got BSODed the same way. Then, I tried it without the SSD. I copied the system partition to another HDD and got BSODed again few days into using it. So I think this now excludes everything I could've tested myself.
The last straw to hold on is a fresh Windows 8 installation, free of all Asus drivers, apps and bloatware. I use only what's provided by windows update. No BSODs so far, after 5 days 24/7 uptime. If I get BSODed again, I fear I'll break my Asus into little pieces instead of bringing it in...I really got sick of it. Especially the idiotic Asus support. Those guys are beyond repair.

 

[malus]

No. I spoke too soon. Same old BSOD on Windows 8 too.
There is nothing more left to do. I'm sending it back for repair. Since I know how the service center works, I know I will be without it for few months...
Thanks guys for all the work you've done to try to help me.
Cheers!

 

[Teerex]

I'm sorry for being right, malus, in that it seems that it was a hardware error. I sympathise with you, and I wish to share this with you - my first N73SV had some scratches on the aluminum lid cover. I returned it and was without it for a month and a half. I got the laptop I'm writing this from, with a better screen, newer hard drive model, better RAM brands. According to the production week of the RAM modules, it was assembled specifically for me , they were brand new. I hope you will find the same satisfaction with the returned computer as I have and that you will not wait for too long.

Make sure you make a system image before you return it, it will make the return an easier and quicker hop into the saddle.