e8400 E0 stuck temp sensor?

[Interitus]

I've read boatloads of posts, articles and reviews on the e8400 and all the usual problems with them. I just recently fired mine up in an Abit IP35 Pro and I appear to have one of the stuck temp sensors or a BIOS that won't properly report temps. I am running the BIOS that came with the board since I haven't had any problems. I haven't counted that out as a potential reason for the temp issue. RealTemp and Coretemp both show idle of 47C. After running Orthos for 20 mins, temp does not change at all. Nothing I have done changes the 47C reading, it has never showed up even 1C off of 47C.

Just a few questions that I couldn't seem to find a definite answer to while googling and looking here...

The IP35 Pro is running BIOS 6.00PG according to CPU-Z 1.50. Would updating the BIOS help the stuck temp readings? I wasn't even sure the e8400 would run properly on this BIOS, but it's chugging along just fine.

Most of what I read indicated that the temp sensor could be stuck permanently, but I have read that lower than normal temperatures could cause the temp to lock at a fixed number until temps rise above where that lock occurs. It's admittedly cold in my office right now. I have a Zalman ZM-MFC2 fan control with the probes set up to take intake airflow readings from the vital parts like the HDD area, PSU, GPU etc.. The probes read 21-23C over the last few days. Could this low temperature be causing the sensor to lock up?

Some pertinent info:

Cooling: Thermalright Ultra Extreme w/ Ceramique, 120mm Yate Loon DM12-SM fan @ 1k RPM
Case: P182, 5 total of the same YL fan, all at 1k RPM, cables are tidy so really good airflow

 

[ch33zw1z]

I'm running almost the exact same setup: TRUE, P182, low rpm cpu fan, and an E8400 E0, all on a P5K vanilla. My sensors are stuck @ 40C, they never change (never go below 40C) until about 10 minutes into Linpack (give that a shot, and use the Linx gui for ease) they hang out at about 44C, and never go above 47C. I recommend using Linpack, Orthos doesn't touch my cpu comparatively...and P95 does a little better.

I would be concerned if under load from linpack you didn't see a temp increase. may need to reseat the HS.

 

[crazylegs]

Hi, i had a similar bot not identicle problem when setting up my E0 stepping E8400 in an Abit IP35 Pro XE.

However my problem was uGuru bugging and sayign my temp was always 103oC :S While CoreTemp would correctly (i hope) have temps @ 36 idle and 51 load.

Flashing my BIOS to the latest (v11) did not help, then lots of googling and i found a tweaked version of the v11 bios (think from some nice Abit ppl in Holland!)

Anyway... long story short:

Yes flash your BIOS to latest available for your board - the new (i.e E0 stepping) E8400 does have some copatibility problems with the Abit IP35 Pro series MB's

Gl

 

[BonzaiDuck]

I must have posted remarks tangent to this issue three times today. For that, I've been too much the busybody, and other members have been kind not to say it. But these complaints and worries have appeared in a litany of threads going back to early last year.

So . . . . ditto to this experience with my E8600. It also seems to occur in some Q9x50 CPUs. Both my cores are stuck at 51C, and show rising temperatures as the tCase sensor reports values approaching 51.

The best you can do, I think, is upgrade the BIOS as already recommended. I'm skeptical about either the usefulness or certainty of RMA'ing the processor. Intel disclaims any accuracy for idle temperatures on these Penryn-based processors.

If the tCase sensor seems to be working properly, you can still evaluate thermal performance against the spec -- which references tCase and not the core sensors.

 

[Interitus]

Well I upgraded to BIOS 17 and temp sensor is still stuck. Kinda disappointing. I really wanted to OC this CPU to around 4ghz but I'm kind of skeptical to do that with no ability to even semi-accurately read temps from the CPU. I might just give the bus a bump to 400mhz for 3.6 since I have DDR2-800 sticks and run 3.6 at 1:1. Shoulda done my homework I guess At least I'll get a decent performance boost over the old e6420.

Thanks to everyone for their info.

 

[Interitus]

Update: Success!

As a last ditch effort, I ran Orthos large FFT's, sealed up the case and dumped the fans down to around 750rpm's. I watched my 8800GTS go from 52C up to 63C and just waited and waited and waited. Still no change...so I tried one last thing...

After running Orthos with the case sealed and the fans at 750rpm, I took a hairdryer on high and hot and aimed it towards the case intake. About 45 seconds of this and the sensor moved...it spiked at 52C for each core and increased smoothly over the 45 second period.

Wow I feel better now. I especially feel good since it took dumping fans down 500rpm and a hairdryer just to hit 50C at load LOL.

I guess I'll be doing that OC after all

 

[BonzaiDuck]

Originally posted by: Interitus
Update: Success!

As a last ditch effort, I ran Orthos large FFT's, sealed up the case and dumped the fans down to around 750rpm's. I watched my 8800GTS go from 52C up to 63C and just waited and waited and waited. Still no change...so I tried one last thing...

After running Orthos with the case sealed and the fans at 750rpm, I took a hairdryer on high and hot and aimed it towards the case intake. About 45 seconds of this and the sensor moved...it spiked at 52C for each core and increased smoothly over the 45 second period.

Wow I feel better now. I especially feel good since it took dumping fans down 500rpm and a hairdryer just to hit 50C at load LOL.

I guess I'll be doing that OC after all

Have you verified that your tCase sensor works properly? My E8600 tCase sensor seems to follow a normal range from idle to load. As I said earlier, the thermal spec is defined in terms of tCase.

The residual frustration arises from the fact that my core temperatures -- stuck at 51C -- rise with Linpack testing. But they lag behind tCase by 1C degree, when they should be 5C or 10C higher.

 

[Interitus]

I haven't actually verified that the tCase sensor is accurate yet. I was just lost in the moment when I saw RealTemp register something other than 47C. That will be my next step. The fact that it doesn't just stay put at 47C no matter what happens is encouraging.

When I get time I'll see if I can get some readings and either figure out how much the sensor is off or come up with some type of relationship between readings so that I can at least form some sort of working compensated measurement.

 

[BonzaiDuck]

Originally posted by: Interitus
I haven't actually verified that the tCase sensor is accurate yet. I was just lost in the moment when I saw RealTemp register something other than 47C. That will be my next step. The fact that it doesn't just stay put at 47C no matter what happens is encouraging.

When I get time I'll see if I can get some readings and either figure out how much the sensor is off or come up with some type of relationship between readings so that I can at least form some sort of working compensated measurement.

Everest Ultimate, licensed or free-trial version, reads tCase. Fact is, I'm peeved that nVidia Monitor no longer shows tCase, when the earlier version did, and Intel still gives its thermal spec relative to tCase. Also, CPUID's HWMonitor also shows tCase.

I can't explain why the core temperatures became the "ultimate guideline" for cooling as the dual-cores came on the market, since tCase is the basis for the thermal spec. In any event, tCase should lag behind the average core temperature by some 5 to 10C.

Ultimately, with some limited faith in the reliability of that one sensor, you can temper your over-clock efforts to vCore voltages within the Intel "safe-range" spec, and feel pretty safe if the over-clock is around 25 to 30%. That is -- provided you are using a better cooling solution than the stock Intel cooler.

 

[Interitus]

I'll give Everest a shot. My main concern is that I'll have to do it by a less convenient method since the BIOS still reads 127C for the CPU. I've got a feeling that the Tcase reading from Everest won't be even remotely accurate. My parents are both electronic engineers, guess now would be a good time to feed off of their toolbox, lol.

-edit-

I should be good on cooling, running a TRUE in a P182 so plenty of airflow and heatsink power. I also planned on at least a 3.6ghz OC, but hey if 4 is there I'll take it

 

[thefoodaddy]

Originally posted by: crazylegs
Hi, i had a similar bot not identicle problem when setting up my E0 stepping E8400 in an Abit IP35 Pro XE.

However my problem was uGuru bugging and sayign my temp was always 103oC :S While CoreTemp would correctly (i hope) have temps @ 36 idle and 51 load.

Flashing my BIOS to the latest (v11) did not help, then lots of googling and i found a tweaked version of the v11 bios (think from some nice Abit ppl in Holland!)

Anyway... long story short:

Yes flash your BIOS to latest available for your board - the new (i.e E0 stepping) E8400 does have some copatibility problems with the Abit IP35 Pro series MB's

Gl

Exact same problem with my IP35 Pro and a Q9550. I get the temperature alarm, but if I silence it, the computer acts totally normal. I let an X264 encode run, and sometime during the night, the machine bluescreened. So it looks like it's back to the ol Q6600 for me unless Abit gets back to me with a solution! I'm not holding out hope, though.

 

[kpo6969]

You could try running a sensor test with RealTemp. Prime95 also is required.

http://i239.photobucket.com/al...eTemp284SensorTest.jpg