DRIVER_POWER_STATE_FAILURE BSOD - New Asus Vivobook - Windows 8.1 x64

N

nzasus

New member
Joined
Oct 26, 2014
Posts
3
OS - Windows 8.1 x64
OEM version - pre installed on system

Laptop is only about 3 months old

CPU - i7-4500U
VIDEO CARD - Nvida Geforce 840M
MOTHERBOARD - ASUSTek computer inc. S551LN
SYSTEM MANUFACTURER - ASUS
MODEL - ASUS A551LN - LAPTOP


I have a Asus Vivobook that is well under warranty however i don't want to have my laptop sent away and be without a computer for weeks so i am trying to solve the BSOD myself.


I have had a total of 34 (DRIVER_POWER_STATE_FAILURE) crashes in just a couple months.

Perfmon failed to generate a report from an elevated command prompt with the following error:

[TABLE="width: 100%"]
[TR]
[TD][/TD]
[TD]An error occured while attempting to generate the report.[/TD]
[TD][/TD]
[/TR]
[TR]
[TD][/TD]
[TD]The operator or administrator has refused the request.[/TD]
[/TR]
[/TABLE]

I also get the below error in my event log, although i do not know if it is related or not


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

The BSOD occurs 90% of the time when running on battery power, only very rarely do i get the error when the laptop is plugged in. Also when going to sleep or hibernation it will end in the same BSOD half the time. I cannot figure out any trends in when the BSOD occur, its seems to be random. Sometimes just opening google chrome will cause a crash.

Reinstalling the Microsoft ACPI - Compliant Method Battery driver seemed to fix the BSOD error for a week? might have just been luck.


Without really knowing what i'm doing i ran a !irp:




*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, ffffe000e842c060, ffffd001947e9930, ffffe000e843e680}
Probably caused by : pci.sys
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
* *
* 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
---------


I then ran driver verifier and instantly got a DRIVER_VERIFIER_IOMANAGER_VIOLATION BSOD of which you can see below:


102614-22171-01.dmp 26/10/2014 4:44:07 p.m. DRIVER_VERIFIER_IOMANAGER_VIOLATION 0x000000c9 00000000`0000021f fffff803`9f088934 ffffcf80`58c9adc0 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+153ca0 x64 ntoskrnl.exe+153ca0 C:\Windows\Minidump\102614-22171-01.dmp 4 15 9600 266,960 26/10/2014 4:51:29 p.m.

i then used WinDbg on this BSOD and got the following;

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C9, {21f, fffff8039f088934, ffffcf8058c9adc0, 0}
Probably caused by : ntkrnlmp.exe ( nt!ViGenericDriverEntry+0 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 000000000000021f, A driver has not filled out a dispatch routine for a required IRP major function.
Arg2: fffff8039f088934, The address in the driver's code where the error was detected.
Arg3: ffffcf8058c9adc0, IRP address.
Arg4: 0000000000000000
Debugging Details:
------------------


BUGCHECK_STR: 0xc9_21f
DRIVER_VERIFIER_IO_VIOLATION_TYPE: 21f
FAULTING_IP:
nt!ViGenericDriverEntry+0
fffff803`9f088934 4883ec38 sub rsp,38h
FOLLOWUP_IP:
nt!ViGenericDriverEntry+0
fffff803`9f088934 4883ec38 sub rsp,38h
IRP_ADDRESS: ffffcf8058c9adc0
DEVICE_OBJECT: ffffe000e156f400
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME: System
CURRENT_IRQL: 2
ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
LOCK_ADDRESS: fffff8039ecd7d40 -- (!locks fffff8039ecd7d40)
Resource @ nt!PiEngineLock (0xfffff8039ecd7d40) Available
WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.
1 total locks
PNP_TRIAGE:
Lock address : 0xfffff8039ecd7d40
Thread Count : 0
Thread address: 0x0000000000000000
Thread wait : 0x0
LAST_CONTROL_TRANSFER: from fffff8039f0786b0 to fffff8039eb56ca0
STACK_TEXT:
ffffd001`5bf561a8 fffff803`9f0786b0 : 00000000`000000c9 00000000`0000021f fffff803`9f088934 ffffcf80`58c9adc0 : nt!KeBugCheckEx
ffffd001`5bf561b0 fffff803`9f07b171 : fffff803`9f06b470 fffff803`9f088934 ffffcf80`58c9adc0 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
ffffd001`5bf561f0 fffff803`9f08472e : ffffcf80`58c9adc0 00000000`0000021f fffff803`9f088934 00000000`00000000 : nt!ViErrorFinishReport+0x10d
ffffd001`5bf56250 fffff803`9f07ac6b : ffffd001`5bf56358 ffffe000`e156f400 ffffe000`e0b111c8 ffffe000`e156f050 : nt!VfWmiVerifyIrpStackDownward+0xfe
ffffd001`5bf562f0 fffff803`9f0717dd : ffffe000`e156f050 ffffd001`5bf56450 ffffcf80`58c9adc0 ffffe000`e0b111c8 : nt!VfMajorVerifyIrpStackDownward+0x83
ffffd001`5bf56350 fffff803`9f077d59 : ffffcf80`58c9adc0 00000000`00000000 ffffe000`e156f050 ffffe000`e0a26c90 : nt!IovpCallDriver1+0x5e5
ffffd001`5bf564a0 fffff803`9f06c88c : ffffcf80`58c9adc0 00000000`00000002 00000000`00000000 00000000`00000000 : nt!VfBeforeCallDriver+0x165
ffffd001`5bf564d0 fffff803`9f088ec9 : ffffcf80`58c9adc0 ffffe000`e156f400 00000000`00000002 ffffe000`e0a26c90 : nt!IovCallDriver+0x348
ffffd001`5bf56520 fffff803`9f06c911 : ffffe000`e156f550 ffffcf80`58c9adc0 00000000`00000000 fffff803`9f078471 : nt!ViFilterDispatchGeneric+0xd1
ffffd001`5bf56560 fffff803`9f0783d6 : ffffcf80`58c9adc0 ffffe000`e156f400 00000000`00000000 ffffe000`dfdcaca0 : nt!IovCallDriver+0x3cd
ffffd001`5bf565b0 fffff803`9f084626 : ffffe000`dba1d470 ffffd001`5bf56769 00000000`00000001 ffffe000`dba1d470 : nt!VfIrpSendSynchronousIrp+0x11e
ffffd001`5bf56620 fffff803`9f07ab56 : 00000000`00000000 ffffd001`5bf56769 00000000`00000001 ffffe000`dba1d470 : nt!VfWmiTestStartedPdoStack+0x5a
ffffd001`5bf566c0 fffff803`9ee154e0 : 00000000`00000000 ffffd001`5bf56769 00000000`00000001 ffffd001`5bf56769 : nt!VfMajorTestStartedPdoStack+0x56
ffffd001`5bf566f0 fffff803`9ee10a3e : ffffe000`dba1e010 ffffd001`00000001 00000000`00000000 00000000`00000000 : nt!PipProcessStartPhase3+0xb8
ffffd001`5bf567d0 fffff803`9ef1de8b : ffffe000`dba4c1a0 00000000`00000001 00000000`00000000 fffff803`9eda10b6 : nt!PipProcessDevNodeTree+0x352
ffffd001`5bf56a50 fffff803`9eaf0160 : 00000001`00000003 00000000`00000000 00000000`00000000 ffffe000`dbfa09c0 : nt!PiProcessStartSystemDevices+0x87
ffffd001`5bf56aa0 fffff803`9ea3fa2b : fffff803`9eaefda0 ffffd001`5bf56bd0 00000000`00000000 00000000`00714940 : nt!PnpDeviceActionWorker+0x3c0
ffffd001`5bf56b50 fffff803`9eadc514 : ffffd001`60b282c0 ffffe000`dbfa0880 ffffe000`dbfa0880 ffffe000`daf59900 : nt!ExpWorkerThread+0x293
ffffd001`5bf56c00 fffff803`9eb5d2c6 : ffffd001`60b1c180 ffffe000`dbfa0880 ffffd001`60b282c0 415d415e`415f4140 : nt!PspSystemThreadStartup+0x58
ffffd001`5bf56c60 00000000`00000000 : ffffd001`5bf57000 ffffd001`5bf51000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: .bugcheck ; kb
SYMBOL_NAME: nt!ViGenericDriverEntry+0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 53d0b7c3
IMAGE_VERSION: 6.3.9600.17238
BUCKET_ID_FUNC_OFFSET: 0
FAILURE_BUCKET_ID: 0xc9_21f_VRF_nt!ViGenericDriverEntry
BUCKET_ID: 0xc9_21f_VRF_nt!ViGenericDriverEntry
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0xc9_21f_vrf_nt!vigenericdriverentry
FAILURE_ID_HASH: {604d8ad3-8bdc-afd2-7008-966616cba61a}
Followup: MachineOwner


I have read somewhere that says that this may be a keyboard issue, which is interesting because my caps lock button seems to work backwards when at the windows login screen but works correctly once i am logged in..... So maybe this has something to do with it.

I have tried many things and my system appears to be healthy apart from this one problem.

If anyone could help me out that would be great!

I have attached the "sysnativefilecollectionapp.zip".

Cheers,





 
I have managed to generate a perfmon report manually, under basic system checks/hardware and device driver checks i received a failed result....

[TABLE="class: block"]
[TR="class: b2"]
[TD="class: string"]PlugAndPlay Device Configured Fail Count[/TD]
[TD="class: number, width: 8%"]123[/TD]
[TD="class: number, width: 8%"]1[/TD]
[TD="class: string"]PlugAndPlay devices.[/TD]
[/TR]
[/TABLE]
 

Attachments

Hi,

Won't be able to debug the 0xC9 as we'll need a kernel-dump to check the devobj, but the 0x9F will work just fine.

DRIVER_POWER_STATE_FAILURE (9f)

This bug check indicates that the driver is in an inconsistent or invalid power state.

Code: 
BugCheck 9F, {3, ffffe000ca861060, ffffd000ef173930, [COLOR=#ff0000]ffffe000d03ba6f0[/COLOR]}

Code: 
>[ 16, 2]   0 e1 ffffe000ca861060 00000000 fffff800b58a2fc4-ffffd000ef14f8f0 Success Error Cancel pending
           \Driver\pci    dxgkrnl!DpiFdoPowerCompletionRoutine
            Args: 00000000 00000001 00000001 00000000
 [ 16, 2]   0 e1 ffffe000cebf91f0 00000000 fffff8003fd3afd8-ffffe000cefe1ed8 Success Error Cancel pending
          Unable to load image \SystemRoot\system32\DRIVERS\[COLOR=#ff0000]nvlddmkm.sys[/COLOR], Win32 error 0n2
*** WARNING: Unable to verify timestamp for [COLOR=#ff0000]nvlddmkm.sys[/COLOR]
*** ERROR: Module load completed but symbols could not be loaded for [COLOR=#ff0000]nvlddmkm.sys[/COLOR]
 \Driver\[COLOR=#ff0000]nvlddmkm    [/COLOR]nt!PopRequestCompletion

The driver that's blocking the IRP for too long is the nVidia video driver.


1. Ensure you have the latest video card drivers. If you are already on the latest video card drivers, uninstall and install a version or a few versions behind the latest to ensure it's not a latest driver only issue. If you have already experimented with the latest video card driver and many previous versions, please give the beta driver for your card a try.

2. Navigate to serivices.msc and disable the nVidia Streaming Service, and then restart the computer.

Regards,

Patrick
 
Patrick ^_^,

I would suggest you to include the line that also try installing the Graphics Drivers from the Manufacturer's website which in this case would be over **HERE** as IMO this fixes the issue 99% of the time unless there is a Hardware Problem.

-Pranav
 
Thank you for your help Patrick! I will do a clean installation of the latest graphics drivers which conveniently just came out. At least now i have an idea of what is blocking the IRP!
I am not entirely convinced that will will fix the problem because i have updated my drivers several times and have received a BSOD with each successive version. If i do get another BSOD i will do as Pranav suggested and install the old drivers for my laptop from the Asus website. I have disabled nVidia Streaming Service also.

If i have the time tomorrow i will try force my laptop into a BSOD to test these fixes.

Thanks again for your help.

ps: should i be worried about "The speed of processor 0 in group 0 is being limited by system firmware" ​in my event log?
 
nzasus said:
Thank you for your help Patrick! I will do a clean installation of the latest graphics drivers which conveniently just came out. At least now i have an idea of what is blocking the IRP!
I am not entirely convinced that will will fix the problem because i have updated my drivers several times and have received a BSOD with each successive version. If i do get another BSOD i will do as Pranav suggested and install the old drivers for my laptop from the Asus website. I have disabled nVidia Streaming Service also.

If i have the time tomorrow i will try force my laptop into a BSOD to test these fixes.

Thanks again for your help.

ps: should i be worried about "The speed of processor 0 in group 0 is being limited by system firmware" ​in my event log?
Click to expand...

I have seen that event in many logs. I would say that it would be safe to ignore until you are facing sluggish performance.

Sure thing, keep us updated ^_^
 
dude!! i am facing exactly the same problem with my laptop that has same configuration..!! mine is dell 3542 i7 model...on battery i get BSOD when trying to run any game or do other stuffs...but on adapter i dont face any BSOD ..!! I contacted dell..they first replaced my hard drive but problem was still there..then they replaced my motherboard...but still i am facing this problem...either its related to RAM or it may be software related!! If u have got any solution then please share it!! thanks!!
 
anu said:
dude!! i am facing exactly the same problem with my laptop that has same configuration..!! mine is dell 3542 i7 model...on battery i get BSOD when trying to run any game or do other stuffs...but on adapter i dont face any BSOD ..!! I contacted dell..they first replaced my hard drive but problem was still there..then they replaced my motherboard...but still i am facing this problem...either its related to RAM or it may be software related!! If u have got any solution then please share it!! thanks!!
Click to expand...

Please make your own thread and someone will assist you.
 
blueelvis said:
nzasus said:
Thank you for your help Patrick! I will do a clean installation of the latest graphics drivers which conveniently just came out. At least now i have an idea of what is blocking the IRP!
I am not entirely convinced that will will fix the problem because i have updated my drivers several times and have received a BSOD with each successive version. If i do get another BSOD i will do as Pranav suggested and install the old drivers for my laptop from the Asus website. I have disabled nVidia Streaming Service also.

If i have the time tomorrow i will try force my laptop into a BSOD to test these fixes.

Thanks again for your help.

ps: should i be worried about "The speed of processor 0 in group 0 is being limited by system firmware" ​in my event log?
Click to expand...

I have seen that event in many logs. I would say that it would be safe to ignore until you are facing sluggish performance.

Sure thing, keep us updated ^_^
Click to expand...

blueelvis is correct.

I've seen these warning events in BDW system as well. From my obtained info that these warnings are caused by mismatching Intel code design & Windows design.
But it won't cause any trouble and performance impact.
:)
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top