BugCheck 51, {1, fffff8a000024010, 1e3f000, 374}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+977a )
Followup: MachineOwner
---------
nt!KeBugCheckEx:
fffff800`03cc0440 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff880`029e83c0=0000000000000051
BugCheck 51, {1, fffff8a000024010, 1e3f000, 374}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+977a )
Followup: MachineOwner
---------
nt!KeBugCheckEx:
fffff800`03cc1440 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff880`0547b3c0=0000000000000051
BugCheck 51, {1, fffff8a000023010, 1e3f000, 374}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+977a )
Followup: MachineOwner
---------
nt!KeBugCheckEx:
fffff800`03c8b440 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff880`02ef23c0=0000000000000051
BugCheck 51, {1, fffff8a000024010, 1e3f000, 374}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+977a )
Followup: MachineOwner
---------
nt!KeBugCheckEx:
fffff800`03ccb440 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff880`029e83c0=0000000000000051
Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!HvMarkDirty+c0 )
Followup: MachineOwner
---------
nt!KeBugCheckEx:
fffff800`03c80440 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff880`036de130=0000000000000050
BugCheck 50, {fffff8a0051bc000, 0, fffff80003f0a2ff, 0}
Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!HvMarkDirty+c0 )
Followup: MachineOwner
---------
nt!KeBugCheckEx:
fffff800`03c72440 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff880`020de130=0000000000000050
BugCheck 50, {fffff8a0051f5000, 0, fffff80003f262ff, 0}
Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!HvMarkDirty+c0 )
Followup: MachineOwner
---------
nt!KeBugCheckEx:
fffff800`03c8e440 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff880`0209e130=0000000000000050