Code:
BugCheck 7A, {fffff6fb800083f8, ffffffffc000000e, 5aea8880, fffff7000107fff8}
Probably caused by : volsnap.sys ( volsnap!VspCleanupVolumeSnapshot+49 )
Followup: MachineOwner
---------
Code:
KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in. Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: fffff6fb800083f8, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Code:
ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.
DISK_HARDWARE_ERROR: There was error with disk hardware
I want you to read the read lines above. As per the crash dumps, it is a disk hardware error. And the disk hardware is a SSD, SanDisk SDSSDHP128G.
Traditional disk checks are not possible for SSDs. You need to try for a firmware update, and before attempting for it, please read this link carefully. Firmware SDSSDP-128G - SanDisk Forums
So before attempting anything in this line, better you ask in SanDisk's forum.
Also let us see a screenshot of the SSD using CrystalDiskInfo.
Quote