• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Temp at first boot (E660 w/ Tuniq)

Hi all,

I just finished assembling my new "dream" computer. At it's core is an E6600 with a Tuniq Tower attached (which was quite a feat to install.) The MoBo is an EVGA nForce 680i and the case is a Silverstone TJ-09 (w/ no additional fans added.) This is an SLI machine w/ two 8800 GTXs.


On first boot, I'm reading a 35C temp for the CPU, and a 33C temp for the board (the MCP temp is 48 C, but I've heard MCP temperature is not as important.) How does that hold-up for an E6600/680/Tuniq setup? I applied Arctic Silver 5 compound between the HS and the Proc, and I understand that it takes a few days to burn in. What sort of temperature drop should I expect if I applied correctly?

Note that I haven't tested under load yet. That will come tomorrow after I decide which OS to install and get everything setup.

Thanks,

Mark.
 
Originally posted by: theYipster
I applied Arctic Silver 5 compound between the HS and the Proc, and I understand that it takes a few days to burn in. What sort of temperature drop should I expect if I applied correctly?
Source
Important Reminder:
Due to the unique shape and sizes of the particles in Arctic Silver 5's conductive matrix, it will take a up to 200 hours and several thermal cycles to achieve maximum particle to particle thermal conduction and for the heatsink to CPU interface to reach maximum conductivity. (This period will be longer in a system without a fan on the heatsink or with a low speed fan on the heatsink.) On systems measuring actual internal core temperatures via the CPU's internal diode, the measured temperature will often drop 2C to 5C over this "break-in" period. This break-in will occur during the normal use of the computer as long as the computer is turned off from time to time and the interface is allowed to cool to room temperature. Once the break-in is complete, the computer can be left on if desired.

 
You forgot to tell us the most important thing, room temp 🙂 35C is about average for idle temps. You'll need to run it under load, idle, and off to let AS5 cure correctly. After it cures you may get a 2-3 degree drop. With good airflow the Tuniq is a killer cooler, I got the tuniq with an antec 900. You might want to consider adding more fans.
 
Room temp is about 70-72. I was able to install Vista 64 in 15 minutes on this thing, which I found to be quite impressive. However, with Vista 64's incompatibility (it can't run TAT for example,) I may revert back to the 32 bit version for the time being.

Mark.
 
Originally posted by: theYipster
...with Vista 64's incompatibility (it can't run TAT for example,)...
I don't understand this!

What could Microsoft have been thinking?!?!?!
 
Update!

I got Core Temp working (unfortunately I couldn't figure out how to get TAT running in Vista x64.) After a day of settling in, it seems my PC is cruising along. Amazingly, CoreTemp reads core 0 at 22-23c at idle, and Core1 at 23-25c. Is CoreTemp usually accurate, or is nvbios notably innacurate?... because the temperature jump is startling.

Keep in mind that I first read the 35c upon turning my PC on for the first time after building it, so I'm not sure if the processor is naturally warmer due to all that activity.

I'm heading out for an hour or two and I'll run Orthos in the mean time to see temps at load.

Mark.
 
What's wrong with TAT?

Right click on it and choose "run as administrator"

Or Disable the Account Protection thing.

You can also try to run in a compatability mode with XP.
 
Tried all but nothing works. The program will display a window for a split second before promptly exiting. UAC is disabled on my machine as for practical purposes. I'm pretty sure the problem is not Vista related, per se, but x64 related (or perhaps a combination of the both.)

TAT doesn't even run in Enable-Unsigned-Drivers mode, while CoreTemp and CPU-Z do. In any case, I'm going to think about which version of Vista I'd like on my machine for the long(er)-term and reformat. I've found Vista x64 to be reasonably more solid than XP 64, but perhaps not enough to warrant long term use.

Mark.
 
Back
Top