BSOD on shutdown, generally after HDMI use, 0x0000009F

Cwright11 · 03 Dec 2013

Hello,

I have an Asus N53SV running windows home premium 64bit. I have been having BSOD problems for the last year however recently they have been occurring much more frequently. I have looked through a lot of threads and tried a few different programs. Also googled the stop codes to no avail of a solution.

So I am hoping here that someone may be able to help me!

The Problem:

When my laptop is running, is will become very hot and I can feel the very warm air coming out of the vents, the speed indicator is sitting at 2.90Ghz constantly so I try to shutdown to stop it, however shutting down screen displays for 5 - 10 mins then i get BSOD with stop code 0x0000009F.
It originally used to happen after i disconnected laptop from HDMI but now occurs randomly as well.
It never happens during use, only on shutdown.

Attached is zip file as instructed in the sticky thread.

Looking forward to your help!!!

(Have tried BlueScreenView as well if that may help?)

- Chris :)

Arc · 03 Dec 2013

Hi Cwright11.

The BSODs are caused by Fresco Logic xHCI (USB3) Device Driver
(c:\windows\system32\drivers\flxhcic.sys).

Code:

Irp is active with 4 stacks 3 is current (= 0xfffffa800ed17780)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
     cmd  flg cl Device   File     Completion-Context
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
>[ 16, 2]   0 e1 fffffa800a4b9060 00000000 00000000-00000000    pending
          Unable to load image \SystemRoot\system32\DRIVERS\FLxHCIc.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for FLxHCIc.sys
*** ERROR: Module load completed but symbols could not be loaded for FLxHCIc.sys
 \Driver\FLxHCIc
            Args: 00016600 00000001 00000004 00000006
 [  0, 0]   0  0 00000000 00000000 00000000-fffffa800f12fc40    

            Args: 00000000 00000000 00000000 00000000

And the driver is old.

Code:

fffff880`05eee000 fffff880`05f3e000   FLxHCIc  T (no symbols)           
    Loaded symbol image file: FLxHCIc.sys
    Image path: \SystemRoot\system32\DRIVERS\FLxHCIc.sys
    Image name: FLxHCIc.sys
    Timestamp:        Thu Feb 24 14:29:52 2011 (4D661E08)
    CheckSum:         0004C3F2
    ImageSize:        00050000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Update it from FRESCO LOGIC INC.===Leap into SuperSpeed===.

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.

Click on the Start button
Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
Select the “Startup” tab.
Deselect all items other than the antivirus.
Apply > OK
Accept then restart.

Anyway, the camera driver ... that is ....

Code:

snp2uvc    c:\windows\vsnp2uvc.exe    Public    HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run

.... it must not start with windows. Use the camera only when it is needed.

Turn off USB Selective Suspend.
USB Selective Suspend - Turn On or Off

Let us know the results.

Cwright11 · 03 Dec 2013

Thankyou very much for your help ARC!

I have done all the things you have said and it did not BSOD on shutdown. I have not tested with HDMI or after unplugging USB's yet will let you know when i get the chance if the problem is still there.

Also, I am wondering how many of the startup processes can i toggle off, because there are a lot there which seem important, like the touchpad or the speakers etc?
Or will these be activated automatically anyway and don't need to be started on startup?

I have switched selective suspend off but when i was reading about it, it seemed like a good thing? What benefit does turning it off have?

Thankyou again so much for your help!!!

Chris
:)

Arc · 03 Dec 2013

Is there touchpad on startup? I did not notice

Dont remove that one from startup in that case.

EDIT: USB Selective Suspend: It suspends the USB devices during power transition (when the computer goes to sleep/hibernate). When it wakes up, the driver sometimes fails to respond back within the stipulated time frame; and BSODs occur. If the Selective Suspend is turned off, the device will not go to sleep, there will be no power transition for the USB devices, and so there will be no chance of a BSOD caused by it.

Startup: Speaker controllers are there in the notification area (systrey) always. If the third party controller is stopped to auto start, you will not loss any functionality. You can call it back anytime from Start> All programs whenever it is needed. It is equally valid for all the applications.

But, the touchpad driver, that is different. If it is not in auto start, it will loss functionality, the touchpad will not work. So it must be there. Same for the antivirus, it is better to keep the antivirusin startup, too.

Cwright11 · 04 Dec 2013

Ok, thankyou very much for clearing that up for me :)

I have disabled about 15 of the startup processes that I had before.

Today though i got another BSOD after the computer was trying to shut down again, took about 15 minutes or so at the shutting down screen then BSOD'd.

I will attach the new zip file, I don't know why, I hadn't used HDMI or plugged in any USB's? Same error, DRIVER_STATE_POWER_FAILURE 0x000009F

Thankyou so much for your help already, I have turned off selective suspend and updated the drivers detailed above, any more help would be greatly appreciated!

Arc · 04 Dec 2013

It is the same thing.

Code:

Irp is active with 4 stacks 3 is current (= 0xfffffa8007900170)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  Pending has been returned
     cmd  flg cl Device   File     Completion-Context
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [ 16, 0]   0  0 fffffa8007ac6a10 00000000 00000000-00000000    
           \Driver\pci
            Args: 00000000 00000000 00000000 00000005
>[ 16, 2]   0 e1 fffffa800bf1bc70 00000000 fffff80003525200-fffffa80115ab170 Success Error Cancel pending
          Unable to load image \SystemRoot\system32\DRIVERS\FLxHCIc.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for FLxHCIc.sys
*** ERROR: Module load completed but symbols could not be loaded for FLxHCIc.sys
 \Driver\FLxHCIc    nt!PopSystemIrpCompletion
            Args: 00016600 00000000 00000006 00000005
 [  0, 0]   0  0 00000000 00000000 00000000-fffffa80115ab170    

            Args: 00000000 00000000 00000000 00000000

Even with the updated driver.

Code:

fffff880`05146000 fffff880`05187000   FLxHCIc  T (no symbols)           
    Loaded symbol image file: FLxHCIc.sys
    Image path: \SystemRoot\system32\DRIVERS\FLxHCIc.sys
    Image name: FLxHCIc.sys
    Timestamp:        Wed Jul 03 08:13:01 2013 (51D38FB5)
    CheckSum:         0004BE35
    ImageSize:        00041000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Have you turned off the USB Selective Suspense?

Cwright11 · 04 Dec 2013

Thankyou for your reply!

Yes i have turned of selective suspense as per the instructions you linked above, just double checked again and it is disabled.
I have also cut down the startup processes, and today i went through and tried to update whichever drivers needed updating according to the windows update drivers program.

It's just frustrating that it is still happenning when i thought we had it solved.

I hope it doesn't matter that there are a whole lot of minidump files on my computer.

With bluescreenview it says the error yesterday came from ntoskrnl.exe and wdf01000.sys
whereas today it is from ntoskrnl.exe and nvlddmkm.sys

If that sheds any light on the situation?

Arc · 04 Dec 2013

I use windbg, which is a superior tool than bsview. Windbg reads it is the failure of the fresco logic usb3 driver.

Let us have some other approach. 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.

Cwright11 · 04 Dec 2013

Ok, here is the result!

Thankyou again for all your help by the way! I hope they pay you for this!

Arc · 04 Dec 2013

Your BSODs are being directly influenced by the FrescoLogic XHCI (USB3) drivers, as I told earlier....

Code:

0: kd> !irp fffffa8007900010
Irp is active with 4 stacks 3 is current (= 0xfffffa8007900170)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  Pending has been returned
     cmd  flg cl Device   File     Completion-Context
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [ 16, 0]   0  0 fffffa8007ac6a10 00000000 00000000-00000000    
           \Driver\pci
            Args: 00000000 00000000 00000000 00000005
>[ 16, 2]   0 e1 fffffa800bf1bc70 00000000 fffff80003525200-fffffa80115ab170 Success Error Cancel pending
          Unable to load image \SystemRoot\system32\DRIVERS\FLxHCIc.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for FLxHCIc.sys
*** ERROR: Module load completed but symbols could not be loaded for FLxHCIc.sys
 \Driver\FLxHCIc    nt!PopSystemIrpCompletion
            Args: 00016600 00000000 00000006 00000005
 [  0, 0]   0  0 00000000 00000000 00000000-fffffa80115ab170

But like almost all the stop 0x9F BSODs, it is also ACPI (Advanced Configuration and Power Interface) related.

Code:

0: kd> !devobj fffffa800bf1bc70 
fffff80003489010: Unable to get value of ObpRootDirectoryObject
Device object (fffffa800bf1bc70) is for:
 InfoMask field not found for _OBJECT_HEADER at fffffa800bf1bc40
 \Driver\FLxHCIc DriverObject fffffa800bf1fe70
Current Irp 00000000 RefCount 0 Type 00000022 Flags 00002050
DevExt fffffa800bf262b0 DevObjExt fffffa800bf1bde8 
ExtensionFlags (0000000000)  
Characteristics (0x00000100)  FILE_DEVICE_SECURE_OPEN
AttachedTo (Lower) fffffa8007ac0310 \Driver\ACPI
Device queue is not busy.

ACPI is complicated. It makes the system vulnerable sometimes. But when it is controlled by a third party app, it becomes worse. And in your CASE, ACPI is controlled by ATK WMIACPI Utility (C:\Program Files (x86)\ASUS\ATK Package\ATK WMIACPI\atkwmiacpi64.sys).

It is an ASUS bundled bloatware. I'd recommend you to Clean Up Factory Bloatware, with a special reference to Point #13

13. Consider a Clean Reinstall - Factory OEM Windows 7 which is often better than getting a new computer considering how pre-installed bloatware can corrupt Windows 7 even if it's completely cleaned up.

Also, if you want to use DisplayLink, make it sure that you are using the latest possible version.