View Full Version : LS powering up system, shutting it down, powering it up, shutting it down over & over
BMORIN
09-10-2005, 10:54 AM
I have a Vapo LS hooked up to my San Diego 3700+, DFI NF3, 2x512 redline and it powers up the system for about 5 seconds, then shuts the system back down, then powers it up for 5 seconds then shuts it down. This happens over and over until I stop it.
I can't figure out why this is happening. I had this problem before but it stopped doing it without reason. I haven't had a problem with it doing this for awhile but now this is all it will do. I have tried swapping out the VC and ram to no avail. Resetting cmos does nothing.
Has anyone experienced this and can anyone tell me what's going on here?
_HL4E_HalfLife_
09-10-2005, 11:46 AM
Hmmm odd problem you got there, Don't those phase systems turn on the pc when the evap reaches a certain temp? If so i can see why it would be doing this, my guess is ur vapo has lost most of its charge but not enough to keep the evap from getting cold enough to turn the pc on (lets say -20c is the system boot temp). So while ur pc is off ur vapo is hitting -20c and it turning the pc on but once its on the heat from the CPU is too much and it brings the evap temp up just enough to turn the pc off (safety feature im guessing).
So you can see where im going with this and why it would be doing this over and over again.
Gray Mole
09-10-2005, 11:56 AM
It's also possible that the temp sensor is bad, what temp is showing on the display and is it movig steadily or dropping sharply as soon as the cpu heats up?
Can you set the boot temp lower and see if it still happens? Will it pull any colder than it is?
Gray
I had this exact same problem. Check if you have version 3.2 of the chill control board. If you do disconnect the usb connector going to it. It will boot. I contacted support to find out why it's doing this.
The 3.2 board is not even listed on thier website and the re-seller I spoke to said he's never seen it before.
Btw I had it happen to me once before also. Shorting jumper 2-3-4 fixed it temporarily but then it started again 1 day later. I found a thread on asetek's site where someone had a problem similar to this and disconnecting the usb cable fixed it. I believe he had to get a replacement board.