Unknown BSOD and impossible-to-find windbg

My old Windows 7 install has been plagued with BSODs for the past few weeks and I eventually decided to just reinstall it entirely, which kept them at bay for about a week but today it went right back to crashing for seemingly no reason.

I've tried to locate an installer for WinDbg so I can find out what the problem is, but the Windows SDK doesn't allow me to install it because it doesn't recognise the version of NET framework I have installed (even though I specifically installed the version it asked for via the go.microsoft link) and I can't find it anywhere else. I even tried to install WinDbg Preview on my Windows 10 laptop but wouldn't you know, the one time I go to get something from the Microsoft Store, it doesn't even download the damn thing. I swear, there isn't a day that I use Windows 10 without it doing something to make me angry.

I uploaded the DM log and the minidump file if anyone wants to take a look but I'd be happy enough if someone could help me install windbg so I can check it out myself, because I'm sure this isn't going to be the last time I have a problem.

Thanks, I downloaded those and I'm trying to follow the BSOD analysis guide, starting with Driver Verifier, but I can't find most of the information that it's supposed to gather. The support page says that after running it and restarting, the results are in property pages like Driver Status, Global Counters, Pool Tracking and Settings, but I can't find those.

The BSOD analysis guide tells me to start verifier.exe and restart my computer, which I did, and Driver Verifier is supposed to "disable faulty drivers in between BSOD and reboots until you finally reach the desktop". Well, my computer booted to the desktop, at which point the TrustedInstaller process occupied the CPU for a while, and that's it. I'm not sure what was supposed to happen here.

WhoCrashed tells me the most recent crashes were caused by ntoskrnl.exe, which might be because of my CPU overheating. I could remove the cooler and reapply thermal paste but if overheating was the problem, I'd have expected that Driver Verifier occupying the CPU at 90% for 15 minutes would have caused it to happen again. The pattern I'm noticing here is that everything is stable for a while, then one BSOD happens, and two or more quickly follow that one if I don't boot windows into safe mode. Is that consistent with overheating?

Oh yeah, about the Windows SDK, NET Framework 4.7.2 is the only version installed on my system, and the SDK installer still says it's only seeing a pre-release version and throws up an error message when I try to install it, but after two hours of downloading the Windows 10 version of WinDbg finally showed up so at least I can use that one.

Yeah, I noticed that ntoskrnl.exe is a system process, I was just quoting the crash report verbatim. I have Windows installed on an Intel SSD I've been using for about three years, and I've been using the motherboard/processor for maybe four. I suspected something might be wrong there but the Intel SSD toolbox reports no problems after a full diagnostic scan on reading functionality and data integrity. The SMART summary doesn't seem to be out of the ordinary either, except for maybe the CRC error count of 2431. However, I have a second SSD that Windows had trouble detecting a few days ago because the SATA cable didn't connect properly. That problem went away after I replaced the cable, but could the same thing be happening to the system drive? Do BSODs ever happen because of bad SATA cables? Or might there be a problem that this program can't detect?

Interesting, because it was the SATA cable without clips that wasn't connecting properly to my other SSD. My system SSD is affixed to the bottom of my case, and even with the shortest SATA cable I have, the angle of it causes some lateral push on the connector, so I'm worried that without a clip it won't connect properly either. I haven't had more BSODs in two days, so I'm going to wait and see if it happens again, and then maybe I can move my system from one SSD to the other as a solution.

In case I run into more/different problems in the future, could either of you help me understand how to properly use Driver Verifier? I'd like to be able to at least eliminate bad drivers if my install goes to hell again like before.