F5F Stay Refreshed Hardware Desktop PC crashes during operation + GPU inquiries

PC crashes during operation + GPU inquiries

PC crashes during operation + GPU inquiries

S
Shyrell
Member
Find
130
04-21-2020, 11:19 AM
#1
Recently my PC began crashing while running demanding games like 4K Days Gone and HL: Alyx. It doesn’t fail in less graphically heavy titles (144hz, FullHD Dota 2, Destiny 2). The system shuts down instantly without any BSOD or error alerts. After the crash, it can’t be restarted, though the RGB remains functional. I have to unplug it from the power supply or switch off/on the PSU.

The crashes occur randomly after just a few hours of gameplay. I suspect either the GPU is overheating or the PSU is failing. I verified all cables and the riser cable are secure, and changing PBO settings didn’t resolve the issue.

I also ran Furmark and it stayed stable for over ten minutes at both 77°C and 100°C hotspots. Could the high temperature be the cause?

Additionally, GPU-Z indicates Resizable BAR is disabled, yet I enabled it in the BIOS. Should I enable it elsewhere as well?

Details of the build:
- Motherboard: Asrock B550 Phantom Gaming 4 itx
- CPU: AMD Ryzen 5 5600x (PBO 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: Silent Loop 2 240
- Case: Dan A4-H2O
Reply
Reply
S
Shyrell
04-21-2020, 11:19 AM #1

Recently my PC began crashing while running demanding games like 4K Days Gone and HL: Alyx. It doesn’t fail in less graphically heavy titles (144hz, FullHD Dota 2, Destiny 2). The system shuts down instantly without any BSOD or error alerts. After the crash, it can’t be restarted, though the RGB remains functional. I have to unplug it from the power supply or switch off/on the PSU.

The crashes occur randomly after just a few hours of gameplay. I suspect either the GPU is overheating or the PSU is failing. I verified all cables and the riser cable are secure, and changing PBO settings didn’t resolve the issue.

I also ran Furmark and it stayed stable for over ten minutes at both 77°C and 100°C hotspots. Could the high temperature be the cause?

Additionally, GPU-Z indicates Resizable BAR is disabled, yet I enabled it in the BIOS. Should I enable it elsewhere as well?

Details of the build:
- Motherboard: Asrock B550 Phantom Gaming 4 itx
- CPU: AMD Ryzen 5 5600x (PBO 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: Silent Loop 2 240
- Case: Dan A4-H2O

Reply
Reply
I
Izzyb2004
Member
Find
152
04-22-2020, 04:11 PM
#2
Begin with a reliable power source offering at least 150W more than your requirements. That’s the first step.
Reply
Reply
I
Izzyb2004
04-22-2020, 04:11 PM #2

Begin with a reliable power source offering at least 150W more than your requirements. That’s the first step.

Reply
Reply
L
LCBadgett
Junior Member
Find
4
05-05-2020, 06:58 AM
#3
PSU operated this equipment for over a year prior to the current one, including a previous setup with a Ryzen 2600, and there were no problems. This indicates it's not a recent installation.
Reply
Reply
L
LCBadgett
05-05-2020, 06:58 AM #3

PSU operated this equipment for over a year prior to the current one, including a previous setup with a Ryzen 2600, and there were no problems. This indicates it's not a recent installation.

Reply
Reply
B
Brentjuh
Member
Find
55
05-14-2020, 04:04 AM
#4
I'd describe that as pure luck above all else. It could even be imagined that the power supply was in excellent condition, managing to exceed its expected limits.
Reply
Reply
B
Brentjuh
05-14-2020, 04:04 AM #4

I'd describe that as pure luck above all else. It could even be imagined that the power supply was in excellent condition, managing to exceed its expected limits.

Reply
Reply
F
Freakiiianyx3
Senior Member
Find
694
05-16-2020, 01:51 AM
#5
Hi, just checking if you activated the XMP setting.
I'm not an expert, but your issue is quite similar to what I faced three years ago with a new PC setup—Ryzen 5 3600, 1660 Super, and 16GB of 3600mhz RAM on a Corsair Vengeance 16GHz kit.
I turned XMP on and set the RAM speed to 3600mhz.
When I play games, my PC randomly shuts down with a black screen, which happens often.
It turns out the motherboard only supports up to 3200mhz, even though it claims support for 4733+mhz (I had to overclock).
I was confused because I enabled XMP but still faced this problem.
Now I’m turning XMP off and setting the RAM speed to 3200mhz, which has stopped the random shutdowns.
If you just enabled XMP, maybe lowering it to 3200mhz would help?
Also, if you kept the 3600mhz setting, could you tell me if you changed the voltage? I’d like to try running at 3600mhz again.
Reply
Reply
F
Freakiiianyx3
05-16-2020, 01:51 AM #5

Hi, just checking if you activated the XMP setting.
I'm not an expert, but your issue is quite similar to what I faced three years ago with a new PC setup—Ryzen 5 3600, 1660 Super, and 16GB of 3600mhz RAM on a Corsair Vengeance 16GHz kit.
I turned XMP on and set the RAM speed to 3600mhz.
When I play games, my PC randomly shuts down with a black screen, which happens often.
It turns out the motherboard only supports up to 3200mhz, even though it claims support for 4733+mhz (I had to overclock).
I was confused because I enabled XMP but still faced this problem.
Now I’m turning XMP off and setting the RAM speed to 3200mhz, which has stopped the random shutdowns.
If you just enabled XMP, maybe lowering it to 3200mhz would help?
Also, if you kept the 3600mhz setting, could you tell me if you changed the voltage? I’d like to try running at 3600mhz again.

Reply
Reply
W
wiw
Member
Find
223
05-17-2020, 12:21 PM
#6
Yeah, I adjusted the XMP a while back, around 8-9 months ago, and it functioned properly.
I identified the issue as a defective socket extension.
Reply
Reply
W
wiw
05-17-2020, 12:21 PM #6

Yeah, I adjusted the XMP a while back, around 8-9 months ago, and it functioned properly.
I identified the issue as a defective socket extension.

Reply
Reply