New Intel build, BSOD 9f Randomly.

Welcome.

Disable USB Selective Suspense.
USB Selective Suspend - Turn On or Off

Code:

Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\USER\Downloads\Compressed\BEEG-PC-Wed_12_31_2014_112919_35\123014-5085-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`02324c32?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`0020e712?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00b9c3c0?
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`02c1a000 PsLoadedModuleList = 0xfffff800`02e5d890
Debug session time: Wed Dec 31 09:43:02.608 2014 (UTC + 6:00)
System Uptime: 1 days 0:04:01.826
Loading Kernel Symbols
...............................................................
................................................................
...............................................
Loading User Symbols
Loading unloaded module list
...........................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa800a580bf0, fffff80000b9c3d8, fffffa800aab5c60}

*** WARNING: Unable to verify timestamp for iusb3hub.sys
*** ERROR: Module load completed but symbols could not be loaded for iusb3hub.sys
Probably caused by : iusb3hub.sys

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: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa800a580bf0, Physical Device Object of the stack
Arg3: fffff80000b9c3d8, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: fffffa800aab5c60, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  iusb3hub.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  52fb553e

MODULE_NAME: iusb3hub

FAULTING_MODULE: fffff8800516e000 iusb3hub

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

TAG_NOT_DEFINED_c000000f:  FFFFF80000BA2FB0

STACK_TEXT:  
fffff800`00b9c388 fffff800`02cff8d2 : 00000000`0000009f 00000000`00000003 fffffa80`0a580bf0 fffff800`00b9c3d8 : nt!KeBugCheckEx
fffff800`00b9c390 fffff800`02c9a85c : fffff800`00b9c4c0 fffff800`00b9c4c0 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x33af0
fffff800`00b9c430 fffff800`02c9a6f6 : fffff800`02e40140 00000000`0054bf07 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`00b9c4a0 fffff800`02c9a5de : 000000c9`ba8d8c98 fffff800`00b9cb18 00000000`0054bf07 fffff800`02e0d368 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9caf0 fffff800`02c9a3c7 : 00000044`f35258c1 00000044`0054bf07 00000044`f35258bc 00000000`00000007 : nt!KiTimerExpiration+0x1be
fffff800`00b9cb90 fffff800`02c878ca : fffff800`02e0ae80 fffff800`02e18cc0 00000000`00000001 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_ffusb2audio_IMAGE_iusb3hub.sys

BUCKET_ID:  X64_0x9F_3_ffusb2audio_IMAGE_iusb3hub.sys

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

0: kd> lmvm iusb3hub
start             end                 module name
fffff880`0516e000 fffff880`051ce000   iusb3hub T (no symbols)           
    Loaded symbol image file: iusb3hub.sys
    Image path: \SystemRoot\system32\DRIVERS\iusb3hub.sys
    Image name: iusb3hub.sys
    Timestamp:        Wed Feb 12 17:04:30 2014 (52FB553E)
    CheckSum:         0005CEC1
    ImageSize:        00060000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 Clean boot

• Troubleshoot Application Conflicts by Performing a Clean Startup

Reduce items at start-up. No software except anti-virus is required plus doing this improves the time for logging into windows:

• How to Change, Add, or Remove Startup Programs in Windows 7

Run the System File Checker that scans the of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible:

• Click on the
• Type CMD on Search
• Left click and Run as Administrator
• Type SFC /scannow

Full tutorial here:

• SFC /SCANNOW Command - System File Checker

That is the nature of a 0x9F BSOD. Post the data following the BSOD posting instructions if you want to get it debugged.