BSOD Help

Discussion in 'Windows 10 Blue Screen of Death (BSOD)' started by gallo2fire, May 10, 2016.

  1. gallo2fire

    gallo2fire New Member

    Joined:
    May 10, 2016
    Messages:
    1
    Likes Received:
    0
    I was playing Overwatch when suddenly I got a bsod. I'm assuming hidusb.sys caused the issue but i'm not sure how to go about fixing it.

    Code:
    Executable search path is:
    Windows 10 Kernel Version 10586 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 10586.212.amd64fre.th2_release_sec.160328-1908
    Machine Name:
    Kernel base = 0xfffff801`b381c000 PsLoadedModuleList = 0xfffff801`b3afacd0
    Debug session time: Mon May  9 23:45:22.463 2016 (UTC - 4:00)
    System Uptime: 0 days 0:45:07.090
    Loading Kernel Symbols
    .
    
    Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
    Run !sym noisy before .reload to track down problems loading symbols.
    
    ..............................................................
    ................................................................
    ..................................................
    Loading User Symbols
    Loading unloaded module list
    ............
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1E, {ffffffffc0000005, fffff80052db1105, 0, ffffffffffffffff}
    
    Probably caused by : hidusb.sys ( hidusb!HumInternalIoctl+2aa )
    
    Followup:     MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    KMODE_EXCEPTION_NOT_HANDLED (1e)
    This is a very common bugcheck.  Usually the exception address pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this address.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff80052db1105, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: ffffffffffffffff, Parameter 1 of the exception
    
    Debugging Details:
    ------------------
    
    
    DUMP_CLASS: 1
    
    DUMP_QUALIFIER: 400
    
    BUILD_VERSION_STRING:  10586.212.amd64fre.th2_release_sec.160328-1908
    
    SYSTEM_MANUFACTURER:  MSI
    
    SYSTEM_PRODUCT_NAME:  MS-7977
    
    SYSTEM_SKU:  Default string
    
    SYSTEM_VERSION:  1.0
    
    BIOS_VENDOR:  American Megatrends Inc.
    
    BIOS_VERSION:  1.60
    
    BIOS_DATE:  12/18/2015
    
    BASEBOARD_MANUFACTURER:  MSI
    
    BASEBOARD_PRODUCT:  Z170A GAMING M5 (MS-7977)
    
    BASEBOARD_VERSION:  1.0
    
    DUMP_TYPE:  2
    
    BUGCHECK_P1: ffffffffc0000005
    
    BUGCHECK_P2: fffff80052db1105
    
    BUGCHECK_P3: 0
    
    BUGCHECK_P4: ffffffffffffffff
    
    READ_ADDRESS: fffff801b3b9a520: Unable to get MiVisibleState
    ffffffffffffffff
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.
    
    FAULTING_IP:
    Wdf01000!FxDevice::DispatchWithLock+65 [d:\th\minkernel\wdf\framework\shared\core\fxdevice.cpp @ 1402]
    fffff800`52db1105 488b78d0        mov     rdi,qword ptr [rax-30h]
    
    EXCEPTION_PARAMETER2:  ffffffffffffffff
    
    BUGCHECK_STR:  0x1E_c0000005_R
    
    CPU_COUNT: 8
    
    CPU_MHZ: fa8
    
    CPU_VENDOR:  GenuineIntel
    
    CPU_FAMILY: 6
    
    CPU_MODEL: 5e
    
    CPU_STEPPING: 3
    
    CPU_MICROCODE: 6,5e,3,0 (F,M,S,R)  SIG: 55'00000000 (cache) 55'00000000 (init)
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    ANALYSIS_SESSION_HOST:  DESKTOP-1C58DV3
    
    ANALYSIS_SESSION_TIME:  05-10-2016 00:32:02.0794
    
    ANALYSIS_VERSION: 10.0.10586.567 x86fre
    
    EXCEPTION_RECORD:  0000000000000001 -- (.exr 0x1)
    Cannot read Exception record @ 0000000000000001
    
    TRAP_FRAME:  ffff95858f669407 -- (.trap 0xffff95858f669407)
    Unable to read trap frame at ffff9585`8f669407
    
    LAST_CONTROL_TRANSFER:  from fffff801b39dbafe to fffff801b395e760
    
    STACK_TEXT: 
    fffff801`b56bba38 fffff801`b39dbafe : 00000000`0000001e ffffffff`c0000005 fffff800`52db1105 00000000`00000000 : nt!KeBugCheckEx
    fffff801`b56bba40 fffff801`b396480d : fffff801`b3b4d000 fffff801`b381c000 0004c74c`007cc000 20202020`44415057 : nt!KiFatalExceptionHandler+0x22
    fffff801`b56bba80 fffff801`b3821139 : 00000000`00000000 00000000`000000e9 fffff801`b56bc080 00000000`00000000 : nt!RtlpExecuteHandlerForException+0xd
    fffff801`b56bbab0 fffff801`b381f5a8 : fffff801`b56bc9c8 fffff801`b56bc6e0 fffff801`b56bc9c8 00000000`00000001 : nt!RtlDispatchException+0x429
    fffff801`b56bc1b0 fffff801`b39693c2 : 00000000`00000001 ffffe001`f08b7f20 ffff9585`8f669407 ffffe001`f5dceaa0 : nt!KiDispatchException+0x144
    fffff801`b56bc890 fffff801`b396787d : 014a2814`14141400 00000006`d7e16c74 00000000`00000000 fffff801`b3a4cc33 : nt!KiExceptionDispatch+0xc2
    fffff801`b56bca70 fffff800`52db1105 : ffffe001`f1532280 00000000`00000000 ffffe001`f15c0c00 ffffe001`f1590720 : nt!KiGeneralProtectionFault+0xfd
    fffff801`b56bcc00 fffff800`52f81367 : ffffe001`f1532280 ffffe001`f1532280 ffffe001`f15c0c00 00000000`00000801 : Wdf01000!FxDevice::DispatchWithLock+0x65 [d:\th\minkernel\wdf\framework\shared\core\fxdevice.cpp @ 1402]
    fffff801`b56bcc60 fffff800`52f810be : ffffe001`eeda3010 00000000`00000007 ffffe001`f1532740 00000000`00000000 : ACPI!ACPIIrpDispatchDeviceControl+0x97
    fffff801`b56bcca0 fffff800`55b0169e : 00000000`00000007 ffffe001`f1532280 fffff801`b56bcdc9 00000000`00000001 : ACPI!ACPIDispatchIrp+0xbe
    fffff801`b56bcd10 fffff800`55b014d4 : ffffe001`f1532280 fffff800`55b13098 ffffe001`f15a2a28 00000000`00000000 : usbccgp!DispatchPdoUrb+0x16e
    fffff801`b56bce30 fffff800`55b011b1 : ffffe001`f1549a28 ffffe001`f1549a20 ffffe001`f1532280 fffff800`55b130a8 : usbccgp!DispatchPdoInternalDeviceControl+0x84
    fffff801`b56bce90 fffff800`55bb12aa : ffffe001`f15498d0 00000000`00000000 ffffe001`00000000 ffffe001`f1532280 : usbccgp!USBC_Dispatch+0x1b1
    fffff801`b56bcf50 fffff800`55bd2222 : ffffe001`00000000 ffffe001`f15d2810 ffffe001`f15d2810 fffff801`b3a4c2a1 : hidusb!HumInternalIoctl+0x2aa
    fffff801`b56bd240 fffff800`55bd2000 : ffffe001`f23d82b0 00000000`00000006 fffff800`55be61f0 00000000`00000008 : HIDCLASS!HidpSubmitInterruptRead+0x152
    fffff801`b56bd2c0 fffff801`b3896596 : ffffe001`f1532280 ffffe001`f1532280 ffffe001`f15d2810 ffffe001`f1532601 : HIDCLASS!HidpInterruptReadComplete+0x750
    fffff801`b56bd3a0 fffff800`52db7ffb : 00000000`00000000 00000000`00000000 ffffe001`f260b900 00000000`00000001 : nt!IopfCompleteRequest+0x216
    fffff801`b56bd4c0 fffff800`52db55f0 : fffff801`b56bd702 fffff800`52dbfd36 ffffe001`00000001 ffffe001`f1532280 : Wdf01000!FxRequest::CompleteInternal+0x25b [d:\th\minkernel\wdf\framework\shared\core\fxrequest.cpp @ 861]
    fffff801`b56bd570 fffff800`55e7287f : ffffe001`f26001c0 ffffe001`f2600020 ffffe001`f260bce0 ffffe001`f26001c0 : Wdf01000!imp_WdfRequestComplete+0x90 [d:\th\minkernel\wdf\framework\shared\core\fxrequestapi.cpp @ 436]
    fffff801`b56bd5d0 fffff800`55e7da69 : ffffe001`f26001c0 ffffe001`f13b1b00 ffffe001`f2600240 fffff801`b56bd748 : USBXHCI!Bulk_Transfer_CompleteCancelable+0x177
    fffff801`b56bd630 fffff800`55e7b309 : 00000000`000004c0 ffffe001`f0898b10 00000000`000004c0 ffffe001`f13b1bb0 : USBXHCI!Bulk_ProcessTransferEventWithED1+0x3d9
    fffff801`b56bd6d0 fffff801`b388a6a0 : 00001b14`45174d8c fffff801`b3b39180 fffff801`b56bd8c0 fffff801`b3b39180 : USBXHCI!Interrupter_WdfEvtInterruptDpc+0x759
    fffff801`b56bd7c0 fffff801`b3889db9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExecuteAllDpcs+0x270
    fffff801`b56bd910 fffff801`b396151a : 00000000`00000000 fffff801`b3b39180 fffff801`b3baf740 ffffe001`f32c8840 : nt!KiRetireDpcList+0xe9
    fffff801`b56bdb60 00000000`00000000 : fffff801`b56be000 fffff801`b56b7000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
    
    
    STACK_COMMAND:  kb
    
    THREAD_SHA1_HASH_MOD_FUNC:  eed988b1b4c2afda972fc7213b2d7f1d2438c739
    
    THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  812402ca51f2a669721ac487eb91380fe9a27329
    
    THREAD_SHA1_HASH_MOD:  10af56dc21cbacd33164e0ff4e09f5a7f1ffb4a4
    
    FOLLOWUP_IP:
    hidusb!HumInternalIoctl+2aa
    fffff800`55bb12aa 8bf8            mov     edi,eax
    
    FAULT_INSTR_CODE:  8844f88b
    
    SYMBOL_STACK_INDEX:  d
    
    SYMBOL_NAME:  hidusb!HumInternalIoctl+2aa
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: hidusb
    
    IMAGE_NAME:  hidusb.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  5632d8e8
    
    IMAGE_VERSION:  10.0.10586.0
    
    BUCKET_ID_FUNC_OFFSET:  2aa
    
    FAILURE_BUCKET_ID:  0x1E_c0000005_R_hidusb!HumInternalIoctl
    
    BUCKET_ID:  0x1E_c0000005_R_hidusb!HumInternalIoctl
    
    PRIMARY_PROBLEM_CLASS:  0x1E_c0000005_R_hidusb!HumInternalIoctl
    
    TARGET_TIME:  2016-05-10T03:45:22.000Z
    
    OSBUILD:  10586
    
    OSSERVICEPACK:  0
    
    SERVICEPACK_NUMBER: 0
    
    OS_REVISION: 0
    
    SUITE_MASK:  784
    
    PRODUCT_TYPE:  1
    
    OSPLATFORM_TYPE:  x64
    
    OSNAME:  Windows 10
    
    OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS Personal
    
    OS_LOCALE: 
    
    USER_LCID:  0
    
    OSBUILD_TIMESTAMP:  2016-03-29 02:19:02
    
    BUILDDATESTAMP_STR:  160328-1908
    
    BUILDLAB_STR:  th2_release_sec
    
    BUILDOSVER_STR:  10.0.10586.212.amd64fre.th2_release_sec.160328-1908
    
    ANALYSIS_SESSION_ELAPSED_TIME: 5637
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:0x1e_c0000005_r_hidusb!huminternalioctl
    
    FAILURE_ID_HASH:  {1db1b3ef-c820-f961-4df4-46999018d214}
    
    Followup:     MachineOwner
    ---------
    
     
  2. holdum333

    holdum333 Banned

    Joined:
    Mar 27, 2016
    Messages:
    1,244
    Likes Received:
    147
    Hi Welcome to the forum. The people that deal with BSOD will help you as soon as they can!
    Please be patient and someone will help you. We have the best BSOD help here on Windows Forum, so just be patient!;)
     
  3. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Joined:
    Aug 28, 2007
    Messages:
    31,830
    Likes Received:
    1,565
    Hi,
    ideally we need to read your actual dump files. Please read the following thread and post the results:
    How to ask for help with a BSOD problem

    hidusb.sys relates to your Windows USB driver although this might not be the actual problem driver which is why we need to see the dump files really.
     

Share This Page

Loading...