• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

celeron D 345

scoop

n00b
Joined
Mar 3, 2005
Messages
23
Long story short: I have a Celeron D 345 running in a HP Pavilion a1110n. (it's my Aunt's pc). For some reason, the cpu fan decided to stop its spin while I was running Memtest on a bootable cd. Perhaps the bios intended to hand off fan control to the OS? Anyways, the pc shut itself down while I was in the other room and the sink was hot to the touch. It didn't turn on for awhile. After awhile, I was able to start it up and it worked fine. My question is, is it likely I damaged the CPU, or did the supposed Intel safeguards save me? I only ask because I figured that it would have shut itself long before it was close to being damaged.

Thanks!
 
I think your most likely fine. These chips have alot of protection to them. plus the heat sink was attached so it can't heat up that fast. The only way you might be able to burn up a chip in this manner is if there was no heat sink and it heated up so fast that part of the chip got hot before the protection circuitry was tripped. It booted up and ran so I wold not worry about it at all.
 
Thanks, I needed to hear something like that. I'd feel like crap if my aunt took her pc back to Michigan and it quit running for her.

Thanks.
 
What I'd be more concerned about is the fact that the fan quit spinning in the first place.

The BIOS doesn't 'hand off' control of the fan to the operating system, the fan is controlled by a set thermal profile in the BIOS. (or in some older configurations it runs at 100% all the time). The fact that it stopped spinning suggests to me either a failing fan or a failing CPU_FAN header on the motherboard.

It could also be something as simple as a loose wire catching in the fan blades and causing the fan to stop.
 
What I'd be more concerned about is the fact that the fan quit spinning in the first place.

The BIOS doesn't 'hand off' control of the fan to the operating system, the fan is controlled by a set thermal profile in the BIOS. (or in some older configurations it runs at 100% all the time). The fact that it stopped spinning suggests to me either a failing fan or a failing CPU_FAN header on the motherboard.

It could also be something as simple as a loose wire catching in the fan blades and causing the fan to stop.

It's definitely not a fan blade obstruction. I would normally agree with you on a failing fan, but I could only replicate this issue after booting to the memtest cd and running it for a few minutes, and it was fairly consistent. While WinXP was running, I couldn't get it to happen at all. I'm thinking there's something wrong in the bios. I guess it could be a bug in Memtest, but this is the first time I've ever noticed the behavior on any PC I've used it on. Does anyone have an idea for a conclusive test on this particular hardware?
 
Back
Top