Code:
BugCheck 4E, {99, 9e001, 2, 9e000}
Probably caused by : win32k.sys ( win32k!memset+b0 )
Followup: MachineOwner
---------
BugCheck 3B, {c0000005, fffff800031e7466, fffff8800390f150, 0}
Probably caused by : ntkrnlmp.exe ( nt!NtCreateFile+46 )
Followup: MachineOwner
---------
BugCheck 1A, {8886, fffffa800192aef0, fffffa80000008d0, 500}
Probably caused by : memory_corruption ( nt!MiUnlinkPageFromLockedList+298 )
Followup: MachineOwner
---------
BugCheck 4E, {99, 12801, 2, 127fb}
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
Followup: MachineOwner
---------
BugCheck 23, {1805f1, 75c0, 0, 0}
Probably caused by : fastfat.SYS ( fastfat!FatCommonRead+892 )
Followup: MachineOwner
---------
BugCheck 24, {1904fb, fffff88002e34718, fffff88002e33f80, fffff880014ead97}
Probably caused by : Ntfs.sys ( Ntfs!NtfsQueryDirectory+8e7 )
Followup: MachineOwner
---------
BugCheck 4E, {99, ba7cf, 2, ba7c8}
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
Followup: MachineOwner
---------
BugCheck 4E, {99, 41335, 2, 553d6}
Probably caused by : win32k.sys ( win32k!memset+b0 )
Followup: MachineOwner
---------
BugCheck 4E, {99, a7a19, 2, a6518}
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
Followup: MachineOwner
---------
BugCheck D1, {10a039c, 2, 0, fffff8800108e774}
Unable to load image \SystemRoot\system32\DRIVERS\nvrd64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvrd64.sys
*** ERROR: Module load completed but symbols could not be loaded for nvrd64.sys
Probably caused by : nvrd64.sys ( nvrd64+f774 )
Followup: MachineOwner
---------
BugCheck A, {1, 8, 1, fffff80002e6cfe9}
Probably caused by : hardware ( nt!KiPageFault+260 )
Followup: MachineOwner
---------
BugCheck 50, {fffff87ff4c01650, 8, fffff87ff4c01650, 5}
Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Could not read faulting driver name
Probably caused by : atikmdag.sys ( atikmdag+36e7a9 )
Followup: MachineOwner
---------
Scan system file check please