might have a faulty expensive psu

Soldato
Joined
28 Aug 2017
Posts
3,063
Location
United Kingdom
the last couple of weeks i've been having some very weird behaviour on my am5 rig, specs below

7950x
32gb dominator 6000mhz (oc'd to 6200mhz)
asus extreme x670-e (bios updated to 1.0.0.8) bios version 1709
500gb samsung 980 pro m.2
samsung 870 qvo 8tb ssd
be quite dark power pro 12 1500w titanium psu
sapphire 7900xtx MBA
custom loop cooling
7x140mm noctua industrial 3000rpm fans

any game i load up after say around 15-25mins i get a full system shutdown, sometimes all rgb is lit up but all fans are stopped, other times it shuts off and no rgb is off but ram led's are lit up. the only way to power on is to pull the power cord.
I have gone into bios and backed off my memory oc back to 6000mhz and limited my cpu to 4.5ghz with 1.1v and undervolted my gpu to -10% but nothing seems to work, i get a bit further when limiting clocks on cpu and gpu but i still get shutdowns when in games with accociated led's/rgb still on, my latest shutdown i heard my psu make a tick sound right as it powered off, so am thinking it could be it.

Temps in games are super low, if i have my cpu at stock settings and gpu i see around 74c on cpu and around 36c core and 55 hotspot on gpu, if i limit my cpu and gpu temps are around 45c for cpu and 32c core and 41c hotspot.

Gpu power draw at stock sppeds is around the 348w mark with spikes around 474w, when power limited it sits around 312w and spikes in the 430w region.

I took some hardware info readings of my system when i started up a game to see what my system was doing

tIONNxt.png


Something to note i think my 5v rail is a bit high but other than that everything looks ok?

any help is appreciated
 
Last edited:
Let’s start with the simple: have you checked all the power cables at both ends And made sure they are fully seated?

it certinally is, on psu side and motherboard/gpu side, idle is no problem at all, but under load, man what a pain.

checking event viewer i see plenty of 6155 errors, a few 10016 error codes, 5 error code 41's kernal power code (dated today around the time(s) the system shut off), system didnt shut down properly, caused if the system stopped responding, crashed, or lost power.
 
Last edited:
checking event viewer i see plenty of 6155 errors, a few 10016 error codes, 5 error code 41's kernal power code (dated today around the time(s) the system shut off), system didnt shut down properly, caused if the system stopped responding, crashed, or lost power.
WHEA errors are likely if you have unstable overclocks, I don't think those other errors are meaningful. Kernel 41 is just "something broke and PC turned off" so it's not overly helpful either.

Something to note i think my 5v rail is a bit high but other than that everything looks ok?
You can hit record I think (+ button), but even if it shows a drop on one of the rails, that's not necessarily informative.

any game i load up after say around 15-25mins i get a full system shutdown, sometimes all rgb is lit up but all fans are stopped, other times it shuts off and no rgb is off but ram led's are lit up. the only way to power on is to pull the power cord.
15-25 minutes suggests overheating, or that the fault only happens when it is hot(ter).

i get a bit further when limiting clocks on cpu and gpu but i still get shutdowns when in games with accociated led's/rgb still on
How much further?

Have you tried going dramatic, e.g. 50% of the GPU clock?

i heard my psu make a tick sound right as it powered off, so am thinking it could be it.
Possibly, but it could be the fan or to this:

"Most of our power supply units (PSUs) have an inrush current bypass relay that makes a *click* noise when the PC turns on and off. This is considered normal and not a defect.

If your PSU is making loud repetitive clicking sounds after you turn your PC on, contact Customer Support."

 
WHEA errors are likely if you have unstable overclocks, I don't think those other errors are meaningful. Kernel 41 is just "something broke and PC turned off" so it's not overly helpful either.


You can hit record I think (+ button), but even if it shows a drop on one of the rails, that's not necessarily informative.


15-25 minutes suggests overheating, or that the fault only happens when it is hot(ter).


How much further?

Have you tried going dramatic, e.g. 50% of the GPU clock?


Possibly, but it could be the fan or to this:




with regard to my event logs i put them in severity order and i have 21 total error code 41's over the last couple of weeks

when i have hwinfo up its always on top so i can see it in any game i play

15-25mins during this time temps are really good under load, everything major is on a custom loop

with regard if i under volt i can get around a 1hr at very best but then get a sudden power off.

havent tried dropping back clocks but in cyberpunk i see around 2600mhz and in destiny 2 around 1600-2200mhz normally, both games still make the system power off.

i just started up destiny 2 and within hwinfo 64 i saw my flck clock jump to a maximum 2497mhz, even though i have it manually set at 2000mhz in bios, could that cause the cpu to trip up and cause a shutdown?
 
Last edited:
i just started up destiny 2 and within hwinfo 64 i saw my flck clock jump to a maximum 2497mhz, even though i have it manually set at 2000mhz in bios, could that cause the cpu to trip up and cause a shutdown?
I've no idea I'm afraid, I've never monitored anything that closely and I don't know how much you can trust those readings to be indicative of what's really happening.

15-25mins during this time temps are really good under load, everything major is on a custom loop

with regard if i under volt i can get around a 1hr at very best but then get a sudden power off.
It's possible that the thing that is overheating isn't getting sufficient cooling for some reason, like maybe it is somewhere on the PCB of the motherboard, graphics card or PSU that isn't receiving enough/any airflow.

Or, it is just not working right anyway and the heat exposes the issue.
 
  • Like
Reactions: sg0
I've no idea I'm afraid, I've never monitored anything that closely and I don't know how much you can trust those readings to be indicative of what's really happening.


It's possible that the thing that is overheating isn't getting sufficient cooling for some reason, like maybe it is somewhere on the PCB of the motherboard, graphics card or PSU that isn't receiving enough/any airflow.

Or, it is just not working right anyway and the heat exposes the issue.

i may have cracked it, after seeing the flck clock go so high i popped into the bios and manually set it from 2033 to 2000 and booted back into windows, currently in game (34mins in) and totally fine flck clock hasnt't gone above 2033 in max reading, cpu temps in the upper 70's (back to oob settings boosting to around 5.6ghz) with gpu chilling at 42c.

might not have been the psu after all, though when i heard the click it did make me think.
 
i may have cracked it, after seeing the flck clock go so high i popped into the bios and manually set it from 2033 to 2000 and booted back into windows, currently in game (34mins in) and totally fine flck clock hasnt't gone above 2033 in max reading
Cool, fingers crossed then!
 
Have still been getting random shutdowns when i lauch any game its been very sporadic, sometimes i can replicate the issue and other times its fine. i eneded up changing the gpu power cable, and having done that i get no more power off's.
 
Last edited:
Back
Top Bottom