v3.0 CLI running my CPU hotter than 2.4 CLI?

[poopaskoopa]

It's too early to tell, but I think my CPU is running hotter than it did when it was running 2.4. I used to run 2.4 on my PC(specs below):

c2 566@901(1.75)
golden orb(4800~4900rpm)
abit bf6
pc100 128mb 2-2-2

I've been looking at Abit's winbond HW doctor to monitor the CPU temp. When I was running 2.4, the case temp used to be between 23.5~25.0 Celsius, and CPU temp would fluctuate between 37~45 Celsius.
Now, I'm running v3.0 CLI, and my case temp is between 21~23(it's gotten really cold in my apt), and my CPU temp fluctuates between 35~48. I don't know how reliable Winbond is any more, but just by staring at the app for the last 5 minutes, I can tell that it thinks the CPU is generally running hotter(only if slightly). Since the ambient temp of the case is 2 full celsius degrees lower, I had expected the CPU to operate at a lower temp on average, assuming that v3.0 CLI pushes the CPU as hard as v2.4 CLI.

I run win2k/98 on my machine, and I had been running my PC on 98 for the past 7 days without rebooting, until today. In the last 2 hours that I've been running v3.0 CLI, my PC has hard locked twice, acting like it's overheating. I would hate to sacrifice the speed for stability and lower temp, for that would be un-overclocker like thing to do.

Does anyone else think v3.0 runs hotter? or should I check my HS/F and thermal paste. Well, i suppose it's always wise to do that.

 

[Assimilator1]

I'll let you know when I eventually get hold of of V3 CLi (server is down atm).
My mobo uses the thermal diode in the cpu to measure its temp so it'll show higher temps than an external sensor like yours has (I think!)
eg running SETI CLi v2.4 now ,case temp 28C ,cpu temp 43C.

I would think it unlikley that the newer version would run it hotter as the older version took ALL spare cpu cycles anyway.

Anyone else?

 

[blade47]

I would think the new client would run the cpu hotter. v2.4 was severly limited by the amount of cache where as v3.0 is more dependant on cpu speed. This should allow the cpu to crunch alot more data. If you compare the mflops/sec v3.0 is running alot more than 2.4 did. I don't know I'm just guessing at all this crap.

BTW Assim1 if you need v3.0cli I'll be happy to email it to you.

 

[cory]

i would not worry to much about that temp range.
( i have overclocked a bunch of pent III's and the
can run as low as 34 but as high as 50 and still be stable)

and i have many pent III's running at 150mhz bus
that are 100mhz cpu's

the one i am on now is a pent III 650 running at 800mhz
at is running about 38 C and has been on for more than
a month solid.

 

[Orange Kid]

Seti 3.0 command line client

Assimilator1;
Use the above link

 

[Assimilator1]

Blade 47

You have a point about 'extra' cpu load but I just don't see any signs of it here ,I'm now running V3 CLi (thanks OBfor sending it via ICQ) ,current case temp is 29C ,cpu temp is 44C ,same correlation.


BTW guys when talking about cpu temps you need to mention how your board measures it ,external cpu sensors ,especially ones mounted on the board(like many older m/brds)give much lower readings than thermal diode sensors in the cpu do.
Also the bios revision can effect the cpu temp reading ,I have seen differences as big as 6c on my Soyo 6BA+III mobo

Orange Kid

Thanks for the link ,but I'm afraid I've got it now ,sorry ,I'm sure others will find it useful ,why not post a new thread with your link in it?

 

[poopaskoopa]

I have been told that, for my setup(abit bf6/slotket/c2 566), the winbond chip on the motherboard reads the built-in thermal diode on the celeron.

 

[office boy]

This is one of the problems that came out during beta testing, and it is just what blade_47 said.

 

[Assimilator1]

I guess my cooling then is just too good to show it

poopaskoopa

48C is nothing to worry about

 

[poopaskoopa]

Hopefully, after I get a water cooling system going(maybe in 2 weeks) I won't have to worry about 48C or 4.8C. I hope to double my 566 to 1.132Ghz.