Volmgr 161 + WHEA

Page 7 of 19 FirstFirst ... 5678917 ... LastLast

  1. Posts : 95
    Windows 10
    Thread Starter
       #61

    DESKTOP-31HHLHG-(2023-04-27_11-35-20).zip

    http://speccy.piriform.com/results/c...KrDSqU5PZmVeao

    One thing I noticed right off the bat is the speccy seems to say my RAM is @ 1800mhz? I double checked and itís certainly set to 3600mhz in bios and says 3600mhz in task manager as well, but still strange. Iím not familiar with the whole SLI thing and not sure if that comes into play here, just thought to mention it.
      My Computer


  2. Posts : 264
    Windows 10 Home 21H2
       #62

    If you haven't already done so, please follow the instructions here to disable Automatic restart when a crash occurs. Also, follow the instructions here in the top reply from Moab to show the parameters of the bugcheck on the BSOD displayed when a crash occurs. If the first parameter ends in 0x10 then it's likely a problem with a PCIe device and usually it means a problem with an NVMe drive or the m.2 slot. That you're not getting dump files suggests one of those is the problem, unless I've missed something in the thread.
      My Computer


  3. Posts : 95
    Windows 10
    Thread Starter
       #63

    I'll keep that in mind, thanks cwsink! Auto-restart has always been disabled, but I'll take a look at the bugcheck parameters next time it occurs.

    So another update- Re-correcting my correction about the bad displayport cable. I just swapped it out with a brand new one, and as soon as I loaded up Apex or Minecraft, this started to occur on the right monitor. I'm feeling like this HAS to have something to do with whatever's going on...

    Video.mov - Google Drive
      My Computer


  4. Posts : 402
    Windows 10 and Windows 11
       #64

    That definitely isn't right and since we're looking at WHEA BSODs I would think it's likely connected. You said in your OP that you've changed every single part of the PC, did that include RTX3060?

    Can you also have a look in C:\Windows\LiveKernelReports and check through any folder structure in there for any dump files please. If you find any then upload them. There have been some live dumps written...
    Code:
    LastWriteTime         Size (MB) FullName                                                        
    -------------         --------- --------                                                        
    4/18/2023 7:56:08 PM    1541.48 C:\Windows\LiveKernelReports\NDIS-20230418-1956.dmp             
    4/18/2023 7:56:08 PM       1.09 C:\Windows\LiveKernelReports\NDIS\NDIS-20230418-1956.dmp        
    4/14/2023 12:46:54 PM      0.25 C:\Windows\LiveKernelReports\USBHUB3\USBHUB3-20230414-1246.dmp  
    4/14/2023 2:23:22 PM       2.26 C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20230414-1423.dmp
    4/22/2023 1:05:05 PM       0.26 C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20230422-1305.dmp
    4/22/2023 9:30:11 PM       0.26 C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20230422-2130.dmp
    4/25/2023 10:50:06 PM      0.26 C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20230425-2250.dmp
    These are dumps taken on-the-fly when a problem occurs (and which are typically recovered). They are sent to Microsoft as part of normal problem reporting and then typically deleted. It's possible then that this folder is empty, but if not please upload.

    For information: The NDIS dumps will be related to a networking issue (NDIS = Networking Driver Interface Specification). The USBHUB3 dump will be related to something attached to a USB3 port. The watchdog dumps are related to something that took longer than expected but which isn't an actual failure. They will be particularly interesting.
      My Computer


  5. Posts : 95
    Windows 10
    Thread Starter
       #65

    It's an RTX 3080, and yes I had that RMA'd as well and they sent me a new one because they couldn't fix the first one...

    NDIS-20230418.dmp file:


    ************* Preparing the environment for Debugger Extensions Gallery repositories **************
    ExtensionRepository : Implicit
    UseExperimentalFeatureForNugetShare : false
    AllowNugetExeUpdate : false

    - Configuring repositories
    ----> Repository : LocalInstalled, Enabled: true
    ----> Repository : UserExtensions, Enabled: true


    ************* Waiting for Debugger Extensions Gallery to Initialize **************
    .
    ----> Repository : UserExtensions, Enabled: true, Packages count: 0
    ----> Repository : LocalInstalled, Enabled: true, Packages count: 36

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


    Loading Dump File [C:\Windows\LiveKernelReports\NDIS-20230418-1956.dmp]
    Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

    Symbol search path is: srv*
    Executable search path is:
    Windows 10 Kernel Version 19045 MP (16 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
    Kernel base = 0xfffff804`7a400000 PsLoadedModuleList = 0xfffff804`7b02a2d0
    Debug session time: Tue Apr 18 19:56:07.077 2023 (UTC - 7:00)
    System Uptime: 0 days 0:11:01.622
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ................................................................
    ..........
    Loading User Symbols

    Loading unloaded module list
    ..........
    For analysis of this file, run !analyze -v
    nt!IopLiveDumpEndMirroringCallback+0xb4:
    fffff804`7adaf0f4 498d8e00010000 lea rcx,[r14+100h]
    0: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    BUGCODE_NDIS_DRIVER_LIVE_DUMP (15e)
    The operating system recovered from an error in a networking driver.
    (This code can never be used for a real BugCheck; it is used to identify live dumps.)
    NDIS has detected and recovered from a serious problem in another network
    driver. Although the system was not halted, this problem may later cause
    connectivity problems or a fatal BugCheck.
    Arguments:
    Arg1: 0000000000000030, NDIS BugCheck subcode
    Arg2: ffff880d4fdda1a0
    Arg3: ffff880d448a8370
    Arg4: 0000000000000000

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

    Unable to load image \SystemRoot\System32\DriverStore\FileRepository\e2f.inf_amd64_b0343b02ae8bdfed\e2f.sys, Win32 error 0n2

    KEY_VALUES_STRING: 1

    Key : Analysis.CPU.mSec
    Value: 2421

    Key : Analysis.Elapsed.mSec
    Value: 3936

    Key : Analysis.IO.Other.Mb
    Value: 9

    Key : Analysis.IO.Read.Mb
    Value: 0

    Key : Analysis.IO.Write.Mb
    Value: 29

    Key : Analysis.Init.CPU.mSec
    Value: 796

    Key : Analysis.Init.Elapsed.mSec
    Value: 43948

    Key : Analysis.Memory.CommitPeak.Mb
    Value: 109

    Key : Bugcheck.Code.KiBugCheckData
    Value: 0x0

    Key : Bugcheck.Code.LegacyAPI
    Value: 0x15e

    Key : Dump.Attributes.AsUlong
    Value: 10

    Key : Failure.Bucket
    Value: LKD_0x15E_Mini_Nbl_Leak_IMAGE_e2f.sys

    Key : Failure.Hash
    Value: {59276725-5445-4777-8035-29f6bbd46a67}

    Key : Hypervisor.Enlightenments.Value
    Value: 0

    Key : Hypervisor.Enlightenments.ValueHex
    Value: 0

    Key : Hypervisor.Flags.AnyHypervisorPresent
    Value: 0

    Key : Hypervisor.Flags.ApicEnlightened
    Value: 0

    Key : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 1

    Key : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key : Hypervisor.Flags.CpuManager
    Value: 0

    Key : Hypervisor.Flags.DeprecateAutoEoi
    Value: 0

    Key : Hypervisor.Flags.DynamicCpuDisabled
    Value: 0

    Key : Hypervisor.Flags.Epf
    Value: 0

    Key : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 0

    Key : Hypervisor.Flags.HardwareMbecAvailable
    Value: 1

    Key : Hypervisor.Flags.MaxBankNumber
    Value: 0

    Key : Hypervisor.Flags.MemoryZeroingControl
    Value: 0

    Key : Hypervisor.Flags.NoExtendedRangeFlush
    Value: 0

    Key : Hypervisor.Flags.NoNonArchCoreSharing
    Value: 0

    Key : Hypervisor.Flags.Phase0InitDone
    Value: 0

    Key : Hypervisor.Flags.PowerSchedulerQos
    Value: 0

    Key : Hypervisor.Flags.RootScheduler
    Value: 0

    Key : Hypervisor.Flags.SynicAvailable
    Value: 0

    Key : Hypervisor.Flags.UseQpcBias
    Value: 0

    Key : Hypervisor.Flags.Value
    Value: 16908288

    Key : Hypervisor.Flags.ValueHex
    Value: 1020000

    Key : Hypervisor.Flags.VpAssistPage
    Value: 0

    Key : Hypervisor.Flags.VsmAvailable
    Value: 0

    Key : Hypervisor.RootFlags.AccessStats
    Value: 0

    Key : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 0

    Key : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 0

    Key : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0

    Key : Hypervisor.RootFlags.HostTimelineSync
    Value: 0

    Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0

    Key : Hypervisor.RootFlags.IsHyperV
    Value: 0

    Key : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 0

    Key : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 0

    Key : Hypervisor.RootFlags.MceEnlightened
    Value: 0

    Key : Hypervisor.RootFlags.Nested
    Value: 0

    Key : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 0

    Key : Hypervisor.RootFlags.Value
    Value: 0

    Key : Hypervisor.RootFlags.ValueHex
    Value: 0

    Key : SecureKernel.HalpHvciEnabled
    Value: 0

    Key : WER.OS.Branch
    Value: vb_release

    Key : WER.OS.Version
    Value: 10.0.19041.1


    BUGCHECK_CODE: 15e

    BUGCHECK_P1: 30

    BUGCHECK_P2: ffff880d4fdda1a0

    BUGCHECK_P3: ffff880d448a8370

    BUGCHECK_P4: 0

    FILE_IN_CAB: NDIS-20230418-1956.dmp

    DUMP_FILE_ATTRIBUTES: 0x10
    Live Generated Dump

    IMAGE_NAME: e2f.sys

    MODULE_NAME: e2f

    FAULTING_MODULE: fffff80493eb0000 e2f

    PROCESS_NAME: System

    STACK_TEXT:
    ffffd886`7a9aa4d0 fffff804`7ad98e3a : ffffffff`ffffffff ffffd886`7a9aa570 00000000`00000000 00000000`00000000 : nt!IopLiveDumpEndMirroringCallback+0xb4
    ffffd886`7a9aa520 fffff804`7adaeb63 : 00000000`00000000 00000000`00000000 ffff880d`553085c0 ffff880d`553085c0 : nt!MmDuplicateMemory+0x2be
    ffffd886`7a9aa5b0 fffff804`7ac990df : ffff880d`553085c0 ffff880d`553085c0 ffffd886`7a9aa948 00000000`00000000 : nt!IopLiveDumpCaptureMemoryPages+0x9f
    ffffd886`7a9aa700 fffff804`7ac8b95c : 00000000`00000000 ffffde00`93c7e340 ffffde00`8dc92490 ffffde00`93c7e340 : nt!IoCaptureLiveDump+0x3e7
    ffffd886`7a9aa8e0 fffff804`7ac8c18c : ffffffff`80004ab4 00000000`00000000 00000000`00000000 00000000`0000015e : nt!DbgkpWerCaptureLiveFullDump+0x14c
    ffffd886`7a9aa940 fffff804`7ac8b79d : 00000000`00000002 00000000`00000000 fffff804`7ede9748 00000000`00000000 : nt!DbgkpWerProcessPolicyResult+0x30
    ffffd886`7a9aa970 fffff804`7ed7ec2d : ffff880d`58d82250 fffff804`7ee37710 ffff880d`42acca20 fffff804`7a68e9b7 : nt!DbgkWerCaptureLiveKernelDump+0x1dd
    ffffd886`7a9aa9d0 fffff804`7ee37758 : 00000000`00000000 fffff804`7aacdbf6 fffff804`7b125440 00000000`00000000 : ndis!ndisMLiveBugCheck+0x49
    ffffd886`7a9aaa30 fffff804`7a68e5c5 : ffff880d`59ed4040 fffff804`7aacdbb0 ffff880d`42acca20 fffff804`00000000 : ndis!ndisNblTrackerWatchdogWorkerRoutine+0x48
    ffffd886`7a9aaa70 fffff804`7a7265f5 : ffff880d`59ed4040 00000000`00000080 ffff880d`42ac8180 00000000`00000080 : nt!ExpWorkerThread+0x105
    ffffd886`7a9aab10 fffff804`7a804848 : ffffc481`ac3cb180 ffff880d`59ed4040 fffff804`7a7265a0 00000000`00000000 : nt!PspSystemThreadStartup+0x55
    ffffd886`7a9aab60 00000000`00000000 : ffffd886`7a9ab000 ffffd886`7a9a4000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


    STACK_COMMAND: .cxr; .ecxr ; kb

    FAILURE_BUCKET_ID: LKD_0x15E_Mini_Nbl_Leak_IMAGE_e2f.sys

    OS_VERSION: 10.0.19041.1

    BUILDLAB_STR: vb_release

    OSPLATFORM_TYPE: x64

    OSNAME: Windows 10

    FAILURE_ID_HASH: {59276725-5445-4777-8035-29f6bbd46a67}

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


    USBHUB3-20230414-1246.dmp


    ************* Preparing the environment for Debugger Extensions Gallery repositories **************
    ExtensionRepository : Implicit
    UseExperimentalFeatureForNugetShare : false
    AllowNugetExeUpdate : false

    - Configuring repositories
    ----> Repository : LocalInstalled, Enabled: true
    ----> Repository : UserExtensions, Enabled: true


    ************* Waiting for Debugger Extensions Gallery to Initialize **************
    .
    ----> Repository : UserExtensions, Enabled: true, Packages count: 0
    ----> Repository : LocalInstalled, Enabled: true, Packages count: 36

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


    Loading Dump File [C:\Windows\LiveKernelReports\USBHUB3\USBHUB3-20230414-1246.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available


    ************* Path validation summary **************
    Response Time (ms) Location
    Deferred srv*
    Symbol search path is: srv*
    Executable search path is:
    Windows 10 Kernel Version 19041 MP (16 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Kernel base = 0xfffff801`11801000 PsLoadedModuleList = 0xfffff801`1242b2d0
    Debug session time: Fri Apr 14 12:46:54.742 2023 (UTC - 7:00)
    System Uptime: 0 days 0:00:16.392
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ........................
    Loading User Symbols
    Mini Kernel Dump does not contain unloaded driver list
    For analysis of this file, run !analyze -v
    UsbHub3!TelemetryData_CreateReport+0xc7:
    fffff803`220cf033 0f1f440000 nop dword ptr [rax+rax]
    14: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    BUGCODE_USB3_DRIVER (144)
    This BugCheck usually happens when the USB3 core stack detects an invalid
    operation being performed by a USB client. This BugCheck may also occur
    due to hardware failure on a USB Boot Device.
    Arguments:
    Arg1: 0000000000003003, USB3_WER_BUGCODE_USBHUB3_DEVICE_ENUMERATION_FAILURE
    A USB device failed enumeration.
    Arg2: ffffef83df1ca5b0, USBHUB3_LIVEDUMP_CONTEXT
    Arg3: 0000000040010000, Failure Reason
    Arg4: 0000000000000000, 0

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


    KEY_VALUES_STRING: 1

    Key : Analysis.CPU.mSec
    Value: 1952

    Key : Analysis.Elapsed.mSec
    Value: 2506

    Key : Analysis.IO.Other.Mb
    Value: 1

    Key : Analysis.IO.Read.Mb
    Value: 0

    Key : Analysis.IO.Write.Mb
    Value: 3

    Key : Analysis.Init.CPU.mSec
    Value: 358

    Key : Analysis.Init.Elapsed.mSec
    Value: 6411

    Key : Analysis.Memory.CommitPeak.Mb
    Value: 85

    Key : Bugcheck.Code.LegacyAPI
    Value: 0x144

    Key : Dump.Attributes.AsUlong
    Value: 18

    Key : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key : Failure.Bucket
    Value: LKD_0x144_USBHUB3_DEVICE_ENUMERATION_FAILURE_UsbHub3!TelemetryData_CreateReport

    Key : Failure.Hash
    Value: {368283b5-92b0-5a0a-92e0-64e1b6e7bb74}


    BUGCHECK_CODE: 144

    BUGCHECK_P1: 3003

    BUGCHECK_P2: ffffef83df1ca5b0

    BUGCHECK_P3: 40010000

    BUGCHECK_P4: 0

    FILE_IN_CAB: USBHUB3-20230414-1246.dmp

    DUMP_FILE_ATTRIBUTES: 0x18
    Kernel Generated Triage Dump
    Live Generated Dump

    PROCESS_NAME: System

    STACK_TEXT:
    ffffef83`df1ca030 fffff803`220cccf9 : 00000000`00000005 ffff9509`ee5f8560 fffff803`220ee9dc 00000000`00000001 : UsbHub3!TelemetryData_CreateReport+0xc7
    ffffef83`df1ca560 fffff803`220c0eb9 : fffff803`221088b0 00000000`00000001 00000000`00000000 fffff803`220a4680 : UsbHub3!WER_CreateReport+0x279
    ffffef83`df1ca630 fffff803`220a9a09 : ffff9509`ee288550 ffff9509`ee5ea560 00000000`000003e8 00000000`00000000 : UsbHub3!HUBMISC_CreateWerReport+0x179
    ffffef83`df1ca6d0 fffff803`220b0de0 : 00000000`00000004 ffffef83`df1ca888 00000000`00000fed ffffef83`df1ca890 : UsbHub3!HUBPDO_ReportDeviceFailure+0x209
    ffffef83`df1ca810 fffff803`2209a737 : 00000000`00000fed fffff803`2209a596 00000000`000011cf fffff803`2210aa0d : UsbHub3!HUBDSM_MarkingUnknownDeviceAsFailed+0x10
    ffffef83`df1ca840 fffff803`2209bafe : 00000000`00000fa0 00000000`00000fed ffffef83`00000fa0 fffff803`220f6b80 : UsbHub3!HUBSM_ExecuteEntryFunctionsAndPushPopStateMachinesForCurrentState+0x87
    ffffef83`df1ca8e0 fffff803`2209af59 : 00000000`00000fed 00000000`00000f00 00000000`00000fa0 fffff803`220f6b01 : UsbHub3!HUBSM_RunStateMachine+0x5f2
    ffffef83`df1ca960 fffff803`16b5a770 : ffff9509`e34f9a90 fffff803`2209ae00 ffff9509`e29f8e00 fffff803`2209aeb0 : UsbHub3!HUBSM_EvtSmWorkItem+0xa9
    ffffef83`df1ca9a0 fffff803`16b5a6f9 : ffff9509`e2aec450 ffff9509`e29f8e00 00000000`00000000 fffff803`16b5a6f0 : ucx01000!Controller_ForwardProgressWorkItemCallback+0x60
    ffffef83`df1ca9d0 fffff801`11a44ee3 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff801`12ebc5c0 : ucx01000!Controller_ForwardProgressWorkItemWdmCallback+0x9
    ffffef83`df1caa00 fffff801`11a8f5c5 : ffff9509`dd8ac080 ffff9509`dd8ac080 fffff801`11a44e50 ffff9509`00000000 : nt!IopProcessWorkItem+0x93
    ffffef83`df1caa70 fffff801`11b275f5 : ffff9509`dd8ac080 00000000`00000080 ffff9509`da2e71c0 000fa4ef`b59bbfff : nt!ExpWorkerThread+0x105
    ffffef83`df1cab10 fffff801`11c05848 : ffffbd80`6614c180 ffff9509`dd8ac080 fffff801`11b275a0 00000000`00000000 : nt!PspSystemThreadStartup+0x55
    ffffef83`df1cab60 00000000`00000000 : ffffef83`df1cb000 ffffef83`df1c4000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


    SYMBOL_NAME: UsbHub3!TelemetryData_CreateReport+c7

    MODULE_NAME: UsbHub3

    IMAGE_NAME: UsbHub3.sys

    IMAGE_VERSION: 10.0.19041.1202

    STACK_COMMAND: .cxr; .ecxr ; kb

    BUCKET_ID_FUNC_OFFSET: c7

    FAILURE_BUCKET_ID: LKD_0x144_USBHUB3_DEVICE_ENUMERATION_FAILURE_UsbHub3!TelemetryData_CreateReport

    OSPLATFORM_TYPE: x64

    OSNAME: Windows 10

    FAILURE_ID_HASH: {368283b5-92b0-5a0a-92e0-64e1b6e7bb74}

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

    USBHUB3-20230427-2351.dmp


    ************* Preparing the environment for Debugger Extensions Gallery repositories **************
    ExtensionRepository : Implicit
    UseExperimentalFeatureForNugetShare : false
    AllowNugetExeUpdate : false

    - Configuring repositories
    ----> Repository : LocalInstalled, Enabled: true
    ----> Repository : UserExtensions, Enabled: true


    ************* Waiting for Debugger Extensions Gallery to Initialize **************
    .
    ----> Repository : UserExtensions, Enabled: true, Packages count: 0
    ----> Repository : LocalInstalled, Enabled: true, Packages count: 36

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


    Loading Dump File [C:\Windows\LiveKernelReports\USBHUB3\USBHUB3-20230427-2351.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available


    ************* Path validation summary **************
    Response Time (ms) Location
    Deferred srv*
    Symbol search path is: srv*
    Executable search path is:
    Windows 10 Kernel Version 19041 MP (16 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Kernel base = 0xfffff806`61200000 PsLoadedModuleList = 0xfffff806`61e2a2d0
    Debug session time: Thu Apr 27 23:51:59.468 2023 (UTC - 7:00)
    System Uptime: 0 days 0:00:06.086
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ........................
    Loading User Symbols
    Mini Kernel Dump does not contain unloaded driver list
    For analysis of this file, run !analyze -v
    UsbHub3!TelemetryData_CreateReport+0xcc:
    fffff806`9896f038 488b03 mov rax,qword ptr [rbx] ds:002b:ffffb28a`b401b010=????????????????
    7: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    BUGCODE_USB3_DRIVER (144)
    This BugCheck usually happens when the USB3 core stack detects an invalid
    operation being performed by a USB client. This BugCheck may also occur
    due to hardware failure on a USB Boot Device.
    Arguments:
    Arg1: 0000000000003003, USB3_WER_BUGCODE_USBHUB3_DEVICE_ENUMERATION_FAILURE
    A USB device failed enumeration.
    Arg2: ffff9485f058a5b0, USBHUB3_LIVEDUMP_CONTEXT
    Arg3: 0000000040010000, Failure Reason
    Arg4: 0000000000000000, 0

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


    KEY_VALUES_STRING: 1

    Key : Analysis.CPU.mSec
    Value: 1905

    Key : Analysis.Elapsed.mSec
    Value: 1903

    Key : Analysis.IO.Other.Mb
    Value: 0

    Key : Analysis.IO.Read.Mb
    Value: 0

    Key : Analysis.IO.Write.Mb
    Value: 0

    Key : Analysis.Init.CPU.mSec
    Value: 343

    Key : Analysis.Init.Elapsed.mSec
    Value: 3431

    Key : Analysis.Memory.CommitPeak.Mb
    Value: 85

    Key : Bugcheck.Code.LegacyAPI
    Value: 0x144

    Key : Dump.Attributes.AsUlong
    Value: 18

    Key : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key : Failure.Bucket
    Value: LKD_0x144_USBHUB3_DEVICE_ENUMERATION_FAILURE_UsbHub3!TelemetryData_CreateReport

    Key : Failure.Hash
    Value: {368283b5-92b0-5a0a-92e0-64e1b6e7bb74}


    BUGCHECK_CODE: 144

    BUGCHECK_P1: 3003

    BUGCHECK_P2: ffff9485f058a5b0

    BUGCHECK_P3: 40010000

    BUGCHECK_P4: 0

    FILE_IN_CAB: USBHUB3-20230427-2351.dmp

    DUMP_FILE_ATTRIBUTES: 0x18
    Kernel Generated Triage Dump
    Live Generated Dump

    PROCESS_NAME: System

    STACK_TEXT:
    ffff9485`f058a030 fffff806`9896ccf9 : 00000000`00000005 00000000`00000000 fffff806`9898e9dc 00000000`00000001 : UsbHub3!TelemetryData_CreateReport+0xcc
    ffff9485`f058a560 fffff806`98960eb9 : fffff806`989a88b0 00000000`00000001 00000000`00000000 fffff806`98944680 : UsbHub3!WER_CreateReport+0x279
    ffff9485`f058a630 fffff806`98949a09 : ffffb28a`b9295310 ffffb28a`b94200d0 00000000`000003e8 00000000`00000000 : UsbHub3!HUBMISC_CreateWerReport+0x179
    ffff9485`f058a6d0 fffff806`98950de0 : 00000000`00000004 ffff9485`f058a888 00000000`00000fed ffff9485`f058a890 : UsbHub3!HUBPDO_ReportDeviceFailure+0x209
    ffff9485`f058a810 fffff806`9893a737 : 00000000`00000fed fffff806`9893a596 00000000`000011cf fffff806`989aaa0d : UsbHub3!HUBDSM_MarkingUnknownDeviceAsFailed+0x10
    ffff9485`f058a840 fffff806`9893bafe : 00000000`00000fa0 00000000`00000fed ffff9485`00000fa0 fffff806`98996b80 : UsbHub3!HUBSM_ExecuteEntryFunctionsAndPushPopStateMachinesForCurrentState+0x87
    ffff9485`f058a8e0 fffff806`9893af59 : 00000000`00000fed 00000000`00000f00 00000000`00000fa0 fffff806`98996b01 : UsbHub3!HUBSM_RunStateMachine+0x5f2
    ffff9485`f058a960 fffff806`9a76a770 : ffffb28a`b4233e90 fffff806`9893ae00 ffffb28a`b9254d60 fffff806`9893aeb0 : UsbHub3!HUBSM_EvtSmWorkItem+0xa9
    ffff9485`f058a9a0 fffff806`9a76a6f9 : ffffb28a`b9385a60 ffffb28a`b9254d60 00000000`00000000 fffff806`9a76a6f0 : ucx01000!Controller_ForwardProgressWorkItemCallback+0x60
    ffff9485`f058a9d0 fffff806`61443ee3 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff806`9e529cb0 : ucx01000!Controller_ForwardProgressWorkItemWdmCallback+0x9
    ffff9485`f058aa00 fffff806`6148e5c5 : ffffb28a`aa85c040 ffffb28a`aa85c040 fffff806`61443e50 ffffb28a`00000000 : nt!IopProcessWorkItem+0x93
    ffff9485`f058aa70 fffff806`615265f5 : ffffb28a`aa85c040 00000000`00000080 ffffb28a`a8ad50c0 000fa4ef`b59bbfff : nt!ExpWorkerThread+0x105
    ffff9485`f058ab10 fffff806`61604848 : ffffc380`619ce180 ffffb28a`aa85c040 fffff806`615265a0 00000000`00000000 : nt!PspSystemThreadStartup+0x55
    ffff9485`f058ab60 00000000`00000000 : ffff9485`f058b000 ffff9485`f0584000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


    SYMBOL_NAME: UsbHub3!TelemetryData_CreateReport+cc

    MODULE_NAME: UsbHub3

    IMAGE_NAME: UsbHub3.sys

    IMAGE_VERSION: 10.0.19041.1202

    STACK_COMMAND: .cxr; .ecxr ; kb

    BUCKET_ID_FUNC_OFFSET: cc

    FAILURE_BUCKET_ID: LKD_0x144_USBHUB3_DEVICE_ENUMERATION_FAILURE_UsbHub3!TelemetryData_CreateReport

    OSPLATFORM_TYPE: x64

    OSNAME: Windows 10

    FAILURE_ID_HASH: {368283b5-92b0-5a0a-92e0-64e1b6e7bb74}

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

    WATCHDOG-202230414-1423.dmp


    ************* Preparing the environment for Debugger Extensions Gallery repositories **************
    ExtensionRepository : Implicit
    UseExperimentalFeatureForNugetShare : false
    AllowNugetExeUpdate : false

    - Configuring repositories
    ----> Repository : LocalInstalled, Enabled: true
    ----> Repository : UserExtensions, Enabled: true


    ************* Waiting for Debugger Extensions Gallery to Initialize **************
    .
    ----> Repository : UserExtensions, Enabled: true, Packages count: 0
    ----> Repository : LocalInstalled, Enabled: true, Packages count: 36

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


    Loading Dump File [C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20230414-1423.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available


    ************* Path validation summary **************
    Response Time (ms) Location
    Deferred srv*
    Symbol search path is: srv*
    Executable search path is:
    Windows 10 Kernel Version 19045 MP (16 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Kernel base = 0xfffff801`82e00000 PsLoadedModuleList = 0xfffff801`83a2a2d0
    Debug session time: Fri Apr 14 14:23:22.651 2023 (UTC - 7:00)
    System Uptime: 0 days 1:29:07.270
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ................................................................
    ...............
    Loading User Symbols
    Mini Kernel Dump does not contain unloaded driver list
    For analysis of this file, run !analyze -v
    watchdog!WdpDbgCaptureTriageDump+0x64a:
    fffff801`99e05e1a 488b4328 mov rax,qword ptr [rbx+28h] ds:002b:ffffab86`2a639658=????????????????
    3: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    VIDEO_ENGINE_TIMEOUT_DETECTED (141)
    One of the display engines failed to respond in timely fashion.
    (This code can never be used for a real BugCheck; it is used to identify live dumps.)
    Arguments:
    Arg1: ffffab862a459010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff801ac1f3730, The pointer into responsible device driver module (e.g. owner tag).
    Arg3: 0000000000000000, The secondary driver specific bucketing key.
    Arg4: 0000000000000804, Optional internal context dependent data.

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

    Unable to load image nvlddmkm.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys

    KEY_VALUES_STRING: 1

    Key : Analysis.CPU.mSec
    Value: 2296

    Key : Analysis.Elapsed.mSec
    Value: 4695

    Key : Analysis.IO.Other.Mb
    Value: 2

    Key : Analysis.IO.Read.Mb
    Value: 0

    Key : Analysis.IO.Write.Mb
    Value: 8

    Key : Analysis.Init.CPU.mSec
    Value: 421

    Key : Analysis.Init.Elapsed.mSec
    Value: 6435

    Key : Analysis.Memory.CommitPeak.Mb
    Value: 105

    Key : Bugcheck.Code.LegacyAPI
    Value: 0x141

    Key : Dump.Attributes.AsUlong
    Value: 18

    Key : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key : Failure.Bucket
    Value: LKD_0x141_IMAGE_nvlddmkm.sys

    Key : Failure.Hash
    Value: {341dd0b3-9ebd-47a8-9de8-23f4b00fabbc}


    BUGCHECK_CODE: 141

    BUGCHECK_P1: ffffab862a459010

    BUGCHECK_P2: fffff801ac1f3730

    BUGCHECK_P3: 0

    BUGCHECK_P4: 804

    FILE_IN_CAB: WATCHDOG-20230414-1423.dmp

    DUMP_FILE_ATTRIBUTES: 0x18
    Kernel Generated Triage Dump
    Live Generated Dump

    TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b


    VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffffab862a459010
    Symbol dxgkrnl!_TDR_RECOVERY_CONTEXT not found.

    PROCESS_OBJECT: 0000000000000804

    PROCESS_NAME: System

    STACK_TEXT:
    ffff8e8e`b2bef510 fffff801`99e10ea0 : ffffab86`2a459010 ffff8e8e`b2bef780 ffffab86`2a459010 ffffab86`2a639630 : watchdog!WdpDbgCaptureTriageDump+0x64a
    ffff8e8e`b2bef5c0 fffff801`9a2a5089 : 00000000`00000002 00000000`00000000 ffffab86`2197f000 ffffab86`00000001 : watchdog!WdDbgReportRecreate+0xd0
    ffff8e8e`b2bef620 fffff801`b56710b9 : ffffab86`00000000 ffffab86`5e2b74c0 ffffab86`2a459010 ffffab86`219f0000 : dxgkrnl!TdrUpdateDbgReport+0x119
    ffff8e8e`b2bef680 fffff801`b57111c5 : ffffab86`219f0000 00000000`00000000 ffffab86`21981000 ffffab86`219f0001 : dxgmms2!VidSchiResetEngine+0x709
    ffff8e8e`b2bef830 fffff801`b56db24f : ffffab86`21981000 00000000`00000001 00000000`00000000 00000000`00000000 : dxgmms2!VidSchiResetEngines+0xb1
    ffff8e8e`b2bef880 fffff801`b56a8142 : ffff8e8e`b2bef901 00000000`00053815 00000000`00989680 00000000`00000001 : dxgmms2!VidSchiCheckHwProgress+0x330df
    ffff8e8e`b2bef8f0 fffff801`b564a11a : ffffab86`20ee38a0 ffffab86`21981000 ffff8e8e`b2befa19 00000000`00989680 : dxgmms2!VidSchiWaitForSchedulerEvents+0x372
    ffff8e8e`b2bef9c0 fffff801`b56cd405 : ffffab86`28736000 ffffab86`21981000 ffffab86`28736010 ffffab86`21a2e620 : dxgmms2!VidSchiScheduleCommandToRun+0x2ca
    ffff8e8e`b2befa80 fffff801`b56cd3ba : ffffab86`21981400 fffff801`b56cd2f0 ffffab86`21981000 ffff9581`c84e5100 : dxgmms2!VidSchiRun_PriorityTable+0x35
    ffff8e8e`b2befad0 fffff801`831265f5 : ffffab86`219ef380 fffff801`00000001 ffffab86`21981000 000fa4ef`b59bbfff : dxgmms2!VidSchiWorkerThread+0xca
    ffff8e8e`b2befb10 fffff801`83204848 : ffff9581`c84e5180 ffffab86`219ef380 fffff801`831265a0 00000000`00000000 : nt!PspSystemThreadStartup+0x55
    ffff8e8e`b2befb60 00000000`00000000 : ffff8e8e`b2bf0000 ffff8e8e`b2be9000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


    SYMBOL_NAME: nvlddmkm+1073730

    MODULE_NAME: nvlddmkm

    IMAGE_NAME: nvlddmkm.sys

    STACK_COMMAND: .cxr; .ecxr ; kb

    FAILURE_BUCKET_ID: LKD_0x141_IMAGE_nvlddmkm.sys

    OSPLATFORM_TYPE: x64

    OSNAME: Windows 10

    FAILURE_ID_HASH: {341dd0b3-9ebd-47a8-9de8-23f4b00fabbc}

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

    WATCHDOG-20230422-1305.dmp


    ************* Preparing the environment for Debugger Extensions Gallery repositories **************
    ExtensionRepository : Implicit
    UseExperimentalFeatureForNugetShare : false
    AllowNugetExeUpdate : false

    - Configuring repositories
    ----> Repository : LocalInstalled, Enabled: true
    ----> Repository : UserExtensions, Enabled: true


    ************* Waiting for Debugger Extensions Gallery to Initialize **************
    .
    ----> Repository : UserExtensions, Enabled: true, Packages count: 0
    ----> Repository : LocalInstalled, Enabled: true, Packages count: 36

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


    Loading Dump File [C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20230422-1305.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available


    ************* Path validation summary **************
    Response Time (ms) Location
    Deferred srv*
    Symbol search path is: srv*
    Executable search path is:
    Windows 10 Kernel Version 19045 MP (16 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Kernel base = 0xfffff802`1f000000 PsLoadedModuleList = 0xfffff802`1fc2a2d0
    Debug session time: Sat Apr 22 13:05:05.303 2023 (UTC - 7:00)
    System Uptime: 0 days 0:00:06.922
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ..............................
    Loading User Symbols
    Mini Kernel Dump does not contain unloaded driver list
    For analysis of this file, run !analyze -v
    watchdog!WdpDbgCaptureTriageDump+0x64a:
    fffff802`374c5e1a 488b4328 mov rax,qword ptr [rbx+28h] ds:002b:ffffd785`a2e9b2d8=????????????????
    2: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    VIDEO_DXGKRNL_LIVEDUMP (193)
    Livedumps triggered by dxgkrnl when a problem is detected.
    (This code can never be used for a real BugCheck; it is used to identify live dumps.)
    Arguments:
    Arg1: 0000000000000804, Reason Code.
    100 Internal
    Arg2: ffffffffc0000001, Reserved.
    Arg3: 0000000000000108, Reserved.
    Arg4: fffff802374eb770, Reserved.

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


    KEY_VALUES_STRING: 1

    Key : Analysis.CPU.mSec
    Value: 2499

    Key : Analysis.Elapsed.mSec
    Value: 3270

    Key : Analysis.IO.Other.Mb
    Value: 0

    Key : Analysis.IO.Read.Mb
    Value: 0

    Key : Analysis.IO.Write.Mb
    Value: 1

    Key : Analysis.Init.CPU.mSec
    Value: 406

    Key : Analysis.Init.Elapsed.mSec
    Value: 3610

    Key : Analysis.Memory.CommitPeak.Mb
    Value: 98

    Key : Bugcheck.Code.LegacyAPI
    Value: 0x193

    Key : Dump.Attributes.AsUlong
    Value: 18

    Key : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key : Failure.Bucket
    Value: LKD_0x193_dxgkrnl!DxgCreateLiveDumpWithWdLogs

    Key : Failure.Hash
    Value: {4b6fafa0-b740-8186-967a-4fb4d108708f}


    BUGCHECK_CODE: 193

    BUGCHECK_P1: 804

    BUGCHECK_P2: ffffffffc0000001

    BUGCHECK_P3: 108

    BUGCHECK_P4: fffff802374eb770

    FILE_IN_CAB: WATCHDOG-20230422-1305.dmp

    DUMP_FILE_ATTRIBUTES: 0x18
    Kernel Generated Triage Dump
    Live Generated Dump

    PROCESS_NAME: csrss.exe

    STACK_TEXT:
    ffffd504`45d72310 fffff802`374d0ea0 : 00000000`00000108 ffffffff`fffffffd ffffd785`a353c180 00000000`00000000 : watchdog!WdpDbgCaptureTriageDump+0x64a
    ffffd504`45d723c0 fffff802`374d0d7d : ffffd785`a353ce68 fffff802`1f2215c9 ffffd785`a2e6f900 00000000`00000000 : watchdog!WdDbgReportRecreate+0xd0
    ffffd504`45d72420 fffff802`3732ff2f : ffffd785`a353ced0 ffffffff`fffffffd 00000000`00000010 fffff802`3732fef0 : watchdog!WdDbgReportCreate+0x3d
    ffffd504`45d72480 fffff802`3730ba8c : 00000000`00000108 ffffffff`fffffffd ffffd785`a353c180 ffffd785`00000000 : dxgkrnl!DxgCreateLiveDumpWithWdLogs+0x3f
    ffffd504`45d724d0 fffff802`372929a8 : ffffffff`fffffffd ffffd785`a353c180 00000000`00000001 00000000`00000001 : dxgkrnl!DpiFdoStartAdapter+0x7a4a8
    ffffd504`45d72650 fffff802`372a7ab0 : ffffb906`fd209630 00000000`00000000 ffffd785`9f3ff0a0 00000000`00000000 : dxgkrnl!DpiFdoStartAdapterThreadImpl+0x308
    ffffd504`45d72800 fffff802`37278eda : fffff802`371c0b00 00000000`00000000 ffffffff`fffffffd ffffd785`9f3ff0a0 : dxgkrnl!DpiFdoStartAdapterThread+0x30
    ffffd504`45d72830 fffff802`37278e3f : 00000000`00000000 ffffffff`fffffffd ffffd785`9f3ff0a0 00000000`00000000 : dxgkrnl!DpiSessionCreateCallback+0x52
    ffffd504`45d72870 fffff802`374ce722 : 00000000`00000000 00000000`00000158 00000000`00000158 00000000`00000154 : dxgkrnl!DxgkNotifySessionStateChange+0xbf
    ffffd504`45d728c0 ffffb906`fdcc12d2 : ffffd785`a16fcc00 00000000`0020001e ffffb906`fd5c62c8 00000000`00000154 : watchdog!SMgrNotifySessionChange+0x92
    ffffd504`45d728f0 ffffb906`fd045aea : 00000000`00000040 00000000`00000000 00000000`00000000 00000000`0000032c : win32k!SysEntrySMgrNotifySessionChange+0x12
    ffffd504`45d72920 ffffb906`fd0454db : 00000000`00000000 ffffd785`a927e080 ffffabd6`6785754f 00000000`c00000bb : win32kbase!DrvNotifySessionStateChange+0x8a
    ffffd504`45d72950 ffffb906`fd0484f4 : 00000000`00000000 00000000`00000158 00000000`00000154 ffffd785`a7e83660 : win32kbase!InitializeGreCSRSS+0x1b
    ffffd504`45d72980 ffffb906`fdcc1486 : ffffd785`a93e64c0 ffffd504`45d72a80 00000000`00000001 00000000`00000001 : win32kbase!Win32kBaseUserInitialize+0x124
    ffffd504`45d729d0 fffff802`1f40f3f5 : ffffd785`a93e6400 00000000`00100000 ffffd504`45d72a80 ffffd785`00000000 : win32k!NtUserInitialize+0x16
    ffffd504`45d72a00 00007ff9`2d7d9b44 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
    000000de`c18bf3c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`2d7d9b44


    SYMBOL_NAME: dxgkrnl!DxgCreateLiveDumpWithWdLogs+3f

    MODULE_NAME: dxgkrnl

    IMAGE_NAME: dxgkrnl.sys

    IMAGE_VERSION: 10.0.19041.2311

    STACK_COMMAND: .cxr; .ecxr ; kb

    BUCKET_ID_FUNC_OFFSET: 3f

    FAILURE_BUCKET_ID: LKD_0x193_dxgkrnl!DxgCreateLiveDumpWithWdLogs

    OSPLATFORM_TYPE: x64

    OSNAME: Windows 10

    FAILURE_ID_HASH: {4b6fafa0-b740-8186-967a-4fb4d108708f}

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

    WATCHDOG-20230422-2130.dmp


    ************* Preparing the environment for Debugger Extensions Gallery repositories **************
    ExtensionRepository : Implicit
    UseExperimentalFeatureForNugetShare : false
    AllowNugetExeUpdate : false

    - Configuring repositories
    ----> Repository : LocalInstalled, Enabled: true
    ----> Repository : UserExtensions, Enabled: true


    ************* Waiting for Debugger Extensions Gallery to Initialize **************
    .
    ----> Repository : UserExtensions, Enabled: true, Packages count: 0
    ----> Repository : LocalInstalled, Enabled: true, Packages count: 36

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


    Loading Dump File [C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20230422-2130.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available


    ************* Path validation summary **************
    Response Time (ms) Location
    Deferred srv*
    Symbol search path is: srv*
    Executable search path is:
    Windows 10 Kernel Version 19045 MP (16 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Kernel base = 0xfffff807`23200000 PsLoadedModuleList = 0xfffff807`23e2a2d0
    Debug session time: Sat Apr 22 21:30:11.686 2023 (UTC - 7:00)
    System Uptime: 0 days 0:00:07.304
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .......................
    Loading User Symbols
    Mini Kernel Dump does not contain unloaded driver list
    For analysis of this file, run !analyze -v
    watchdog!WdpDbgCaptureTriageDump+0x64a:
    fffff807`3ccc5e1a 488b4328 mov rax,qword ptr [rbx+28h] ds:002b:ffffaf85`1374caf8=????????????????
    2: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    VIDEO_DXGKRNL_LIVEDUMP (193)
    Livedumps triggered by dxgkrnl when a problem is detected.
    (This code can never be used for a real BugCheck; it is used to identify live dumps.)
    Arguments:
    Arg1: 0000000000000804, Reason Code.
    100 Internal
    Arg2: ffffffffc0000001, Reserved.
    Arg3: 0000000000000108, Reserved.
    Arg4: fffff8073cceb770, Reserved.

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


    KEY_VALUES_STRING: 1

    Key : Analysis.CPU.mSec
    Value: 2531

    Key : Analysis.Elapsed.mSec
    Value: 2542

    Key : Analysis.IO.Other.Mb
    Value: 0

    Key : Analysis.IO.Read.Mb
    Value: 0

    Key : Analysis.IO.Write.Mb
    Value: 0

    Key : Analysis.Init.CPU.mSec
    Value: 358

    Key : Analysis.Init.Elapsed.mSec
    Value: 4462

    Key : Analysis.Memory.CommitPeak.Mb
    Value: 98

    Key : Bugcheck.Code.LegacyAPI
    Value: 0x193

    Key : Dump.Attributes.AsUlong
    Value: 18

    Key : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key : Failure.Bucket
    Value: LKD_0x193_dxgkrnl!DxgCreateLiveDumpWithWdLogs

    Key : Failure.Hash
    Value: {4b6fafa0-b740-8186-967a-4fb4d108708f}


    BUGCHECK_CODE: 193

    BUGCHECK_P1: 804

    BUGCHECK_P2: ffffffffc0000001

    BUGCHECK_P3: 108

    BUGCHECK_P4: fffff8073cceb770

    FILE_IN_CAB: WATCHDOG-20230422-2130.dmp

    DUMP_FILE_ATTRIBUTES: 0x18
    Kernel Generated Triage Dump
    Live Generated Dump

    PROCESS_NAME: csrss.exe

    STACK_TEXT:
    ffffc004`1ec0f310 fffff807`3ccd0ea0 : 00000000`00000108 ffffffff`fffffffd ffffaf85`0e2cb180 00000000`00000000 : watchdog!WdpDbgCaptureTriageDump+0x64a
    ffffc004`1ec0f3c0 fffff807`3ccd0d7d : ffffaf85`0e2cbe68 fffff807`234215c9 ffffaf85`0d2a58b0 00000000`00000000 : watchdog!WdDbgReportRecreate+0xd0
    ffffc004`1ec0f420 fffff807`3cb2ff2f : ffffaf85`0e2cbed0 ffffffff`fffffffd 00000000`00000010 fffff807`3cb2fef0 : watchdog!WdDbgReportCreate+0x3d
    ffffc004`1ec0f480 fffff807`3cb0ba8c : 00000000`00000108 ffffffff`fffffffd ffffaf85`0e2cb180 ffffaf85`00000000 : dxgkrnl!DxgCreateLiveDumpWithWdLogs+0x3f
    ffffc004`1ec0f4d0 fffff807`3ca929a8 : ffffffff`fffffffd ffffaf85`0e2cb180 00000000`00000001 00000000`00000001 : dxgkrnl!DpiFdoStartAdapter+0x7a4a8
    ffffc004`1ec0f650 fffff807`3caa7ab0 : fffffccd`dd609630 00000000`00000000 ffffaf85`0c0ca050 00000000`00000000 : dxgkrnl!DpiFdoStartAdapterThreadImpl+0x308
    ffffc004`1ec0f800 fffff807`3ca78eda : fffff807`3c9c0b00 00000000`00000000 ffffffff`fffffffd ffffaf85`0c0ca050 : dxgkrnl!DpiFdoStartAdapterThread+0x30
    ffffc004`1ec0f830 fffff807`3ca78e3f : 00000000`00000000 ffffffff`fffffffd ffffaf85`0c0ca050 00000000`00000000 : dxgkrnl!DpiSessionCreateCallback+0x52
    ffffc004`1ec0f870 fffff807`3ccce722 : 00000000`00000000 00000000`00000158 00000000`00000158 00000000`00000154 : dxgkrnl!DxgkNotifySessionStateChange+0xbf
    ffffc004`1ec0f8c0 fffffccd`dde812d2 : ffffaf85`0d2f8c00 00000000`0020001e fffffccd`dd9c62c8 00000000`00000154 : watchdog!SMgrNotifySessionChange+0x92
    ffffc004`1ec0f8f0 fffffccd`dd445aea : 00000000`00000040 00000000`00000000 00000000`00000000 00000000`00000354 : win32k!SysEntrySMgrNotifySessionChange+0x12
    ffffc004`1ec0f920 fffffccd`dd4454db : 00000000`00000000 ffffaf85`135c0080 ffffaa52`6983eed2 00000000`c00000bb : win32kbase!DrvNotifySessionStateChange+0x8a
    ffffc004`1ec0f950 fffffccd`dd4484f4 : 00000000`00000000 00000000`00000158 00000000`00000154 ffffaf85`12af8fe0 : win32kbase!InitializeGreCSRSS+0x1b
    ffffc004`1ec0f980 fffffccd`dde81486 : ffffaf85`133ca080 ffffc004`1ec0fa80 00000000`00000001 00000000`00000001 : win32kbase!Win32kBaseUserInitialize+0x124
    ffffc004`1ec0f9d0 fffff807`2360f3f5 : ffffaf85`133ca000 00000000`00100000 ffffc004`1ec0fa80 ffffaf85`00000000 : win32k!NtUserInitialize+0x16
    ffffc004`1ec0fa00 00007ff8`34bd9b44 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
    00000052`c996f5d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`34bd9b44


    SYMBOL_NAME: dxgkrnl!DxgCreateLiveDumpWithWdLogs+3f

    MODULE_NAME: dxgkrnl

    IMAGE_NAME: dxgkrnl.sys

    IMAGE_VERSION: 10.0.19041.2311

    STACK_COMMAND: .cxr; .ecxr ; kb

    BUCKET_ID_FUNC_OFFSET: 3f

    FAILURE_BUCKET_ID: LKD_0x193_dxgkrnl!DxgCreateLiveDumpWithWdLogs

    OSPLATFORM_TYPE: x64

    OSNAME: Windows 10

    FAILURE_ID_HASH: {4b6fafa0-b740-8186-967a-4fb4d108708f}

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

    WATCHDOG-20230425-2250.dmg


    ************* Preparing the environment for Debugger Extensions Gallery repositories **************
    ExtensionRepository : Implicit
    UseExperimentalFeatureForNugetShare : false
    AllowNugetExeUpdate : false

    - Configuring repositories
    ----> Repository : LocalInstalled, Enabled: true
    ----> Repository : UserExtensions, Enabled: true


    ************* Waiting for Debugger Extensions Gallery to Initialize **************
    .
    ----> Repository : UserExtensions, Enabled: true, Packages count: 0
    ----> Repository : LocalInstalled, Enabled: true, Packages count: 36

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


    Loading Dump File [C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20230425-2250.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available


    ************* Path validation summary **************
    Response Time (ms) Location
    Deferred srv*
    Symbol search path is: srv*
    Executable search path is:
    Windows 10 Kernel Version 19045 MP (16 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Kernel base = 0xfffff803`0cc00000 PsLoadedModuleList = 0xfffff803`0d82a2d0
    Debug session time: Tue Apr 25 22:50:06.503 2023 (UTC - 7:00)
    System Uptime: 0 days 0:00:07.122
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .................................
    Loading User Symbols
    Mini Kernel Dump does not contain unloaded driver list
    For analysis of this file, run !analyze -v
    watchdog!WdpDbgCaptureTriageDump+0x64a:
    fffff803`23dd5e1a 488b4328 mov rax,qword ptr [rbx+28h] ds:002b:ffff9388`12b70d28=????????????????
    2: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    VIDEO_DXGKRNL_LIVEDUMP (193)
    Livedumps triggered by dxgkrnl when a problem is detected.
    (This code can never be used for a real BugCheck; it is used to identify live dumps.)
    Arguments:
    Arg1: 0000000000000804, Reason Code.
    100 Internal
    Arg2: ffffffffc0000001, Reserved.
    Arg3: 0000000000000108, Reserved.
    Arg4: fffff80323dfb770, Reserved.

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


    KEY_VALUES_STRING: 1

    Key : Analysis.CPU.mSec
    Value: 2546

    Key : Analysis.Elapsed.mSec
    Value: 2543

    Key : Analysis.IO.Other.Mb
    Value: 0

    Key : Analysis.IO.Read.Mb
    Value: 0

    Key : Analysis.IO.Write.Mb
    Value: 0

    Key : Analysis.Init.CPU.mSec
    Value: 359

    Key : Analysis.Init.Elapsed.mSec
    Value: 3611

    Key : Analysis.Memory.CommitPeak.Mb
    Value: 98

    Key : Bugcheck.Code.LegacyAPI
    Value: 0x193

    Key : Dump.Attributes.AsUlong
    Value: 18

    Key : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key : Failure.Bucket
    Value: LKD_0x193_dxgkrnl!DxgCreateLiveDumpWithWdLogs

    Key : Failure.Hash
    Value: {4b6fafa0-b740-8186-967a-4fb4d108708f}


    BUGCHECK_CODE: 193

    BUGCHECK_P1: 804

    BUGCHECK_P2: ffffffffc0000001

    BUGCHECK_P3: 108

    BUGCHECK_P4: fffff80323dfb770

    FILE_IN_CAB: WATCHDOG-20230425-2250.dmp

    DUMP_FILE_ATTRIBUTES: 0x18
    Kernel Generated Triage Dump
    Live Generated Dump

    PROCESS_NAME: csrss.exe

    STACK_TEXT:
    ffff8686`690aa310 fffff803`23de0ea0 : 00000000`00000108 ffffffff`fffffffd ffff9388`0d846180 00000000`00000000 : watchdog!WdpDbgCaptureTriageDump+0x64a
    ffff8686`690aa3c0 fffff803`23de0d7d : ffff9388`0d846e68 fffff803`0ce215c9 ffff9388`0d6719c0 00000000`00000000 : watchdog!WdDbgReportRecreate+0xd0
    ffff8686`690aa420 fffff803`23c3ff2f : ffff9388`0d846ed0 ffffffff`fffffffd 00000000`00000010 fffff803`23c3fef0 : watchdog!WdDbgReportCreate+0x3d
    ffff8686`690aa480 fffff803`23c1ba8c : 00000000`00000108 ffffffff`fffffffd ffff9388`0d846180 ffff9388`00000000 : dxgkrnl!DxgCreateLiveDumpWithWdLogs+0x3f
    ffff8686`690aa4d0 fffff803`23ba29a8 : ffffffff`fffffffd ffff9388`0d846180 00000000`00000001 00000000`00000001 : dxgkrnl!DpiFdoStartAdapter+0x7a4a8
    ffff8686`690aa650 fffff803`23bb7ab0 : fffff9e3`6a6e9630 00000000`00000000 ffff9388`09aff440 00000000`00000000 : dxgkrnl!DpiFdoStartAdapterThreadImpl+0x308
    ffff8686`690aa800 fffff803`23b88eda : fffff803`23ad0b00 00000000`00000000 ffffffff`fffffffd ffff9388`09aff440 : dxgkrnl!DpiFdoStartAdapterThread+0x30
    ffff8686`690aa830 fffff803`23b88e3f : 00000000`00000000 ffffffff`fffffffd ffff9388`09aff440 00000000`00000000 : dxgkrnl!DpiSessionCreateCallback+0x52
    ffff8686`690aa870 fffff803`23dde722 : 00000000`00000000 00000000`00000158 00000000`00000158 00000000`00000154 : dxgkrnl!DxgkNotifySessionStateChange+0xbf
    ffff8686`690aa8c0 fffff9e3`69e012d2 : ffff9388`0bdfcc00 00000000`0020001e fffff9e3`6a2e62c8 00000000`00000154 : watchdog!SMgrNotifySessionChange+0x92
    ffff8686`690aa8f0 fffff9e3`6a525aea : 00000000`00000040 00000000`00000000 00000000`00000000 00000000`00000330 : win32k!SysEntrySMgrNotifySessionChange+0x12
    ffff8686`690aa920 fffff9e3`6a5254db : 00000000`00000000 ffff9388`129a60c0 ffff2738`ca4a2abc 00000000`c00000bb : win32kbase!DrvNotifySessionStateChange+0x8a
    ffff8686`690aa950 fffff9e3`6a5284f4 : 00000000`00000000 00000000`00000158 00000000`00000154 ffff9388`12b18ce0 : win32kbase!InitializeGreCSRSS+0x1b
    ffff8686`690aa980 fffff9e3`69e01486 : ffff9388`12b89140 ffff8686`690aaa80 00000000`00000001 00000000`00000001 : win32kbase!Win32kBaseUserInitialize+0x124
    ffff8686`690aa9d0 fffff803`0d00f3f5 : ffff9388`12b89100 00000000`00100000 ffff8686`690aaa80 ffff9388`00000000 : win32k!NtUserInitialize+0x16
    ffff8686`690aaa00 00007fff`28fd9b44 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
    00000015`8166f458 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`28fd9b44


    SYMBOL_NAME: dxgkrnl!DxgCreateLiveDumpWithWdLogs+3f

    MODULE_NAME: dxgkrnl

    IMAGE_NAME: dxgkrnl.sys

    IMAGE_VERSION: 10.0.19041.2311

    STACK_COMMAND: .cxr; .ecxr ; kb

    BUCKET_ID_FUNC_OFFSET: 3f

    FAILURE_BUCKET_ID: LKD_0x193_dxgkrnl!DxgCreateLiveDumpWithWdLogs

    OSPLATFORM_TYPE: x64

    OSNAME: Windows 10

    FAILURE_ID_HASH: {4b6fafa0-b740-8186-967a-4fb4d108708f}

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

    That's all of them in the LiveKernelReports Files. Fingers crossed you find the needle in the haystack :/
      My Computer


  6. Posts : 402
    Windows 10 and Windows 11
       #66

    I meant upload the dump files themselves so that we could have a look through them. However, what you have uploaded is useful...

    The NDIS problem looks to be some sort of memory leak in e2f.sys, part of the Intel LAN driver. You could check for an update to the LAN driver, it won't hurt. I don't think this is of huge consequence for you.

    The two USB3 problems look to be just device enumeration issues, that's likely a minor or transient problem with device detection and is probably nothing for you to worry about. You can check for chipset driver updates, or a specific USB3 driver update, and you might also check any USB3 devices you have connected too. I don't think these are a big deal.

    The WATCHDOG problems are interesting, as I thought they might be. They are all graphics related. One is an issue with the graphics driver nvlddmkm.sys, which could just as easily be a card problem. The others are all issues with dxgkrnl.sys; the Windows DirectX kernel. In all the call stacks (that we can see anyway) there is communication with the graphics adapter (the card) taking place. I's interesting that this gells with the display issue you just noticed, although the most recent of those watchdog live dumps was on 25th April.

    Can you see whether the system misbehaves with just one monitor connected? I suppose it's out of the question to see how it is with the RTX3080 removed and one monitor plugged in to the motherboard and using the iGPU?
      My Computer


  7. Posts : 95
    Windows 10
    Thread Starter
       #67

    I checked for updates on all the aforementioned things and windows did not find any.

    I feel like with all of Nvidia's constant issues, that there's always been a good chance it was the GPU's fault, regardless of how many times I RMA'd/updated/etc. with it...

    Is there anything particular I should/have to do regarding the dxgkrnl.sys- the windows directx kernel? I'm not sure what part this plays but happy to do whatever you recommend :)

    The display issue is making no sense to me, as it seems just swapping around all new displayport cables seems to temporarily fix the issue. As in 1. Boot up PC. 2. Start game. 3. right monitor flickers. 4. swap DP cables. 5. Everything is fine. 6. Turn off PC, go to bed
    Next morning, have to do it all over again, although haven't needed to the last couple days- as if this all wasn't odd enough lol.

    The system doesn't seem to misbehave with only one monitor running, however I wouldn't be able to tell if I'm just not plugging the issue itself in, you know what I mean?

    I also did try disabling the RTX 3080 and just using the iGPU, but it's not strong enough to run anything with any kind of decent performance, so it's hard to test reliably. That being said, it did not crash while using the iGPU despite how terribly everything was running.
      My Computer


  8. Posts : 402
    Windows 10 and Windows 11
       #68

    Can you move the GPU to a different PCIe slot (I've not looked at your board to see whether you have another suitable slot)? From what you're saying this does sound like a GPU issue, or possibly a driver issue. I don't know whether you've already done this (it's a long thread to read back through!) but have you tried the two driver versions immediately prior to the latest?

    This is starting to sound GPU related, but it could still be a PSU issue of course. I think that's an 850W PSU? The spikes running three displays could be too much for it - perhaps? That it's fine with one monitor running might support that theory?

    BTW. You asked earlier about your 1800MHz RAM? It's DDR - Double Data Rate, it reads/write on both the rising and falling clock pulse, so an 1800MHJz clock gives you 3600MHz RAM speed (1800 * 2).
      My Computer


  9. Posts : 95
    Windows 10
    Thread Starter
       #69

    Yes I have tried all the latest as Nvidia regularly rolls new ones out, and have manually installed countless previous versions as well. I have an 860 watt PSU installed (corsairís platinum line, which im told should never have an issue), and swaptested to prove this wasnt the issue. Good to know the DDR is reading correctly then, cool thanks.
    The RTX3080 being the physical size that it is does not allow me move it to another pcie slot, however i did swap motherboards a little while back so techinally that should rule out the slot itself being the issue.
      My Computer


  10. Posts : 402
    Windows 10 and Windows 11
       #70

    Can you try and make it BSOD using just one monitor then? It would seem that there is something going on in the GPU area, yet you have a new GPU and new motherboard, and you've tried all the latest GPU drivers. The only thing left, since you've replaced the PSU as well, is that the PSU is being overloaded by power spikes as the CPU and GPU ramp up...?

    Can you beg/borrow/steal a 1000W PSU to test...?
      My Computer


 

  Related Discussions
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 09:22.
Find Us




Windows 10 Forums