Is it possible for a "bad" processor to still function?

ahsumdude

Senior member
Nov 12, 2000
531
0
0
I have a XP 1900 in my son's PC. For the past month he's been getting random lockup. I performed a fresh install of XP and still the PC crashes with A BSOD. I figured the mainboard has gone bad. However before I replace the MB I want to make certain it isn't the CPU. The only thing I haven't done is swap his CPU for my CPU.


Is it possible to run windows normally and still have a bad CPU? Temps on the core are usually around 95 to 100 F.

I ran GOLDMEMEORY tester on this board and all three stick of PC 150 cas 2 showed errors. However when I tested this same ram on my daughter's PC they all were fine. This lends me to thinks my A7V has gone south on me.
 

DeschutesCore

Senior member
Jul 20, 2002
360
0
0
Yes, CPU's can run and still have damage. Usually this occurs out of the box or in the event of a heat failure. Don't be too quick to blame the CPU though. You might want to run a DOS based RAM test and check temperatures, too.

Second, are those temperatures in celcius or fahrenheit?

DC
 

PHiuR

Diamond Member
Apr 24, 2001
9,539
2
76
i think either motherboard or powersupply =] try... powersupply first
 

Maggotry

Platinum Member
Dec 5, 2001
2,074
0
0
I had a bad cpu about a year ago. It was a brand-spanking new, retail boxed, 1GHz Athlon. I would get constant .dll crashes. After tons of work that got me nowhere, I finally bought a new cpu and never had another crash. So, from my experience, you can definitely have a bad cpu that sometimes works, and sometimes doesn't. The mobo I was using was an A7V133. The memory would test fine after a clean boot. But, if I tested the memory right after getting a .dll crash, the memory would fail. Your problem sounds a whole lot like what I went through...almost the same mobo too.

One last thing, that mobo came out way before the XP processor. Make sure you're using the latest BIOS for that mobo. ASUS's site says it's version 1011, right here.