BugCheck 3B, {c0000005, fffff8000305601e, fffff880091b0e20, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExEnterCriticalRegionAndAcquireFastMutexUnsafe+26 )
Followup: MachineOwner
---------
BugCheck 50, {fffff900c2fb47a0, 0, fffff960006ddc51, 0}
Unable to load image \SystemRoot\System32\cdd.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for cdd.dll
*** ERROR: Module load completed but symbols could not be loaded for cdd.dll
Could not read faulting driver name
Probably caused by : cdd.dll ( cdd+dc51 )
Followup: MachineOwner
---------
BugCheck 3B, {c0000005, fffff8000308701e, fffff88009133e20, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExEnterCriticalRegionAndAcquireFastMutexUnsafe+26 )
Followup: MachineOwner
---------
BugCheck 124, {0, fffffa8004ae6038, 0, 0}
Probably caused by : hardware
Followup: MachineOwner
---------
BugCheck 3B, {c0000005, fffff8000305201e, fffff88009e13e20, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExEnterCriticalRegionAndAcquireFastMutexUnsafe+26 )
Followup: MachineOwner
---------
BugCheck 50, {fffff900c1ee1030, 0, fffff960002bc69d, 0}
Unable to load image \SystemRoot\System32\win32k.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Could not read faulting driver name
Probably caused by : win32k.sys ( win32k+27c69d )
Followup: MachineOwner
---------
BugCheck 3B, {c0000005, fffff96000174283, fffff88005d4c060, 0}
Unable to load image \SystemRoot\System32\win32k.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : win32k.sys ( win32k+c4283 )
Followup: MachineOwner
---------