Solved BSOD after resuming from sleep/hibernate, and delayed shutdowns (9f)

[ZosoCoder]

Hi,

I have a Dell XPS 15z (L511z). I've noticed recently that when opening my laptop while its in sleep mode, the computer sounds like its coming to life, but the screen doesn't turn on. After a while, the BSOD shows up and restarts the computer.

Also, I always get the Waiting For Programs To Close message when shutting down, but there are no programs in the list. I usually just let it do its thing and it eventually shuts down.

Please find attached the dumps obtained via SF_Diagnostic_Tool.

Thanks in advance for your help.

 

[Saurabh A]

Hi ZosoCoder,

Analysis of the crash dump reports the following information:

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

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa800d1bd580, fffff80004d8b3d8, fffffa8007534a60}

Probably caused by : [COLOR="Red"]vwifibus.sys[/COLOR]	

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

[COLOR="red"]DRIVER_POWER_STATE_FAILURE (9f)[/COLOR]
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa800d1bd580, Physical Device Object of the stack
Arg3: fffff80004d8b3d8, Functional Device Object of the stack
Arg4: fffffa8007534a60, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  vwifibus.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bcc39

MODULE_NAME: vwifibus

FAULTING_MODULE: fffff88006f69000 vwifibus

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

STACK_TEXT:  
fffff800`04d8b388 fffff800`038f78c2 : 00000000`0000009f 00000000`00000003 fffffa80`0d1bd580 fffff800`04d8b3d8 : nt!KeBugCheckEx
fffff800`04d8b390 fffff800`0389284c : fffff800`04d8b4c0 fffff800`04d8b4c0 00000000`00000000 00000000`00000003 : nt! ?? ::FNODOBFM::`string'+0x33af0
fffff800`04d8b430 fffff800`038926e6 : fffff880`07b47780 fffff880`07b47780 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`04d8b4a0 fffff800`038925ce : 0000004e`59c6cbad fffff800`04d8bb18 00000000`0020ea44 fffff800`03a05b08 : nt!KiProcessExpiredTimerList+0xc6
fffff800`04d8baf0 fffff800`038923b7 : 00000014`9bf9c0c4 00000014`0020ea44 00000014`9bf9c071 00000000`00000044 : nt!KiTimerExpiration+0x1be
fffff800`04d8bb90 fffff800`0387f90a : fffff800`03a02e80 fffff800`03a10cc0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`04d8bc40 00000000`00000000 : fffff800`04d8c000 fffff800`04d86000 fffff800`04d8bc00 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_3_vwifimp_IMAGE_vwifibus.sys

BUCKET_ID:  X64_0x9F_3_vwifimp_IMAGE_vwifibus.sys

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

This crash is caused due to the driver vwifibus.sys
Driver related to: Virtual WiFi Bus Driver
Driver updated with 'Windows updates'

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

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa800b3214c0, fffff80000b9c3d8, fffffa800d1a3010}

Probably caused by : [COLOR="red"]HDAudBus.sys[/COLOR]

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

[COLOR="red"]DRIVER_POWER_STATE_FAILURE (9f)[/COLOR]
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa800b3214c0, Physical Device Object of the stack
Arg3: fffff80000b9c3d8, Functional Device Object of the stack
Arg4: fffffa800d1a3010, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

DRIVER_OBJECT: fffffa800a05fe70

IMAGE_NAME:  HDAudBus.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7a65e

MODULE_NAME: HDAudBus

FAULTING_MODULE: fffff88005600000 HDAudBus

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

STACK_TEXT:  
fffff800`00b9c388 fffff800`0393d8c2 : 00000000`0000009f 00000000`00000003 fffffa80`0b3214c0 fffff800`00b9c3d8 : nt!KeBugCheckEx
fffff800`00b9c390 fffff800`038d884c : fffff800`00b9c4c0 fffff800`00b9c4c0 00000000`00000000 00000000`00000003 : nt! ?? ::FNODOBFM::`string'+0x33af0
fffff800`00b9c430 fffff800`038d86e6 : fffffa80`0a036168 fffffa80`0a036168 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`00b9c4a0 fffff800`038d85ce : 00000015`c648eda1 fffff800`00b9cb18 00000000`000925c1 fffff800`03a4caa8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9caf0 fffff800`038d83b7 : 00000005`ba259ec4 00000005`000925c1 00000005`ba259e87 00000000`000000c1 : nt!KiTimerExpiration+0x1be
fffff800`00b9cb90 fffff800`038c590a : fffff800`03a48e80 fffff800`03a56cc0 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cc40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cc00 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_3_IMAGE_HDAudBus.sys

BUCKET_ID:  X64_0x9F_3_IMAGE_HDAudBus.sys

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

This crash reports the 'High Definition Audio Bus Driver' (HDAudBus.sys) as the main culprit.
This driver is also updated through Windows updates.

Please try the following steps to see if they help:

1. Remove 'Avast anti-virus' from the system and install 'Microsoft Security Essentials'; check results.

Start Menu\Programs\avast! Free Antivirus

- Click avast! Uninstall Utility | Download aswClear for avast! Removal to remove 'Avast' from the system
- Click Download Microsoft Security Essentials from Official Microsoft Download Center to download and install Microsoft Security Essentials.

2. Click Microsoft Windows Update to find the steps to install 'Windows Updates'. This is likely to update both the drivers, that were observed to cause the system crashes. (HDAudBus.sys & vwififlt.sys).

3. Almost all the crash reports mention 'Bug Check 0x9F: DRIVER_POWER_STATE_FAILURE' as the error code. This bug check indicates that a driver is in an inconsistent or invalid power state. Installing Windows updates is likely to update the culprit driver. You may also try an anti-virus scan with 'Microsoft Security Essentials'. Would also recommend you to follow the steps listed in 'Option 2' of the following tutorial to run 'Chkdsk /F command from Command Prompt': http://www.sevenforums.com/tutorials/433-disk-check.html.

4. If the issue persists, try running hardware diagnostics to confirm the hardware functionality of the system. http://dell.to/17Ri00I

Hope this helps. Do reply with the findings. Will take it forward from there.

 

[ZosoCoder]

Saurabh A,

Thank you very much for you help. These four steps solved my BSOD problem. I can now successfully resume from sleep/hibernate.

I'm curious why I needed to uninstall Avast. Should I avoid using it from now on?

Thanks

 

[Saurabh A]

Hi ZosoCoder,

Glad that the issue is fixed; thank you for confirming.

'Avast' could be one of the possible reasons for the crashes. I have observed many users reporting better results with 'Microsoft Security essentials', instead. It is an effective anti-virus solution that comes with Windows updates. You may still want to try swapping the 'anti-virus software' again to see how the system behaves. If the issue re-occurs, it will confirm 'Avast' as the root cause. Otherwise, you may continue using it.

Updating Windows may have installed updates for the drivers 'HDAudBus.sys & vwififlt.sys'. That could have done the trick as well.

Hope you find the information useful. Do reply if you have any further questions. Would be glad to assist.

 

[ZosoCoder]

Hi Saurabh A,

It looks like I spoke too soon. It was working for a few tries, but yesterday I got the BSOD again with the same error after closing the lid of my laptop and returning to it a few hours later. The same thing happened: the laptop started up, but the screen was completely black. Then after a few minutes, the BSOD appears and reboots my laptop. So I did step four from your original reply and ran the PSA Diagnostics in thorough test mode. Everything passed.

I ran the SF_Diagnostic_Tool again, and attached the results to this post.

Thanks for your help,
ZosoCoder

 

[Saurabh A]

Hi ZosoCoder,

Thank you for the response.

This crash points at the USB 3.0 Host Controller driver.

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa800ac9e110, fffff80000b9c3d8, fffffa800e560810}

Unable to load image \SystemRoot\system32\DRIVERS\nusb3hub.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nusb3hub.sys
*** ERROR: Module load completed but symbols could not be loaded for nusb3hub.sys
*** WARNING: Unable to verify timestamp for nusb3xhc.sys
*** ERROR: Module load completed but symbols could not be loaded for nusb3xhc.sys
Probably caused by : [COLOR="Red"]nusb3xhc.sys[/COLOR]

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa800ac9e110, Physical Device Object of the stack
Arg3: fffff80000b9c3d8, Functional Device Object of the stack
Arg4: fffffa800e560810, The blocked IRP

Driver Description: NEC Electronics USB 3.0 Host Controller Driver
You may try updating the driver from Dell Support website: http://dell.to/11Va0yX

Also update the following 'Intel Chipset drivers':
Intel Cougar Point chipset Driver: http://dell.to/14tlgQb
Intel HECI (Management Engine Interface) Driver: http://dell.to/11VdcKO

Follow the on-screen instructions to install each files one by one. Restart the system when prompted. Recheck results.

Do reply with the findings; will take it forward from there.

 

[ZosoCoder]

Hi Saurabh A,

Thanks for the reply. I installed the three drivers and some quick sleep/hibernate tests and it seems to be working again.
I will leave it in sleep mode for a while like I did last time when it crashed. I'll reply here with the results.

Thanks again,

ZosoCoder

 

[ZosoCoder]

After several more attempts, varying in duration of hibernation/sleep, the laptop successfully resumes from hibernate/sleep. I'll mark this thread as solved, again.

Thanks!

 

[Saurabh A]

Hi ZosoCoder,

Thank you for the response.
Things look settled now. However, you may want to observe the system for few more days to see if the issue re-occurs. Feel free to share the crash dump, if required. We will take it forward from there.

Let me know if you have any further questions. I would be glad to assist you.