HP3000-L Archives

August 2002, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Arthur Frank <[log in to unmask]>
Reply To:
Arthur Frank <[log in to unmask]>
Date:
Mon, 5 Aug 2002 10:55:06 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (19 lines)
Dust can be a killer, in the heat department.  At home, my Windows 2000 box was acting a little odd (totally random BSODs), and I noticed that the CPU was running hot, hot, hot.  I shut down, cracked the case, and shoo-ee-doggie, there was a lot of dust in there.  The CPU heatsink was COMPLETELY clogged with dust.  After blowing the dust out and giving it a good vacuuming, all was well.

The moral of this tale:  watch the dust in those PC cases!  At work, I really don't see that much dust in the cases, but at home...  watch out!  Especially with these new-fangled high-speed (high-heat) CPUs.

Art Frank
Manager of Information Systems
OHSU Foundation
[log in to unmask] 
(503) 220-8320

>>> "Wayne R. Boyer" <[log in to unmask]> 08/05/02 09:44AM >>>
<snip>
FYI: Flaky temperature sensors can cause flaky readings resulting in LOTS of false console messages.  When we had this in the past I think that a thorough cleaning out of dust inside the CPU enclosure cured this.  It wasn't the CPU chip/board that was too hot, just a dust covered sensor.

Wayne Boyer

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2