Windows 10: BSOD: KMODE_EXCEPTION_NOT_HANDLED (1e) usbvideo.sys

Discus and support BSOD: KMODE_EXCEPTION_NOT_HANDLED (1e) usbvideo.sys in Windows 10 BSOD Crashes and Debugging to solve the problem; Hello! While I was streaming the game Dead by Daylight using 2 USB cameras to capture me, my PC encountered a BSOD. I analyzed the dump file, but I'm... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by ChrisChen05, Apr 14, 2019.

  1. BSOD: KMODE_EXCEPTION_NOT_HANDLED (1e) usbvideo.sys


    Hello!


    While I was streaming the game Dead by Daylight using 2 USB cameras to capture me, my PC encountered a BSOD. I analyzed the dump file, but I'm not totally sure what device, process or action specifically caused this crash. Could anyone please take a look at the analysis results? Thanks a lot!


    Regards


    Link for the dump file: https://1drv.ms/u/s!AiJmB2r9w9SohZUkoHRrWe50zHY8Qw



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


    Loading Dump File [D:\Users\****\Downloads\041419-6593-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available


    ************* Path validation summary **************
    Response Time (ms) Location
    Deferred SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows 10 Kernel Version 17134 MP (6 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 17134.1.amd64fre.rs4_release.180410-1804
    Machine Name:
    Kernel base = 0xfffff800`f0a01000 PsLoadedModuleList = 0xfffff800`f0dae2b0
    Debug session time: Sun Apr 14 15:58:42.343 2019
    System Uptime: 0 days 3:14:37.127
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .............................................................
    Loading User Symbols
    Loading unloaded module list
    ..............
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1E, {ffffffffc0000094, fffff80caa352426, ffffef7f91400800, fffff800f0882180}

    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    Probably caused by : usbvideo.sys ( usbvideo!CaptureInitializeStreamHeader+156 )

    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: ffffffffc0000094, The exception code that was not handled
    Arg2: fffff80caa352426, The address that the exception occurred at
    Arg3: ffffef7f91400800, Parameter 0 of the exception
    Arg4: fffff800f0882180, Parameter 1 of the exception

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


    KEY_VALUES_STRING: 1


    STACKHASH_ANALYSIS: 1

    TIMELINE_ANALYSIS: 1


    DUMP_CLASS: 1

    DUMP_QUALIFIER: 400

    BUILD_VERSION_STRING: 17134.1.amd64fre.rs4_release.180410-1804

    SYSTEM_PRODUCT_NAME: To Be Filled By O.E.M.

    SYSTEM_SKU: To Be Filled By O.E.M.

    SYSTEM_VERSION: To Be Filled By O.E.M.

    BIOS_VENDOR: American Megatrends Inc.

    BIOS_VERSION: P1.20

    BIOS_DATE: 10/24/2018

    BASEBOARD_MANUFACTURER: ASRock

    BASEBOARD_PRODUCT: Z390M-ITX/ac

    BASEBOARD_VERSION:

    DUMP_TYPE: 2

    BUGCHECK_P1: ffffffffc0000094

    BUGCHECK_P2: fffff80caa352426

    BUGCHECK_P3: ffffef7f91400800

    BUGCHECK_P4: fffff800f0882180

    EXCEPTION_CODE: (NTSTATUS) 0xc0000094 - {EXCEPTION} Integer division by zero.

    FAULTING_IP:
    usbvideo!CaptureInitializeStreamHeader+156
    fffff80c`aa352426 f7f1 div eax,ecx

    EXCEPTION_PARAMETER1: ffffef7f91400800

    EXCEPTION_PARAMETER2: fffff800f0882180

    BUGCHECK_STR: 0x1E_c0000094

    CPU_COUNT: 6

    CPU_MHZ: e70

    CPU_VENDOR: GenuineIntel

    CPU_FAMILY: 6

    CPU_MODEL: 9e

    CPU_STEPPING: c

    CPU_MICROCODE: 6,9e,c,0 (F,M,S,R) SIG: 9E'00000000 (cache) 9E'00000000 (init)

    BLACKBOXBSD: 1 (!blackboxbsd)


    BLACKBOXPNP: 1 (!blackboxpnp)


    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

    PROCESS_NAME: DeadByDaylight

    CURRENT_IRQL: 2

    ANALYSIS_SESSION_HOST: ****

    ANALYSIS_SESSION_TIME: 04-14-2019 21:57:28.0531

    ANALYSIS_VERSION: 10.0.17763.132 amd64fre

    DPC_STACK_BASE: FFFFF800F380AFB0

    EXCEPTION_RECORD: 0000000000000007 -- (.exr 0x7)
    Cannot read Exception record @ 0000000000000007

    LAST_CONTROL_TRANSFER: from fffff800f0c41b4a to fffff800f0bab0a0

    STACK_TEXT:
    fffff800`f3809108 fffff800`f0c41b4a : 00000000`0000001e ffffffff`c0000094 fffff80c`aa352426 ffffef7f`91400800 : nt!KeBugCheckEx
    fffff800`f3809110 fffff800`f0bb394d : fffff800`f0df1000 fffff800`f0a01000 00058218`00952000 00000000`00000000 : nt!KiFatalExceptionHandler+0x22
    fffff800`f3809150 fffff800`f0abfb16 : fffff800`f3809280 fffff800`f3809740 00000000`00000000 fffff800`f380a058 : nt!RtlpExecuteHandlerForException+0xd
    fffff800`f3809180 fffff800`f0ac1613 : fffff800`f380a058 fffff800`f3809da0 fffff800`f380a058 ffffa486`29034110 : nt!RtlDispatchException+0x416
    fffff800`f3809870 fffff800`f0bbbd42 : 00000000`00000007 00000000`00000000 fffff800`f3809fc9 00000074`00000011 : nt!KiDispatchException+0x1f3
    fffff800`f3809f20 fffff800`f0bb57c6 : ffffa486`1ebd5870 ffffa486`1f6abaf0 ffffa486`1f6abaf0 fffff800`f0a99e69 : nt!KiExceptionDispatch+0xc2
    fffff800`f380a100 fffff80c`aa352426 : 00000000`00000000 ffffa486`2394d030 00000000`00000000 ffffa486`2482db28 : nt!KiDivideErrorFault+0x2c6
    fffff800`f380a290 fffff80c`aa352885 : 00000000`00000002 fffff80c`aa358e78 ffffa486`00000000 ffffa486`1f742000 : usbvideo!CaptureInitializeStreamHeader+0x156
    fffff800`f380a320 fffff80c`aa35398f : ffffa486`1f6f6700 ffffa486`1f742000 ffffa486`1f685590 fffff80c`aa2e165a : usbvideo!CaptureEjectAndAcquireDataFrame+0xf1
    fffff800`f380a3c0 fffff80c`aa346bdc : ffffa486`1f7421b8 fffff800`f380a598 ffffa486`1f742000 ffffa486`1f685590 : usbvideo!CaptureProcessDataPayload+0xb8b
    fffff800`f380a530 fffff80c`aa346914 : ffffa486`1f685590 ffffa486`00000000 00000000`00000000 ffffa486`1f6d77b0 : usbvideo!CaptureCompleteBulk+0x2bc
    fffff800`f380a5e0 fffff800`f0a9c72f : ffffa486`1f6ac010 fffff800`f380a6c9 ffffa486`23db7630 ffffa486`1f6ac443 : usbvideo!CaptureCompleteCallbackBulk+0x54
    fffff800`f380a610 fffff800`f0a9c5f7 : ffffa486`23ad62e0 00000000`00000200 fffff80c`a4fcde40 00000000`0000000a : nt!IopfCompleteRequest+0x11f
    fffff800`f380a730 fffff80c`a4f29627 : ffffa486`2439f670 ffffa486`1f6ac010 00000000`00000002 ffffa486`1f700020 : nt!IofCompleteRequest+0x17
    fffff800`f380a760 fffff80c`a4f272fb : fffff800`00000001 fffff80c`00000000 00000000`ffffff02 ffffa486`00000001 : Wdf01000!FxRequest::CompleteInternal+0x247 [minkernel\wdf\framework\shared\core\fxrequest.cpp @ 869]
    fffff800`f380a820 fffff80c`ac42f336 : 00000000`ffffff02 ffffa486`2439f670 ffffa486`1f700400 ffffa486`1f700400 : Wdf01000!imp_WdfRequestComplete+0x8b [minkernel\wdf\framework\shared\core\fxrequestapi.cpp @ 436]
    fffff800`f380a880 fffff80c`ac42d469 : ffffa486`2439f810 00000000`00000001 ffffa486`2439f8a0 fffff800`f380ab68 : USBXHCI!Bulk_Transfer_CompleteCancelable+0x182
    fffff800`f380a8e0 fffff80c`ac42bde0 : ffffa486`23890900 fffff80c`00000000 ffffa486`1f6dca00 00000000`00000000 : USBXHCI!Bulk_ProcessTransferEventWithED1+0x40d
    fffff800`f380a9a0 fffff80c`ac4212c3 : 00000000`00000000 00000002`253498a0 00000000`00000000 00000000`00000000 : USBXHCI!Bulk_EP_TransferEventHandler+0x10
    fffff800`f380a9d0 fffff80c`ac414608 : 00000000`00000001 00000000`00000004 ffffa486`2429f2f0 fffff800`f380aad1 : USBXHCI!TR_TransferEventHandler+0x17
    fffff800`f380aa00 fffff80c`ac4337ae : fffff800`f380ab68 fffff800`f380ab38 00000000`00000000 fffff800`f380ab40 : USBXHCI!Endpoint_TransferEventHandler+0x148
    fffff800`f380aa90 fffff80c`ac41744d : ffffa486`2429f220 fffff800`f380ab89 ffffa486`2429f2f0 00000000`00000000 : USBXHCI!UsbDevice_TransferEventHandler+0x92
    fffff800`f380aaf0 fffff80c`ac417e6c : ffffa486`27fba000 ffffa486`1d4d0190 00000000`00000f68 ffffa486`2429f020 : USBXHCI!Interrupter_DeferredWorkProcessor+0x4c5
    fffff800`f380abf0 fffff80c`a4f21fad : 00000000`00000f44 00000000`00400a02 00000000`00000000 fffff800`f0882180 : USBXHCI!Interrupter_WdfEvtInterruptDpc+0xc
    fffff800`f380ac20 fffff800`f0a40367 : fffff800`f380acb8 ffffa486`1d4ce000 fffff800`f0882180 fffff800`00000002 : Wdf01000!FxInterrupt::_InterruptDpcThunk+0x9d [minkernel\wdf\framework\shared\irphandlers\pnp\km\interruptobjectkm.cpp @ 410]
    fffff800`f380ac60 fffff800`f0a3f9bb : 00000000`0000000e 00000000`00000000 ffffa486`1f16a700 00000000`00000019 : nt!KiExecuteAllDpcs+0x2e7
    fffff800`f380ada0 fffff800`f0bb1ff5 : 00000000`00000000 fffff800`f0882180 ffffb80c`f4bdeeb0 00000000`00000000 : nt!KiRetireDpcList+0x1db
    fffff800`f380afb0 fffff800`f0bb1df0 : ffffb80c`f4bdee10 00000000`00000000 00000000`01000010 00000000`00000287 : nt!KxRetireDpcList+0x5
    ffffb80c`f4bdee00 fffff800`f0bb1573 : ffffa486`27e1d700 fffff800`f0bb2175 ffffdf81`c9be1180 ffffa486`291bc700 : nt!KiDispatchInterruptContinue
    ffffb80c`f4bdee30 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDpcInterrupt+0x2a3


    THREAD_SHA1_HASH_MOD_FUNC: 07c708ea5d52e685320e27f0ddbce0efacafac16

    THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 3c39466f5e4de89bed62d4b61f5635825af6e591

    THREAD_SHA1_HASH_MOD: 95b79b12114ff2df78dc9164c3861573302ada8e

    FOLLOWUP_IP:
    usbvideo!CaptureInitializeStreamHeader+156
    fffff80c`aa352426 f7f1 div eax,ecx

    FAULT_INSTR_CODE: b541f1f7

    SYMBOL_STACK_INDEX: 7

    SYMBOL_NAME: usbvideo!CaptureInitializeStreamHeader+156

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: usbvideo

    IMAGE_NAME: usbvideo.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 225955d2

    IMAGE_VERSION: 10.0.17134.1

    STACK_COMMAND: .thread ; .cxr ; kb

    BUCKET_ID_FUNC_OFFSET: 156

    FAILURE_BUCKET_ID: 0x1E_c0000094_usbvideo!CaptureInitializeStreamHeader

    BUCKET_ID: 0x1E_c0000094_usbvideo!CaptureInitializeStreamHeader

    PRIMARY_PROBLEM_CLASS: 0x1E_c0000094_usbvideo!CaptureInitializeStreamHeader

    TARGET_TIME: 2019-04-14T07:58:42.000Z

    OSBUILD: 17134

    OSSERVICEPACK: 706

    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: 2019-04-02 15:50:10

    BUILDDATESTAMP_STR: 180410-1804

    BUILDLAB_STR: rs4_release

    BUILDOSVER_STR: 10.0.17134.1.amd64fre.rs4_release.180410-1804

    ANALYSIS_SESSION_ELAPSED_TIME: 1b0e

    ANALYSIS_SOURCE: KM

    FAILURE_ID_HASH_STRING: km:0x1e_c0000094_usbvideo!captureinitializestreamheader

    FAILURE_ID_HASH: {45a03334-b1fd-ffd1-719d-2681e4ee530c}

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

    :)
     
    ChrisChen05, Apr 14, 2019
    #1
  2. axe0 Win User
  3. Shirubidu Win User
    KMODE_EXCEPTION_NOT_HANDLED (wdf01000.sys)


    Here's the BIOS values


    BSOD: KMODE_EXCEPTION_NOT_HANDLED (1e) usbvideo.sys [​IMG]
     
    Shirubidu, Apr 14, 2019
    #3
  4. BSOD: KMODE_EXCEPTION_NOT_HANDLED (1e) usbvideo.sys

    KMODE_EXCEPTION_NOT_HANDLED on igdkmd64.sys

    My computer keeps giving me the blue screen of death and giving me error code

    KMODE_EXCEPTION_NOT_HANDLED on igdkmd64.sys

    How can this be fixed?
     
    JordanLees1, Apr 14, 2019
    #4
Thema:

BSOD: KMODE_EXCEPTION_NOT_HANDLED (1e) usbvideo.sys

Loading...
  1. BSOD: KMODE_EXCEPTION_NOT_HANDLED (1e) usbvideo.sys - Similar Threads - BSOD KMODE_EXCEPTION_NOT_HANDLED usbvideo

  2. BSOD: KMODE_EXCEPTION_NOT_HANDLED 1e

    in Windows 10 BSOD Crashes and Debugging
    BSOD: KMODE_EXCEPTION_NOT_HANDLED 1e: I've been using my computer fine since i upgraded like 2 weeks ago, but since today I'm getting back to back bluescreens and I have no idea what's going on. the dumpfile showed the following: SYMBOL_NAME: nt!MiReadyStandbyPageForActive+b8MODULE_NAME: ntSTACK_COMMAND: .cxr;...
  3. BSOD: KMODE_EXCEPTION_NOT_HANDLED 1e

    in Windows 10 Gaming
    BSOD: KMODE_EXCEPTION_NOT_HANDLED 1e: I've been using my computer fine since i upgraded like 2 weeks ago, but since today I'm getting back to back bluescreens and I have no idea what's going on. the dumpfile showed the following: SYMBOL_NAME: nt!MiReadyStandbyPageForActive+b8MODULE_NAME: ntSTACK_COMMAND: .cxr;...
  4. BSOD: KMODE_EXCEPTION_NOT_HANDLED 1e

    in Windows 10 Software and Apps
    BSOD: KMODE_EXCEPTION_NOT_HANDLED 1e: I've been using my computer fine since i upgraded like 2 weeks ago, but since today I'm getting back to back bluescreens and I have no idea what's going on. the dumpfile showed the following: SYMBOL_NAME: nt!MiReadyStandbyPageForActive+b8MODULE_NAME: ntSTACK_COMMAND: .cxr;...
  5. KMODE_EXCEPTION_NOT_HANDLED 1e BSOD

    in Windows 10 Gaming
    KMODE_EXCEPTION_NOT_HANDLED 1e BSOD: Always get a BSOD for my computer in recent month.I already use DISM.exe /Online /Cleanup-image /Restorehealthsfc /scannowto check and no error reported form these toolsThe recent BSOD error dump:********************************************************************************...
  6. KMODE_EXCEPTION_NOT_HANDLED 1e BSOD

    in Windows 10 Software and Apps
    KMODE_EXCEPTION_NOT_HANDLED 1e BSOD: Always get a BSOD for my computer in recent month.I already use DISM.exe /Online /Cleanup-image /Restorehealthsfc /scannowto check and no error reported form these toolsThe recent BSOD error dump:********************************************************************************...
  7. KMODE_EXCEPTION_NOT_HANDLED 1e BSOD

    in Windows 10 BSOD Crashes and Debugging
    KMODE_EXCEPTION_NOT_HANDLED 1e BSOD: Always get a BSOD for my computer in recent month.I already use DISM.exe /Online /Cleanup-image /Restorehealthsfc /scannowto check and no error reported form these toolsThe recent BSOD error dump:********************************************************************************...
  8. BSOD: KMODE_EXCEPTION_NOT_HANDLED 1E

    in Windows 10 BSOD Crashes and Debugging
    BSOD: KMODE_EXCEPTION_NOT_HANDLED 1E: Hi there,Standard BSOD issue. Minidump below.https://www.dropbox.com/s/bd7t6u4odp0gnv1/062721-10750-01.dmp?dl=0If anyone can help troubleshoot what the issue is would be much appreciated.Thanks....
  9. BSOD KMODE_EXCEPTION_NOT_HANDLED 1e

    in Windows 10 BSOD Crashes and Debugging
    BSOD KMODE_EXCEPTION_NOT_HANDLED 1e: A friend gets BSOD all the time after reboot in 1~10 min. The memory dump file gives the following information. I dont know how to pinpoint witch driver or application is failing. Can you help me? KMODE_EXCEPTION_NOT_HANDLED 1eThis is a very common bugcheck. Usually the...
  10. KMODE_EXCEPTION_NOT_HANDLED 1e

    in Windows 10 BSOD Crashes and Debugging
    KMODE_EXCEPTION_NOT_HANDLED 1e: Hey everybody, I've been searching for a sulution to my problem for quite some time and decided to ask in this Forum. So everytime I livestream using OBS i get the BSOD KMODE_EXCEPTION_NOT_HANDLED and I don't know what's causing this. Here's a Dropbox link for a zip...