Strange overheating after hibernate

[lgrenie]

Hi,

I have a computer with watercooling. The water cools the CPU and my Nvidia chip (not its memory). Right now the CPU is overclocked and the GPU is underclocked. The CPU idle temperature is usually 37ºC/99ºF. When I use the Hibernate function of Win XP to shutdown and restart, the idle temp goes up to 45ºC/113ºF (even after several hours). Since the CPU is idle, I think the overheating comes from the graphic chip. I've so far tried several things: I've changed back and forth the freq. of the GPU using Rivatuner, reloaded the graphics driver, use several versions of Nvidia driver. The temperatures remain the same: 37/99 idle before Hibernate, 45/113 after. As a side note: I've run nature test from 3DMark'01 and it's the same before and after hibernate (which could mean after all that the problem is not graphic chip related). Anybody has any idea ?

Thank you,

SurJector

 

[RCPilot]

No expert here, but I'd guess that the water isn't circulating in hibernation. At least that's where I'd start looking myself.

If it ain't broke, take it apart & see why not!

 

[Lonemagi]

Doesnt hibernation shut your computer off? or are you going into sleep mode?

<font color=red>*</font color=red><font color=white>*</font color=white><font color=blue>*</font color=blue>
... And I'm proud to be an American, where at least I know I'm free, and I won't forget the men who died, who gave that right to me.

 

[lhgpoobaa]

Uh... hibernate mode is supposed to save the system state to the hard drive then shut everything down... u sure u are hibernating or just on standby mode?

<b>Damn War! I'm too young to watch other people die!</b>
<A HREF="http://members.iinet.net.au/~lhgpoobaa/images" target="_new">My Images!</A>

 

[lgrenie]

To reply to all three of you together:

- Hibernate is an ``educated shutdown'': the computer is shut down (I can, and often do, unplug it from the wall socket) but Windows takes notes of the programs and the driver running and saves their state. That way the boot is faster and the programs you were using are retarted as they were. During that state the computer is off, so that the water cooling, as the processor, hard disks, graphic, memory and everything else is stopped.

- The overheating is stable: all temperatures I give are measured after the computer has been idle for several hours. It is not just a transient problem due to boot up/resume. Worse: when I do a warm reboot, the temperatures go down from (roughly) 41/106 to 37/99. When I do a resume from Hibernate (without leaving enough time for the processor to cool to ambient temp 21/70), the temperatures go up from 41/106 to 45/113. (Note: the BIOS is full of busy looping, so that the CPU heats a little during a warm reboot because it is already warm and the busy looping heats it quite a bit).

- As you can guess I already have tested with and without unplugging the computer between Hibernate and Restore: the overheating is still there.

Thank you for any help,

SurJector

 

[RCPilot]

Well to me it sounds like it heats up until the water starts circulating again. I'm no water cooling expert by any means, but I though with water you have to wait for the water pump to come up before you light up the CPU.

Just trying to help out, but this is all the stuff I would consider if it was my rig. I won't post again but will follow the thread to see what happens.

Hibernation & sleep modes have caused some problems for others around here. Personally I don't mess with either of them. With CPU's as fast as they are the boot is way fast already. My 2400 boots in less than 30 sec.'s. My old 1 gig T-bird boots in less than 1 minute. I don't need it to boot any faster myself. You can't even read the post screens on the 2400 when it boots as it is.

Actually when you get right down to it, my monitor takes at least 20 sec.'s to come awake. When it lights up I'm at the Windows Welcome screen. Before the colors even come in I'm on the desk top already. Any faster boot & my monitor wouldn't even be lit up & I'd be in Windows already. It really is a pain in a way. If I want to get into BIOS. I have to boot to get the monitor lit up, then restart to get into BIOS so that I can at least see when to hit Del. to get there.

If it ain't broke, take it apart & see why not!

 

[lgrenie]

> Well to me it sounds like it heats up until the water starts
> circulating again. I'm no water cooling expert by any means,
> but I though with water you have to wait for the water pump
> to come up before you light up the CPU.

Actually you don't have to wait until the water starts: it's perfectly fine if the pumps and and CPU start together. If you had to wait for the pumps, the CPU would cool down after a while but instead it does not cool down. It remains at 45/113 until I shut it down, even after several hours. A little example: it happened once that one of the hoses was angled too much and water could hardly circulate; it took around one hour to reach 60ºC/140ºF that shut down the computer.

> Hibernation & sleep modes have caused some problems for
> others around here. Personally I don't mess with either of
> them. With CPU's as fast as they are the boot is way fast
> already. My 2400 boots in less than 30 sec.'s. My old 1 gig
> T-bird boots in less than 1 minute. I don't need it to boot
> any faster myself. You can't even read the post screens on
> the 2400 when it boots as it is.

Unfortunately there is (at least) one driver that slows the boot and slows far less the resume from hibernate. I suspect (without proof) the Promise driver. So far, I use std reboot, but it would be better if I could use the hibernate func.

> Actually when you get right down to it, my monitor takes at
> least 20 sec.'s to come awake. When it lights up I'm at the
> Windows Welcome screen. Before the colors even come in I'm on
> the desk top already. Any faster boot & my monitor wouldn't
> even be lit up & I'd be in Windows already. It really is a
> pain in a way. If I want to get into BIOS. I have to boot to
> get the monitor lit up, then restart to get into BIOS so that
> I can at least see when to hit Del. to get there.

You can also press [Del] (or whatever) key blindly, it works for me (if you have an ASUS board, you can also stop the computer whil it boots and restart it, it goes straight to BIOS setup).

SurJector

 

[RCPilot]

You can also press [Del] (or whatever) key blindly, it works for me (if you have an ASUS board, you can also stop the computer while it boots and restart it, it goes straight to BIOS setup).

I do own a ASUS board & have done that as well. Another thing is you can press Pause on the keyboard to read the post screens as well. It will stop it on that screen.

I'm also running the Promise controller myself & it doesn't seem to hold up the boot at all. Maybe you need to try & reinstall the driver?

One thing that really did slow down the boot on my machine was the RAID controller that's on board. I took that out of the boot seq. in BIOS so it wouldn't look for it on post & give me a message something like "Nothing on the FasTrack controller BIOS not loaded". Once I got that figured out the boot took off like gang busters.

I don't know, just trying to be helpful is all.


If it ain't broke, take it apart & see why not!

 

[LtBlue14]

nothing i can think of would cause a problem like that except a broken sensor
maybe when you come out of hibernate, whatever software is behind the sensor doesn't resume correctly and gives false readings. just a guess, because nothing else makes sense

<A HREF="http://www.tweaktown.com/document.php?dType=guide&dId=120&dPage=1" target="_new">WinXP tweak guide</A>
<A HREF="http://www.tweaktown.com/document.php?dType=guide&dId=145&dPage=1" target="_new">WinXP tweak guide 2</A>

 

[lgrenie]

> nothing i can think of would cause a problem like that except a broken sensor
> maybe when you come out of hibernate, whatever software is behind the sensor
> doesn't resume correctly and gives false readings. just a guess, because nothing else makes sense

That would be a nice idea, but unfortunately this is not it: my case is a Koolance and gives the temperature of the water on the front. After resume the water is definitely warmer (and the fans spin faster as well). I agree with you: it does not make sense (that's why I asked for help in the first place).

SurJector

 

[svol]

The only thing I can think of at the moment is that after you shut down the PC the water heats up because of the remaining heat. But even then I don't suspect water temps to increase like this.

You're sure that when the PC is off the pump stops running... pumps also create heat and I found that after running a test-setup for my watercooler (pump only heat source) the water started to heat up after some time. My pump creates 25W of heat when running and if the radiator fan is off then the water will slowly start to heat up.

My dual-PSU PC is so powerfull that the neighbourhood dims when I turn it on 😱

 

[mrwhipper]

I have a Koolance 601 case also.. The temps are not measured for the water. There is a sensor that is mounted in the CPU side of the CPU water block. I can't help more.. Sorry.. I don't use the hibernation. The only thing that I can figure is that the pumps slow down or shutting downin hiber mode. I can let my 2700+ on an Asus A7N8X Del, sit idle all day and the water block temp never exceeds 85F and the CPU(using MBM5) never exceeds 94F. I would give Koolance a call. They are great to deal with. I'm shure that they can help you. Good luck.. If you call post the responce. Take care.

They are our, fathers, mothers, brothers, sisters, sons, daughters, friends, neighbors. They are OUR TROOPS! Please support them.

 

[lgrenie]

Found it !!

My CPU is an Athlon and my motherboard is an ASUS, the chipset
is not configured to disconnect when the CPU is idle. When I
do a normal boot, using WPCRSET I configure the chipset to
disconnect (set high order bit of byte 0x92 to 1) at each boot
(but not at each Resume From Hibernate). Believe it or not,
putting this bit to 1 effectively lowers temperature !

Now I have to find how to execute a program at each resume.
But I think I can handle it.

Thank you for your help,

Loïc

 

[svol]

With a little researching you should be able to change the BIOS to automatically set the bit to 1 at start-up.

My dual-PSU PC is so powerfull that the neighbourhood dims when I turn it on 😱

 

[lgrenie]

> With a little researching you should be able to change the
> BIOS to automatically set the bit to 1 at start-up.

That could be an idea. That should be even easy. Thank you
for the suggestion.

SurJector