W10 Unexpected Store Exception followed by BSOD boot loop

I’ve encountered a very frightening situation with my PC. I have been dealing with stability and performance issues for a while now, but today I had my first serious BSOD, and now my PC won’t boot past the loading Windows screen - it BSODs almost immediately, but the BSOD screen goes away almost immediately and the system POSTs again, bringing up the system repair dialog. I’ve ran the repair tool and it hasn’t done anything to fix this. I haven’t tried things like re-seating components or running memtest86 yet because I had to leave right after this happened, but I would love to hear troubleshooting suggestions. I’ve read things about Windows updates causing this specific BSOD for some users, but nothing about a BSOD at boot.

Windows 10 Pro
GIGABYTE GA-B85M-GAMING 3
Intel Pentium G3260 (not overclocked)
Nvidia Geforce GTX 750 Ti
Sandisk SSD
Avast Antivirus

(I’m just declaring this information from memory; please ask for more details if needed)

I’ll be working on this machine later this evening and should post an update then.

[Update 1] Re-seated all potential problem-causing components, and let the PC run Startup Repair once again. It threw this fun error:

Problem Event Name: StartupRepairOffline
Problem Signature 01: 6.1.7600.16385 (PS02 is same value)
Problem Signature 03: unknown
Problem Signature 04: 876
Problem Signature 05: AutoFailover
Problem Signature 06: 1
Problem Signature 07: NoRootCause
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033

[Update 2] I really wanted to catch the BSOD codes so I recorded a video to catch the few frames it was visible. The codes it is throwing are: 0x0000007B (0x80786B58, 0xC0000034, 0x0, 0x0). It seems this could either be a corrupted registry problem OR a dead drive... Hopefully not, considering this drive is less than 3 years old. But the performance issues I’ve been having lately could have been tied to declining read speeds. Unfortunately I don’t know enough about SSDs to be able to confidently make that call.

[Update 3] Ummm... I decided on a whim to flip through my BIOS and found a list of connected SATA devices and... my SSD isn’t showing up. At all. Well, crap. I guess that means the drive is more than likely dead? How would I go about troubleshooting this/trying to salvage what’s on it? Thankfully none of my important stuff was on it, as I store everything except installed programs on external HDDs.

[Update 3.1] I realized rather late into this process that because the SSD is not detectable at all, what my PC was actually doing when “loading Windows” for a brief moment before throwing a STOP BSOD was trying to boot from the HHD that was still plugged in, but it has no actual Windows installation on it anymore (though apparently it’s still flagged as bootable? guess it’s not enough to just delete the Windows folder lol). So yeah, the SSD is fully fried at this point. I’m going to install Linux onto a USB and try to run scans on my other HDDs to make sure I wasn’t hit by a horrible virus or something.