Is my CPU dead

WorldHavok

Member
Apr 14, 2007
28
0
0
My CPU shows up in the BIOS. The computer attempts to start and gets to the Norton GoBack screen and then freezes. It had given me a CPU overtemp warning several times but seemed to be running fine. Is there any way to check that it is the CPU without swapping with another CPU? Any help would be appreciated.
Thanks
 

Narse

Moderator<br>Computer Help
Moderator
Mar 14, 2000
3,826
1
81
1. Your CPU should never give you a overheat warning, pull off the HSF, reapply some good thermal paste and reattach the HSF properly, make sure no dust etc is in the fins and make sure the fan is working properly.
 

jackschmittusa

Diamond Member
Apr 16, 2003
5,972
1
0
You should never keep running with a cpu over temp alarm. Alarms are danger signals. The alarm should be set to signal an over temp condition close to, but below the temp that will cause permanent damage to the cpu. Even if you run it close to max temp for extended periods, it can damage it.

When you pull the hsf, clean it (and the cpu) with alcohol before applying new thermal paste.
 

WorldHavok

Member
Apr 14, 2007
28
0
0
I know that having any warning message is bad. I leave for months at a time...the comp was ok when I left. I cleaned the heat sink and CPU fan when I got home, All I want to know is there a way to be sure its the CPU? As I said the machine tries to boot but stalls...Any way to be sure before a rebuild?
 

cubby1223

Lifer
May 24, 2004
13,518
42
86
Cpus are by far the most durable component in the computer. I've seen one running for a day at ~150 C (the computer stalled of course). It was a 3ghz xeon, the cpu fan stopped working. I still have the scar on my finger from accidentally brushing against the heatsink for the briefest fraction of a second. That was 3 years ago. Replaced the fan, system is still running stable today. I've also worked with flood damaged computers, even when submerged in water while powered on, the cpu always comes out working perfectly.

What I'm getting at is the likely culprit is Norton GoBack, or something else with the system. If you want to run the cpu through something anyways, have the computer boot to a memtest+ cd. I'll betcha the system will run for hours on end. :)