Sign in with
Sign up | Sign in
Your question
Closed

Driver_power_state_failure BSOD - Windows 8.1

Last response: in Windows 8
Share
November 3, 2013 10:15:25 PM

Been having some problems with my Lenovo G500 laptop since updating to 8.1.

Everytime I try to change the MAC address of my wireless card (a Broadcom 802.11n wireless adapter) on the 'Advanced' Tab of the card (Under the Locally Administered MAC address setting), the window freezes (I can close it with Task Manager) and the wireless card becomes seemingly permanently disabled (unless I reboot/Shut down). I try to re-enable it and it says enabling but remains black outed and disabled. Once I try to reboot the laptop, the laptop hangs then the BSOD shows up with the error of Driver_power_state_failure. Googling it entails that something occurs when the system is put to sleep or waking up from sleep but my laptop is not going to sleep at all. I've been able to replicate the incident step by step and it always causes a BSOD.

I've updated the WLAN drivers (as well as most other drivers like the LAN, BIOS, etc.) as supplied by Lenovo's support page to the latest drivers and yet I still receive this error. Prior to going to 8.1, I was fine changing my MAC address. I've even tried to uninstall the card/drivers but the system just hangs for a long time stating that it is "uninstalling" but never proceeding anywhere. I always have to end up rebooting/shutting down it to re-enable my wireless. I have uninstalled it on SAFE mode which does uninstall it and when I reinstall the most recent driver (or even older versions) it still causes a BSOD.

I have wireless internet which operates fine but doing what I said earlier causes a BSOD that really irritates me to no end.

*Skydrive Minidumps: http://sdrv.ms/173wbA2

*Crash Dump from Whocrashed.exe:

On Mon 11/4/2013 1:08:46 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\110413-15937-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x150B36)
Bugcheck code: 0x9F (0x4, 0x12C, 0xFFFFE00000EB8040, 0xFFFFD00020472860)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 11/4/2013 1:08:46 PM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x9F (0x4, 0x12C, 0xFFFFE00000EB8040, 0xFFFFD00020472860)
Error: DRIVER_POWER_STATE_FAILURE
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 11/3/2013 12:46:16 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\110313-14218-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x150B36)
Bugcheck code: 0x9F (0x4, 0x12C, 0xFFFFE00006A98880, 0xFFFFD00020472860)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 11/3/2013 6:50:53 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\110313-13484-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x150B36)
Bugcheck code: 0x9F (0x4, 0x12C, 0xFFFFE00004073880, 0xFFFFD000205F6860)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 11/2/2013 1:33:09 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\110213-14203-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x150B36)
Bugcheck code: 0x9F (0x4, 0x12C, 0xFFFFE00001219040, 0xFFFFD000201FD860)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

*Bluescreen viewer (most recent crash):


Bug check string: DRIVER_POWER_STATE_FAILURE
Bug check code: 0x0000009f
Parameter 1: 00000000`00000004
Parameter 2: 00000000`0000012c
Parameter 3: ffffe000`00eb8040
Parameter 4: ffffd000`20472860
Processor: x64
Caused by driver: NETIO.SYS
Caused by address: NETIO.SYS+1ddb2
Crash address: ntoskrnl.exe+150b36


Any help or suggestions are greatly appreciated.
a b D Laptop
a b * Windows 8
November 4, 2013 10:38:44 AM

no permission to view skydrive file. or file not found.
you can run whocrashed.exe to get a first look at the cause of the failure.
Score
0
November 4, 2013 6:30:47 PM

johnbl said:
no permission to view skydrive file. or file not found.
you can run whocrashed.exe to get a first look at the cause of the failure.


I'm sorry. It has been awhile since I used Skydrive and I must have trekked the settings somehow and caused it to do something like that. I have used your suggestion to use whocrashed.exe and I've also added the details from Bluescreen viewer on the first post.
Score
0
Related resources
November 5, 2013 2:00:47 AM

Just to mention a few more details that I've done with the limited free time I have (due to work):
I have booted into safe mode and uninstalled my wireless adapter then reinstalled it on normal boot (and updating the driver) and it still causes BSOD.
Falling back to an earlier version of the driver still causes BSOD.
I am internet sharing (using netsh wlan set hostednetwork on command prompt) which didn't cause any problems prior to updating to 8.1. Doing so doesn't cause any problems.
Googling the error states that it usually occurs due to putting the laptop to sleep or waking it up from sleep but I can put my laptop to sleep and wake it up anytime I want and the laptop has no problems on doing so (still retains Wireless internet, etc.).
It always will BSOD when I tinker around with the advanced settings on my wireless adapter, especially if I enter a custom MAC (it will freeze, I shut down then my laptop upon reboot will use the custom MAC I entered- then if I remove the custom MAC it will freeze and BSOD again).
I am currently running verifier.exe as described on http://www.sevenforums.com/tutorials/101379-driver-veri... and for the few hours it has been on nothing adverse has happened.
Score
0
a b D Laptop
a b * Windows 8
November 5, 2013 9:59:24 AM

driver did not release a lock when it attempted to stop. This caused a system bugcheck after 300 seconds of waiting.

I would update the lenova power management drivers to a current version for 8.1 ver 8.0.2.14
dated oct 16 2013.

I am not sure what net card you have but, it sounds like a bug when you change the mac address.
I would suggest doing a stop on the network driver, changing the address, then doing a start on the driver and see if you still get a bugcheck after 300 seconds. Other than that I would try to get a new driver directly from the network vendor.

the bugcheck, I looked at had Lenovo bios v 1.04 dated 4/72013 and looked like a clean install of windows 8.1 without any vendor specific drivers installed. I will take a look at another one of your crash dumps to see if BIOS update was applied correctly.

Score
0
a b D Laptop
a b * Windows 8
November 5, 2013 11:02:25 AM

second crash had same info:
2: kd> kA
Child-SP RetAddr Call Site
ffffd000`35b2c160 fffff803`7d8bddae nt!KiSwapContext+0x76
ffffd000`35b2c2a0 fffff803`7d8bd847 nt!KiSwapThread+0x14e
ffffd000`35b2c340 fffff803`7d8e04f8 nt!KiCommitThreadWait+0x127
ffffd000`35b2c3a0 fffff800`00f86009 nt!KeWaitForSingleObject+0x248
ffffd000`35b2c440 fffff800`00f447f2 ndis!ndisPnPIrpRemoveDevice+0xa5
ffffd000`35b2c4a0 fffff800`00314660 ndis!ndisPnPDispatch+0x1d2
ffffd000`35b2c510 fffff800`002a0cf3 Wdf01000!FxPkgFdo::p rocessRemoveDeviceOverload+0x94
ffffd000`35b2c540 fffff800`00288936 Wdf01000!FxPkgPnp::_PnpRemoveDevice+0x127
ffffd000`35b2c5b0 fffff800`00283a18 Wdf01000!FxPkgPnp::D ispatch+0xd2
ffffd000`35b2c620 fffff803`7dca074a Wdf01000!FxDevice::D ispatchWithLock+0x7d8


BIOS version v 1.07 dated 07/05/2013
I think you might be able to find drivers released after windows 8.1 shipped.



Score
0
November 5, 2013 5:38:15 PM

johnbl said:
second crash had same info:
2: kd> kA
Child-SP RetAddr Call Site
ffffd000`35b2c160 fffff803`7d8bddae nt!KiSwapContext+0x76
ffffd000`35b2c2a0 fffff803`7d8bd847 nt!KiSwapThread+0x14e
ffffd000`35b2c340 fffff803`7d8e04f8 nt!KiCommitThreadWait+0x127
ffffd000`35b2c3a0 fffff800`00f86009 nt!KeWaitForSingleObject+0x248
ffffd000`35b2c440 fffff800`00f447f2 ndis!ndisPnPIrpRemoveDevice+0xa5
ffffd000`35b2c4a0 fffff800`00314660 ndis!ndisPnPDispatch+0x1d2
ffffd000`35b2c510 fffff800`002a0cf3 Wdf01000!FxPkgFdo::p rocessRemoveDeviceOverload+0x94
ffffd000`35b2c540 fffff800`00288936 Wdf01000!FxPkgPnp::_PnpRemoveDevice+0x127
ffffd000`35b2c5b0 fffff800`00283a18 Wdf01000!FxPkgPnp::D ispatch+0xd2
ffffd000`35b2c620 fffff803`7dca074a Wdf01000!FxDevice::D ispatchWithLock+0x7d8


BIOS version v 1.07 dated 07/05/2013
I think you might be able to find drivers released after windows 8.1 shipped.





I've also ran SFC /scannow a few times and it has come back finding corrupted files that it was unable to fix/repair. I've attached a compressed folder to the skydrive account I mentioned in the first post with the CBS log from the scan. I've also updated the driver for power management as well as for all current drivers that I could find from Lenovo that apply to my laptop.
Score
0
a b D Laptop
a b * Windows 8
November 5, 2013 11:09:00 PM

Try this command to repair the corrupted files from a online version
dism.exe /online /cleanup-image /restorehealth

then attempt to run your sfc.exe /scannow command again to see if you get a clean image.
Score
0
November 6, 2013 1:34:54 AM

johnbl said:
Try this command to repair the corrupted files from a online version
dism.exe /online /cleanup-image /restorehealth

then attempt to run your sfc.exe /scannow command again to see if you get a clean image.


I ran that command on command prompt and then ran sfc /scannow several times and now sfc finds that there are no longer any integrity violations.

However, the original problem of spoofing my MAC on my wireless card still produces BSOD:

*whocrashed.exe*:

On Wed 11/6/2013 8:56:48 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\110613-16093-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x150B36)
Bugcheck code: 0x9F (0x4, 0x12C, 0xFFFFE00006FC7040, 0xFFFFD000201FD860)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

*Bluescreenviewer*

Dump File: 110613-16093-01.dmp
Crash Time: 11/6/2013 6:56:48 PM
Bug check string: DRIVER_POWER_STATE_FAILURE
Bug check code: 0x0000009f
Parameter 1: 00000000`00000004
Parameter 2: 00000000`0000012c
Parameter 3**: ffffe000`06fc7040
Parameter 4**: ffffd000`201fd860
Processor: x64
Caused by driver: NETIO.SYS
Caused by address: NETIO.SYS+1ddb2
Crash address: ntoskrnl.exe+150b36

**=different values than the original Bluescreenviewer posted on first post.

This link provides an updated dump analysis as well as my laptop's driver list and other useful info:

http://sdrv.ms/1aEoHJN

It's compressed to save space.
Score
0
a b D Laptop
a b * Windows 8
November 6, 2013 8:15:51 AM

BCM43XX Broadcom 802.11 Networ Kernel 8/7/2013 2:04:47PM
bcmfn2 bcmfn2 Service Kernel 8/3/2013 9:59:11 AM

can you stop the service for the Broadcom driver before you change the mac address? Wait 3 mins to see if you get a bugcheck. If no bugcheck then change the mac address and restart the service?
(just want to see if the shutdown of the driver is broken or if change of the mac address is required).

you might also try booting windows 8 into safe mode and see if you can change the driver there. (if it bugchecks, it is going to be a driver bug in bcmwl63a driver)

-maybe disconnect the device from the router for 3 mins before changing the address. (so there is no pending send/recv packets before the device is removed for the MAC address change)

Score
0
November 7, 2013 2:40:10 AM

johnbl said:
BCM43XX Broadcom 802.11 Networ Kernel 8/7/2013 2:04:47PM
bcmfn2 bcmfn2 Service Kernel 8/3/2013 9:59:11 AM

can you stop the service for the Broadcom driver before you change the mac address? Wait 3 mins to see if you get a bugcheck. If no bugcheck then change the mac address and restart the service?
(just want to see if the shutdown of the driver is broken or if change of the mac address is required).

you might also try booting windows 8 into safe mode and see if you can change the driver there. (if it bugchecks, it is going to be a driver bug in bcmwl63a driver)

-maybe disconnect the device from the router for 3 mins before changing the address. (so there is no pending send/recv packets before the device is removed for the MAC address change)



I tried to disable the wireless adapter but that also resulted in a BSOD.

I booted up under legacy mode and into Safe mode and uninstalled the adapter successfully, then updated it to the most current driver only for it to again cause a BSOD.

I've yet to try the last method do to lack of time but I will get back to you when I have the time to try it.

I've added more files to view on Skydrive on the most recent crashes:

http://sdrv.ms/17OJVSQ
Score
0
a b D Laptop
a b * Windows 8
November 8, 2013 9:25:38 AM

The driver was not handling the outstanding packets (irps) when it went to shutdown. It has a 300 second timer before the bugcheck goes off. (sorry I said 3 mins but it should be 300 seconds)

- leaves you needing a updated driver or to find a work around to make sure there are no pending packets before you make your configuration change.
Score
0
November 8, 2013 7:59:39 PM

johnbl said:
The driver was not handling the outstanding packets (irps) when it went to shutdown. It has a 300 second timer before the bugcheck goes off. (sorry I said 3 mins but it should be 300 seconds)

- leaves you needing a updated driver or to find a work around to make sure there are no pending packets before you make your configuration change.


I tried what you suggested (using 300 seconds instead of 3 minutes) by disconnecting from the router (and not being on an Ethernet cable) and trying to change the MAC address but it resulted in the same BSOD with whocrashed.exe and bluescreenview displaying the exact same data.

I'm thinking that either the driver is not working correctly, that the wireless card is defective or that some combination with an incompatibility with Windows 8.1 caused this situation (as I was able to do this willy-nilly with just Windows 8).

I've already purchased a different brand of wireless card (an Intel) and plan to try switch the broadcom card with it as I've been frustrated that Broadcom's website doesn't offer any drivers and whatnot for their cards.

Lenovo does, however, whitelist the wireless cards you can use (I don't think they do that with the RAM or HD since the manual does instruct you on how to change them but neglects to mention that the wireless card can also be swapped) but from this website:

http://www.bios-mods.com/forum/Thread-Request-Lenovo-G5...

It is possible to flash the BIOS to eliminate this restriction (that is one example- there are others who have been successful in swapping their cards). I plan to flash my BIOS and swap the card in to test if the card/driver is the problem or something else.
Because of Veteran's Day my card's shipping from Amazon will be delayed until the end of next week so I can't mention anything yet.

Failing that, I plan to factory restore my laptop or roll back from Windows 8.1 to see if the problem still persists. After that, if it still persists than the laptop is still under warranty and I may have to send it in for repairs and whatnot.

If you have any suggestions prior to swapping my card by the end of next week then I am free and willing to try anything as I believe I've nearly exhausted any method to solve this dilemma. From just doing some independent research it seems that people with a similar problem have trouble when their computer sleeps or wakes up from sleep but I've had absolutely no problem with either task and it only seems to occur when the advanced tab's settings are modified (Not only changing the MAC but also enabling/disabling/auto on other settings).

Thanks again for the help and I'll report back if swapping the card does fix it or not.
Score
0
December 22, 2013 1:14:12 AM

Mr C G said:
Careful what you say; you could get banned for suggesting such things.

It could be that Windows 8.1 is faulty.
Note
A couple of accounts have already been banned recently and posts removed by a mod at tomshardware for pointing out that the account holders two i7 computers randomly BSoD re-boot themselves, but their older computers running Windows 8.1 do not auto-reboot.

So, one might ask; does Intel or Miscrosoft fund any of this site?


Whatever the case, the problem turned out to be the wireless card and not Windows 8 or 8.1. Leave it to Lenovo for using junky Broadcom cards. An Intel card that I replaced it with worked flawlessly in both OS's.

This thread should be closed even though I didn't find any answer here.
Score
0
!