Hi -
Overclocking can cause all sorts of problems. If you are overclocking your system, please return all overclocked components to their stock speeds. If the BSOD's are found not to be caused by the overclock, you can re-overclock the components once we have finished the diagnostics.
Please upload your msinfo32.nfo file. To get this: Start Menu -> Type msinfo32 into the Search programs and files box -> When it opens, go to File, Save -> Save as msinfo32.nfo and save in a place you will remember -> Let it finish the process of gathering and saving the system info -> Right click the .nfo file, click send to compressed (zipped) folder -> Upload the .zip file here.
Please upload your msinfo32.txt file. To get this: Start Menu -> Type msinfo32 into the Search programs and files box -> When it opens, go to File, Export -> Save as msinfo32.txt and save in a place you will remember -> Let it finish the process of gathering and saving the system info -> Right click the .txt file, click send to compressed (zipped) folder -> Upload the .zip file here.
Please disable
driver verifier for the time being.
Update the Etron USB 3.0 Extensible Hub Driver to the latest version available.
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000009F, {4, 258, fffffa8006789b50, fffff800060e33d0}
*** WARNING: Unable to verify timestamp for EtronHub3.sys
*** ERROR: Module load completed but symbols could not be loaded for EtronHub3.sys
Implicit thread is now fffffa80`06789b50
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : EtronHub3.sys ( EtronHub3+5f51 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time (usually 10 minutes).
Arguments:
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
subsystem.
Arg2: 0000000000000258, Timeout in seconds.
Arg3: fffffa8006789b50, The thread currently holding on to the Pnp lock.
Arg4: fffff800060e33d0, nt!TRIAGE_9F_PNP on Windows 7
Debugging Details:
------------------
Implicit thread is now fffffa80`06789b50
DRVPOWERSTATE_SUBCODE: 4
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff800046bc652 to fffff800046c9b8a
STACK_TEXT:
fffff880`035af070 fffff800`046bc652 : fffffa80`06789b50 fffffa80`06789b50 00000000`00000000 00000000`00000000 : nt!KiSwapContext+0x7a
fffff880`035af1b0 fffff800`046cda9f : fffffa80`0d51f4f0 00000000`00000002 00000000`00000000 fffff880`05b88ff8 : nt!KiCommitThreadWait+0x1d2
fffff880`035af240 fffff880`05b88f51 : 00000000`00000000 00000000`00000000 fffffa80`0ca52000 fffff800`049ae700 : nt!KeWaitForSingleObject+0x19f
fffff880`035af2e0 00000000`00000000 : 00000000`00000000 fffffa80`0ca52000 fffff800`049ae700 fffff880`03365180 : EtronHub3+0x5f51
STACK_COMMAND: kb
FOLLOWUP_IP:
EtronHub3+5f51
fffff880`05b88f51 ?? ???
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: EtronHub3+5f51
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: EtronHub3
IMAGE_NAME: EtronHub3.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4d67ec3b
FAILURE_BUCKET_ID: X64_0x9F_4_EtronHub3+5f51
BUCKET_ID: X64_0x9F_4_EtronHub3+5f51
Followup: MachineOwner
---------
0: kd> lmvm EtronHub3
start end module name
fffff880`05b83000 fffff880`05b8cf80 EtronHub3 T (no symbols)
Loaded symbol image file: EtronHub3.sys
Image path: \SystemRoot\System32\Drivers\EtronHub3.sys
Image name: EtronHub3.sys
Timestamp: Fri Feb 25 23:51:55 2011 (4D67EC3B)
CheckSum: 00011316
ImageSize: 00009F80
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4 HDD:
Upload a screenshot of your hard disk using CrystalDiskInfo:
Make a hard drive test from the hard drive manufacturers website:
RAM:
Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

Note
Pay close attention to part 3 of the tutorial in order to rule out the faulty stick.

Information
Errors are sometimes found after 8 passes.

Tip
Do this test overnight, before going to bed.
Keep us posted.