[Scott F]

Hey,

My computers been working fine, (17 MBP C2D) up until the update of 10.5.3, now it's running super hot, doing nothing!

In my life, I have NEVER had it run close to 100C, especially in a A/C'ed room!



Scott

[TheoCryst]

Can you take a screenshot of the Activity Monitor, sorted by CPU so that the highest usage is on top?

That's dangerously hot, especially with the fans running at 6000 RPM. My initial thought is that the sensor is damaged, and the fans aren't actually running. Can you feel/hear them running as fast as it claims?

[frdmfghtr]

100C is boiling (literally--water boils at 100C/212F), and the processor would I would think that the CPU would have shut itself down well before reaching that temperature.

I'm guessing that whatever utility you are using the monitor the temperature and fan sensors didn't like the upgrade. Try using iStat Pro and see what it says for the fans and temperatures. I know this one works, I use it on my MacBook.

[P]

I agree. Intel CPUs go into emergency shutdown mode long before 100C.

[amazing]

When you're pulling up Activity Monitor, make sure the pull-down menu is set to "All Processes". Something is pegging your processors, so figure out what it is and how to turn it off. Runaway processes are most likely third-party, since few others are reporting problems like that with 10.5.3

[OreoCookie]

One candidate for this is syslogd.
If syslogd is consuming about 90+ % cpu for a long time, then do the following.
(1) Log in as an Administrator (i. e. the box `this user is allowed to administer this computer' needs to be checked).
(2) Launch the Terminal. Type

Code:
sudo -s

and press Enter. The password is the same as your administrator password.
(3) Type

Code:
cd /var/log/

and press Enter.
(4) Type

Code:
rm asl.db

and press Enter.

This should take care of the problem.

[mduell]

Probably just a bug with the temperature monitoring widget.

[leightj]

Originally Posted by P 

I agree. Intel CPUs go into emergency shutdown mode long before 100C.

I could only hope. My macbook (mid 2007 2.16 C2D) has suffered from overheating problems for a while now, routinely sitting around 60-80C (~90% idle), and peaking yesterday at 96C (compiling webkit). I've taken it in to the Apple store several times and the consensus from the Genius Bar is that its normal...

I have used iStat, smcfancontrol, and several other utilities and they all agree on the numbers. I have also upped the fan speed with smcfancontrol to help keep things cooler.

[turtle777]

Originally Posted by OreoCookie 

One candidate for this is syslogd.
If syslogd is consuming about 90+ % cpu for a long time, then do the following.
(1) Log in as an Administrator (i. e. the box `this user is allowed to administer this computer' needs to be checked).
(2) Launch the Terminal. Type

Code:
sudo -s

and press Enter. The password is the same as your administrator password.
(3) Type

Code:
cd /var/log/

and press Enter.
(4) Type

Code:
rm asl.db

and press Enter.

This should take care of the problem.

Good stuff. Need to remember that for the next timesyslogd goes buck-wild.

-t

[LeeG]

Had this happen last night, removed the system.log file, shut down overnight, and it seems to have settled down, but my BRAND NEW 24" imac was churning away with syslogd using 100% of one core. The back was too hot to touch- we should stickie this tip....

L