BSOD caused by ntkrnlmp.exe

Cosmin T 1 Reputation point

Hello! I recently started having crashes (either BSOD or just crash and restart). The following link has the latest dump file generated (I'm sorry it's a full dump, I've just changed the option to small files):!AoLayrOv6Yo12lunCPlzRR7V5rHu?e=quLekM
The latest crashed happened while I was playing Destiny 2. You can probably check my important specs, but here are the full specs anyways:
CPU: AMD Ryzen 7 2700x
GPU: MSI GeForce RTX 2070 SUPER Ventus
Motherboard: Gigabyte Aorus X470 Ultra Gaming
Memory: Corsair Vengeance LPX 16GB 3200mhz dual channel
Storage: 2 Intel 660p Series 1TB SSD's
PSU: Seasonic Focus 80+ Gold 650W
Notes: I've had this build for more than a year now, I've done the memory check, stress tests, a clean reinstallation of my Windows and drivers. I have no OC, I do not experience crashes in every game I play, these crashes only happened in Destiny 2 and in the newest CoD titles (both Modern Warfare and Black Ops Cold War). I do use the XMP profile that my motherboard provides, although I tried running the games with the profile on and off with no success.
Games I didn't experience any crashes in: Escape from Tarkov, Overwatch, League of Legends, Apex Legends.
My guess is that some sort of driver has to be corrupted, but I've run out of options.

Not Monitored
Not Monitored
Tag not monitored by Microsoft.
36,428 questions
0 comments No comments
{count} votes

3 answers

Sort by: Most helpful
  1. Teemo Tang 11,351 Reputation points

    Due to limited condition, we can’t analyze your full dump files, it is too big(more than 900MB). You could download WinDbg tool from the following website to analyze dump file, usually WinDbg Preview in Store is enough.
    Download Debugging Tools for Windows


    If the Answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

  2. Cosmin T 1 Reputation point

    Hello! 3 days later I get a sudden crash in a completely different game, so I have an obvious problem. Here is the link to the dump file (small this time)!AoLayrOv6Yo12mAXLX2X4V-h5sVt?e=SXTeaD

    0 comments No comments

  3. Teemo Tang 11,351 Reputation points
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If kernel debugger is available get stack backtrace.
    Arg1: 0000000000000198, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
    Arg4: fffff80615c11336, address which referenced memory
    Debugging Details:
    *** WARNING: Unable to verify timestamp for USBXHCI.SYS
        Key  : Analysis.CPU.mSec
        Value: 1953
        Key  : Analysis.DebugAnalysisProvider.CPP
        Value: Create: 8007007e on WX-69143
        Key  : Analysis.DebugData
        Value: CreateObject
        Key  : Analysis.DebugModel
        Value: CreateObject
        Key  : Analysis.Elapsed.mSec
        Value: 15417
        Key  : Analysis.Memory.CommitPeak.Mb
        Value: 78
        Key  : Analysis.System
        Value: CreateObject
      Kernel Generated Triage Dump
    BUGCHECK_P1: 198
    BUGCHECK_P2: 2
    BUGCHECK_P3: 1
    BUGCHECK_P4: fffff80615c11336
    WRITE_ADDRESS: fffff806114fa390: Unable to get MiVisibleState
    Unable to get NonPagedPoolStart
    Unable to get NonPagedPoolEnd
    Unable to get PagedPoolStart
    Unable to get PagedPoolEnd
    fffff8061140f330: Unable to get Flags value from nt!KdVersionBlock
    fffff8061140f330: Unable to get Flags value from nt!KdVersionBlock
    unable to get nt!MmSpecialPagesInUse
    BLACKBOXBSD: 1 (!blackboxbsd)
    BLACKBOXNTFS: 1 (!blackboxntfs)
    BLACKBOXPNP: 1 (!blackboxpnp)
    PROCESS_NAME:  System
    TRAP_FRAME:  ffffe18efac29140 -- (.trap 0xffffe18efac29140)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=01d700b21406238a rbx=0000000000000000 rcx=0000000000000000
    rdx=ffff808b811c2c50 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80615c11336 rsp=ffffe18efac292d0 rbp=0000000000000000
     r8=0000000000000008  r9=000000000000016c r10=ffff808b81130000
    r11=ffffe18efac29260 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    fffff806`15c11336 49898698010000  mov     qword ptr [r14+198h],rax ds:00000000`00000198=????????????????
    Resetting default scope
    ffffe18e`fac28ff8 fffff806`10c07769     : 00000000`0000000a 00000000`00000198 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
    ffffe18e`fac29000 fffff806`10c03a69     : 00000000`00000000 00000000`00000000 00000000`00000000 ffff808b`816fd418 : nt!KiBugCheckDispatch+0x69
    ffffe18e`fac29140 fffff806`15c11336     : ffff808b`81898ae0 fffff806`19302ec5 ffff808b`818b50d0 ffff808b`8ffbd1e0 : nt!KiPageFault+0x469
    ffffe18e`fac292d0 fffff806`10b16f56     : ffff808b`818b50d0 ffff808b`91d26560 ffff808b`8113bdc0 ffffe18e`fac293c9 : ucx01000!Urb_LegacyTransferUrbCompletion+0x76
    ffffe18e`fac29310 fffff806`10a4885e     : ffff808b`818b50d0 ffffe18e`fac293c9 ffff808b`8113bdc0 ffff808b`818b5503 : nt!IopUnloadSafeCompletion+0x56
    ffffe18e`fac29340 fffff806`10a48727     : 00000000`00000001 00000000`00000000 ffff808b`8189d5f0 00000000`00000002 : nt!IopfCompleteRequest+0x11e
    ffffe18e`fac29430 fffff806`137b811a     : 00000000`00000000 ffff808b`80fe7050 ffff808b`818b50d0 ffffe18e`fac29510 : nt!IofCompleteRequest+0x17
    ffffe18e`fac29460 fffff806`137b5bbf     : ffff808b`81a88c02 ffff808b`818807a0 ffff808b`818b50d0 00000000`00000000 : Wdf01000+0x811a
    ffffe18e`fac294f0 fffff806`15b7b91c     : 00000000`ffffff02 ffff808b`81a88a80 ffff808b`8189d9d0 ffff808b`8189d9d0 : Wdf01000+0x5bbf
    ffffe18e`fac29550 00000000`ffffff02     : ffff808b`81a88a80 ffff808b`8189d9d0 ffff808b`8189d9d0 00000000`00000008 : USBXHCI+0xb91c
    ffffe18e`fac29558 ffff808b`81a88a80     : ffff808b`8189d9d0 ffff808b`8189d9d0 00000000`00000008 ffffe18e`fac295f8 : 0xffffff02
    ffffe18e`fac29560 ffff808b`8189d9d0     : ffff808b`8189d9d0 00000000`00000008 ffffe18e`fac295f8 00000000`00000008 : 0xffff808b`81a88a80
    ffffe18e`fac29568 ffff808b`8189d9d0     : 00000000`00000008 ffffe18e`fac295f8 00000000`00000008 ffffe18e`fac29600 : 0xffff808b`8189d9d0
    ffffe18e`fac29570 00000000`00000008     : ffffe18e`fac295f8 00000000`00000008 ffffe18e`fac29600 00000000`00000008 : 0xffff808b`8189d9d0
    ffffe18e`fac29578 ffffe18e`fac295f8     : 00000000`00000008 ffffe18e`fac29600 00000000`00000008 00000000`00000000 : 0x8
    ffffe18e`fac29580 00000000`00000008     : ffffe18e`fac29600 00000000`00000008 00000000`00000000 ffff808b`8189d9d0 : 0xffffe18e`fac295f8
    ffffe18e`fac29588 ffffe18e`fac29600     : 00000000`00000008 00000000`00000000 ffff808b`8189d9d0 fffff806`15b7b7e1 : 0x8
    ffffe18e`fac29590 00000000`00000008     : 00000000`00000000 ffff808b`8189d9d0 fffff806`15b7b7e1 ffff808b`81a88c20 : 0xffffe18e`fac29600
    ffffe18e`fac29598 00000000`00000000     : ffff808b`8189d9d0 fffff806`15b7b7e1 ffff808b`81a88c20 00000000`00000009 : 0x8
    SYMBOL_NAME:  ucx01000!Urb_LegacyTransferUrbCompletion+76
    MODULE_NAME: ucx01000
    IMAGE_NAME:  ucx01000.sys
    IMAGE_VERSION:  10.0.19041.1030
    STACK_COMMAND:  .thread ; .cxr ; kb
    FAILURE_BUCKET_ID:  AV_ucx01000!Urb_LegacyTransferUrbCompletion
    OSNAME:  Windows 10
    FAILURE_ID_HASH:  {6fdd3b5d-5d79-7820-599c-40d8777db652}
    Followup:     MachineOwner

    Run sfc /scannow command to repair system files.
    Next, refer to this similar case, check your GPU driver.