From: "Cecil H. Whitley" <cwhitley@earthlink.net>
To: <speakup@braille.uwo.ca>
Subject: cpu overheat during compiles
Date: Sat, 25 Feb 2006 17:06:17 -0500 [thread overview]
Message-ID: <004701c63a57$b3d2f2f0$6401a8c0@computer> (raw)
I noticed this previously, got a can of air and blew the dust out of the cpu
fan. That resolved it for me. Unfortunately, I have to repeat the process
about every 2 or 3 months. Most newer cpu's run hot and need good air
circulation. I've actually got 4 case fans, but if I don't keep the cpu fan
clean it still runs hot. I've considered getting a larger heat sink/fan for
the cpu, but the system needs a good dusting anyway.
Cecil
reply other threads:[~ UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='004701c63a57$b3d2f2f0$6401a8c0@computer' \
--to=cwhitley@earthlink.net \
--cc=speakup@braille.uwo.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).