Question PC hard crashes + GPU questions

[smtn]

Lately my PC started crashing during hardware intensive gaming: 4K Days Gone and HL: Alyx, but it doesn't crash in less graphically intensive games (144hz, FullHD Dota 2, Destiny 2)
PC turns off instantly, without BSOD or error messages. It can't be turned on after the crash (but the RGB is still working after the crash), I have to disconnect it from the socket or switch off/on the PSU.
The crash happens randomly after less than 1-5+ hours of gameplay.

I think that's either GPU overheating or PSU dying. I checked all the PSU cables and the riser cable, and they are secure. Turning PBO on/off didn't help.
However, I tried to crash the PC by running Furmark, bit it stays stable for 10+ minutes at 77C and 100C Hotspot. Could 100C hotspot causing this?
I've also got another question, GPU-Z shows that Resizable BAR is disabled, but I turned it on in the BIOS. Should I activate it somewhere else too?

Specs:
Motherboard - Asrock B550 Phantom Gaming 4 itx
CPU - AMD Ryzen 5 5600x (PBO turned on)
GPU - NVIDIA Palit Jetstream 3070 8GB (Stock)
RAM - 2x16GB G.Skill Trident Z (3600Mhz XMP)
PSU - Fractal Design Ion SFX-L 500W Gold
Storage - 2TB m.2 NVME WD black + 512GB m.2 NVME Kingston
Cooling - be quiet! Silent Loop 2 240
Case - Dan A4-H2O

 

[punkncat]

As a start you need a good power supply with at least 150W more output than the one you spec. I would start there.

https://www.google.com/search?q=307...g2MDcxajBqMagCALACAA&sourceid=chrome&ie=UTF-8

 

[smtn]

As a start you need a good power supply with at least 150W more output than the one you spec. I would start there.

https://www.google.com/search?q=307...g2MDcxajBqMagCALACAA&sourceid=chrome&ie=UTF-8

PSU was running this hardware for more than a year (and a year before that with Ryzen 2600) without issues, it's not a new build

 

[punkncat]

PSU was running this hardware for more than a year (and a year before that with Ryzen 2600) without issues, it's not a new build

I would call that luck more than anything else. Could go even further to surmise that it was a darned good power supply to be reaching into overhead it was never rated to have.

 

[danny phantom]

hi, just asking, did you just enabled the xmp ?

im no expert but your problem is kinda similar to what i experienced 3 years ago when my pc were freshly built. ryzen 5 3600, 1660 super , and 16gigs of 3600mhz cl18 corsair vengeance kit.
i enabled xmp and set the ram to run at 3600mhz.
whenever im gaming my pc randomly shuts down, all black screen, it happens a lot of times, turned out because the mobo basically only supports up to 3200mhz. despite saying supports up to 4733+ mhz (need to OC)

and i was so confused why, because i turned the xmp on, but yeah thats what happens to my rig, so now im enabling xmp but set down the speed to 3200 mhz, not 3600. never shuts down randomly anymore.

if you just enabled the xmp, maybe set it down to 3200mhz and see how it works?
and if the xmp 3600mhz was set all along, may i know did you change the voltage? because i wanna try to run at 3600mhz again

 

[smtn]

hi, just asking, did you just enabled the xmp ?

im no expert but your problem is kinda similar to what i experienced 3 years ago when my pc were freshly built. ryzen 5 3600, 1660 super , and 16gigs of 3600mhz cl18 corsair vengeance kit.
i enabled xmp and set the ram to run at 3600mhz.
whenever im gaming my pc randomly shuts down, all black screen, it happens a lot of times, turned out because the mobo basically only supports up to 3200mhz. despite saying supports up to 4733+ mhz (need to OC)

and i was so confused why, because i turned the xmp on, but yeah thats what happens to my rig, so now im enabling xmp but set down the speed to 3200 mhz, not 3600. never shuts down randomly anymore.

if you just enabled the xmp, maybe set it down to 3200mhz and see how it works?
and if the xmp 3600mhz was set all along, may i know did you change the voltage? because i wanna try to run at 3600mhz again

Yeah I set the XMP long time ago, like 8-9 months ago, it worked fine

I figured the culprit, it was a faulty socket extension.