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

malus · 11 Mar 2013

Hey guys,

I'm having random BSOD's on my Asus N76Vz since the day one. It's been going on for approx. 4 months now. I get approx 2 BSODs per week randomly. It's always the same thing; error 0x0000009f (DRIVER_POWER_STATE_FAILURE). It happens randomly, although it seems that it happens more often when computer is idle (not standby). I did several stress tests, and I never got the BSOD during the process.

There are few things I should mention;

1. Asus states that this computer supports a maximum 8GB RAM, however I am using 2x8GB, as many other people too (although they are not reporting problems similar to mine). I did run the memtest, and everything seemed to be fine.

2. My system drive is OCZ Agility 3 SSD 120GB, and recently I have flashed the latest available firmware, which seems to have reduced the number of BSODs slightly, but not eliminated. This could be accidental, but I thought I should mention it.

3. Many users of this series (Asus N76) are reporting issues with sound card producing crackling noise, when the sound card wakes up from longer period after not being used. This also affects my machine. As a workaround, many people set the Stereo Mix as Default recording device in Realtek HD Audio settings, which solves the crackling problem, and doesn't change anything in functionality. I have a feeling it has something to do with power management, which might also have something to do with BSODs.

4. There were some problems with Optimus driver switching from Intel integrated GPU to NVIDIA, which resulted in constant color settings resets. This got solved by uninstalling crappy Asus/Intel bloatware.

Regarding the drivers, I have tried all possible combinations I could think of. Especially the Nvidia GPU drivers. Now I'm using drivers provided as latest on Asus website. It doesn't seem to matter. Any drivers I try, I always get the BSOD eventually.

In normal conditions, I would've already send my latop to the service center, however, the only available service center, here where I live is notorious for extremely long waiting periods (30-180 days) and even worse, for returning computers in worse shape than they were shipped in. All kinds of bad things happen there, like breaking cases, stealing components and such stuff. And I want to avoid this if possible.

Otherwise than the BSOD's, once properly set up, this is a fine machine. That's also the reason why I have hung on it for so long inspite of BSOD's.

Please help,
Thanks

Dsprague · 11 Mar 2013

It looks like every one of your BSODs has been caused by your video card driver:

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa800d2d2a10, fffff80000b9c3d8, fffffa80143ce190}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : pci.sys

Followup: MachineOwner
---------

Looking through the history of your changing drivers, by checking the time stamps on your video card drivers the newest one you had installed was the driver Nvidia released during December of last year which was a known causer of BSODs. currently there is a driver for your video card available on the Nvidia website:NVIDIA DRIVERS 314.07WHQL

Before installing however please uninstall the current driver you have installed and follow this tutorial:Drivers - Clean Left over Files after Uninstalling

malus · 11 Mar 2013

Hm. Interesting. The NVIDIA driver I'm using right now is provided on ASUS support download site as 28th Feb 2013 version. I didn't bother to check the actual date/version nr. I was sure I was installing newer drivers from NVIDIA after December. I could be wrong though.

Regarding the NVIDIA driver removal, should I remove the drivers (NVIDIA Graphics Driver) from "Uninstal or change program" prior to using the Driver Sweeper in Safe Mode?

BTW Thanks a lot.

Dsprague · 11 Mar 2013

Regarding the NVIDIA driver removal, should I remove the drivers (NVIDIA Graphics Driver) from "Uninstal or change program" prior to using the Driver Sweeper in Safe Mode?

BTW Thanks a lot.

Yes and you are very much welcome.

malus · 11 Mar 2013

I did as you instructed.
- Removed the drivers
- Used Driver Sweeper in Safe Mode
- Installed 314.07 NVIDIA driver

I guess the time will tell. Hopefully, this will solve it.

malus · 12 Mar 2013

Unfortunately it didn't help. I just got the BSOD. It happened while laptop was at idle (wasn't used).

==================================================
Dump File : 031213-7675-01.dmp
Crash Time : 12.3.2013. 12:19:44
Bug Check String : DRIVER_POWER_STATE_FAILURE
Bug Check Code : 0x0000009f
Parameter 1 : 00000000`00000003
Parameter 2 : fffffa80`0d2d0a10
Parameter 3 : fffff800`00b9c3d8
Parameter 4 : fffffa80`14baf3f0
Caused By Driver : dxgmms1.sys
Caused By Address : dxgmms1.sys+1011b
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+75c40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\031213-7675-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 1.155.696
==================================================

SF Fiagonostic Tool folder is attached.

Dsprague · 12 Mar 2013

OK looking through the files it is the same BSOD and same apparent cause as before so please do the following:

Firstly uninstall Tuneup utilities it is likely doing more harm than good.

Next run the system file checker:

Go to Start and type in "cmd.exe" (without the quotes)
At the top of the search box, right click on the cmd.exe and select "Run as adminstrator"
In the black window that opens, type "SFC.EXE /SCANNOW" (without the quotes) and press Enter.
Let the program run and post back what it says when it's done.

Last run furmark, to check for GPU stability and over heating (anything above 80c):
FurMark: Graphics Card Stability and Stress Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net

FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature" (BurnIn test in newer versions).
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exit

malus · 12 Mar 2013

I uninstalled TuneUp Utilities. Restarted. I must say that I am using TuneUp for years and never had a single issue with it. I find it rather useful, since it has few powerful tools in one place.

I ran the "SFC.EXE /SCANNOW".
It said:
Windows Resource Protection did not find any integrity violations.

I'm running the Furmark for 17min now. After 5 mins it seemed to be set at 78-80C. No troubles so far.
However I didn't find an option to select "Multi-GPU". Looks like it is reading the data for Nvidia.
It says; OpenGL renderer: GeForce GT 650M/....
GPU 1 - GeForce GT 650M/....
etc...

EDIT: Furmark running for 30mins, still 78-80. No issues.

PS Usually I use active cooling pad, but not now. I tried to turn it on, and when the temp started to drop, I turned it back off.

I must say that I never got a feeling that the laptop is running hot. I'm using it sometimes for 3D rendering (CPU intensive) and CUDA video rendering (GPU intensive), and I never had any issues or instablities. It is also quiet. I hear the fans speeding up when loaded though. BSODs tend to happen when laptop is idle.

Dsprague · 12 Mar 2013

That's because you don't have multiple GPUs so a Multi-GPU test would be impossible, the only other GPU your laptop has is the On board graphics. Tune up utilities, registry cleaners, and all things of such a nature are really not needed in windows seven weather you know it or not windows seven does automatically most of the things that that program claims it does, the only thing windows 7 wont do is clean its own registry and that is because cleaning your registry is a terrible terrible idea. Most of the programs that "clean" your registry know less about it than you do.

The temperatures on your GPU are a little bit high try lifting the back of the laptop to get better air flow, or if you have one use a laptop cooling pad. But the good news is it doesn't seem you are getting any errors with furmark which leads me to one final trouble shooting step before I call on some one more experienced than myself:

Use this technique to "reset" your pagefile:
a ) Go to Start...Run...and type in "sysdm.cpl" (without the quotes) and press Enter.
-Then click on the Advanced tab,
-then on the Performance Settings Button,
-then on the next Advanced tab,
-then on the Virtual Memory Change button.
b ) In this window, note down the current settings for your pagefile (so you can restore them later on).
-Then click on the "No paging file" radio button, and
- then on the "Set" button. Be sure, if you have multiple hard drives, that you ensure that the paging file is set to 0 on all of them.
-Click OK to exit the dialogs.
c ) Reboot (this will remove the pagefile from your system)
d ) Then go back in following the directions in step a ) and re-enter the settings that you wrote down in step b ). Follow the steps all the way through (and including) the reboot.
e ) Once you've rebooted this second time, go back in and check to make sure that the settings are as they're supposed to be.

malus · 12 Mar 2013

Oh. Ok. I thought the onboard graphics would count as second GPU. Nevermind.
I am using a cooling pad. A good one. I just wasn't using it for the test on purpose.

Now regarding the reseting pagefile, by default it was set to "Automatically manage paging file size for all drives". And it said;
Minimum allowed: 16 MB
Recommended 24403 MB
Currently allocated 16269 MB

So what I did;
1. set it to none on both drives
2. rebooted
3. set it back to "Automatically manage paging file size for all drives"
4. rebooted
5. checked if it was as before last reboot (it was)

I'm not sure if I got that right. It seems so, when I'm reading your instructions.