Sudden crashes with no error message

Your max temps—61°C for the CPU and 69°C for the GPU—are perfectly fine. Things only get critical once you hit the 90°C range, and the system won't force a shutdown until it reaches about 100°C (though the GPU usually handles the heat a bit better than the CPU does). We can officially rule out overheating as the culprit here. Which specific games are actually crashing? Honestly, Windows 10 isn't the best OS for gaming anyway—especially when it comes to older titles. A lot of those classics require a specific patch or switching the compatibility mode to Windows 7 to run properly.

It’s not even like some ancient, outdated titles causing me grief here:
Hitman 2
Mafia 3
Metro Exodus
etc.

I’m getting kicked straight back to my desktop constantly, and lately, it’s even escalated to full-blown Blue Screens of Death. It feels like if I’m not crashing to the desktop, I'm hitting a BSOD instead.
Honestly, I’m at my wit's end here and have no clue what's going on anymore.
If anyone can help me figure this mess out, please do.

Maybe try loading the XMP profile in your UEFI if you haven't already. If that doesn't work, I guess you could try lowering the RAM speed; it might just be causing some instability.

Grab this tool and send over some screenshots of those BSODs:

https://www.nirsoft.net/utils/blue_screen_view.html

Here is what you need to do:
1) Run a RAM test (use the standard Windows Memory Diagnostic, then try an extended version)
https://www.windowscentral.com/how-c...ems-windows-10
2) Perform a file system check via CMD
chkdsk c: /f
Confirm the scheduled scan for when you reboot—and if you have any other partitions, run them too:
chkdsk d: /f
etc. Usually, d: is just your DVD-RW drive, so swap out the letter for whatever your actual secondary partition is (if you even have one)
3) Open Control Panel, go to Device Manager, and select "Show hidden devices" to see if all your drivers are actually behaving—you shouldn't see any yellow or red warning icons
4) If none of those first three steps do the trick, then a clean reinstall of Windows is pretty much inevitable
5) And if step 4 fails? Take that Gigashit bucket back to the store. Like I said at the start of this thread, that company is dead to me after the nightmare I dealt with regarding their Motherboard and GPU.

So, I just went through the whole hassle of doing a totally clean Windows installation today. I wiped everything, grabbed all the latest GPU drivers and the chipset drivers for my motherboard, then downloaded a game from Steam. Now, the game crashes even when I have everything set to optimal settings. This time, unlike last time, I actually made sure to install those AMD chipset drivers for the B350 chipset. But the real kicker is that instead of just crashing silently in the background, I'm getting hit with BSODs left and right now. The game barely survives 10 minutes before it goes down. I even had another BSOD happen while I wasn't even gaming, accompanied by this loud, annoying noise coming from inside the case. Here’s what I’m seeing in the Event Viewer: "The computer has rebooted from a bugcheck. The bugcheck was: 0x00000050 (0xffffffffffffffff, 0x0000000000000010, 0xffffffffffffffffffff, 0x0000000000000002). A dump was saved in: C:\Windows\MEMORY.DMP. Report ID"

"The following boot-start or system-start driver(s) did not load:
dam
EhStorClass"

When things go south and the system hits those critical levels that trigger the crash, the source points back to Kernel-Power.
I’m honestly starting to think this isn't some software glitch at all—it feels like a hardware nightmare. Like, we're looking at either a failing power supply or some other component just giving up the ghost.

If all your drivers look solid after a clean Windows 10 reinstall—meaning no yellow or red exclamation marks in Device Manager—then I’m about 90% certain you're looking at a hardware failure. That's what's triggering those Blue Screens. The other 10%? It could just be buggy software from Gigashit or their absolute garbage BIOS. Did you actually run the RAM test I suggested earlier? If the modules pass, my honest advice is to take that bucket of bolts back to the retailer. You aren't going to find any peace of mind with a Gigashit machine.

Honestly, I’ve decided I’m done messing around with this thing myself. I’m just gonna haul it down to the repair shop after work today and let them deal with the headache. Diagnostics are free there, so it shouldn't be a big deal unless they try to pull some nonsense about needing to buy a brand new, high-end Motherboard to fix it.

I can only charge you for diagnostics if it turns out the issue is actually rooted in your settings or Windows itself.

Alright folks, here's the lowdown on how this whole situation wrapped up. I finally got my rig back from the guys over at Future IT today after the repair, and man, you won't believe the way they handled this. I went in thinking the issue was tucked away in either the RAM slots, the motherboard, or maybe even the CPU, right? Well, get this—these guys were apparently in such a massive rush during their testing phase that instead of actually doing the legwork to pinpoint the specific culprit, they just swapped out basically every single component for brand-new ones. It’s like if you take your car to a mechanic because the engine makes a weird clicking sound, and instead of checking the belt, they just replace the entire engine, transmission, and exhaust system all at once. I honestly don't know if this is just their standard "we don't have time for deep diagnostics" playbook, but I figured I'd give you all a heads-up.
The PC is running smooth as silk now and hasn't given me any grief whatsoever.

Whatever, at least they got you sorted out quickly. I guess they'll just keep running tests on the components...