*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 154, {ffffc88a9b77b000, ffffb40bfc776390, 2, 0}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : hardware_disk
Followup: MachineOwner
FAILURE_BUCKET_ID: 0x154_c0000006_c00000c0_IMAGE_hardware_disk
Sounds good.I will update you with any new crash dumps.
Which is why I mentioned about two drives failing one after another, this is rare and may indicate something else is actually going on.Ok, so i ran seatools and got no issues, then i decided to run crystaldiskinfo again just cause that was weird and crystaldiskinfo says my hard drive is healthy again. This is very confusing as from my limited knowledge hard drives don't usually bounce back from being damaged. I have not had the opportunity to test the drive in a different machine.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {3f, f57c, ed104183, 1c028621}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
Followup: memory_corruption
---------
*** Memory manager detected 1 instance(s) of corrupted pagefilepage(s) while performing in-page operations.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {6001, ffffffffc000000e, 24b50000, ffffd70f62616ed0}
Probably caused by : memory_corruption ( nt!MmStoreProbeAndLockPages+10d2b7 )
Followup: MachineOwner
Checking file system on C:
The type of the file system is NTFS.
A disk check has been scheduled.
Windows will now check the disk.
Stage 1: Examining basic file system structure ...
187392 file records processed.
File verification completed.
6661 large file records processed.
0 bad file records processed.
Stage 2: Examining file name linkage ...
6376 reparse records processed.
256876 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.
6376 reparse records processed.
Stage 3: Examining security descriptors ...
Cleaning up 535 unused index entries from index $SII of file 0x9.
Cleaning up 535 unused index entries from index $SDH of file 0x9.
Cleaning up 535 unused security descriptors.
Security descriptor verification completed.
34743 data files processed.
CHKDSK is verifying Usn Journal...
36645560 USN bytes processed.
Usn Journal verification completed.
Stage 4: Looking for bad clusters in user file data ...
187376 files processed.
File data verification completed.
Stage 5: Looking for bad, free clusters ...
214565843 free clusters processed.
Free space verification is complete.
Windows has scanned the file system and found no problems.
No further action is required.
976131071 KB total disk space.
117435952 KB in 141732 files.
109684 KB in 34744 indexes.
0 KB in bad sectors.
322059 KB in use by the system.
65536 KB occupied by the log file.
858263376 KB available on disk.
4096 bytes in each allocation unit.
244032767 total allocation units on disk.
214565844 allocation units available on disk.
Internal Info:
00 dc 02 00 67 b1 02 00 e6 a1 05 00 00 00 00 00 ....g...........
54 00 00 00 94 18 00 00 00 00 00 00 00 00 00 00 T...............
Windows has finished checking your disk.
Please wait while your computer restarts.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 154, {ffff9c043896a000, ffffcf8030e85550, 2, 0}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : hardware_disk
Followup: MachineOwner
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 154, {ffff8f8c68388000, ffffe784ff31dfb0, 2, 0}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : hardware_disk
Followup: MachineOwner