BSOD: Driver Power State Failure ntoskrnl.exe 0x9F

[Darkness Within]

Hello,

I've been having bsod's for a while ever since I disabled the Automatic Restart. I'm going to say that I figure it might have something to do with my Toshiba external hdd but I hope I can get a fix for this. I've spent days researching online - I've tried to find if I had any drivers to update by going to my Device Manager but all "update driver" results I get are the same: they are up to date.

My zipped minidump files: http://sdrv.ms/YPs4lS


Win7 Home Premium x64
Dell Inspiron 580S
Intel Pentium G6950 2.80GHz
4GB of RAM
Service Pack 1

Most recent crash info:

[FONT=Segoe UI, Arial]On Sun 2/24/2013 1:44:16 AM GMT your computer crashed[/FONT]
[FONT=Segoe UI, Arial]crash dump file: C:\Windows\Minidump\022313-16130-01.dmp[/FONT]
[FONT=Segoe UI, Arial]This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x75C40) [/FONT]
[FONT=Segoe UI, Arial]Bugcheck code: 0x9F (0x3, 0xFFFFFA80059EB060, 0xFFFFF80000B9C518, 0xFFFFFA80074604B0)[/FONT]
[FONT=Segoe UI, Arial]Error: [FONT=Segoe UI, Arial]DRIVER_POWER_STATE_FAILURE[/FONT][/FONT]
[FONT=Segoe UI, Arial]file path: C:\Windows\system32\ntoskrnl.exe[/FONT]
[FONT=Segoe UI, Arial]product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT][/FONT]
[FONT=Segoe UI, Arial]company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT][/FONT]
[FONT=Segoe UI, Arial]description: NT Kernel & System[/FONT]
[FONT=Segoe UI, Arial]Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.[/FONT]
[FONT=Segoe UI, Arial]This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. [/FONT]
[FONT=Segoe UI, Arial]The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. [/FONT]
​

Any help is greatly appreciated!

 

[Dinesh]

Hi and welcome to the forums.

Seems like a core Kernel level issue.

Things to do:

Run System File Checker to verify/repair the integrity of system files.
Full tutorial here: http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Uninstall COMODO Internet Security and replace it with Microsoft Security Essentials - Microsoft Windows
Update it and run a full scan.

Go to Start>Run
Type MSCONFIG and press Enter.
Click on Startup tab, now click on Disable All.
Click Apply and OK. Reboot the system.

In addition, run chkdsk /f to repair corrupt hard drive sectors.
Full tutorial here: http://www.sevenforums.com/tutorials/433-disk-check.html

If all of the above fails, as a test, I'd suggest you to Enable Driver Verifier to find out which driver/software is causing the BSOD. Once you enable it, expect some frequent BSODs. After 24 hrs, disable the Driver Verifier and re-upload the dump files for analysis.

Let us know if it works.

The below is for information purpose only:

BugCheck Analysis:

ADDITIONAL_DEBUG_TEXT:  
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.

MODULE_NAME: nt

FAULTING_MODULE: fffff80002e56000 nt

DEBUG_FLR_IMAGE_TIMESTAMP:  503f82be

DRVPOWERSTATE_SUBCODE:  3

DEVICE_OBJECT: fffffa8005bca060

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x9F

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002f3f6d2 to fffff80002ed4fc0

STACK_TEXT:  
fffff800`00b9c4c8 fffff800`02f3f6d2 : 00000000`0000009f 00000000`00000003 fffffa80`05bca060 fffff800`00b9c518 : nt+0x7efc0
fffff800`00b9c4d0 00000000`0000009f : 00000000`00000003 fffffa80`05bca060 fffff800`00b9c518 fffffa80`04bb94d0 : nt+0xe96d2
fffff800`00b9c4d8 00000000`00000003 : fffffa80`05bca060 fffff800`00b9c518 fffffa80`04bb94d0 00000000`00000000 : 0x9f
fffff800`00b9c4e0 fffffa80`05bca060 : fffff800`00b9c518 fffffa80`04bb94d0 00000000`00000000 00000000`00000000 : 0x3
fffff800`00b9c4e8 fffff800`00b9c518 : fffffa80`04bb94d0 00000000`00000000 00000000`00000000 fffff800`0307cb20 : 0xfffffa80`05bca060
fffff800`00b9c4f0 fffffa80`04bb94d0 : 00000000`00000000 00000000`00000000 fffff800`0307cb20 fffffa80`00000002 : 0xfffff800`00b9c518
fffff800`00b9c4f8 00000000`00000000 : 00000000`00000000 fffff800`0307cb20 fffffa80`00000002 00000000`00018000 : 0xfffffa80`04bb94d0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt+7efc0
fffff800`02ed4fc0 48894c2408      mov     qword ptr [rsp+8],rcx

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt+7efc0

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  ntoskrnl.exe

BUCKET_ID:  WRONG_SYMBOLS

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

 

[Arc]

Alongwith everything suggested by Dinesh, opt for updating the driver of 802.11 USB Wireless LAN Card from MediaTek - Downloads Windows. If the updates are not available, Stop using that extremely old device, and uninstall its drivers.

Scan the system for possible virus infection, too.

• Anti-rootkit utility TDSSKiller

 

[Darkness Within]

Hello,

I want to thank both of you, Dinesh and Arc. I've updated my USB Wireless driver (I'll probably replace with something newer in the upcoming weeks) and done the first half of Dinesh's recommendation. I have not had a BSOD since I've done this so turning off the computer at night isn't nightmare inducing. If it happens again, I will run the driver verifier and go from there.

Thank you again for all your help!

 

[Dinesh]

Sounds great!

 

[Arc]

Good to know. If problems persist, let us know.