revelation
New Member
I'm running a core 2 duo e8500 and using realtemp I found that core 0's temp sensor was stuck. it would only read at 27 degrees. core 1's sensor wasn't stuck but read at about the same temperature anyway so i figured I was safe. After all I'm using a case with 2x230mm intakes(front&side), 1x230 exhaust(top) and 1x120 exhaust(rear). This thing moves air like crazy, and my computer room is quite cold. 10-15 celsius(50-60 fahrenheit)
Now when i use realtemp both sensors have a movement of 9-11 while it says typical movement is 3-15 so I guess it managed to, somehow, unstick itself. The problem is, now it says i'm idling at 58-65 and getting up into the upper 70's during gameplay. Is this just a messed up temp sensor or is it really running that hot and i didn't know it because it was stuck before?
I do plan on reseating the cooler. it's a zalman9500. No overclocking done except to bring it up to stock specs. was a wrong multiplier and mhz when installed.it was 8x and 333 instead of 8.5 and 372.
Also, the thermal paste i used was AS5, but it was the extra in the tube from an old build. probably 9months before my build. It was still liquid and normal looking but could that be the problem anyway?
Now when i use realtemp both sensors have a movement of 9-11 while it says typical movement is 3-15 so I guess it managed to, somehow, unstick itself. The problem is, now it says i'm idling at 58-65 and getting up into the upper 70's during gameplay. Is this just a messed up temp sensor or is it really running that hot and i didn't know it because it was stuck before?
I do plan on reseating the cooler. it's a zalman9500. No overclocking done except to bring it up to stock specs. was a wrong multiplier and mhz when installed.it was 8x and 333 instead of 8.5 and 372.
Also, the thermal paste i used was AS5, but it was the extra in the tube from an old build. probably 9months before my build. It was still liquid and normal looking but could that be the problem anyway?
Last edited:
