Plagued by BSODs - sometimes stuck on BSOD at 0% or random restarts

Tinylime, if your Anti-virus is Windows Defender, try disabling it, then run the4 V2 log collector, the re-enable Windows Defender. I've seen a few people report some part of Windows Defender has affected running the V2 collector.

• Open Start. . ...
• Open Settings. . ...
• Click. Update & Security. ...
• Click Windows Security. This tab is in the upper-left side of the window.
• Click Virus & threat protection. ...
• Click Virus & threat protection settings. ...
• Disable Windows Defender's real-time scanning.

Enable again after running V2 log collector.

Unfortunately, it looks like Windows has become corrupted again.

What memory tests did you run?

Unfortunately, I cannot say what is corrupted. Recently there are some problems with the tool Windbg that we use to look into dumps. Windbg requires files called symbols to recognize files from Windows allowing someone to look in-depth in the dump, but as it happens there are symbol issues so Windbg is not able to provide much insight in the dumps.

All I know is that the second parameter of the bugcheck in the screenshot below means that a file's hash is not what was expected what explains the bugcheck. To elaborate on the latter, during the process that Windows boots Windows marks a few files as 'critical', this means that if anything with these files is being done, e.g. something is touching the memory of these files or the files are being touched, these files are being compromised and the processes of these files will be terminated. As these files are marked as critical it also means that Windows cannot run without them, so when the related processes are being terminated Windows can do only one thing and that is crash the system.
Attachment 238509

Because the hash of one of the critical files has changed it means the file is corrupted. With what you mentioned, Windows being corrupted before, the only reason to all this is hardware.


In regards to SFC, I barely know anything about it, but I do know that it checks the hashes of protected system files and matches the hashes against the hashes stored in the COMPONENTS hive to find corrupted files. I don't know which files on a Windows system are protected system files, but I think it is safe to assume the critical file isn't one of them. Doesn't make sense at first, but if with SFC it is possible to replace the critical file, the system needs to close the processes related to the file to replace it and that causes a problem.


Do you have access to another pc you could use to prepare some things? We'll need to run some tests to hopefully identify the culprit.

@Ztruker, that list of files is almost complete, it's just missing dxdiag.txt and dumps.

Hard drive and memory tests, Windows Memory Diagnostic test isn't really known for its quality so I recommend MemTest86 free for memory and SeaTools for Hard drive.
SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums
Test RAM with PassMark MemTest86 | Sysnative Forums