Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

DRIVER_POWER_STATE_FAILURE, BSOD, windows 8.1

brand new Asus Vivobool

  • Please log in to reply

#1
neveragainasus

neveragainasus

    New Member

  • Member
  • Pip
  • 7 posts

Hi all, 

 

I have an issue with my new asus vivobook. It is only a few months old and definitely under warranty however i require use of it everyday so cannot afford to have it taken in for repair.

 

Therefore i have been trying to solve this problem my self. Having updated every driver and trying many many things i am starting to run out of ideas. Once a dat i am getting a DRIVER_POWER_STATE_FAILURE  BSOD. This only occurs when running on battery or when waking up from sleep or hibernation.

 

 

Also everyday i get this error in my eventlog, i do not know if it is related; 

 

"The speed of processor 0 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report" I don't know how what this means. 

 

 

If anyone out there is happy to help me it would be greatly appreciated, i am computer literate so feel free to ask for any information what so ever. 

 

Cheers.

 

 

-------------------------BSOD-------------------------------

 

DRIVER_POWER_STATE_FAILURE
0x0000009f 00000000`00000003 ffffe001`4043f2c0 ffffd001`0bbed930 ffffe001`45fed360
ntoskrnl.exe
 
 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffffe000e842c060, Physical Device Object of the stack
Arg3: ffffd001947e9930, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffe000e843e680, The blocked IRP
 
Debugging Details:
------------------
 
 
DRVPOWERSTATE_SUBCODE:  3
 
IMAGE_NAME:  pci.sys
 
DEBUG_FLR_IMAGE_TIMESTAMP:  53d0f1d4
 
MODULE_NAME: pci
 
FAULTING_MODULE: fffff800e5800000 pci
 
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
 
BUGCHECK_STR:  0x9F
 
PROCESS_NAME:  System
 
CURRENT_IRQL:  2
 
ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
 
DPC_STACK_BASE:  FFFFD001947F0FB0
 
STACK_TEXT:  
ffffd001`947e98f8 fffff800`a5810586 : 00000000`0000009f 00000000`00000003 ffffe000`e842c060 ffffd001`947e9930 : nt!KeBugCheckEx
ffffd001`947e9900 fffff800`a58104a6 : ffffe000`e843ee78 00000000`ffffffff 00000000`00000000 fffff800`a565a190 : nt!PopIrpWatchdogBugcheck+0xde
ffffd001`947e9960 fffff800`a5656760 : 00000000`00000000 ffffd001`947e9ab0 ffffe000`e843eeb0 fffff800`a57ee628 : nt!PopIrpWatchdog+0x32
ffffd001`947e99b0 fffff800`a576b7ea : ffffd001`947c0180 ffffd001`947c0180 ffffd001`947cc2c0 ffffe000`ef79f080 : nt!KiRetireDpcList+0x4f0
ffffd001`947e9c60 00000000`00000000 : ffffd001`947ea000 ffffd001`947e4000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
 
 
STACK_COMMAND:  kb
 
FOLLOWUP_NAME:  MachineOwner
 
IMAGE_VERSION:  6.3.9600.17238
 
FAILURE_BUCKET_ID:  0x9F_3_ACPI_IMAGE_pci.sys
 
BUCKET_ID:  0x9F_3_ACPI_IMAGE_pci.sys
 
ANALYSIS_SOURCE:  KM
 
FAILURE_ID_HASH_STRING:  km:0x9f_3_acpi_image_pci.sys
 
FAILURE_ID_HASH:  {20ddeb92-07eb-ebdc-bd08-44da71ffbd68}
 
Followup: MachineOwner

 


Edited by neveragainasus, 06 October 2014 - 04:46 PM.

  • 0

Advertisements


#2
phillpower2

phillpower2

    Tech Staff

  • Technician
  • 20,007 posts

:welcome:   neveragainasus,

 

Have you checked the Device Manager for any yellow ! or red X.

 

Couple of suggestions;

 

1: Create a new restore point,  Go into Device Manager, Click on Batteries, right click on Microsoft ACPI - Compliant Method Battery, select Uninstall, restart the computer, allow Windows to reinstall it and test. 

 

2: Right click on the battery icon on the taskbar and make sure that it is set to the Balanced option.

 

3: Refresh Windows by following the steps below;

 

  1. Swipe in from the right edge of the screen, tap Settings, then tap Change PC settings.
    (If you're using a mouse, point to the top-right corner of the screen, move the mouse pointer down, click Settings, then click Change PC settings.)

  2. Tap or click Update and recovery, then tap or click Recovery.

  3. Under Refresh your PC without affecting your files, tap or click Get started.

  4. Follow the instructions on the screen.

Let us know how you get on.


  • 1

#3
neveragainasus

neveragainasus

    New Member

  • Topic Starter
  • Member
  • Pip
  • 7 posts

:welcome:   neveragainasus,

 

Have you checked the Device Manager for any yellow ! or red X.

 

Couple of suggestions;

 

1: Create a new restore point,  Go into Device Manager, Click on Batteries, right click on Microsoft ACPI - Compliant Method Battery, select Uninstall, restart the computer, allow Windows to reinstall it and test. 

 

2: Right click on the battery icon on the taskbar and make sure that it is set to the Balanced option.

 

3: Refresh Windows by following the steps below;

 

  1. Swipe in from the right edge of the screen, tap Settings, then tap Change PC settings.
    (If you're using a mouse, point to the top-right corner of the screen, move the mouse pointer down, click Settings, then click Change PC settings.)

  2. Tap or click Update and recovery, then tap or click Recovery.

  3. Under Refresh your PC without affecting your files, tap or click Get started.

  4. Follow the instructions on the screen.

Let us know how you get on.

 

Thanks for your reply phillpower2,  

 

There no no warning symbols next to anything in device manager. 

 

I have done as you instrusted with the Microsoft ACPI - Compliant Method Battery driver reinstallation, i will test my laptop throughout the rest of the day. 

 

Why should i make sure my battery is set to balanced? at the moment it is set to high performance, i would rather performance over battery life as i often deal with demanding modelling software. 

 

If i encounter another BSOD i will refresh Windows and report back. 

 

Cheers. 


  • 0

#4
phillpower2

phillpower2

    Tech Staff

  • Technician
  • 20,007 posts

Thanks for the update neveragainasus  :thumbsup:

 

Balanced power will make the notebook more stable.

 

Can I ask what modelling software it is that you are using.

 

You are welcome btw  :)


  • 0

#5
neveragainasus

neveragainasus

    New Member

  • Topic Starter
  • Member
  • Pip
  • 7 posts

Thanks for the update neveragainasus  :thumbsup:

 

Balanced power will make the notebook more stable.

 

Can I ask what modelling software it is that you are using.

 

You are welcome btw  :)

 

Yeah sure, mostly Leapfrog Geo and ArcGIS. I have not had a BSOD so far, although i am not convinced that the solution was so easy! 


Edited by neveragainasus, 08 October 2014 - 03:50 AM.

  • 0

#6
phillpower2

phillpower2

    Tech Staff

  • Technician
  • 20,007 posts

O ye of little faith let us hope that it was  :D

 

Thanks for the additional information, I was wanting to check how demanding on your hardware that the software was, looks like you may need an upgraded spec to get the best out of leapfrog;

 

Leapfrog Geo system requirements here

ArcGIS system requirements here


  • 0

#7
neveragainasus

neveragainasus

    New Member

  • Topic Starter
  • Member
  • Pip
  • 7 posts

Well i have not had another BSOD since, to think that was all it needed to be fixed . Wish i knew this 30 BSOD's ago !  Hope it didnt do any damage to my system crashing so much but i guess we can call this fixed! Thank you! 


  • 0

#8
neveragainasus

neveragainasus

    New Member

  • Topic Starter
  • Member
  • Pip
  • 7 posts

Sorry but i have to take back my last post.... I just had a BSOD while simply trying to open google chrome. Chrome was not responding and then shortly after i got a BSOD.

 

Crash details: 

 

101314-34046-01.dmp 13/10/2014 4:39:46 p.m. DRIVER_POWER_STATE_FAILURE 0x0000009f 00000000`00000003 ffffe001`a8e2c060 ffffd000`ff773930 ffffe001`a8f66b40 ntoskrnl.exe ntoskrnl.exe+153ca0 x64 ntoskrnl.exe+153ca0 C:\Windows\Minidump\101314-34046-01.dmp 4 15 9600 908,776 13/10/2014 4:42:06 p.m.

 
Event log: 
 
The program chrome.exe version 37.0.2062.124 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.
 Process ID: 1578
 Start Time: 01cfe697424ef26e
 Termination Time: 2
 Application Path: C:\Program Files (x86)\Google\Chrome\Application\chrome.exe
 Report Id: 8508844b-528a-11e4-82a3-10c37b67bb37
 Faulting package full name: 
 Faulting package-relative application ID: 
 
 
I am beginning to think i might have to try using Driver Verifier?  What other diagnostics can i try?   I think i will try windows memory diagnostics.
 
I know that there is a hot fix - http://support.microsoft.com/kb/975599 but it is only for winodws 7 or windows server 2008 R2 and wont let me install it. ...  
 
i will Refresh my pc now .

  • 0

#9
neveragainasus

neveragainasus

    New Member

  • Topic Starter
  • Member
  • Pip
  • 7 posts

Ok so looking more closely in my event viewer i get the following leading up to a BSOD.  Edit: actually these seem to be after the 4:39:46 p.m. time stamp of the BSOD..

 

-----------------------

 

20416 System Information 13/10/2014 4:41:06 p.m. Microsoft-Windows-Kernel-General 0 12 SYSTEM ASUS 0 264 6
3
9600
17238
0
0
2014-10-13T03:41:06.498505000Z
 
----------------------
20426 System Information 13/10/2014 4:41:07 p.m. Microsoft-Windows-FilterManager 0 6 SYSTEM Ryan-ASUS 0 264   
0x0
6
3
8
FileInfo
2014-02-23T01:13:10.000000000Z
 
 
--------------
 
20427 System Information 13/10/2014 4:41:07 p.m. Microsoft-Windows-FilterManager 0 6 SYSTEM Ryan-ASUS 0 252
0x0
6
3
3
Wof
2014-03-13T21:27:29.000000000Z
-------------------------
 
20428 System Information 13/10/2014 4:41:17 p.m. Microsoft-Windows-Ntfs 0 98 SYSTEM ASUS 0 204
C:
\Device\HarddiskVolume4
0
------------------------------- 
20430 System Information 13/10/2014 4:41:20 p.m. Microsoft-Windows-FilterManager 0 6 SYSTEM Ryan-ASUS 0 256
 
0x0
6
2
6
eamonm
2013-08-16T03:53:50.000000000Z
----------------------------- 
20430 System Information 13/10/2014 4:41:20 p.m. Microsoft-Windows-FilterManager 0 6 SYSTEM Ryan-ASUS 0 256
 
 
0x0
6
2
5
excfs
2013-11-19T11:00:10.000000000Z
 
-------------------- 
20431 System Information 13/10/2014 4:41:20 p.m. Microsoft-Windows-FilterManager 0 6 SYSTEM Ryan-ASUS 0 264
 
0x0
6
3
9
npsvctrig
2013-08-23T00:38:22.000000000Z
--------------------
 
20433 System Information 13/10/2014 4:41:21 p.m. Microsoft-Windows-Ntfs 0 98 SYSTEM Ryan-ASUS 0 204
D:
\Device\HarddiskVolume5
0
----------------------
 
20434 System Information 13/10/2014 4:41:21 p.m. MEIx64 0 2 Ryan-ASUS 40 144 Intel® Management Engine Interface driver has started successfully.  
 
Intel® Management Engine Interface driver has started successfully.
 
Event Data:
0000   00 00 00 00 01 00 00 00 00 00 00 00 02 00 07 40    ...............@
0010   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
0020   00 00 00 00 00 00 00 00                            ........        
 
-------------------
20435 System Information 13/10/2014 4:41:21 p.m. NETwNb64 0 7036 Ryan-ASUS 48 248 The \Device\NDMP2 service entered the Intel® Dual Band Wireless-N 7260 state.  
The \Device\NDMP2 service entered the Intel® Dual Band Wireless-N 7260 state.
 
Event Data:
0000   00 00 08 00 02 00 38 00 00 00 00 00 7C 1B 00 40    ......8.....|..@
0010   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
0020   00 00 00 00 00 00 00 00 57 44 52 56 D3 03 00 00    ........WDRV....
----------------------
20436 System Information 13/10/2014 4:41:21 p.m. Microsoft-Windows-Ntfs 0 98 SYSTEM Ryan-ASUS 0 296
\\?\Volume{41ef1919-1090-42bb-a613-a0e9da1a7339}
\Device\HarddiskVolume6
0
-------------------------------
20437 System Information 13/10/2014 4:41:21 p.m. Microsoft-Windows-Ntfs 0 98 SYSTEM Ryan-ASUS 0 296
\\?\Volume{c3a08008-e49c-4a1b-8f61-26f1523ac02e}
\Device\HarddiskVolume2
0
----------------------------------
20438 System Information 13/10/2014 4:41:21 p.m. Microsoft-Windows-Kernel-Processor-Power 47 55 SYSTEM Ryan-ASUS 0 228 Hyper-V logical processor 0 exposes the following power management capabilities:    Idle state type: 1 (3 state(s))    Performance state type: 1  Nominal Frequency (MHz): 2401  Maximum performance percentage: 100  Minimum performance percentage: 31  Minimum throttle percentage: 31  
Hyper-V logical processor 0 exposes the following power management capabilities:
 
Idle state type: 1 (3 state(s))
 
Performance state type: 1
Nominal Frequency (MHz): 2401
Maximum performance percentage: 100
Minimum performance percentage: 31
Minimum throttle percentage: 31
------------------------
20439 System Information 13/10/2014 4:41:21 p.m. Microsoft-Windows-Kernel-Processor-Power 47 55 SYSTEM Ryan-ASUS 0 228 Hyper-V logical processor 2 exposes the following power management capabilities:    Idle state type: 1 (3 state(s))    Performance state type: 1  Nominal Frequency (MHz): 2401  Maximum performance percentage: 100  Minimum performance percentage: 31  Minimum throttle percentage: 31  
 
Hyper-V logical processor 2 exposes the following power management capabilities:
 
Idle state type: 1 (3 state(s))
 
Performance state type: 1
Nominal Frequency (MHz): 2401
Maximum performance percentage: 100
Minimum performance percentage: 31
Minimum throttle percentage: 31
-----------------------------------------
20440 System Information 13/10/2014 4:41:21 p.m. Microsoft-Windows-Kernel-Processor-Power 47 55 SYSTEM Ryan-ASUS 0 228 Hyper-V logical processor 1 exposes the following power management capabilities:    Idle state type: 1 (3 state(s))    Performance state type: 1  Nominal Frequency (MHz): 2401  Maximum performance percentage: 100  Minimum performance percentage: 31  Minimum throttle percentage: 31  
 
Hyper-V logical processor 1 exposes the following power management capabilities:
 
Idle state type: 1 (3 state(s))
 
Performance state type: 1
Nominal Frequency (MHz): 2401
Maximum performance percentage: 100
Minimum performance percentage: 31
Minimum throttle percentage: 31
------------------------------------
20441 System Information 13/10/2014 4:41:21 p.m. Microsoft-Windows-Kernel-Processor-Power 47 55 SYSTEM Ryan-ASUS 0 228 Hyper-V logical processor 3 exposes the following power management capabilities:    Idle state type: 1 (3 state(s))    Performance state type: 1  Nominal Frequency (MHz): 2401  Maximum performance percentage: 100  Minimum performance percentage: 31  Minimum throttle percentage: 31  
 
Hyper-V logical processor 3 exposes the following power management capabilities:
 
Idle state type: 1 (3 state(s))
 
Performance state type: 1
Nominal Frequency (MHz): 2401
Maximum performance percentage: 100
Minimum performance percentage: 31
Minimum throttle percentage: 31
--------------------------
 

  • 0

#10
phillpower2

phillpower2

    Tech Staff

  • Technician
  • 20,007 posts

The cause of the previous and the latest crashes are not the same as in it looks like another driver or bad system setting is the cause this time.

 

Have you made any hardware or software changes since the computer became stable again.

Have you tried restoring the computer back to a point before the latest issue first happened. 

 

Try restoring the computers default settings in the BIOS, they may be listed as factory default or most stable settings, if there is an optimized settings option available please do not select it as it overclocks the computers hardware and will make things worse, there are different keys used on the various ASUS models but holding down the Del, Esc or F2 key when restarting the computer are common options, it make take a few restarts to gain access.

 

To see if we can identify any driver conflicts please refer to the copy/paste details below provided courtesy of jcgriff2  :thumbsup: 

 

1. Create a Windows System Restore Point -

Vista - START | type rstrui - create a restore point
Windows 7 - START | type create | select "Create a Restore Point"
Windows 8/ 8.1 - Using Microsoft System Restore (Windows*8) | HP® Support

2. Run Driver Verifier -

Windows 7 & Vista - START | type verifier 
Windows 8.1 & 8 - Press WIN +X keys | select "Command Prompt (Admin)" | type verifier 

Make these selections - 

1. Select 2nd option - Create custom settings (for code developers)
2. Select 2nd option - Select individual settings from a full list

3. Check these boxes -

▪ Special Pool 
▪ Pool Tracking 
▪ Force IRQL checking
▪ Deadlock Detection
▪ Security Checks (new as of Windows 7)
▪ Concurrency Stress Test (new as of Windows 8)
▪ DDI compliance checking (new as of Windows 8) 
▪ Miscellaneous Checks

4. Select last option - Select driver names from a list
5. Click on the Provider heading - sorts list by Provider
6. Check ALL boxes where "Microsoft" IS NOT the Provider
7. Click on Finish 
8. Re-boot
[/HIDE]

 

 

- If the Driver Verifier (DV) finds a violation, it will result in a BSOD

 

- After re-start, you may not be able to log on to normal Windows

... • Boot into SAFEMODE - tap the F8 key repeatedly during boot-up

... • Select "System Restore"

... • Choose the restore point that you created in step #1

 

- For Driver Verifier status

--- select last option, 1st screen -or-

--- type verifier /query (in a cmd/DOS screen)

- To turn Driver Verifier off - verifier /reset then re-boot

 

- The Driver Verifier needs to run as long as possible - even if the status screen appears clear.

- All future BSOD dumps must be VERIFIER_ENABLED_MINIDUMPs - otherwise the dump(s) are of no use

 

If your system does BSOD while the Driver Verifier is running, please retrieve the dump file from c:\windows\minidump and attach it to your next reply.

 

Please note that DV may not cause an instant BSOD and may need to be allowed to run for up to 72hrs, it will not affect the computers performance in any way.


  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP