MillbrookWest

Pretty much this. The event viewer is filled with errors, even for a brand new install. They aren't always generated close together either. The error i was asking after gets logged a little while after booting - hence the clarity (as i have no way of knowing what you looked for; the two listed are almost always visible on the same section and for people, that's usually enough). But as i say, a system dropping is a sign of a hardware issue of some sort; it's unlikely its a terminal issue [the hardware itself] as a terminal issue would affect more processes. More likely the drivers - These can be for your keyboard, mouse, sound etc,. If you have a spare GPU laying around, try swapping it in and seeing if the issue goes away. EDIT: If swapping the GPU still does nothing, then start with the other things you plug-in, failing that try (if you even remember which) removing programs that asked for admin privileges (either to run, or when installing [e.g. Afterburner]).

No reference to what i asked in OP. Ironically, that's the same thread i replied in saying the exact same thing. OP from that thread was unwilling to test with an FPS cap. Also ironically, is that i said the same thing there as i did here; 'what's the event log say?' Specifically the WHEA-Logger as AMD will throw an error here if it's CPU. If it's not CPU, you can look elsewhere. But, as i say, a program can't crash a system (see user-mode). It merely exposes an issue. It's why Cinebench (or whatever) will crash your system with a bad overclock. The program does not care, it did the same thing is both cases. It's that hardware that took issue with the task asked, and the strain given.