On Wed, 8 Oct 2003, mathieu perrenoud wrote: > > Yes and no. It could be because you were compiling OO, but not OO's > > fault. Building OO is a very processor intensive task. If you've already > > been having problems with overheating, then the first thing I'd try is > > to get better fans. Although, if this has been a problem for a while, > > there is a good chance that the mobo is damaged anyway from the > > overheating. Before you get the mobo, get better/more cooling fans. If > > that doesn't help, get the new mobo, and you'll already have the better > > fans to use with it :) > > I've got 2 brand new fans, and I've monitored temp, usage disk and whatever > during compilation. everything was fine.
What's the temp of the north bridge and RAM? > > As for the processor and RAM, it is okay to keep the old ones as long as > > you know that they work fine. Try running memtest86 on your RAM to > > make sure its in decent condition. Unless you're getting weird errors > > and segfaults everywhere, your processor is probably fine. > > If I understand well: if the mem is fine then the cpu is fine too? Probably but not necessarily. memtest86 is still not the most cpu-intensive program, since the only thing it does is memory. On the other hand, if memtest86 were to crash, you know you've got a bad cpu. I once had a board I was using memtest86 on. It always found bad RAM at a certain memory range, even with completely different RAM (which had tested good elsewhere) and a different CPU. It seemed the motherboard itself was bad. -- Marshal Newrock, unemployed Linux user in Lansing, MI Caution: Product will be hot after heating -- [EMAIL PROTECTED] mailing list
