Driver_power_state_failure

My R3 frequently bluescreens on me. It usually will bluescreen when waking up from Sleep. Sometimes it will wake up with no problem. The other times, the screen will remain blank while the AlienFX lights come on and the Alien's eyes flash (indicating HDD access, I believe). Sometimes the Caps Lock light will respond when pressed, other times it won't. After being in one of these states for a couple of minutes, the system will bluescreen with the fault being DRIVER_POWER_STATE_FAILURE. It will do it plugged in or on battery. Here are some of the bluescreen messages I have recieved:

05/03/12
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 9f
BCP1: 0000000000000003
BCP2: FFFFFA800989AA10
BCP3: FFFFF80000B9C3D8
BCP4: FFFFFA800738A880
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\050312-10810-01.dmp
C:\Users\Benjamin\AppData\Local\Temp\WER-24866-0.sysdata.xml

05/03/12
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 9f
BCP1: 0000000000000003
BCP2: FFFFFA8007FF1A10
BCP3: FFFFF800046113D8
BCP4: FFFFFA800A22D610
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\050312-11778-01.dmp
C:\Users\Benjamin\AppData\Local\Temp\WER-37596-0.sysdata.xml

05/02/12
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 9f
BCP1: 0000000000000003
BCP2: FFFFFA800987CA10
BCP3: FFFFF80000B9C3D8
BCP4: FFFFFA800CE3E9D0
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\050212-11731-01.dmp
C:\Users\Benjamin\AppData\Local\Temp\WER-27144-0.sysdata.xml

04/26/12
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 9f
BCP1: 0000000000000003
BCP2: FFFFFA80077FE380
BCP3: FFFFF800046073D8
BCP4: FFFFFA8007A7C010
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\042612-15553-01.dmp
C:\Users\Benjamin\AppData\Local\Temp\WER-30373-0.sysdata.xml

I know it is a driver failure and updating my drivers may fix the problem. However, there are so many drivers, I'm not sure which one is causing it.

I have included the .txt report from DxDiag 64-bit.

I can upload the minidump files if someone can tell me how to.
Any help on this would be great. Thanks.

 

You have to archive the dump file as .zip and upload it as an attachement.

Or what you could do is download WhoCrashed, press the Analyze button and scroll down.
Your latest errors should be listed there and you can click one of the links to find answers.

 

Do as katalin says (zip and upload you dump files from C:\Windows\Minidump\) and I'll analyze your dumps for you.

 

Ok, it bluescreened again, so here is the most recent message. The minidump from this one is also in the .zip

05/03/12
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 9f
BCP1: 0000000000000003
BCP2: FFFFFA800987CA10
BCP3: FFFFF80000B9C3D8
BCP4: FFFFFA800D17D910
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\050312-11575-01.dmp
C:\Users\Benjamin\AppData\Local\Temp\WER-23946-0.sysdata.xml

Hope the minidumps provide a wealth of information. If you want to know any other specs, driver versions, etc. just ask.
Thanks!

 

Looks like you've have quite a few. I'll look it over and post back with a preliminary analysis.

edit: Preliminary Analysis:
All of the dump files that you uploaded report the same Stop Error 0x9F DRIVE_POWER_STATE_FAILURE. Here's one of your dumps:

Spoiler

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa8009879a10, fffff80000b9c3d8, fffffa8007b0a530}

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8009879a10, Physical Device Object of the stack
Arg3: fffff80000b9c3d8, Functional Device Object of the stack
Arg4: fffffa8007b0a530, The blocked IRP

Debugging Details:
------------------


DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  pci.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7928f

MODULE_NAME: pci

FAULTING_MODULE: fffff88000d44000 pci

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

STACK_TEXT: 
fffff800`00b9c388 fffff800`03152092 : 00000000`0000009f 00000000`00000003 fffffa80`09879a10 fffff800`00b9c3d8 : nt!KeBugCheckEx
fffff800`00b9c390 fffff800`030ef95c : fffff800`00b9c508 fffff800`00b9c508 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x34040
fffff800`00b9c430 fffff800`030ef7f6 : fffff880`0c260990 fffff880`0c260990 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`00b9c4a0 fffff800`030ef6de : 00000009`9e3fd5d5 fffff800`00b9cb18 00000000`00040a64 fffff800`0325cf08 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9caf0 fffff800`030ef4c7 : 00000002`3f4dd4c5 00000002`00040a64 00000002`3f4dd46c 00000000`00000064 : nt!KiTimerExpiration+0x1be
fffff800`00b9cb90 fffff800`030dc98a : fffff800`03259e80 fffff800`03267cc0 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cc40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cc00 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_3_ACPI_IMAGE_pci.sys

BUCKET_ID:  X64_0x9F_3_ACPI_IMAGE_pci.sys

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

The faulting module/driver was pci.sys which is a system file. However there is involvement of your GPU Driver (nvlddmkm.sys). As such the first thing that I would try is uninstall all of your GPU drivers and reinstalling them by following the instructions here: GeForce Driver Installation Guide A guide to ensure your drivers are installed properly. Make sure you reinstall with the latest drivers. During installation, choose custom installation and make sure you choose "Perform a clean install".

After reinstalling the GPU drivers, use your computer as you would normally and see if the BSOD's persist. Post back to let us know how it goes.

 

I followed the directions on the link you sent as best I could. The only files that did not delete were the files that dealt with the "Synaptics Pointing Device" and something else. I have experienced BSODs a little more often during normal operation (not in 'Sleep' mode exclusively), but especially battery. Could it be some driver or device that is being throttled to conserve power? I also think it could be from a Windows Update. I have the factory HDD image that Alienware put into the recovery partition and I haven't had the R3 for long, so I wouldn't mind copying my important stuff to a portable HDD and restoring to the factory image if you think we should test it pre-update.

Here are the three new BSODs I have gathered:

05/03/12
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 9f
BCP1: 0000000000000003
BCP2: FFFFFA800B17DA00
BCP3: FFFFF8000460F3D8
BCP4: FFFFFA80098AEC60
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\050312-15818-01.dmp
C:\Users\Benjamin\AppData\Local\Temp\WER-31496-0.sysdata.xml

05/04/12
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 9f
BCP1: 0000000000000003
BCP2: FFFFFA8007FD6A10
BCP3: FFFFF80000B9C3D8
BCP4: FFFFFA800CBB2C00
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\050412-12168-01.dmp
C:\Users\Benjamin\AppData\Local\Temp\WER-27144-0.sysdata.xml

05/04/12
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 9f
BCP1: 0000000000000003
BCP2: FFFFFA8007FD6A10
BCP3: FFFFF80000B9C3D8
BCP4: FFFFFA800CBB2C00
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\050412-12168-01.dmp
C:\Users\Benjamin\AppData\Local\Temp\WER-27144-0.sysdata.xml

Hope this helps in troubleshooting.

 

Which nvidia graphics card do you have? 460/560/580?

 

I have the nVidia 580m.
If you want more stats, there is the DxDiag report on the first post.
I can provide even more info if you want it.

 

if would call dell, maybe your card is bad and they can replace it, they did it with my 460
good luck

 

The last dumps that you uploaded were the exact same Stop Error. Please try running a system file check by following the instructions under option 2 here: SFC /SCANNOW Command - System File Checker

 

It says "Windows Resource Protection did not find any integrity violations."

 

Please enable Driver Verifier by following the instructions here: Using Driver Verifier to identify issues with Drivers. Please also read this before proceeding: DRIVER VERIFIER. It is very important that you create a system restore point before enabling Driver Verifier.
With DV enabled, please continue to use your computer normally. If/when DV finds a bad driver it will trigger a BSOD and create a dump with further info on your drivers. In the event of a BSOD, please upload the resulting dump file and then disable DV.

 

Ok, I followed the instructions as best I could. Here is the minidump that came from it. Let me know if it has the extended diagnostics. I'm not certain that I did it right.

 

That was indeed a verifier_enabled_minidump and it's still pointing to pci.sys as the faulting driver. However this time the nVidia driver was not involved. Instead it pointed to HDAudBus which is the Microsoft High Definition Bus driver for your audio. As such I would suggest uninstalling your audio drivers, clean with CCleaner or DriverSweeper and reinstalling the audio drivers.

 

I had a very similar error when I first got my machine, after doing all Windows updates it resolved and never happened again.

I don't know if you have done all updates, but it might be worth a try.

 

On my Device Manager, it says that I have both "IDT High Definition Audio CODEC" and "Intel(R) Display Audio" and both list the same Device ID that is associated with the hdaudbus.sys driver. How should I go about fixing it. Clean install both?

 

If you haven't already, that would be a worth a try. Good point

Yes, go ahead and reinstall both of them. Right click them on the device manager, click uninstall then restart. Use CCleaner or DriverSweeper to clean the registry entries then reinstall the them after a fresh restart.

 

Do you know where I could find the driver installers? Dell does not have any updates for these (least to my understanding..). Also, what is ACPI.sys? The Application Log file points that some BSODs were caused by it.

 

If you uninstall them and restart Windows should reinstall Intel Audio. For the IDT drivers, just get the latest version from the Dell website.

ACPI stands for Advanced Configuration and Power Interface. Usually Driver_Power_State_Failure stop errors will involve ACPI.sys and the file itself isn't usually a likely cause. There is a hotfix available from Microsoft but we'll eliminate all other possibilities before we apply the hotfix.

 

It might be the same problem I was having, I have the 460m and I would get the same bsod weekly until I figured out it wasn't the discrete GPU but the intel gpu included into sandy bridge. This is taking a risk but try flashing the modded A08 bios and disabling the IGPU all together and see if that fixes it.

 

Ok, it took a while for me to find it, but I removed both drivers, reinstalled IDT from Dell's site and reinstalled the Intel Display Audio driver by updating the Intel Graphics 3000 drivers (it seemed to include the audio drivers, too).

Edit: aznpos531, I've seen you post that McAfee can cause errors...
A version of McAfee is currently installed. Should I remove it and install Microsoft Security Essentials instead? At this point, I'm not sure it it is a hardware or software issue..

 

Do you have an SSD? If so, are you in RAID or AHCI mode?

 

Keep using your computer as you would normally for now. McAfee has been known to cause BSOD's but not in every case. In the long run I would suggest changing over to MSE but we'll change things one at a time while we try to troubleshoot the stop errors. Please keep us updated if any new BSOD's pop up.

 

Bartlett: Hmm.. This is interesting, I didn't know what I had till I opened it up and looked at it. I have a single 500Gb, 7200 RPM, Seagate Momentus XT. Isn't there some problems associated with the Momentus XT (Hybrid drive, I believe..)?

Aznpos531: McAfee was acting up and wouldn't "Activate" so I went ahead and installed MSE.

It has had the error a number of times, I haven't always waited for it to BSOD, however. Here are the dumps from the ones that I did wait for.

 

MSE works much better than McAfee IMO.
Your latest BSOD was blamed on nusb3xhc.sys which is your USB 3.0 driver. Please try reinstalling them. Also, do you have anything plugged into your USB 3.0 ports?

 

No, not usually. If I do use the USB ports, I by habit use the ones on the right side, the 2.0.

 

I double checked and it seems the USB 3.0 driver you have installed is from September 2010. Please reinstall with this one: NEC USB 3.0

 

Ok, will do. Also, I think there is an update for my hybrid firmware...

Edit:Should I uninstall it from Device Manager or just run the update?

 

Might be worth a try as well. Good luck

 

Ok, I installed the USB 3.0. Under the "Renesas Electronics USB 3.0..." (both devices) in Device Manager, they have a 2010 date stamp, but the driver files are version 2.0.26.0. So, I think they installed correctly...
Past that, I'm not going to install the Segate firmware update just yet. On one front it says I need it, on the other it doesn't find any updates...

I'll post back when I find out more about the Hybrid Drive update and any more BSODs.

Edit: It BSOD'd again. Here is the dump.

 

Are you running in AHCI mode? If so, run in RAID mode. This won't fix the problem until you format your hard drive or at the least, although I just recommend the format, you can run chkdsk /r and chkdsk /f in the CMD prompt and boot from your Windows 7 CD and do a repair. I believe I had the same problem as you when I first received my R3 running in AHCI mode. Regardless of my efforts to make it work under that mode, it just didn't. Thus I had to run in RAID mode and format the SSD. I am almost 100% sure my solution is for your specific problem.

 

Hmm... well in BIOS, I have the ATA, AHCI and RAID mode choices and RAID was the one already selected.

 

Hmm I see. Try running "sfc.exe /scannow" in the CMD prompt to replace any problem files. If that doesn't fix it, I would suggest following my aforementioned steps but instead of going from AHCI to RAID, try going from RAID to AHCI. Make sure you follow the driver installation guide over here as well. Let me know what happens.

 

You latest dump file indicated usbhub.sys as the cause. Please follow the instructions here: USB Driver - General Fix for Problems

SFC system file checker as suggested by Bartlett is a good suggestions as well. Here are the instructions for your reference: SFC /SCANNOW Command - System File Checker. You'll want to follow option 2.
I would save the repair install (instructions: Repair Install) and changing SATA Operation modes (requires a clean install of Windows) as a last, all-else-has-failed option.

 

I installed the USB driver and still experienced the error. Don't think I waited for the bluescreen to appear, I'll check the minidump and upload it if there is a new one.
I also switched to AHCI mode on BIOS. Windows 7 installed the drivers for the controllers and worked like normal. Sleep, however, still caused the computer to malfunction.
Some additional information: Hybrid Sleep and Hibernate functions also fail. It will open up into a similar state as when Sleep fails. I have to reboot and delete 'recovery data' or whatever it was that the computer stored prior to shutting off.
I also checked the event logs. Apparently the first events occurred on 4/4/12. The first BlueScreen event shows up on 4/18/12. And that seems right because I don't remember having this issue for the first couple of weeks. Is it possible it was a Windows Update?

 

Another member here posted that he experienced BSOD's after a Windows Update and after a fresh install of Windows with no updates the BSOD's seem to have gone away. However I'm up to the latest updates and I haven't had any problems.
Have you confirmed whether there is a firmware update?

 

Well, the website says that for the ST95005620AS drive, SD28 is the new firmware. I am currently running DEM4. However the "firmware check' they did said that there were no updates and that usually the oem is responsible for publishing updates... also that it should not be part of troubleshooting unless other checks are done (file system error checking, virus scanning).

 

Well, I restored my computer to the factory image and did not allow windows update to run. It has been working fine in the past couple of weeks since I did it. It has had a 9f error about twice, but besides that, it sleeps and hibernates properly. I'm not sure what the problem was.