Question PSU will not work until pins are jumped

Apr 12, 2022
6
0
10
I have a strange issue that I am experiencing where one day my computer completely had no power. No lights or anything. Flipping the PSU switch did not do anything, and different outlets and external power cables had no effect. Re-plugging the 24pin PSU cable did not help.
The only thing I could think of that would cause this issue is either motherboard or PSU. I use a paperclip to jump pins 4 and 5 on the PSU and it actually starts up. I plug it into the motherboard and even the computer turns on.
I thought it was a one off issue until today, a couple days later, I found the computer dead again. Jump the pins one more time and it's back up again.

The computer itself was built back in December 2021 so its fairly new.

I'm thinking it's more of a PSU issue than a motherboard issue, but wanted to see what others think. My thinking is that the only thing that changed was the jumping of the PSU and nothing else.

PSU: Seasonic Prime TX-850
Motherboard: ASUS Prime Z690M-Plus
CPU: Intel i7-12700k
 
Last edited:
? The switch on the back of the PSU doesn't turn it on or off. Off, or O, and it won't turn on at all. On, or | allows it to turn on. But it still needs the signal from the board to start. You said you jumpered the pins, why is the case power button not plugged in?
 
? The switch on the back of the PSU doesn't turn it on or off. Off, or O, and it won't turn on at all. On, or | allows it to turn on. But it still needs the signal from the board to start. You said you jumpered the pins, why is the case power button not plugged in?

When I say I jumped the pins, I mean I jumped the PSU pins, not the power button pins on the motherboard.

When the issue occurs, the computer is completely dead
  1. The switch on the back of the PSU does nothing
  2. The case power button does nothing
In order to get the computer to start again, I have to
  1. Remove the 24pin power cable from the motherboard
  2. Jump the 4 and 5 pins on the PSU cable to start the PSU
  3. Switch off the PSU
  4. Plug the 24pin power cable back into the motherboard
Then the computer will start normally.
 
Last edited:
This is the second time it happened. The first time was a couple of days ago. I can try to jump the pins on the motherboard, but as mentioned before, when the issue occurs, none of the LEDs on the motherboard are lit.
This is worrying because I run a NAS with hard drives in parity, and I risk data corruption when there is an unexpected shutdown. That's actually the other important piece here of information here, is that when the issue happens, I find my computer completely shutdown even though it's supposed to be running.
 
Last edited:
Years ago Jguru was mentioning that sometimes the wires in the ATX bundle seemed loose. Perhaps one isn't making contact the way it should. Perhaps you can try looking at the bundle and making sure it's good.

{quote]This is worrying because I run a NAS with hard drives in parity, and I risk data corruption when there is an unexpected shutdown.[/quote]


What about your backup? With your backup this shouldn't be that big an issue. Also, to me, drives in parity means you are using RAID1. All data is duplicated across both drives. You might loose whatever block was being wrote when the shutdown happened, but all the data is there. You really only need to worry if you are stripping the data across drives, what I call AID0. Then you can have issues. Because when the RAID driver craps out, there goes your data.
 
Years ago Jguru was mentioning that sometimes the wires in the ATX bundle seemed loose. Perhaps one isn't making contact the way it should. Perhaps you can try looking at the bundle and making sure it's good.

{quote]This is worrying because I run a NAS with hard drives in parity, and I risk data corruption when there is an unexpected shutdown.


What about your backup? With your backup this shouldn't be that big an issue. Also, to me, drives in parity means you are using RAID1. All data is duplicated across both drives. You might loose whatever block was being wrote when the shutdown happened, but all the data is there. You really only need to worry if you are stripping the data across drives, what I call AID0. Then you can have issues. Because when the RAID driver craps out, there goes your data.
[/QUOTE]
'parity' may also refer to a RAID 5.

But in either case, another backup is still needed.

That RAID only gives protection for physical drive fail.
Not real data protection.
 
Right. I should have said RAID1 or higher. Which is less of a concern because data on such drives doesn't have a high risk of loss due to shutdown. Even if the shutdown causes a loss of the RAID driver, all the data is still around and can be read/rebuilt. It's really only an issue if he's using AID0. Which I assume he isn't seeing as he said parity.