Windows 10: Random BSODs

  1.    02 Jun 2018 #1

    Random BSODs


    Hello, i was hoping somebody could help me with some issues i've been having, this is the second BSOD i have had in a while, they both seem to come at random, what doesn't change however is the error code; DPC Watchdog Violation.

    From what i can tell this is a software issue, a driver specifically, however i do not know where the problem lies exactly, nor can i seem to figure it out. So, i thought posting here would be the best course of action. The required file has been attached to this post.

    DESKTOP-04VRTSG-za_02-06-2018_104300,02.zip
      My ComputerSystem Spec

  2. axe0's Avatar
    Posts : 13,714
    Windows 10 Pro
       02 Jun 2018 #2




    Random BSODs Diagnostic Test Random BSODs
     DRIVER VERIFIER

    warning   Warning
    Please make a backup of your important files and get your rescue media or create one.
    Please create a restore point.

    Please follow this tutorial to run driver verifier.

    Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

    Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

    If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.

    Note   Note
    Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.
      My ComputersSystem Spec

  3. philc43's Avatar
    Posts : 3,594
    64bit Win 10 Pro ver 1809 Build 17763.55 and W10 Insider Build 18262
       02 Jun 2018 #3

    Scanning the memory records in the stack provides the following clues:

    Code:
     
    0: kd> !dpx
    PDE v11.3 - Copyright 2017 Andrew Richards
    =========================================================================================
    Start memory scan  : 0xfffff8002feb3b78 ($csp)
    End memory scan    : 0xfffff8002feb4000 (ISR Stack Base)
    
    0xfffff8002feb3ba0 : 0xfffff8002d8ee378 : nt!KeDpcWatchdogProfileGlobalTriageBlock
    0xfffff8002feb3bd8 : 0xfffff8002d4f1b8d : nt!KiUpdateRunTime+0x5d
    0xfffff8002feb3c28 : 0xfffff8002d4f2c73 : nt!KeClockInterruptNotify+0x8f3
    0xfffff8002feb3ca8 : 0xfffff8002d8552c8 : nt!KiClockTickTraces+0x48
    0xfffff8002feb3cb8 : 0xfffff8002d535331 : nt!KeInsertQueueDpc+0x11
    0xfffff8002feb3cf8 : 0xfffff8072ef92375 : storport!StorPortNotification+0x85
    0xfffff8002feb3d08 : 0xfffff8002d535331 : nt!KeInsertQueueDpc+0x11
    Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_f32bf428bbff8aa5\nvlddmkm.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Unable to load image \SystemRoot\System32\drivers\iaStorA.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for iaStorA.sys
    *** ERROR: Module load completed but symbols could not be loaded for iaStorA.sys
    0xfffff8002feb3f20 : 0xfffff8002d467d60 : hal!HalpKInterruptHeap+0x8b0
    0xfffff8002feb3f38 : 0xfffff8002d406883 : hal!HalpTimerClockInterrupt+0x63
    0xfffff8002feb3f68 : 0xfffff8002d549195 : nt!KiCallInterruptServiceRoutine+0xa5
    0xfffff8002feb3f70 : 0xfffff8002d467cb0 : hal!HalpKInterruptHeap+0x800
    0xfffff8002feb3f88 : 0xfffff8002d629eaf : nt!KiInterruptSubDispatch+0x10f
    0xfffff8002feb3fa8 : 0xfffff8002d62a10a : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
    0xfffff8002feb3fb8 : 0xfffff8002d467cb0 : hal!HalpKInterruptHeap+0x800
    0xfffff8002feb3fd8 : 0xfffff8002d62a6f7 : nt!KiInterruptDispatchNoLockNoEtw+0x37
    Driver details:
    nvlddmkm.sys Tue May 22 13:18:34 2018
    iaStorA.sys Fri May 2 16:06:56 2014

    The Intel driver looks a little old so it would be worth updating. The graphics driver could simply need reinstalling after completely removing all the graphics related software. The best way to do this is to uninstall everything of Nvidia using Display Driver Uninstaller and install new drivers from your Graphics card manufacturer or from the NVidia website. When you do this be sure the "clean install" box is checked and only install the Graphics driver and the PhysX driver.
      My ComputersSystem Spec

  4. axe0's Avatar
    Posts : 13,714
    Windows 10 Pro
       02 Jun 2018 #4

    @philc43, do you get symbol errors? I do always with this kind of crashes and have a different stack
    Code:
    0: kd> !dpx fffff8002fea0000 fffff8002fea6000 -u
    Start memory scan  : 0xfffff8002fea0000
    End memory scan    : 0xfffff8002fea6000
    
    0xfffff8002fea4fa0 : 0x0000000000000001 :  Trap @ fffff8002fea4fa0
    0xfffff8002fea4fb8 : 0xfffff807311426a3 : pacer!QosTimerConvertPerformanceCounterToMicroseconds+0x1b
    0xfffff8002fea5008 : 0xfffff8072f727434 : tcpip!FlSendNetBufferListChainComplete+0x64
    0xfffff8002fea50c8 : 0xfffff8072fe44e4f : ndis!NdisAllocateNetBufferAndNetBufferList+0x12f
    0xfffff8002fea50e0 : 0xfffff8072fe41c80 : ndis!ndisMSendCompleteNetBufferListsInternal
    0xfffff8002fea5108 : 0xfffff80734d03bd7 : RNDISMP6!ReceivePacketMessage+0x3a7
    0xfffff8002fea51d8 : 0xfffff80734d03733 : RNDISMP6!RndisMIndicateReceive+0x1f3
    0xfffff8002fea5248 : 0xfffff80734cf36f4 : usb80236!IndicateRndisMessage+0xac
    0xfffff8002fea5288 : 0xfffff80734cf1ce5 : usb80236!ReadPipeCompletion+0x95
    0xfffff8002fea52b8 : 0xfffff8002d4e53af : nt!IopfCompleteRequest+0x11f
    0xfffff8002fea5320 : 0xffffba800634ea80 :  dt Wdf01000!FxIoQueue
    0xfffff8002fea5328 : 0xfffff8072e75b7c2 : Wdf01000!FxIoQueue::DispatchEvents+0x1f2
    0xfffff8002fea5358 : 0xfffff8072e75513a : Wdf01000!FxNonPagedObject::Unlock+0x1a
    0xfffff8002fea5378 : 0xfffff8002d78932e : nt!ExFreePoolWithTag+0x2ce
    0xfffff8002fea53a0 : 0xffffba8ffee22020 :  dt Wdf01000!FxIoQueue
    0xfffff8002fea53c8 : 0xffffba8ffe4658a0 :  dt Wdf01000!FxRequestFromLookaside
    0xfffff8002fea53d8 : 0xfffff8002d4e5277 : nt!IofCompleteRequest+0x17
    0xfffff8002fea53f0 : 0xfffff8072e7fde40 : Wdf01000!WPP_FxObject_hpp_Traceguids
    0xfffff8002fea5400 : 0xffffba8ffe4658a0 :  dt Wdf01000!FxRequestFromLookaside
    0xfffff8002fea5408 : 0xfffff8072e759627 : Wdf01000!FxRequest::CompleteInternal+0x247
    0xfffff8002fea5410 : 0xffffba8ffe4658a0 :  dt Wdf01000!FxRequestFromLookaside
    0xfffff8002fea5428 : 0xffffba8ffee22020 :  dt Wdf01000!FxIoQueue
    0xfffff8002fea5458 : 0xfffff8002d78801b : nt!ExFreePool+0xb
    0xfffff8002fea54a8 : 0xffffba8ffa90c570 :  dt Wdf01000!FxDevice
    0xfffff8002fea54c0 : 0xffffba8ffe4658a0 :  dt Wdf01000!FxRequestFromLookaside
    0xfffff8002fea54c8 : 0xfffff8072e7572fb : Wdf01000!imp_WdfRequestComplete+0x8b
    0xfffff8002fea5528 : 0xfffff80732b5f336 : USBXHCI!Bulk_Transfer_CompleteCancelable+0x182
    0xfffff8002fea5538 : 0xffffba8ffe4658a0 :  dt Wdf01000!FxRequestFromLookaside
    0xfffff8002fea5558 : 0xfffff80732b5e3fc : USBXHCI!Bulk_Stage_FreeScatterGatherList+0xc0
    0xfffff8002fea5588 : 0xfffff80732b5d469 : USBXHCI!Bulk_ProcessTransferEventWithED1+0x40d
    0xfffff8002fea5630 : 0xffffba8ffa901f00 : 0xfffff80732b47d20 : USBXHCI!Interrupter_WdfEvtCleanupCallback
    0xfffff8002fea5648 : 0xfffff80732b5bde0 : USBXHCI!Bulk_EP_TransferEventHandler+0x10
    0xfffff8002fea5658 : 0xfffff8002d4f4aa5 : nt!PpmUpdatePerformanceFeedback+0x155
    0xfffff8002fea5668 : 0xfffff8002d4f5492 : nt!KeResumeClockTimerFromIdle+0xd2
    0xfffff8002fea5678 : 0xfffff80732b512c3 : USBXHCI!TR_TransferEventHandler+0x17
    0xfffff8002fea56a8 : 0xfffff80732b44608 : USBXHCI!Endpoint_TransferEventHandler+0x148
    0xfffff8002fea56d0 : 0xffffba8ffa993220 :  !da ""00 INT00""
    0xfffff8002fea56d8 : 0xfffff80732b48292 : USBXHCI!WPP_RECORDER_SF_ddddxdLL+0x17a
    0xfffff8002fea5730 : 0xffffba8ffa901f00 : 0xfffff80732b47d20 : USBXHCI!Interrupter_WdfEvtCleanupCallback
    0xfffff8002fea5738 : 0xfffff80732b637ae : USBXHCI!UsbDevice_TransferEventHandler+0x92
    0xfffff8002fea5798 : 0xfffff80732b4744d : USBXHCI!Interrupter_DeferredWorkProcessor+0x4c5
    0xfffff8002fea5858 : 0xfffff8002d4b7fb6 : nt!ExpQueueWorkItem+0x1c6
    0xfffff8002fea5868 : 0xfffff8002fea5b20 : 0xfffff8072e751f10 : Wdf01000!FxInterrupt::_InterruptDpcThunk
    0xfffff8002fea5898 : 0xfffff80732b47e6c : USBXHCI!Interrupter_WdfEvtInterruptDpc+0xc
    0xfffff8002fea58b0 : 0xfffff8002d8497a0 : nt!PpmCheckStartDpc
    0xfffff8002fea58b8 : 0xffffba8ffa901d20 :  dt Wdf01000!FxInterrupt
    0xfffff8002fea58c0 : 0xfffff8002d84b628 : nt!PpmPerfPolicyLock+0x8
    0xfffff8002fea58c8 : 0xfffff8072e751fad : Wdf01000!FxInterrupt::_InterruptDpcThunk+0x9d
    0xfffff8002fea58e8 : 0xfffff8002d56a39d : nt!ExQueueWorkItem+0x3d
    0xfffff8002fea5908 : 0xfffff8002d4efcc7 : nt!KiExecuteAllDpcs+0x2e7
    0xfffff8002fea5928 : 0xfffff80734de3c97 : dxgmms2!VidMmRangeCurationDpc+0x27
    0xfffff8002fea5940 : 0xffffba8ffa901d20 :  dt Wdf01000!FxInterrupt
    0xfffff8002fea5958 : 0xffffba8ffa901d20 :  dt Wdf01000!FxInterrupt
    0xfffff8002fea5960 : 0xfffff8072e751f10 : Wdf01000!FxInterrupt::_InterruptDpcThunk
    0xfffff8002fea5980 : 0xfffff8002d90b400 : nt!KiInitialThread
    0xfffff8002fea5a20 : 0xfffff8002d90b400 : nt!KiInitialThread
    0xfffff8002fea5a30 : 0xfffff8002d90b400 : nt!KiInitialThread
    0xfffff8002fea5a48 : 0xfffff8002d4ef31b : nt!KiRetireDpcList+0x1db
    0xfffff8002fea5a50 : 0xfffff8002d90b400 : nt!KiInitialThread
    0xfffff8002fea5a58 : 0xfffff8002d51b84a : nt!KiStartThreadCycleAccumulation+0x4a
    0xfffff8002fea5a70 : 0xfffff8002d90b400 : nt!KiInitialThread
    0xfffff8002fea5a88 : 0xfffff8002d538c33 : nt!KiGroupSchedulingGenerationEnd+0xaf
    0xfffff8002fea5a98 : 0xfffff8002d4084e6 : hal!HalPerformEndOfInterrupt+0x16
    0xfffff8002fea5aa8 : 0xfffff8002d90b400 : nt!KiInitialThread
    0xfffff8002fea5ac8 : 0xfffff8002d62a1a5 : nt!KiInterruptDispatch+0x85
    0xfffff8002fea5b20 : 0xfffff8072e751f10 : Wdf01000!FxInterrupt::_InterruptDpcThunk
    0xfffff8002fea5c18 : 0xfffff8002d630a9d : nt!SwapContext+0x42d
    0xfffff8002fea5c58 : 0xfffff8002d62c3aa : nt!KiIdleLoop+0x5a
    0xfffff8002fea5c78 : 0xfffff8002d90b400 : nt!KiInitialThread
      My ComputersSystem Spec

  5. philc43's Avatar
    Posts : 3,594
    64bit Win 10 Pro ver 1809 Build 17763.55 and W10 Insider Build 18262
       02 Jun 2018 #5

    @axe0 Yes I did get a symbol error. Here is the full result:

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 133, {0, 501, 500, fffff8002d8ee378}
    
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that     ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands to work properly, your symbol path           ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: TickPeriods                                   ***
    ***                                                                   ***
    *************************************************************************
    *** WARNING: Unable to verify checksum for win32k.sys
    Probably caused by : RNDISMP6.SYS ( RNDISMP6!ReceivePacketMessage+3a7 )
    
    Followup:     MachineOwner
    ---------
    
    nt!KeBugCheckEx:
    fffff800`2d628670 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffff800`2feb3b80=0000000000000133
    0: kd> .load pde;!dpx
    =========================================================================================
     PDE v11.3 - Copyright 2017 Andrew Richards
    =========================================================================================
    Start memory scan  : 0xfffff8002feb3b78 ($csp)
    End memory scan    : 0xfffff8002feb4000 (ISR Stack Base)
    
    0xfffff8002feb3ba0 : 0xfffff8002d8ee378 : nt!KeDpcWatchdogProfileGlobalTriageBlock
    0xfffff8002feb3bd8 : 0xfffff8002d4f1b8d : nt!KiUpdateRunTime+0x5d
    0xfffff8002feb3c28 : 0xfffff8002d4f2c73 : nt!KeClockInterruptNotify+0x8f3
    0xfffff8002feb3ca8 : 0xfffff8002d8552c8 : nt!KiClockTickTraces+0x48
    0xfffff8002feb3cb8 : 0xfffff8002d535331 : nt!KeInsertQueueDpc+0x11
    0xfffff8002feb3cf8 : 0xfffff8072ef92375 : storport!StorPortNotification+0x85
    0xfffff8002feb3d08 : 0xfffff8002d535331 : nt!KeInsertQueueDpc+0x11
    Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_f32bf428bbff8aa5\nvlddmkm.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Unable to load image \SystemRoot\System32\drivers\iaStorA.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for iaStorA.sys
    *** ERROR: Module load completed but symbols could not be loaded for iaStorA.sys
    0xfffff8002feb3f20 : 0xfffff8002d467d60 : hal!HalpKInterruptHeap+0x8b0
    0xfffff8002feb3f38 : 0xfffff8002d406883 : hal!HalpTimerClockInterrupt+0x63
    0xfffff8002feb3f68 : 0xfffff8002d549195 : nt!KiCallInterruptServiceRoutine+0xa5
    0xfffff8002feb3f70 : 0xfffff8002d467cb0 : hal!HalpKInterruptHeap+0x800
    0xfffff8002feb3f88 : 0xfffff8002d629eaf : nt!KiInterruptSubDispatch+0x10f
    0xfffff8002feb3fa8 : 0xfffff8002d62a10a : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
    0xfffff8002feb3fb8 : 0xfffff8002d467cb0 : hal!HalpKInterruptHeap+0x800
    0xfffff8002feb3fd8 : 0xfffff8002d62a6f7 : nt!KiInterruptDispatchNoLockNoEtw+0x37

    Full stack:

    Code:
    0: kd> kv
     # Child-SP          RetAddr           : Args to Child                                                           : Call Site
    00 fffff800`2feb3b78 fffff800`2d6692d3 : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
    01 fffff800`2feb3b80 fffff800`2d4f1b8d : 00020d24`96ad1337 fffff800`2c023180 00000000`00000246 00000000`018f9cd4 : nt!KeAccumulateTicks+0x174613
    02 fffff800`2feb3be0 fffff800`2d4f2c73 : fffff780`00000340 fffff800`2c023180 00000000`018f9cd4 00000000`00000000 : nt!KiUpdateRunTime+0x5d
    03 fffff800`2feb3c30 fffff800`2d406883 : 00020d24`96acfb3c ffffba80`02c0102c 00000000`00000000 fffff800`2fea4fa0 : nt!KeClockInterruptNotify+0x8f3
    04 fffff800`2feb3f40 fffff800`2d549195 : fffff800`2d467cb0 ffffba80`02ad5000 00000000`00000000 fffff800`2d629eaf : hal!HalpTimerClockInterrupt+0x63
    05 fffff800`2feb3f70 fffff800`2d62a10a : fffff800`2fea5020 fffff800`2d467cb0 ffffba80`00b69470 ffffba8f`fef975e0 : nt!KiCallInterruptServiceRoutine+0xa5
    06 fffff800`2feb3fb0 fffff800`2d62a6f7 : 00000000`00000001 00000000`00000000 00000000`00000001 fffff807`311426a3 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea (TrapFrame @ fffff800`2feb3e70)
    07 fffff800`2fea4fa0 fffff807`34d03bd7 : 00000000`00000000 ffffba80`00b69470 00000000`00000000 ffffba80`0177d1a0 : nt!KiInterruptDispatchNoLockNoEtw+0x37 (TrapFrame @ fffff800`2fea4fa0)
    08 fffff800`2fea5130 fffff807`34d03733 : 00000000`00000000 ffffba80`02c01000 00000000`00000000 ffffcb65`0000018b : RNDISMP6!ReceivePacketMessage+0x3a7
    09 fffff800`2fea51e0 fffff807`34cf36f4 : ffffba8f`ff21e1c0 ffffba8f`fdc74230 00000000`00000001 ffffba8f`ff21e1c0 : RNDISMP6!RndisMIndicateReceive+0x1f3
    0a fffff800`2fea5250 fffff807`34cf1ce5 : ffffba8f`fdc74230 00000000`00000000 00000000`00000000 00000000`73556f49 : usb80236!IndicateRndisMessage+0xac
    0b fffff800`2fea5290 fffff800`2d4e53af : ffffba8f`f723b2e0 fffff800`2fea5379 00000000`00000000 ffffba8f`f723b7a3 : usb80236!ReadPipeCompletion+0x95
    0c fffff800`2fea52c0 fffff800`2d4e5277 : ffffba8f`fa78bc50 00000000`00000200 fffff807`2e7fde40 00000000`0000000a : nt!IopfCompleteRequest+0x11f
    0d fffff800`2fea53e0 fffff807`2e759627 : ffffba8f`fe4658a0 ffffba8f`f723b2e0 00000000`00000002 ffffba8f`fee22020 : nt!IofCompleteRequest+0x17
    0e (Inline Function) --------`-------- : --------`-------- --------`-------- --------`-------- --------`-------- : Wdf01000!FxIrp::CompleteRequest+0xd (Inline Function @ fffff807`2e759627) [minkernel\wdf\framework\shared\inc\private\km\fxirpkm.hpp @ 75] 
    0f fffff800`2fea5410 fffff807`2e7572fb : fffff800`00000001 fffff807`00000000 00000000`ffffff02 ffffba8f`00000003 : Wdf01000!FxRequest::CompleteInternal+0x247 [minkernel\wdf\framework\shared\core\fxrequest.cpp @ 869] 
    10 (Inline Function) --------`-------- : --------`-------- --------`-------- --------`-------- --------`-------- : Wdf01000!FxRequest::Complete+0x31 (Inline Function @ fffff807`2e7572fb) [minkernel\wdf\framework\shared\inc\private\common\fxrequest.hpp @ 805] 
    11 fffff800`2fea54d0 fffff807`32b5f336 : 00000000`ffffff02 ffffba8f`fe4658a0 ffffba8f`fee22400 ffffba8f`fee22400 : Wdf01000!imp_WdfRequestComplete+0x8b [minkernel\wdf\framework\shared\core\fxrequestapi.cpp @ 436] 
    12 fffff800`2fea5530 fffff807`32b5d469 : ffffba8f`fe465a40 00000000`00000001 ffffba8f`fe465ad0 fffff800`2fea5818 : USBXHCI!Bulk_Transfer_CompleteCancelable+0x182
    13 fffff800`2fea5590 fffff807`32b5bde0 : fffff800`2c028f08 fffff800`2d4f4aa5 00000011`ea84c300 fffff800`2d4f5492 : USBXHCI!Bulk_ProcessTransferEventWithED1+0x40d
    14 fffff800`2fea5650 fffff807`32b512c3 : ffffd52e`704fa1e5 fffff800`00000077 00000000`00000000 00000000`018f97d3 : USBXHCI!Bulk_EP_TransferEventHandler+0x10
    15 fffff800`2fea5680 fffff807`32b44608 : 00000000`00000000 00000000`00000004 ffffba8f`fa901ff0 fffff800`2fea5781 : USBXHCI!TR_TransferEventHandler+0x17
    16 fffff800`2fea56b0 fffff807`32b637ae : fffff800`2fea5818 fffff800`2fea57e8 00000000`00000000 fffff800`2fea57f0 : USBXHCI!Endpoint_TransferEventHandler+0x148
    17 fffff800`2fea5740 fffff807`32b4744d : ffffba8f`fa901f20 fffff800`2fea5839 ffffba8f`fa901ff0 00000145`a37aa164 : USBXHCI!UsbDevice_TransferEventHandler+0x92
    18 fffff800`2fea57a0 fffff807`32b47e6c : fffff800`2fea5b40 fffff800`2c023180 fffff800`2d8497a0 ffffba8f`fa901d20 : USBXHCI!Interrupter_DeferredWorkProcessor+0x4c5
    19 fffff800`2fea58a0 fffff807`2e751fad : fffff800`2fea5a10 000003b8`b4407600 fffff800`00000001 fffff800`2d56a39d : USBXHCI!Interrupter_WdfEvtInterruptDpc+0xc
    1a (Inline Function) --------`-------- : --------`-------- --------`-------- --------`-------- --------`-------- : Wdf01000!FxInterrupt::DpcHandler+0x70 (Inline Function @ fffff807`2e751fad) [minkernel\wdf\framework\shared\irphandlers\pnp\km\interruptobjectkm.cpp @ 75] 
    1b fffff800`2fea58d0 fffff800`2d4efcc7 : 000003b8`b442d8d1 fffff800`2fea5a10 00000000`00024b26 fffff807`34de3c97 : Wdf01000!FxInterrupt::_InterruptDpcThunk+0x9d [minkernel\wdf\framework\shared\irphandlers\pnp\km\interruptobjectkm.cpp @ 410] 
    1c fffff800`2fea5910 fffff800`2d4ef31b : fffff800`2d90b400 fffff800`2d51b84a 00000000`00000001 ffffba8f`f6153080 : nt!KiExecuteAllDpcs+0x2e7
    1d fffff800`2fea5a50 fffff800`2d62c3aa : 00000000`00000000 fffff800`2c023180 00000000`001a6560 fffff800`2d90b400 : nt!KiRetireDpcList+0x1db
    1e fffff800`2fea5c60 00000000`00000000 : fffff800`2fea6000 fffff800`2fea0000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
    Last edited by philc43; 02 Jun 2018 at 14:28.
      My ComputersSystem Spec


 

Related Threads
random BSODs in BSOD Crashes and Debugging
Hello, I've been experiencing many BSOD's lately, happening randomly, mainly while just browsing Internet or even when idle. I've reinstalled Windows 2 days ago, blocked drvier installation via WIndows Update, installed drivers from the Acer's...
Random BSODs in BSOD Crashes and Debugging
Hi! I have some issues with my PC. Its restarts randomly, but is not the usual restart. The screen goes black and if i dont press the reset button it will not boot againit just hangs in there. I looked in event manager and the restart is...
Hi, I would really appreciate it if anyone could shed any light on this. The PC was originally Windows 7 and I upgraded to Windows 10 last year. The crashes seem to be random, sometimes when it's sitting idle, sometimes whilst I'm working. ...
Random BSODs in BSOD Crashes and Debugging
Hi, a few weeks ago i build a System from scratch with this specifications: 2x Xeon E5-2630 V4, Asus Z10PE-D8 WS Mainboard, 64 Gig ECC Ram, Geforce GTX 970, Soundblaster Z, Samsung SSD 950 Pro 512GB NVMe and a bequiet 650 Watt powersupply. After...
Random BSODs on new PC in BSOD Crashes and Debugging
Hi, i'm getting random BSOD erros, on a new computer. I already ran the memtest 86, no erros, and i can't seem to solve the problem. Here is the dump files...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 02:18.
Find Us