Right, I'll go into this one in a bit more depth as it's the same as last time. I think I may have reached a conclusion but I'll get to that at the end of the post.
The Bugcheck 0x9F is again which means a DRIVER_POWER_STATE_FAILURE, and that is down to one thing; a device driver. The ASMedia USB 3.0 hub is being blamed again at the first look.
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, fffffa8008448cd0, fffff80000b9c3d8, fffffa800e883af0}
[B][COLOR=Red]*** WARNING: Unable to verify timestamp for asmthub3.sys
*** ERROR: Module load completed but symbols could not be loaded for asmthub3.sys[/COLOR][/B]
Probably caused by : asmthub3.sys
Digging deeper though the
VIA Labs VL810 Superspeed USB Hub Controller Filter Driver is being flagged again.
Code:
0: kd> !devobj fffffa800f12ace0
Device object (fffffa800f12ace0) is for:
InfoMask field not found for _OBJECT_HEADER at fffffa800f12acb0
\Driver\asmthub3 DriverObject fffffa800f2789c0
Current Irp 00000000 RefCount 0 Type 00008600 Flags 00002040
DevExt fffffa800f12ae30 DevObjExt fffffa800f12af90
ExtensionFlags (0x00000800) DOE_DEFAULT_SD_PRESENT
Characteristics (0x00000080) FILE_AUTOGENERATED_DEVICE_NAME
AttachedDevice (Upper) fffffa800f12ee00Unable to load image \SystemRoot\system32\DRIVERS\vl810filter.sys, Win32 error 0n2
[B][COLOR=Red]*** WARNING: Unable to verify timestamp for vl810filter.sys
*** ERROR: Module load completed but symbols could not be loaded for vl810filter.sys[/COLOR][/B]
\Driver\vl810filter
[B][COLOR=Blue]AttachedTo (Lower) fffffa8008448cd0 \Driver\asmthub3[/COLOR][/B]
You can see at the bottom of that code that that particular controller is attached to the ASMedia USB Host Controller. Quite how I'm still yet to find out, but the firmware update you carried out hasn't updated the driver for it as you can see below.
Code:
0: kd> lmvm vl810filter
start end module name
fffff880`0850a000 fffff880`08512000 vl810filter T (no symbols)
Loaded symbol image file: vl810filter.sys
Image path: \SystemRoot\system32\DRIVERS\vl810filter.sys
Image name: vl810filter.sys
Timestamp: [B][COLOR=Red]Mon Dec 06 03:00:01 2010[/COLOR][/B] (4CFC51B1)
CheckSum: 0000FB98
ImageSize: 00008000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Looking at the text on their site it's no real surprise, they're not endorsing this firmware for end users and state it's specifically for the USB controller manufacturers to test.
View attachment 323000
Now whether this comes down to the ASMedia controller (it's not as nobody else has had trouble with ASMedia USB 3.0 controllers, it's quite common) or the motherboard itself is open to interpretation. I've been doing some reading of customer reviews on your board while at work and it's quite surprising how many people have complained about USB 3.0 problems and BSODs, as you stated on page 1 of this thread.
At this point I'm pretty much at a loss as to how to fix this, I've trawled high and low to find any evidence of successful firmware/driver updates to solve the issue but have found nothing.
My advice would be to contact EVGA with the all the evidence you've gathered from this thread so far and see what they say. They've responded openly to negative reviews on Amazon asking customers to contact them so you may get some joy there. I've no idea whether an RMA is out of the question, or even a replacement, but seeing as you have an OEM copy of Windows a motherboard replacement could be tricky when it comes to reactivating Windows.
Given the extenuating circumstances I think Microsoft may side with and provide you with a new key to activate if it comes to that, but don't take my word for it. It has been known in the past, I'd have to ask an activation expert to give some more input on that one.
Let me know what you think, but basically I'm putting the blame on the motherboard here and I'm not sure if there's anything else I can recommend. I'll ask for some more bods to take a look in here and see if they can see anything I've missed.
