Does this sound like a heat related crash?

Jman13

Senior member
Apr 9, 2001
811
0
76
On the rig in my sig, AthlonXP 1700+ @ 1540, (using retail HSF with thermal pad...so not too cool), it's been running just fine and very solid at that speed...going days without crashes or reboots. I added a third HD, which didn't drop the voltage to the chip any, and it only increased the heat inside the case by MAYBE a degree C. I run SETI 24/7. My GF went to print off the web the night I installed the HD, and I ended up with a blue screen error (don't remember exactly what it said) that completely locked the machine. (this is WinXP...blue screens are NOT common) Just to be on the safe side, I lowered my FSB to 137 from 140, and haven't had any more crashes. Do you think this could be an OCing issue? (perhaps the new HD doesn't like 140FSB?). I don't think it is, it seems like it would be farm more likely to crash while playing games or something, but SETI was running, so the processor wasn't just sitting idle.

What I feel is far more likely to have caused the crash is the fact that I tested my UPS by pulling the plug on it. The 2 USB hubs are connected to the UPS, but not on the battery backup (just machine and monitor are backed up). They went out and reset themselves...the printer is USB. I think it was most likely that the printer didn't reinitialize properly, but I don't want to take a chance with OCing the processor or HDs too far, but 140 FSB is not exactly high...the HDS are only running at 35 MHz on the PCI bus. What do you think? Am I being too cautious here?

Temps are 30C chassis, 48-49C CPU while at 1540. 28C chassis, 46-47C while at 1506.
 

Jman13

Senior member
Apr 9, 2001
811
0
76
Ok...nevermind. I think I can safely say it was not heat related, as I'm now running @ 1606MHz, at stock voltage, with no problems so far (2 runs through 3DMark, etc). We'll see if it continues to be stable at this speed. No noticably heat increase too...which is pretty cool.

Jman
 

sandorski

No Lifer
Oct 10, 1999
70,709
6,266
126
Yea, I'll second MoFunk's question. There maybe some problems with the printer drivers, if it BSODs again, take a look at it, it will state a driver as causing the problem.