Frequent random BSOD CRITICAL_OBJECT_TERMINATION by ntoskrnl.exe

[anonofrebirth]

I have been getting repeated blue screens of death, most of which have the error CRITICAL_OBJECT_TERMINATION caused by ntoskrnl.exe. They tend to come at complete random. The latest one happened as I was downloading a game. However, I have had several happen while simply browsing the internet so the cause seems borderline random as far as I can tell. The crashes sometimes fail to output minidump logs.
This is a relatively fresh installation of Windows, less than two months old and it has had issues since very early on but the issues have never been consistent (as you can tell by the variety of BSODs I've experienced). This is just the latest set.
I have recently upgraded my RAM. I've since reinstalled Windows and ran Windows Memory Diagnostics and Memtest86+, which did not yield any errors so I assume that's not the cause of the issue. Googling previous BSODs suggested Hard Drive errors so I unplugged my HDD entirely but the PC still produced blue screens.
In addition to CRITICAL_OBJECT_TERMINATION BSODs, I have equally random computer freezes with similar frequency. My computer will entirely freeze up, with every single program not responding. The only option then is to hard-power off. The most recent one was after a reboot. I only had time to switch on my browser.
One suggestion that I have tried is disabling the virtual memory paging file (which deletes it), then reenabling it. This seems to possibly delay the blue screens somewhat but I haven't seen enough of them to be sure whether that's truly the case or just a coincidence.

I have attempted numerous fixes and nothing has seemed to work. This is probably the most obtuse computer issue I've ever come across and I could really use the help.
My profile lists my hardware specifications and I am providing the required log files.
AR-PC-Fri_04_17_2020__60431_57.zip - Google Drive
If you require any more information, I will provide it if possible. Thank you in advance for your help.

 

[MrPepka]

Do you mention that you disconnected the HDD, which disk exactly did you disconnect? Because a lot indicates a failure of the disk on which the system is. Have you replaced this disk with another one?

 

[anonofrebirth]

Do you mention that you disconnected the HDD, which disk exactly did you disconnect? Because a lot indicates a failure of the disk on which the system is. Have you replaced this disk with another one?

I have an HDD and an SSD. I disconnected the HDD, as I think I had some weird file access issues on it and thought that might have been causing it (I believe a few files got corrupted or something of the sort). However, that really did nothing to help. I also formatted that disk entirely as well after the fact.
My OS is installed on the SSD so I haven't removed it or replaced it for obvious reasons. I've been considering trying to remove my SSD and install the OS to my HDD but due to the bother of having to back up hundreds of gigabytes of files and reinstalling my OS a sixth time, as well as the performance loss, I don't want to waste the time doing that without any certainty that it might actually help. I thought I'd ask for advice here before I waste my time, as I've already wasted time on numerous fruitless fixes that I thought "might help".

Might I ask, is it the blue screens themselves that indicate that, or simply my description of the error? I'm somewhat interested in this kinda stuff and want to know what it is exactly that implies that type of hardware failure.
If it's really likely that it's a system drive issue, I'll certainly try to move the OS and all my files. However, considering how fickle this error is (usually happening two or three times a day, then not happening for three days to a week at a time), even if I was to do that, it would take a while before I could say with any certainty whether anything has worked.

I want to mention an additional detail that I noticed after making that post. After I had that freeze (not the BSOD, but the freeze where all programs not respond and I have to hard reset), my PC refused to boot into the OS. It got past the typical motherboard splash screens, blinked a white dash in the top left which disappeared after ten seconds and just gave up. Never got to the Windows logo. I believe a previous BSOD has also caused this once but the majority of the time this does not happen. The solution is to unplug one of the drives (does not seem to matter which), turn the computer on and off, then replug the drive and try again. I usually unplug my HDD.

I would not have been surprised if it was an HDD error, as my HDD is quite old (at least 8 years) but my SSD is much newer (4 years) and that's the drive that contains my OS and most important files.

 

[torchwood]

Hi

It would appear you are using KMSPico to circumvent Validation of the system
note this program has been known to include malware
You also have an MSI retail motherboard using an Asus OEM key
Not sure if MS has picked this up, as you only have 6 updates

please obtain genuine product keys, and we will then help you further

Roy