*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 4A, {7759f2ca, 2, 0, fffff88006812ca0}
Probably caused by :
ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )
Followup: MachineOwner
---------
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa8004a518f8, 0, 0}
Probably caused by :
hardware
Followup: MachineOwner
---------
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000005, fffff80003cf8b74, 0, ffffffffffffffff}
Probably caused by :
win32k.sys ( win32k!DEC_SHARE_REF_CNT+e4 )
Followup: MachineOwner
---------
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000005, fffff80003c95b74, 0, ffffffffffffffff}
Probably caused by :
memory_corruption ( nt!MiUnlinkFreeOrZeroedPage+1ca )
Followup: MachineOwner
---------
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa8004a418f8, 0, 0}
Probably caused by :
hardware
Followup: MachineOwner
---------