Normal Temperature for a P4 2.6 ghz

[JamminJimmy]

Can someone tell me the normal temperature for a non overclocked 2.6 ghz P4? I'm getting a reading of 140 F. which seems kind of high. My temperature sensor is taped to the bottom of the heatsink as close to the actual CPU as I could get.

 

[neutralizer]

Too lazy to convert, but what is it in C?

And what hsf? Stock?

 

[pcman83]

I would seriously shut down and check that heatsink. I have a 3ghz and it runs at like 105. So you should check your thermal paste, the fan, and the connection between the die and the p4. Also see if you have a motherboard monitor that will give you a different temp.

 

[waylman]

yeah, thats a bit toasty. I dont run Pentium but my 2500+ runs around 118F/48C with stock heatsink and fan

 

[apoppin]

Normal - Under Load or idle?

My 2.80c normally runs in the hi30s/low40s (it is O/C'd ~3.4Ghz @ default voltage) and then into the low 50s when under max usage.

(EDIT: I only use my sensor to record case temp; my CPU temps come from monitoring in BIOS/software - Abit Ic7)

 

[JamminJimmy]

I've been mainly using the computer for games so I guess that's a load temp. It's been very stable, although I just built it yesterday and I've only used it for about 3 hours. It's got a stock fan that came with the CPU. I'm wondering if maybe my temperature sensor got caught between my heatsink and the CPU. That's a good idea to check the temp in the BIOS. I'll do that when I get home tonight, thanks.

 

[apoppin]

I was also concerned about placement, so I didn't use my temp sensor for anything but case temp. ANY gap between HS and CPU would be bad.

I'd say 140F under load is fine . . . doesn't Intel quote ~80*C as Max?

 

[pcman83]

140 is to hot, and it cant be good there is something wrong. But it could just be the temp sensor

 

[apoppin]

Originally posted by: pcman83
140 is to hot, and it cant be good there is something wrong. But it could just be the temp sensor

60C is too hot? Under load?

I'd say it is a bit high - too high it it is an "average, but not "peak"- still well within Intel specs . . . I also doubt that the "sensor" is terribly accurate since it can only sit NEXT to the CPU('s edge) and not BETWEEN it and the HS (IF it IS between, then it's probably the CAUSE of the overheating on such a tiny die area).

Check the reading in BIOS (install MotherBoard Monitor so you can monitor it in Windows) . . . and let us know . . .

finally, when you get your temps "settled", try raising the FSB (without raising the v-core) . . . "free" performance is always nice.

 

[JamminJimmy]

Motherboard Monitor? Where do I get that from? Did that come on the CD that came with the motherboard? Or do you download that from somewhere?

 

[apoppin]

There is probably some kind of Hardware monitoring on your MB CD . . .

Get MB monitor here

 

[kamper]

Originally posted by: apoppin

Originally posted by: pcman83
140 is to hot, and it cant be good there is something wrong. But it could just be the temp sensor

60C is too hot? Under load?

I'd say it is a bit high - too high it it is an "average, but not "peak"- still well within Intel specs . . . I also doubt that the "sensor" is terribly accurate since it can only sit NEXT to the CPU('s edge) and not BETWEEN it and the HS (IF it IS between, then it's probably the CAUSE of the overheating on such a tiny die area).

Check the reading in BIOS (install MotherBoard Monitor so you can monitor it in Windows) . . . and let us know . . .

finally, when you get your temps "settled", try raising the FSB (without raising the v-core) . . . "free" performance is always nice.

60c maybe isn't too hot, but it's far hotter than it should be. Gaming will probably not push the thing to it's top temp (try seti and/or prime95 for that) so I'll bet given his current setup he could get it hotter (which would be too hot). That thing should idle no higher than 35 with proper installation and good thermal paste. Word on the moboMonitor , I'd also say take that sensor out, clean everything off nicely and reseat with some arctic silver. Jimmy, I have the same motherboard, AsusProbe on the drivers cd should also give you temps.

apoppin: Nice oc What hsf are you using? I've got a 2.8 and can't reliably push it past 3.2 or so (with stock cooling).

 

[Corporate Thug]

meh, i'm lazy and havent order intake fans so my CPU (2.8C) idles at 45-50C to gets to 60-62C under load and it is ROCK STABLE
so i dont really care

 

[InlineFive]

That's pretty toasty. My Barton 3200+ runs at around 43c load.

 

[nitromullet]

Originally posted by: JamminJimmy
I've been mainly using the computer for games so I guess that's a load temp. It's been very stable, although I just built it yesterday and I've only used it for about 3 hours. It's got a stock fan that came with the CPU. I'm wondering if maybe my temperature sensor got caught between my heatsink and the CPU. That's a good idea to check the temp in the BIOS. I'll do that when I get home tonight, thanks.

As others have posted, check the temps in the motherboard BIOS. These temps are quite high, but I also think the thermal pad does require some burn in time during which you will see abnormally high temps. Anyone know anything about this?

 

[Rhombuss]

Ideally, the P4Cs should be kept under 60 degrees celsius at idle. I know my Abit IC7 has a little funky temperature monitor discrepancy as do many of them, but I'm unsure of your Asus board.

 

[NokiaDude]

My AMD Barton 2500+ runs 35C on air.

 

[redass1876]

i have 3.0 E and runs 95 F or 35 C with stock HSF

 

[apoppin]

Originally posted by: kamper

Originally posted by: apoppin

Originally posted by: pcman83
140 is to hot, and it cant be good there is something wrong. But it could just be the temp sensor

60C is too hot? Under load?

I'd say it is a bit high - too high it it is an "average, but not "peak"- still well within Intel specs . . . I also doubt that the "sensor" is terribly accurate since it can only sit NEXT to the CPU('s edge) and not BETWEEN it and the HS (IF it IS between, then it's probably the CAUSE of the overheating on such a tiny die area).

Check the reading in BIOS (install MotherBoard Monitor so you can monitor it in Windows) . . . and let us know . . .

finally, when you get your temps "settled", try raising the FSB (without raising the v-core) . . . "free" performance is always nice.

60c maybe isn't too hot, but it's far hotter than it should be. Gaming will probably not push the thing to it's top temp (try seti and/or prime95 for that) so I'll bet given his current setup he could get it hotter (which would be too hot). That thing should idle no higher than 35 with proper installation and good thermal paste. Word on the moboMonitor , I'd also say take that sensor out, clean everything off nicely and reseat with some arctic silver. Jimmy, I have the same motherboard, AsusProbe on the drivers cd should also give you temps.

apoppin: Nice oc What hsf are you using? I've got a 2.8 and can't reliably push it past 3.2 or so (with stock cooling).

My O/C is with the retail Intel HS/Fan . . . I am still "playin'" with it as my rig is only a few weeks old. To get it completely (rock solid) stable @3.4(+)Ghz., I need to add extra voltage . . . since I am a wuss and afraid to damage my CPU, I run it completely at default voltage (probably a bit undervolted with my Abit Ic7) and regularly at 3.31ghz . . . the "serious" o/c will come later, when my system is lagging and I need those Xtra FPS . . .

I also agree that 60C is too hot for a regular non o/c'd running temp for a Northwood (a Prescott is a hot running beastie) - but nothing to be afraid of at "peak" . . .

 

[JamminJimmy]

After much investigating it turns out I guess I was reading the wrong Thermaltake temp gage. The 140 represents when the alarm will sound. Under the 140 there was another temperature reporting which was 102. The BIOS reported 99.5 under load, 80 idle. The thing I don't understand is since the 140 is the alarm why does it change like as if it were sensing the temperature of some hardware device. One second it reports 140.1 and 5 seconds later it reports 140.5

 

[Joemonkey]

Originally posted by: JamminJimmy
After much investigating it turns out I guess I was reading the wrong Thermaltake temp gage. The 140 represents when the alarm will sound. Under the 140 there was another temperature reporting which was 102. The BIOS reported 99.5 under load, 80 idle. The thing I don't understand is since the 140 is the alarm why does it change like as if it were sensing the temperature of some hardware device. One second it reports 140.1 and 5 seconds later it reports 140.5

the alarm is probably based on the case temperature as well. If your CPU is running at 140 while the case is at 120, that wouldn't be a reason to alarm, but if the case is at 70, then the CPU being at 140 would be cause for alarm. the alarm is probably going up and down based on fluctuations in the case temp