BugCheck 3B, {c0000005, fffff80002d634f8, fffff88007ecdf00, 0}
Probably caused by : memory_corruption ( nt!MiRelocateImageAgain+48 )
Followup: MachineOwner
---------
BugCheck 1E, {ffffffffc0000005, fffff96000082f18, 0, 1}
Probably caused by : win32k.sys ( win32k!GreExtTextOutWLocked+12b8 )
Followup: MachineOwner
---------
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
Followup: MachineOwner
---------
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
Followup: MachineOwner
---------
BugCheck C1, {fffff980123d2ff0, fffff980123d2ffc, 41000c, 24}
Unable to load image \??\C:\Windows\gdrv.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for gdrv.sys
*** ERROR: Module load completed but symbols could not be loaded for gdrv.sys
Probably caused by : gdrv.sys ( gdrv+30c7 )
Followup: MachineOwner
---------
BugCheck 3B, {c0000005, fffff80002a848c2, fffff880028f2180, 0}
Probably caused by : ntkrnlmp.exe ( nt!KeSetEvent+332 )
Followup: MachineOwner
---------
BugCheck 1E, {ffffffffc0000005, fffff80002adbc8a, 0, ffffffffffffffff}
Probably caused by : ntkrnlmp.exe ( nt!KeWaitForMultipleObjects+2b0 )
Followup: MachineOwner
---------
BugCheck 3B, {c0000005, fffff88004da10a4, fffff88008782810, 0}
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiInterlockedRemoveHeadListIfExist+30 )
Followup: MachineOwner
---------
BugCheck D1, {fffff7fffaa5ed94, 2, 8, fffff7fffaa5ed94}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
Followup: MachineOwner
---------