Solved Random BSOD's DRIVER_POWER_STATE_FAILURE ntoskrnl.exe (SF File incl)

[nielsvann]

Since the last 9 Months my PC is having BSOD’s randomly.

DRIVER_POWER_STATE_FAILURE
Caused By Driver: ntoskrnl.exe

In the previous 9 months I spend over 200 hours trying to solve this issue but without success so posting this here is like my last hope…

In Attachment my SF_Diagnostic_Tool File.
Most dmp files in it are Small memory dumps but the most recent one (012314-13494-01.dmp) is a Kernel memory dump I believe.
It may be important to know that these are all my dmp files collected over my different setups
Sometimes if a BSOD happened and a dmp was generated, I copied the dmp file to an external drive and rolled back with my EaseUs Backup to a previous backup to try to go back to a point where the BSOD would not happen. The furthest I went back to a backup of Nov 2012. But the BSOD’s still kept coming.

I tried to read them out with bluescreenview and also use MyEventViewer but with no success.

Thank you so much for your advice and help…

 

[Arc]

Hi nielsvann.

The BSOD crash dump is incompletely recorded, and so not readable.

Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus and the touchpad driver, SynTPEnh.
5. Apply > OK
6. Accept then restart.

Then put the computer to sleep again, and wake it up. It will BSOD, and hopefully we will get a complete crash dump to determine the root cause of the BSOD.

 

[nielsvann]

Hi Arc,

Thanks for your help. Indeed I just saw that the latest was indeed incompletely recorded...
I believe the other dmp files are correct maybe there is a clue in those.
I'm backing up my files currently and afterwards will do directly the steps you advised and keep you posted.
You want that I setup windows to create small Memory Dump 256 kb (like it is setup currently) OR you prefer I change it to create a Kernel Memory Dump?

Thanks again...

 

[Arc]

A small memory dump (minidump) will be enough.

 

[nielsvann]

I the steps exactly as advised but the notebook did not BSOD.
(Did all steps 3 times with 20 min between to make sure)

I placed two zipped BSOD Small memory dumps that where created successfully in the previous 40 days in attachment instead. Hope those will give you and insight.

PS: Just so you know, the next 24hours I will not be able to reply since I will be working but I look forward to hear from you. Thanks

 

[Arc]

            Args: 00000000 00000000 00000000 00000000
>[ 16, 2]   0 e1 fffffa8007183940 00000000 fffff8800f57d4a4-fffffa800a180b60 [COLOR=Red]Success Error Cancel pending
           \Driver\ACPI    nvlddmkm[/COLOR]
            Args: 00000000 00000001 00000001 00000000
 [ 16, 2]   0 e1 fffffa800a0c9480 00000000 00000000-00000000    pending
           \Driver\nvlddmkm
            Args: 00000000 00000001 00000001 00000000

Very common issue with switchable graphics and nvidia optimus. Whwnever graphics switch between the onboard and dedicated, the BSOD occurs.

I find it the hard most to debug. Because it is indigenous to the system configuration.

At the first try, Install the NVIDIA DRIVERS 314.22WHQL only.

• Uninstall All nvidia items in Control Panel > Programs and features
  • 3D Vision Control Driver
  • 3D Vision Driver
  • Graphics Driver
  • HD Audio Driver
  • PhysX
  • nvidia Update
  (Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
• Now follow Drivers - Clean Left over Files after Uninstalling
• Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:
  
  

Be patient, it may take a time to work and rework to get rid of this issue. And let us know the situation.

 

[nielsvann]

Thanks for the detailed info Arc. Tomorrow I have the day off and will follow the procedure exactly as you wrote. As my BSOD's happened sometimes twice a day and other times once a month it could take a while before my next post. In any case I will let hear something. Thank you sooo much for your great advise! Wish you the best...

 

[nielsvann]

Next BSOD

Got a new BSOD today. I was playing a 1080p youtube video in Firefox then I placed my Notebook in hibernate. My screen went black but the sound of the video kept still playing for 10-15 min, then got my BSOD.

My SF Diagnostic Zip that includes the new dmp file is in att. of this post.

Thanks in advance for the advice.

 

[Arc]

So the earlier steps did not work for you. No wonder in it. Yours is not is display issue at all.

Before suggesting anything further, or before saying that I am unable (not actually, but it is a public forum) to do anything more, I would like to see one more thing, in search of some external thing influencing the ACPI.

Upload the list of all the third party drivers Using NirSoft DriverView :

• Download and execute Driverview
• View > Hide Microsoft Drivers
• Edit > Select all
• File > Save Selected Items
• In the Save dialog, Set the path to desktop, Put "Driverview" in the name field, and save.
• Zip the .txt file and upload it.

 

[nielsvann]

Thanks for the quick answer Arc. In att. you will find my driverview file. Thanks for your help...

 

[Arc]

No. Nothing is there that I was searching for.

In my explanation, your issue is caused by some ACPI (Advanced Configuration and Power Interface) settings of the switchable graphics mechanism. Whenever the graphics switches, the BSOD occurs.

If you are interested, you may boot into the BIOS. Disable the integrated GPU. Use the dedicated GPU only as the desktop computers do; and perform a clean reinstall as on that state.

I confess that I dont know any other thing that can be done here.

 

[nielsvann]

Hi Arc, thank you for all the time and energy spend on this issue. As I got still 7 months warranty on this notebook I will send it in for repair. Do you suggest I tell them something specifically to get them started in the right direction?
Might this be a hardware problem from the HD4000 integrated graphics or the Nvidia card or is the ACPI related to that?
Thanks and have a great day...

 

[Arc]

It is not any hardware or driver issue, mate. It is simply ACPI that is causing the problems. When the power state of the GPU is changing, the issue is occurring.

Device states The device states D0–D3 are device-dependent:

• D0 Fully On is the operating state.
• D1 and D2 are intermediate power-states whose definition varies by device.
• D3 Off has the device powered off and unresponsive to its bus.
  • D3 Hot & Cold: The D3 state is further divided into D3 Hot (has aux power), and D3 Cold (no power provided). A device in D3 Hot state can assert power management requests to transition to higher power states.

Source: Advanced Configuration and Power Interface - Wikipedia, the free encyclopedia

Usually you can configure the ACPI at your own from Control Panel > Power Options. But for your system, it is controlled by Optimus Technology. Sounds very good, but fails in the same way very frequently. We should keep things simple, IMHO.

From your latest BSOD:

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

Use !analyze -v to get detailed debugging information.

[URL="http://carrona.org/bsodindx.html#0x0000009F"]BugCheck 9F[/URL], {3, fffffa80071b4a10, fffff80000b9c3d8, fffffa800e80ba20}

Unable to load image nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
[COLOR=Blue]*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys[/COLOR]
[B][COLOR=Red]Probably caused by : ACPI.sys[/COLOR][/B]

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

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

[URL="http://carrona.org/bsodindx.html#0x0000009F"]DRIVER_POWER_STATE_FAILURE (9f)[/URL]
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: fffffa80071b4a10, Physical Device Object of the stack
Arg3: fffff80000b9c3d8, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: fffffa800e80ba20, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

[COLOR=SeaGreen]IRP_ADDRESS: fffffa800e80ba20[/COLOR]

[COLOR=Purple]DEVICE_OBJECT: fffffa80094ba0f0[/COLOR]

[COLOR=Sienna]DRIVER_OBJECT: fffffa80069ac470[/COLOR]

[COLOR=Red]IMAGE_NAME:  ACPI.sys[/COLOR]

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce79294

[COLOR=Red]MODULE_NAME: ACPI
[/COLOR]
FAULTING_MODULE: fffff88000d5e000 ACPI

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

DPC_STACK_BASE:  FFFFF80000BA2FB0

[COLOR=Green]IRP_ADDRESS: fffffa800e80ba20[/COLOR]
------------------------------------------------
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
>[ 16, 2]   0 e1 fffffa80094ba0f0 00000000 fffff88005bd7f18-fffffa800b6c0780 [COLOR=Red]Success Error Cancel pending
           \Driver\ACPI    nvlddmkm[/COLOR]
            Args: 00000000 00000001 00000001 00000000
 [ 16, 2]   0 e1 fffffa8009ece480 00000000 00000000-00000000  [COLOR=Red]  pending
           \Driver\nvlddmkm[/COLOR]
            Args: 00000000 00000001 00000001 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-fffffa800b877a50    

            Args: 00000000 00000000 00000000 00000000

[COLOR=DarkOrchid]DEVICE_OBJECT: fffffa80094ba0f0[/COLOR]
---------------------------------------------------
fffff80003440010: Unable to get value of ObpRootDirectoryObject
Device object (fffffa80094ba0f0) is for:
[COLOR=Red] InfoMask field not found for _OBJECT_HEADER at fffffa80094ba0c0
 \Driver\ACPI DriverObject fffffa80069ac470[/COLOR]
Current Irp 00000000 RefCount 0 Type 00000032 Flags 00004000
DevExt fffffa8006bf0010 DevObjExt fffffa80094ba240 
Characteristics (0x00000100)  FILE_DEVICE_SECURE_OPEN
[COLOR=Red]AttachedDevice (Upper) fffffa8009ece480 \Driver\nvlddmkm[/COLOR]
Device queue is not busy.

[COLOR=Sienna]DRIVER_OBJECT: fffffa80069ac470[/COLOR]
------------------------------------------------------
fffff80003440010: Unable to get value of ObpRootDirectoryObject
fffff80003440010: Unable to get value of ObpRootDirectoryObject
[COLOR=Red]Driver object (fffffa80069ac470) is for:
 \Driver\ACPI[/COLOR]
Driver Extension List: (id , addr)

Device Object list:
fffffa800ba10e40: Could not read device object


[COLOR=Red]DriverEntry:   fffff88000dadc30    ACPI!GsDriverEntry[/COLOR]
DriverStartIo: 00000000    
[COLOR=Red]DriverUnload:  fffff88000d69d0c    ACPI![U][B]ACPIUnload[/B][/U][/COLOR]
AddDevice:     00000000    

Dispatch routines:
[00] IRP_MJ_CREATE                      fffff88000d69914   [COLOR=Red] ACPI!ACPIDispatchIrp[/COLOR]
[01] IRP_MJ_CREATE_NAMED_PIPE           fffff88000d69914    [COLOR=Red]ACPI!ACPIDispatchIrp[/COLOR]
[02] IRP_MJ_CLOSE                       fffff88000d69914    [COLOR=Red]ACPI!ACPIDispatchIrp[/COLOR]
[03] IRP_MJ_READ                        fffff88000d69914   [COLOR=Red] ACPI!ACPIDispatchIrp[/COLOR]
[04] IRP_MJ_WRITE                       fffff88000d69914    [COLOR=Red]ACPI!ACPIDispatchIrp[/COLOR]
[05] IRP_MJ_QUERY_INFORMATION           fffff88000d69914  [COLOR=Red]  ACPI!ACPIDispatchIrp[/COLOR]
[06] IRP_MJ_SET_INFORMATION             fffff88000d69914   [COLOR=Red] ACPI!ACPIDispatchIrp[/COLOR]
[07] IRP_MJ_QUERY_EA                    fffff88000d69914   [COLOR=Red] ACPI!ACPIDispatchIrp[/COLOR]
[08] IRP_MJ_SET_EA                      fffff88000d69914   [COLOR=Red] ACPI!ACPIDispatchIrp[/COLOR]
[09] IRP_MJ_FLUSH_BUFFERS               fffff88000d69914   [COLOR=Red] ACPI!ACPIDispatchIrp[/COLOR]
[0a] IRP_MJ_QUERY_VOLUME_INFORMATION    fffff88000d69914    [COLOR=Red]ACPI!ACPIDispatchIrp[/COLOR]
[0b] IRP_MJ_SET_VOLUME_INFORMATION      fffff88000d69914    [COLOR=Red]ACPI!ACPIDispatchIrp[/COLOR]
[0c] IRP_MJ_DIRECTORY_CONTROL           fffff88000d69914    [COLOR=Red]ACPI!ACPIDispatchIrp[/COLOR]
[0d] IRP_MJ_FILE_SYSTEM_CONTROL         fffff88000d69914   [COLOR=Red] ACPI!ACPIDispatchIrp[/COLOR]
[0e] IRP_MJ_DEVICE_CONTROL              fffff88000d69914    [COLOR=Red]ACPI!ACPIDispatchIrp[/COLOR]
[0f] IRP_MJ_INTERNAL_DEVICE_CONTROL     fffff88000d69914    [COLOR=Red]ACPI!ACPIDispatchIrp[/COLOR]
[10] IRP_MJ_SHUTDOWN                    fffff88000d69914    [COLOR=Red]ACPI!ACPIDispatchIrp[/COLOR]
[11] IRP_MJ_LOCK_CONTROL                fffff88000d69914    [COLOR=Red]ACPI!ACPIDispatchIrp[/COLOR]
[12] IRP_MJ_CLEANUP                     fffff88000d69914    [COLOR=Red]ACPI!ACPIDispatchIrp[/COLOR]
[13] IRP_MJ_CREATE_MAILSLOT             fffff88000d69914    [COLOR=Red]ACPI!ACPIDispatchIrp[/COLOR]
[14] IRP_MJ_QUERY_SECURITY              fffff88000d69914    [COLOR=Red]ACPI!ACPIDispatchIrp[/COLOR]
[15] IRP_MJ_SET_SECURITY                fffff88000d69914    [COLOR=Red]ACPI!ACPIDispatchIrp[/COLOR]
[16] IRP_MJ_POWER                       fffff88000d69914    [COLOR=Red]ACPI!ACPIDispatchIrp[/COLOR]
[17] IRP_MJ_SYSTEM_CONTROL              fffff88000d69914    [COLOR=Red]ACPI!ACPIDispatchIrp[/COLOR]
[18] IRP_MJ_DEVICE_CHANGE               fffff88000d69914    [COLOR=Red]ACPI!ACPIDispatchIrp[/COLOR]
[19] IRP_MJ_QUERY_QUOTA                 fffff88000d69914    [COLOR=Red]ACPI!ACPIDispatchIrp[/COLOR]
[1a] IRP_MJ_SET_QUOTA                   fffff88000d69914    [COLOR=Red]ACPI!ACPIDispatchIrp[/COLOR]
[1b] IRP_MJ_PNP                         fffff88000d69914    [COLOR=Red]ACPI!ACPIDispatchIrp[/COLOR]

Fast I/O routines:
Cannot read _FAST_IO_DISPATCH at fffff88000d92360

If we try to summerize the long story, we can say that your issue is a stop 0x9F, Driver Power state failure. It is simply a driver issue. A driver is failing to react within the stipulated time period during the state of power transition, and the BSOD is taking place.

In your case, the driver that is failing is the display driver, nvlddmkm.sys. It is also said clearly in the crash dump that the driver is not failing at its own, but ACPI is making it fail. Father analysis shows that when ACPI is unloading, the issue is occurring for sure.

We have tried multiple versions of the display driver, got the essentially same result. Which keeps the drivers in the safe side. They are not failing on themselves -- the concept is concrete.

That is why I think it is the issue inbuilt in the graphics switching mechanism only, and the possible way to overcome the issue is to keep the things simple. NO DESKTOP faces this issue. A laptop without dual graphics does not face his issue.

There is no scope to suspect any hardware for the issue, and power here does not have any connection to POWER SUPPLY AND PSU!

That is what all I can say.

So you can see that I am giving only one suggestion to you. If you want, I can ask other members (most of them are much more efficient and experienced than I am) to see the issue, and suggest you accordingly.

 

[nielsvann]

Ok thanks, the greatly detailed info you just gave. This will definitely get the company that build/composed my system on the right track.

Now until then, might it work to keep the BSOD’s away if I change the following things in the Nvidia Controle Panel? At the moment in [FONT=&quot]Manage 3D settings & Set PhysX Configuration I have the standard settings of ‘Auto-Select’. [/FONT]
[FONT=&quot]If I would change this to CPU for the PhysX Configuration and to integrated graphics for Manage 3D settings would [/FONT]Nvidia Controle Panel by this way override Optimus Technology’s urge to switch between the two modes?

The reality is I only need the Nvidia GPU maximum once by month when I game so I do not mind If it is totally disabled when I do not game. Maybe in this way it only uses the HD4000 and does not try to switch = no BSOD?

I appreciate all the time spend on my issue so I propose to just answer with a yes or no to my question above so I do not take up any additional time from you.
[FONT=&quot] [/FONT]
No need to ask other forum members, thanks for suggesting. Wish you all the best…

 

[Arc]

Nvidia control panel has nothing to do anything there. As it controls the GPU features only, not the ACPI.

If you force the laptop either the dedicated graphics only or the integrated graphics only (by disabling the other), then there should not be any chance to switch, and theoretically there should be no similar BSOD driver power state failure.

 

[nielsvann]

Ok thanks for everything Arc. I will let know when to notebook comes back from RMA what was done and if it solved the issue. It may be helpful if other people have the same problem in the future. All the best...

 

[Arc]

You are welcome mate.

Wish you all the best, too

 

[nielsvann]

Hi, I got my notebook back from RMA 6 weeks ago and since then have not had a BSOD. After doing a BIOS update they where not able anymore to recreate the BSOD. So my issue is solved. Thanks again for all your help! All the best...

 

[Arc]

Good news.

Let us know for any further issue.