BSOD doing general tasks, vague idea of cause

About a month ago I finally had to take the plunge into the most recent Win10 update (1809) despite my hesitance. Last time I updated, I encountered this same frequent BSOD (unexpected store error) and while I was able to revert to the previous version, the option is no longer available to me. I was able to generate and read the dump file which mentioned IO_ERROR: (NTSTATUS) 0xc000000e - A device which does not exist was specified and also kept mention my hard disk drive.

What's weird about this is that when I try to scan my SSD (where windows + most programs are stored, I use my HDD for everything else) I crash my computer, sometimes not even generating the BSOD. Even weirder is that every single disk health utility I've used (Crystal disk, different cmd prompts) has turned up nothing and reported perfection.

My vague idea is that my SSD or HDD are failing since I've made sure that all my drivers are good, anti-virus disabled (Windows Defender only), etc and this is the only potential cause. I've attached the log and dump file at the bottom, I really hope you guys can help me with this and sorry for the long post.

Hello and welcome to TenForums!

There have been several BIOS updates for your motherboard. Try using the latest and see if it helps. Make sure the firmware is also up to date for the SSD drive.

Confirmed that SSD and HDD were both running latest firmware, can't believe I didn't think to check BIOS updates! Finished updating it, if nothing crashes in the next day or so I'll go ahead and mark this as solved. Thanks for the help!

Welp, had a crash again, same error code. What's worse is that while a dump is being generated, it seems to be corrupted as I can't even open it in WinDbg. Plus when opening the file in Notepad I can see "PAGEPAGE" sprayed everywhere. Any way I can still get data out of here, or am I screwed?

Another crash, same error code. This time it happened after I closed out of Wargroove and was opening up a couple tabs in Chrome. Same issue with the dump file being corrupted and unreadable. Would it help if I posted the files here for someone to take a look at?

Please post a full set of logfiles as requested in the BSOD Posting Instructions - use the beta log collector

Here's the newest set of logfiles. Sorry for the trouble or if I seem impatient

Yes the recent crash dumps are all corrupted.

Try setting up dump file creation to automatic:
Configure Windows 10 to Create Minidump on BSOD

New day, new crash. Despite setting dump file creation to automatic I'm still getting corrupt/unreadable files. Here's the new betalogs