Probably caused by : ntkrnlmp.exe ( nt!KeAccumulateTicks+1187d5 )
Followup: MachineOwner
---------
nt!KeBugCheckEx:
fffff800`5c038490 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff800`5ebf2bd0=0000000000000133
BugCheck 3B, {c0000005, fffff8029ab80a4e, ffffb50b56cfe9d0, 0}
Probably caused by : memory_corruption ( nt!MmEnumerateAddressSpaceAndReferenceImages+12e )
Followup: MachineOwner
---------
nt!KeBugCheckEx:
fffff802`9a7ac490 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffb50b`56cfe100=000000000000003b
BugCheck 3B, {c0000005, fffff802c1d9953a, ffffa606e971e3f0, 0}
Probably caused by : memory_corruption ( nt!MiGetProtoPteAddress+8a )
Followup: MachineOwner
---------
nt!KeBugCheckEx:
fffff802`c1e47490 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffa606`e971db20=000000000000003b