When I run PC Probe II which came with it, it has a threshold for the
motherboard set at 45 degrees. With the room temperature around 30
degrees, it currently shows the motherboard temp at 46 degrees.
Is this something I should be worried about? The CPU temperature is well
below the threshold.
--
Long-time resident of Adelaide, South Australia,
which may or may not influence my opinions.
My mobile must have scrambled my bwain because my telepathy is not
working so I can't tell what processor it is.
But 46 is not a lot, if it's an AMD, if it's not 55+ it's not working.
And if it's a iQuad Core, somebody get me some eggs and a slab of
bacon...
More fans boy..below 40 is comertable.
It not the CPU temperature I'm worried about. It's the motherboard
temperature. As I said, the CPU temperature is well below the threshold
(38 vs 65 currently, but that's in a air-conditioned environment of 26
degrees). The CPU is an Intel Core 2 Duo E8400.
According to PC Probe II (I haven't looked inside the case) the only fan
seems to be the CPU, because when I try to enable the "chassis" and
"power" fan options, it generates a warning and says those fan speeds
are zero.
I don't know who actually built the system, but I bought it through
Deals Direct. I assume they would have put more fans in if they thought
it needed them.
The motherboard temperature sensor on that board has been placed next to the
memory VRM (voltage regulator module) if it looks like this.
http://eservice.asus.com.tw/eService/eService/sShowImage?id=EB5D469C-777C-9172-539C-8D8E15FB9F90.JPG
Asus recommend a temperature range for that sensor of between 0�C and 65�C
so it looks like you are well within range.
You could check cable routing around the memory module area or direct air
through the area if it becomes a concern.
You could also change the alarm threshold.
My Mistake
46 for a Mother is way way too hot regardless of what system.
The motherboard gets hot from air blowing off the Processor
Depending on the Case, If the Fans in Power Supply aren't blowing
enough air out (dust) then the box will slowly overheat.
If the Heatsink on Processor gets clogged or even half clogged with
dust, the Fan will sound like Jet trying to cool it. This will also
raise the temperature in the Box.
The most common fault by far, is the CPU Heatsink clogged (after
Microsoft of Course).
Heatsink's on 3D's Videos also get clogged, these can really cook
if dirty or the fans stops on Card.
Basic test, if you can't touch the Heatsink when the PC is Idle, it's cook'n
OK, thanks for that. I'll take the cover off and have a look inside. I'm
not comfortable fiddling with the innards of PCs, but I can at least see
what it looks like, in terms of dust, etc (although I think it's a bit
too new for dust to be a problem yet).
Well, that seems to be in conflict with Fred's comments on ASUS
motherboards, but thanks for the info. I'll have a look inside, but I
doubt that clogging would be a problem, as the hardware is only a few
weeks old.
It is unusual for a Manufacter to make that sort of Mistake
None of those components have sinks, they shouldn't get that hot
that they need one.
If everything is working Okie Dokie then 34-38 ish should be norm
What mistake are you referring to?
Placing a Thermal Sensor in the middle of hot components
Ah OK. Yes, unless it was the temp of those components they were
primarily worried about. But I guess it explains why they say the sensor
reading can go up to 65, according to Fred.
I doubt that the placement of the sensor was a mistake. On that board the
designers have decided you should be mindful of RAM temperature for system
stability.
Yes, that make sense. Perhaps it's just a pity that PC Probe II uses a
default of 45 degrees for that threshold, but maybe that was a
compromise across different boards.
No.
I was referring to PC Faults. Microsoft is at the top of the list
for computer problems. And Clogged Heatsinks would be after that.
I have good reason to 'ate Microshit. Their crap is full of problems.
Windoze Me, legendary
Vista, see Windoze Me
IIS, is there anybody that actually likes this product, except
Hackers.
Small Business Server 2003, what a pain in the Ass to Setup
Small Business Server 2008, if half the problems I've read are
true, give me 2003 any day.
M$ Office, take your pick, each one full of bugs,
incompatibilities, or just a pain in the Ass to use.
Who else but M$ can release a Version with major Bugs,
Then Fix those Bugs, then re-Introduce those same bugs
in later versions. They have done this several times
over the years.
Not Paranoia, I'm a realist
Check the Internet for those Products and Problems
It's NOT just MY Opinion their products are crap
> M$ Office, take your pick, each one full of bugs,
> incompatibilities,
That is the old dinosaur attitude. Trying to make it hard for other
people to read .doc files.
> or just a pain in the Ass to use.
Most of that is eye candy related. Suckers in the plebs into thinking
that is what is important.
Maybe I should be thankful for creating so much work for IT people.
The thing that Pisses me Off, Being an IT Person you are the first port
of Call. They always blame you first when Microsoft Software F's Up, and
you Inform them it's a Microsoft Software Fault they say, Oh Ok.
Then you get the ones, I hate all you F'n IT people you're all the same.
But really, the previous person was unable to resolve a Microsoft
Created problem. The Computer guy gets the Blame and M$ gets away scott
free again.
> The Computer guy gets the Blame
Sometimes it is deserved. The "we come to your home for free and only
charge on success" deserve every bit of blame they get ladled at them.
Charge on Success, how does that work ?
You could spend freak'n hours tracking down a Microsoft Problem and Fix.
What Should be 15-30 minute fix could blow out to 4 - 6 Hours.
So any basic Quote and time are just throw out the Window. There is no
way you can come out ahead on bad M$ problem.