New Build Machine BSOD 9F (driver power state) errors randomly

[wigwam12]

Hi
New member - please be gentle if I haven't followed the correct procedures
Okay I rebuilt my PC completely following a mobo failure, retaining the hard drives; I was really impressed Win7 Ult x64 booted straight into the desktop.
I removed old mobo drivers, added new ones
Had a few glitched with the USB ports which I think I fixed by deleting and reintalling new drivers

I have had some BSODs - 2 one after the other just now and at least 1 earlier one while the machine was unattended
In each case it was a BCCode 9f and I got the error message driver_power_state_failure.
Now I have the crashdrump logs.
I think it has zipped 3 but I know the most recent one related to the crash I just saw is called 112905-15444

On a whim in the interim I have also just now uninstalled the Asus AI Suite 3 that came with the mobo (Asus z170 pro gamer) as I know it has an energy management module and even though I have tried to disable that anyway I thought might be a cause for error

I would be most grateful for help in tracking down the cause of this error and advice on fixing it please!

Thanks

 

[axe0]

Daemon tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known cause for BSOD's.
Please remove Daemon Tools and run the SPTD pass through remover.

1. Uninstall Daemon Tools
2. Download the SPTD standalone installer and follow these steps:
   • Double click the executable to open it
   • Click on the button shown below

If the button is grayed out, like in the image, there is no more SPTD installation on your system, and you can close the window.

Please remove every USB connection, except for mouse and keyboard.
The Asmedia USB driver has been flagged, this has a few possible causes

• Driver problem,
• Faulty port,
• Faulty connection from the connected device

*** WARNING: Unable to verify timestamp for asmtxhci.sys
*** ERROR: Module load completed but symbols could not be loaded for asmtxhci.sys
0: kd> lmvm asmtxhci
start             end                 module name
fffff880`07000000 fffff880`0706c000   asmtxhci T (no symbols)           
    Loaded symbol image file: asmtxhci.sys
    Image path: \SystemRoot\system32\DRIVERS\asmtxhci.sys
    Image name: asmtxhci.sys
    Timestamp:        [COLOR="Red"]Thu Feb 12 07:57:01 2015[/COLOR] (54DC4EBD)
    CheckSum:         0006DBBB
    ImageSize:        0006C000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[wigwam12]

Thanks. I suspected that might be the cause. I have a usb3 external hdd. When I plugged it into the usb3.0 port it was intermittently being picked up and giving errors in device manager.
Plugging it into one of the 2 usb2 ports seemed to be fine except for the "one of your devices could run quicker" message.
So I recently uninstalled it from device manager, then uninstalled and reinstalled the Asmedia usb3 driver and plugged the drive into the usb3.1 port and now it shows up all the time and other odd problems I was having with flash drives have all gone.

My printer is plugged into the usb3 port the hdd was in originally and works fine so the physical port I think is fine.

Problem is the bsod is so intermittent so hard to pin.
Since the last bsod as I said I've also uninstalled the AI suite including a usb3 speed boost function (which I haven't used).
It is a brand new board and chipset and no new drivers I think so I'm otherwise pretty stuck aren't I?

I'll remove daemon as well - it is the pro version provided by Asus.

Further advice on what to do to fix?
There are no warnings in device manager.
Leave hdd on usb3.1 or switch it to a usb2 port?

 

[axe0]

If the HDD is not highly required, for example for work, I wouldn't connect it while troubleshooting.

Let me know how it goes.

 

[wigwam12]

Okay since last time I uninstalled Daemon and ran the SPTD tool
I have also remove ALL the Asus AI tools completely even the EZ Updater etc
Family have not reported any problems but I have been using the computer and I just had 2 blue screens once again one after the other like last time.
The difference this time is that I plugged the external USB drive from the rear 3.1 port to a front case 3.0 port between the 2 BSODs but still it crashed

I did notice a similarity between the 2 events for me - on both occasions I have also been running a Citrix portal session when the crashes occured (I need to do this for on call work)
Admittedly I have barely used the machine without doing this but certainly wife and kids have with no more ill effects

THe USB Drive did appear to be asleep as when I unplugged it and plugged it into the new port it whirred up - although that didn't stop it causing the BSOD 2nd time!

So now I have attached the new logs but also done the following:
In Device Manager I have changed the power management setting for USB Root to untick allow this device to sleep and in Power Management I have disabld USB Selecitve suspend setting in case that is the cause

Latest dump attached although the 1-4 loocked the same to me?
I have unplugged the external drive too although this is supposed to be my backup/sync device

Any more help greatly appreciated

 

[axe0]

The Intel graphics driver, a Kaspersky driver and Citrix USB driver have been flagged

fffff800`00b9a578  fffff880`06755b4eUnable to load image \SystemRoot\system32\DRIVERS\igdkmd64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
 igdkmd64+0x10ab4e

fffff800`00b9a4c8  fffff880`0180beb4Unable to load image \SystemRoot\system32\DRIVERS\klflt.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for klflt.sys
*** ERROR: Module load completed but symbols could not be loaded for klflt.sys
 klflt+0xbeb4

fffff800`00b9a420  fffff880`04cbc700Unable to load image \SystemRoot\system32\DRIVERS\ctxusbm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ctxusbm.sys
*** ERROR: Module load completed but symbols could not be loaded for ctxusbm.sys
 ctxusbm+0xa700

0: kd> lmvm igdkmd64
start             end                 module name
fffff880`0664b000 fffff880`06c98000   igdkmd64 T (no symbols)           
    Loaded symbol image file: igdkmd64.sys
    Image path: \SystemRoot\system32\DRIVERS\igdkmd64.sys
    Image name: igdkmd64.sys
    Timestamp:        [COLOR="red"]Thu Oct 01 20:35:51 2015[/COLOR] (560D7D07)
    CheckSum:         00625EBB
    ImageSize:        0064D000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

0: kd> lmvm klflt
start             end                 module name
fffff880`01800000 fffff880`01839000   klflt    T (no symbols)           
    Loaded symbol image file: klflt.sys
    Image path: \SystemRoot\system32\DRIVERS\klflt.sys
    Image name: klflt.sys
    Timestamp:        [COLOR="red"]Thu Sep 24 13:52:05 2015[/COLOR] (5603E3E5)
    CheckSum:         0002D21E
    ImageSize:        00039000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

0: kd> lmvm ctxusbm
start             end                 module name
fffff880`04cb2000 fffff880`04cc7f00   ctxusbm  T (no symbols)           
    Loaded symbol image file: ctxusbm.sys
    Image path: \SystemRoot\system32\DRIVERS\ctxusbm.sys
    Image name: ctxusbm.sys
    Timestamp:        [COLOR="Red"]Mon Sep 09 18:02:22 2013[/COLOR] (522DF10E)
    CheckSum:         0001CE78
    ImageSize:        00015F00
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Update link Intel graphics driver: Driver Reference Table - igdkmd64.sys
Please remove Kaspersky while troubleshooting and use Microsoft Security Essentials as alternative: Service articles & Microsoft Security Essentials - Microsoft Windows
Update link for Citrix USB driver: Driver Reference Table - ctxusbm.sys

 

[wigwam12]

Okay so I have done the following:
Checked and seen all Intel and Asmedia drivers are latest available
Updated BIOS to latest
Updated to latest Citrix Receiver
Updated to latest KIS 2016 (newer version was 3 days newer than one I had!)

I have also enabled xHCI Hand Off in BIOS (disabled by default, reading around says this should be enabled in Win7??)

I have also unplugged the external hdd and will see if any crashes in interim and also see if any new firmware for it

If all okay for a week will plug it in again and see