BSOD pretty much at random

Pochly · 04 Jul 2015

About a month back I started to get BSOD every other day for about a week. It seemed to happen mostly when I played Hearthstone, but it wasn't only when I was playing. Also around that time I bought a new psu but since it happened rarely I didn't think it was the issue. It's been a few weeks without any BSOD until today.

Arc · 04 Jul 2015

Uninstall Networx, it is always problematic.

Update the Intel USB3 driver from ASRock > Z77 Extreme6

Report us for any further BSOD after doing these two.
__________________________________________________

Code:

BugCheck 100000B8, {fffffa8007958b50, fffff80003658cc0, 0, 0}

*** WARNING: Unable to verify timestamp for iusb3xhc.sys
*** ERROR: Module load completed but symbols could not be loaded for iusb3xhc.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : iusb3xhc.sys ( iusb3xhc+5fe8 )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

ATTEMPTED_SWITCH_FROM_DPC (b8)
A wait operation, attach process, or yield was attempted from a DPC routine.
This is an illegal operation and the stack track will lead to the offending
code and original DPC routine.
Arguments:
Arg1: fffffa8007958b50, Original thread which is the cause of the failure
Arg2: fffff80003658cc0, New thread
Arg3: 0000000000000000, Stack address of the original thread
Arg4: 0000000000000000

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


FAULTING_THREAD:  fffffa8007958b50

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0xB8

PROCESS_NAME:  SeriousBit.Net

CURRENT_IRQL:  2

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

DPC_STACK_BASE:  FFFFF80000BA0FB0

LAST_CONTROL_TRANSFER:  from fffff800034ce802 to fffff800034cd2aa

STACK_TEXT:  
fffff800`00ba0860 fffff800`034ce802 : fffffa80`07958b50 fffffa80`07958b50 fffff880`00000000 fffff880`00000000 : nt!KiSwapContext+0x7a
fffff800`00ba09a0 fffff800`034d251f : fffffa80`11a65090 fffffa80`0b423988 fffffa80`000000ba fffff880`04d08e20 : nt!KiCommitThreadWait+0x1d2
fffff800`00ba0a30 fffff880`04ca2fe8 : fffff880`04d17e00 00000000`00000000 fffffa80`0b2de000 fffff880`04d17e00 : nt!KeWaitForSingleObject+0x19f
fffff800`00ba0ad0 fffff880`04d17e00 : 00000000`00000000 fffffa80`0b2de000 fffff880`04d17e00 fffff800`0364ae80 : iusb3xhc+0x5fe8
fffff800`00ba0ad8 00000000`00000000 : fffffa80`0b2de000 fffff880`04d17e00 fffff800`0364ae80 fffff880`04cc5901 : iusb3xhc+0x7ae00


STACK_COMMAND:  .thread 0xfffffa8007958b50 ; kb

FOLLOWUP_IP: 
iusb3xhc+5fe8
fffff880`04ca2fe8 ??              ???

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  iusb3xhc+5fe8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: iusb3xhc

IMAGE_NAME:  iusb3xhc.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4f4b6175

FAILURE_BUCKET_ID:  X64_0xB8_VRF_iusb3xhc+5fe8

BUCKET_ID:  X64_0xB8_VRF_iusb3xhc+5fe8

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0xb8_vrf_iusb3xhc+5fe8

FAILURE_ID_HASH:  {ed1d5ca9-1293-c11f-6e93-1840ffc15d66}

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

0: kd> lmvm iusb3xhc
start             end                 module name
fffff880`04c9d000 fffff880`04d61000   iusb3xhc T (no symbols)           
    Loaded symbol image file: iusb3xhc.sys
    Image path: iusb3xhc.sys
    Image name: iusb3xhc.sys
    Timestamp:        Mon Feb 27 16:26:53 2012 (4F4B6175)
    CheckSum:         000C5E11
    ImageSize:        000C4000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4