PDA

View Full Version : My First Vapochill Build



Tutto
10-09-2006, 10:11 AM
I just built a Vapo LS running a P5W DH Deluxe and everytime I try to restart the computer, the system shuts down and I have to start remanually :( Also, on restart I get an error message in the bios stating that overclocking/overvoltage failed when it didn't. Do this have something to do with the mobo or do I possibly have a problem with my chill control. Has anybody else experience this annoying problem?

Ssilencer
10-09-2006, 06:46 PM
I just built a Vapo LS running a P5W DH Deluxe and everytime I try to restart the computer, the system shuts down and I have to start remanually :( Also, on restart I get an error message in the bios stating that overclocking/overvoltage failed when it didn't. Do this have something to do with the mobo or do I possibly have a problem with my chill control. Has anybody else experience this annoying problem?

It's a common problem with the chillcontrol and the asus boards, the only fix I know is to use a separate psu for the vapochill.

Tutto
10-09-2006, 08:29 PM
Could you explain to me how I could use a seperate power supply for the vapochill? Also, is it only a problem with ASUS boards. It would seem like Asetek could come up with a fix if its such a common problem? Thanks for the reply.

Ssilencer
10-10-2006, 02:20 AM
I'm not Asetek, I don't know why they didn't fix that yet.
The problem looks like to be the delay between restart on the asus boards and the impossibility to the chillcontroll to understand that behavior, using a separate psu the chillcontrol will not detect that restart (and also will not detect a failure in your system if happens)

girth_maul
10-10-2006, 05:34 AM
@Tutto - I saw your post on the asetek forum, lets hope they listen!

You could see if someone here could mod your unit with a custom controller, but i guess after spending all the money you'd want it to do it out of the box?

rapty
10-10-2006, 06:00 AM
They have Fixed the problem

Version 3.22 CC board

I had the problem a while back after expalaning the Problem to Asetek they released a new revision which has Ironed out the Boot Problem with the USB Dongle

In the meentime Take the USB dongle off the CC Board Start the Unit up the System should post then Plug the USB dongle back in.

It's to do with a crappy startup system with the earlier boards

You have a PM

Durzel
10-10-2006, 07:43 AM
They have Fixed the problem

Version 3.22 CC board

I had the problem a while back after expalaning the Problem to Asetek they released a new revision which has Ironed out the Boot Problem with the USB Dongle

In the meentime Take the USB dongle off the CC Board Start the Unit up the System should post then Plug the USB dongle back in.

It's to do with a crappy startup system with the earlier boards

You have a PMSorry I'm confused by this...

What does the "USB dongle" have to do with the motherboard powering down? I've not even had the USB dongle plugged in and the Vapo still shuts down once it detects the motherboard has switched off.. I don't know if it does it when it detects the Molex connector is not powered, or if its the 2-wire cable that goes from the CC to the PWR-SW on motherboard (feedback?).

Either way, I don't think the 4-pin USB connector that goes in the motherboard has anything to do with the Vapo staying on. :confused:

dominick32
10-10-2006, 09:36 AM
The only easy solution to this is this without the upgraded chillcontrol board (or firmware):
1. Pick up a cheap secondary PSU
2. Plug in the AUX 12v connector on the chill control and the Vapo main power into this spare secondary PSU
3. You are going to need to jump power to the chillcontrol unit by CROSSING/SHORTING the POWER SW pins on the chillcontrol board. I have created a custom button with some wire and a push button from home depot.
4. Make sure the USB connection is made from the chillcontrol unit to the motherboard for proper heating element and temperature control.

Unfortunately that is the only way to ensure 24/7 operation right now unless you bypass the chill control completely which is not recommended.

Hope this helps.

Tutto
10-18-2006, 10:03 AM
I contacted Asetek by way of creating a service ticket and then sending an email directly. As hard as it is for me to believe, this is the reply I got:

Hi Bob,

No, we are not working on a fix, the problem only occurs on ASUS, and it has to to with the way they change the frequency.

Try asking in our user forum, if anybody has a workaround for it.

Best regards,
Jesper D. Jensen
Customer Service Assistent


I was shocked by this reply. Obviously they could care less!

pazza316
10-18-2006, 03:49 PM
Get one of the custom builders to put a Froster XE in!!! That solves it hey Mr S!

Tutto
10-18-2006, 04:16 PM
Who exactly should I contact? Do you know the approximate cost? Thx

pazza316
10-18-2006, 04:28 PM
It depends on your location mate. If your in Europe either myself or Johann amongst others. In the US Chilly1 or Jinu ampngst others. Argentina SSilencer just PM one of us and we cans ort you out.

I cant talk cost on here that would be have to be done through PM.

MrDeeds
10-18-2006, 08:35 PM
I was shocked by this reply. Obviously they could care less!

It really isnt their fault that this happens. They should however have a delay built in to make sure that the vapo stays on even during a short cold boot. 3-5 secs should do.

But hey its a known problem, also the reason i didnt go with an asus board this time around. Hopefully they are going to start going a different route on future boards.

Tutto
10-18-2006, 08:39 PM
Do you know if the Asus 965 chip boards have the same problem. I also have a P5WDG2 WSPRO and it does have. What board did you decide on? Thx

MrDeeds
10-18-2006, 10:17 PM
Do you know if the Asus 965 chip boards have the same problem. I also have a P5WDG2 WSPRO and it does have. What board did you decide on? Thx

I went with an Abit AW9D-Max.

Some have reported that the P5b deluxe with the latest bios update doesnt cold boot. You should check out the intel forums for more info.

Nosfer@tu
10-19-2006, 06:05 AM
Asetek really dosent care :banana::banana::banana::banana: about thire customers.

The also sold defect reversion of the S775 kit for a 100 £ and never told users that it had a flaw.

I almost lost a cpu and motherboard because of that!

So to solv the problem we have to disconnect the usb cord and reconnect it when in windows?

Damm :/

maybe and off/ on button would do??

runmc
10-20-2006, 03:47 AM
I have just finished putting a new compressor in a Vapo LS for one of the guys here on the forums. He didn't send me the USB connector when he sent the Vapo, so all I had connected to the ChillControl that was also connected to the Asus motherboard was the PSU molex plug. During testing of the Vapo LS (overclocking) everytime I reset the motherboard, the Vapo shut off.

This problem with Asus is not only bad for compressors, but is also hard on hard drives.
You need a second PSU to work around this problem to keep the compressor from shutting down.

Master_G
10-20-2006, 08:32 AM
Asetek have since said that they are working on a solution, no release date as yet, but hopefully should be soon.

G

Nosfer@tu
10-20-2006, 08:38 AM
Master G.

Maybe they are maybe they are not.

I dont trust them over a dor step.
An official reply form them wouldent enven help.

I trust #9 more than you :) Even thoug I know you are a moderator on the fora.

When I got my LS, the chill controlle dident even work, you couldent connect to it. The usb software/hardware was so porly build that it was only until 260 fsb you got contact 1 out of 10 times.

It took them over 9 Months to fix that issue, And they dident do a recall, they only offer it to those that Complain!

Master_G
10-21-2006, 04:48 AM
I'm just trying to relay information to help people out, Asetek posted on their forums saying that they would, and so i posted here saying that so people are aware of the fact, despite what they previously said.
I would link to the thread but the Asetek forums seem to be down for me atm.

G

Gray Mole
10-21-2006, 05:17 AM
If Asetek say they are working on a fix then they are.

I don't agree with the non-implementation of a firmware upgrade by the end user, but considering that the Prometeia firware that was meant to fix the issue hasn't, I can't really say it would be any better if they did :rolleyes:

The fact that both Unseen's and Ssilencer's controllers have already dealt with it really shows that they are FAR more in tune with the needs of the overclockers out there. It also shows that a small company can move much more quickly to improve their product, a lesson that the bigger companies should learn :D

Asetek has had some weak moments in their service, but I have dealt with them time and again and they've ALWAYS come through for me so I'm inclined to trust that while a little slow (and whether Prommie or Vapo) they will get it done when they can.

Besides, Master G has always done his best to relay the most accurate info he can get form Asetek :toast: and I trust his word more than most :fact:


Cheers

Gray

PS. And besides, this really isn't the fault of either Vapo or Prommie, it's the absolutely idiotically implemented Bios boot setup that Asus is using. I mean really, it's almost like one of their programmers decided he didn't like phase change, and made sure that the system would do as much damage as he could :rolleyes: (kidding, but you know what I mean)

elsupremo
10-29-2006, 12:10 PM
So, on the P5W DH DLX with the newest 1407 Bios, is this still an issue?

Tutto
10-29-2006, 02:35 PM
Yes, but the 1503 solves the problem

elsupremo
10-29-2006, 03:33 PM
Thanks Tutto, good to know :D

Tutto
10-31-2006, 04:11 AM
I have noticed a new problem when I change the multiplier, either up or down, in that it won't restart sometimes so I went back to default. At 4.26GHz, my SuperPI 32M is a little over 14 min and I thought I needed to raise the FSB to improve it.