Your drive is bad.
Code:
Bugcheck code 00000050
Arguments ffffc588`1daf9d38 00000000`00000002 fffff807`30adc2e8 00000000`00000002
0x50 bug check, with the memory at 'ffffc588`1daf9d38' being written to by the instruction at address 'fffff807`30adc2e8'.
Code:
3: kd> !pte ffffc5881daf9d38
VA ffffc5881daf9d38
PXE at FFFFAD56AB55AC58 PPE at FFFFAD56AB58B100 PDE at FFFFAD56B1620768 PTE at FFFFAD62C40ED7C8
contains 0000000000000000
not valid
The memory being written to is invalid. Let's find more about our instruction that wrote to the memory. We need to find the trapframe regarding the exception that was raised that caused the bugcheck to access it.
Code:
3: kd> kv
# Child-SP RetAddr : Args to Child : Call Site
00 fffffd0e`57766cc8 fffff807`30c85e9b : 00000000`00000050 ffffc588`1daf9d38 00000000`00000002 fffffd0e`57766fb0 : nt!KeBugCheckEx
01 fffffd0e`57766cd0 fffff807`30baa957 : 0000007f`5773d000 00000000`00000002 00000000`00000000 ffffc588`1daf9d38 : nt!MiSystemFault+0x1ac1db
02 fffffd0e`57766e10 fffff807`30c63f83 : 00000000`00000056 00000000`00000000 00000000`00000000 ffffd588`2aa5c080 : nt!MmAccessFault+0x327
03 fffffd0e`57766fb0 fffff807`30adc2e8 : 00000000`00000000 0000007f`5773e710 ffffd588`2a3959a0 fffff801`feae2df4 : nt!KiPageFault+0x343 (TrapFrame @ fffffd0e`57766fb0)
Code:
3: kd> .trap fffffd0e`57766fb0
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffc5881daf9d30 rbx=0000000000000000 rcx=0000000000000003
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80730adc2e8 rsp=fffffd0e57767140 rbp=0000000000000001
r8=ffffd5882a395b2c r9=0000007f5773e710 r10=fffff801feb0b800
r11=fffff801feb0b000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!EtwActivityIdControl+0x28:
fffff807`30adc2e8 f0480fc15008 lock xadd qword ptr [rax+8],rdx ds:ffffc588`1daf9d38=????????????????
The instruction at the time of the exception which wrote to the invalid memory was a prefix instruction (lock), which was working with an exchange and add instruction (xadd) to exchange the destination operand w/ the source operand, and then loading the sum into the destination.
So basically: rdx > dereferenced memory at rax+8 > rdx
If we look at rax's register: ffffc5881daf9d30
and then add +8 it becomes: ffffc5881daf9d3
8
Code:
3: kd> !pte ffffc588`1daf9d38
VA ffffc5881daf9d38
PXE at FFFFAD56AB55AC58 PPE at FFFFAD56AB58B100 PDE at FFFFAD56B1620768 PTE at FFFFAD62C40ED7C8
contains 0000000000000000
not valid
The dereferenced memory (rax+8) is invalid.
Code:
3: kd> dd ffffc5881daf9d38
ffffc588`1daf9d38 ???????? ???????? ???????? ????????
ffffc588`1daf9d48 ???????? ???????? ???????? ????????
ffffc588`1daf9d58 ???????? ???????? ???????? ????????
ffffc588`1daf9d68 ???????? ???????? ???????? ????????
ffffc588`1daf9d78 ???????? ???????? ???????? ????????
ffffc588`1daf9d88 ???????? ???????? ???????? ????????
ffffc588`1daf9d98 ???????? ???????? ???????? ????????
ffffc588`1daf9da8 ???????? ???????? ???????? ????????
Let's look at the stack again at the time of the crash.
Code:
00 fffffd0e`57767140 fffff801`feae2df4 nt!EtwActivityIdControl+0x28
01 fffffd0e`57767160 fffff801`feb1e336 rdbss!RxFsdCommonDispatch+0x3a4
02 fffffd0e`577672e0 fffff801`ff2b7afc rdbss!RxFsdDispatch+0x86
03 fffffd0e`57767330 fffff807`30c0fd2a mrxsmb!MRxSmbFsdDispatch+0xfc
04 fffffd0e`57767380 fffff807`313c6f49 nt!IopfCallDriver+0x56
05 fffffd0e`577673c0 fffff807`30cca053 nt!IovCallDriver+0x275
06 fffffd0e`57767400 fffff801`fcedd8b0 nt!IofCallDriver+0x16efd3
07 fffffd0e`57767440 fffff801`fcedd3e9 mup!MupiCallUncProvider+0xb0
08 fffffd0e`577674b0 fffff801`fcedd32a mup!MupStateMachine+0x59
09 fffffd0e`577674e0 fffff807`30c0fd2a mup!MupFsdIrpPassThrough+0x17a
0a fffffd0e`57767550 fffff807`313c6f49 nt!IopfCallDriver+0x56
0b fffffd0e`57767590 fffff807`30cca053 nt!IovCallDriver+0x275
0c fffffd0e`577675d0 fffff801`fb324a63 nt!IofCallDriver+0x16efd3
0d fffffd0e`57767610 fffff807`30c0fd2a FLTMGR!FltpDispatch+0xe3
0e fffffd0e`57767670 fffff807`313c6f49 nt!IopfCallDriver+0x56
0f fffffd0e`577676b0 fffff807`30cca053 nt!IovCallDriver+0x275
10 fffffd0e`577676f0 fffff807`311164c1 nt!IofCallDriver+0x16efd3
11 fffffd0e`57767730 fffff807`3114143a nt!IopSynchronousServiceTail+0x1b1
12 fffffd0e`577677e0 fffff807`310ce086 nt!IopXxxControlFile+0x68a
13 fffffd0e`57767920 fffff807`30c67685 nt!NtDeviceIoControlFile+0x56
14 fffffd0e`57767990 00007ffe`d470f754 nt!KiSystemServiceCopyEnd+0x25
15 0000007f`57bff808 00000000`00000000 0x00007ffe`d470f754
We're going through a lot of file system stuff here, going off the rails ultimately doing some event tracing work. You have verifier enabled also and it failed to catch any drivers messing w/ the file system:
Code:
3: kd> !verifier
Verify Flags Level 0x001209bb
STANDARD FLAGS:
[X] (0x00000000) Automatic Checks
[X] (0x00000001) Special pool
[X] (0x00000002) Force IRQL checking
[X] (0x00000008) Pool tracking
[X] (0x00000010) I/O verification
[X] (0x00000020) Deadlock detection
[X] (0x00000080) DMA checking
[X] (0x00000100) Security checks
[X] (0x00000800) Miscellaneous checks
[X] (0x00020000) DDI compliance checking
Your drive readings and stats are bad as listed much earlier in this post. IDK what more proof you need.
Replace your drive.