I am 100% sure, I ran chkdsk on my system drive today and checked the result in event viewer
The only difference is that the tag is different, the tag is 'Wininit'.
If you can find a chkdsk log with the tag 'Wininit' then it means chkdsk did save the log
Log Name: Application
Date: 01-Oct-16 11:20:09
Event ID: 1001
Task Category: None
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 ...
436992 file records processed.
File verification completed.
6751 large file records processed.
0 bad file records processed.
Stage 2: Examining file name linkage ...
501022 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.
Stage 3: Examining security descriptors ...
Cleaning up 937 unused index entries from index $SII of file 0x9.
Cleaning up 937 unused index entries from index $SDH of file 0x9.
Cleaning up 937 unused security descriptors.
Security descriptor verification completed.
32016 data files processed.
CHKDSK is verifying Usn Journal...
33924832 USN bytes processed.
Usn Journal verification completed.
Stage 4: Looking for bad clusters in user file data ...
436976 files processed.
File data verification completed.
Stage 5: Looking for bad, free clusters ...
53385808 free clusters processed.
Free space verification is complete.
Windows has scanned the file system and found no problems.
No further action is required.
244478975 KB total disk space.
30285932 KB in 133598 files.
102568 KB in 32017 indexes.
0 KB in bad sectors.
547243 KB in use by the system.
65536 KB occupied by the log file.
213543232 KB available on disk.
4096 bytes in each allocation unit.
61119743 total allocation units on disk.
53385808 allocation units available on disk.
00 ab 06 00 df 86 02 00 22 fa 04 00 00 00 00 00 ........".......
dd 00 00 00 66 00 00 00 00 00 00 00 00 00 00 00 ....f...........
Windows has finished checking your disk.
Please wait while your computer restarts.
The dump 0x74 is a bad configuration of the system information.
I have one more question,
Is it normal for a SSD to not get detected when hitting the reset switch on the front panel? When my PC gets a BSOD I cant just hit the reset button and boot back. The disk doesnt get detected and I have to leave the PC on for 20 mins and then shut it down, wait for about 2 more mins and then start it for the disk to get detected and to boot in to Windows. Sometimes I have to do this 2 times. Sometimes I just shut down and use the PC the next day.
System information is loaded into the temporary part of the registry everytime the system boots, this so the system knows what it works with. To be able to do this the system information must be loaded into the memory.
I can't remember the exact process of what happens again, so I'm not sure if the system information is verified before it is loaded into the temporary registry.
My point, with the 0x74 the suspected causes are the memory (information being loaded in bad memory) or a registry issue.
I would like to start with a memory diagnostics test, as that is easier. Please read the instructions below carefully.
Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 10 Forums
MemTest86+ needs to be run for at least 8 complete passes
for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero
errors here. Even a single error will indicate RAM failure.
Make a photo of the result and post it.
If errors show up you can stop the test, remove all sticks but 1 and test this single stick in each slot for 8 passes or until errors show, switch sticks and repeat.
If errors show up and you see them a lot later, no problem, the errors don't affect the test.