Jump to content
Corsair Community

HX620W rebooting my system


Recommended Posts

Hey all,


I was hoping you could help me with my "little" problem...


I bought a Corsair HX620 about a month ago, it was meant to be my savior since my old PSU died.. but since installing it, i get random reboots. Sometimes it will reboot while i am in the middle of gaming, and other times it reboots overnight whilst my PC is running nothing but downloads.


I was also getting alot of system crashes, and program crashes back to desktop so i reinstalled my windows and turned off the Automatically reboot when a BSOD comes up. Since the reformatting/installing of my system i am no longer getting system crashes, but i still get the random restarts.


I also did a memtest, i found a few errors in some of my ram i am currently in the process of singling out which module it is. But i don't think that the RAM would be the reason for it randomly restarting without giving me BSOD's...


At times the PC doesn't switch on aswell, it was weird but when it didn't switch on, i opened up my case and i touched the PSU and it started working... it wasn't a coincidence because it has happened again (the not turning on) and i flicked my PSU on the side and it started up.


My PC specs are;


Motherboard - P5B

CPU - Dual Core E6400

RAM - 2 x 1GB Kingston and 2 x 512mb

Harddrives - 1 x 500GB WD and 1 x 250GB WD

PSU - Corsair HX620W

GFX Card/s - I recently purchased Leadtek 8800GT 256mb but i also have my 7600GS.


I really an quite stumped with this problem, i will be trying out a PSU that i know works tonight if i can get ahold of it, but in the meantime does anyone else have any clues as to what else it could be...





Link to comment
Share on other sites

  • Corsair Employees

If you are able to isolate which memory module is faulty then I would suggest that you test the PSU with the module which is passing memtest. If the restarts are still occuring, then there are 2 possibilities. One is that the PSU is tripping the "Over Current Protection" or "Over Voltage Protection" due to an out of spec signal from the motherboard. The second possibility is that there may be a bad component in the PSU.


Before having the PSU replaced, if possible, you may want to test it in a known working system. If it gives you the same issues, we would definitely want to have it replaced, however if there are no problems in another system, you may want to RMA the board.

Link to comment
Share on other sites

well i found out which module was erroring, and i removed it...


I haven't had a restart or an error since taking it out...


Still not to sure how the RAM could have been the issue but doesn't matter now :p


I'll come back if it happens again :)


thanks for the help,



Link to comment
Share on other sites

  • 3 weeks later...



Glad to here you solved your problem. You indicated you didn't understand how memory problems could cause your system to reboot. Actually this is quite common. Basically any thing that can cause a BSOD will reboot your system unless you chnage the Windows Default setting for System Startup and Recovery. Many time this will happen overnight and the only thing you will notice is that in the morning you will be greated by the login prompt and wonder why your machine rebooted.


If you happen to be looking at the screen when the problem occurs you may see a momentary BSOD followed by a reboot. The reason this is occuring is because Microsoft chose to make Automatic Reboot on system failure the default setting. I have no idea why they chose to do this unless they thought BSODs occured so infrequently that an auto reboot once in a while wouldn't bother anybody.


Changig the default is easy. Right Click My Computer, click Properties, click the Advanced tab on the Properties screen, click the button labeled Startup and Recovery Options then clear the checkbox that says Automatically Reboot of System Failure. Close all the windows and reboot your system. Now if you system has a BSOD you system will not reboot and the BSOD will be there until you hard reset or power cycle the system.


My wife runs a consulting business installing and maintaing home and small business systems and every client we setup is configured this way to allow us to properly troubleshoot system problems. Doing this will also prevent you from getting into the nasty situation where you load a bad driver that causes a BSOD every time it loads and you can't get the system to stay up long enough to kill the default reboot setting. If you go on Google and search for XP Stop Codes you will find a wealth of info about the meaning of the various Windows Stop Codes and possible causes. While most are driver or OS related there are a few that indicate hardware problem including bad memory.


If you memory is good and your system is operating properly you should be able to run memtest for 24 hours with no problems. Unless your PSU is seriously underpowered for the system it will usually not be the cause of subtle problems like intermittent memory problems. Its almost always catastrophic failure like system won't start, CPU fan doesn't turn, or starts to turn then stops or the PSU smells bad.


Hope this helps somebody.



Link to comment
Share on other sites


This topic is now archived and is closed to further replies.

  • Create New...