Help: CPU is unworkable or has been changed

[Guest]

I installed an Athlon 1.2 GHz T-bird into my KT7-RAID about a month
ago. Right after I first installed it, I got a "CPU is unworkable or
has been changed" error on boot up, but after a few resets, the error
went away. I never saw that error again until today (and I've rebooted
plenty of times since then). My computer worked fine when I rebooted
it last night, but every time I reboot it today, I get that error
message. I didn't make any changes at all since last night. It's
happening all of a sudden for no reason. In some old posts, people
have suggested that you disable the CPU Error Hold setting, but I can't
change that in my A9 BIOS (it's grayed out, but set to Disabled
anyway). In other posts, people have suggested that the CMOS battery
may be the problem, but all of my custom BIOS settings are still
intact. Or could the battery cause this error without losing all the
CMOS settings? I'll go out and get a new battery, but in case that
doesn't solve the problem, does anyone have any other ideas as to why
I'm suddenly seeing this error for no apparent reason? Thanks.

 

[0_Qed]

I installed an Athlon 1.2 GHz T-bird into my KT7-RAID about a month
ago. Right after I first installed it, I got a "CPU is unworkable or
has been changed" error on boot up, but after a few resets, the error
went away. I never saw that error again until today (and I've rebooted
plenty of times since then). My computer worked fine when I rebooted
it last night, but every time I reboot it today, I get that error
message. I didn't make any changes at all since last night. It's
happening all of a sudden for no reason. In some old posts, people
have suggested that you disable the CPU Error Hold setting, but I can't
change that in my A9 BIOS (it's grayed out, but set to Disabled
anyway). In other posts, people have suggested that the CMOS battery
may be the problem, but all of my custom BIOS settings are still
intact. Or could the battery cause this error without losing all the
CMOS settings? I'll go out and get a new battery, but in case that
doesn't solve the problem, does anyone have any other ideas as to why
I'm suddenly seeing this error for no apparent reason? Thanks.

A new bat ?mite? help, and cant hurt.

A 'SWAG' ....

*IF* W98 ...
try re_flashing to the 'A9' BIOS rev ...
That'll give you a fresh ESCD, along with a cleared CMOS( a "U_do" ) .
Hopefully W98 boots and realigns it's Reg to the new ESCD .

*IF* XP ... Retail or OEM ???
similar but you're in for a re_activate, **IF** you're allowed.

Qed.

 

[kony]

I installed an Athlon 1.2 GHz T-bird into my KT7-RAID about a month
ago. Right after I first installed it, I got a "CPU is unworkable or
has been changed" error on boot up, but after a few resets, the error
went away.

You're supposed to get that message. You just enter the
bios, check the FSB & Memory speeds, and save the changes
(even if you don't change anything, you save it anyway).

I never saw that error again until today (and I've rebooted
plenty of times since then). My computer worked fine when I rebooted
it last night, but every time I reboot it today, I get that error
message.

Try saving it (bios, as mentioned above).

I didn't make any changes at all since last night. It's
happening all of a sudden for no reason. In some old posts, people
have suggested that you disable the CPU Error Hold setting, but I can't
change that in my A9 BIOS (it's grayed out, but set to Disabled
anyway). In other posts, people have suggested that the CMOS battery
may be the problem, but all of my custom BIOS settings are still
intact. Or could the battery cause this error without losing all the
CMOS settings? I'll go out and get a new battery, but in case that
doesn't solve the problem, does anyone have any other ideas as to why
I'm suddenly seeing this error for no apparent reason? Thanks.

You might also try manually setting the bios to the spec'd
FSB and multipler for that CPU, if it was set to auto...
then manually set the memory too. If it then requires
manually setting the memory timings, use "CPU-Z" first in
windows(?) to see what timings it was using previously so
you can be sure that (presuming it's currently stable
that...) stability is retained through using same timings
just set manually rather than SPD/automagically.