CPU Host clock failing! (???) w/ 2500+Barton??

[BadGoat]

This problem is rather hit and miss....my details of my rig are in my sig. But when I seem to restart my computer or just turn it off and turn it right back on and my computer is getting ready to POST I get an error message telling me that my "CPU Host clock is failing! blah blah blah..." So I then enter CMOS to verify my clock setting and everything is correct. I exit and save CMOS and the computer restarts and boots just fine. If I get the error message and just hit F1 my computer continues to boot up normally and everything is just fine.

Now I have recently flashed the BIOS on my mobo as it didn't support the Barton core. Everything went fine during the flash and I wouldn't think that was my problem. However, I have read on forums before that it is recommended to repartition/reformat your harddrive after installing a critical component such as the CPU. However, what I don't understand about that recommendation is "Why would that have anything to do with the way things boot up or run?? Windows hasn't loaded by then and a reformat shouldn't affect anything."

Am I wrong with this assumption? Or should I follow through with a reformat? Is my CPU junk?(I wouldn't think so if everything is running just fine when up and running...)

Any suggestions or leads in the right direction would be greatly appreciated! Thanks.

 

[Harvey]

If the problem did not happen with the previous BIOS version (and previous CPU), you could have gotten a bad flash, or the new BIOS has some problems. If you are using the default settings, and you set it for autodetect, did you check the FSB, voltage and other settings for your Barton chip to see if they are correct?

You could also clear the CMOS or reset it for the default, boot it, and set it to your preferences. I've run into this with boards when updating the CMOS.

Hope that helps. Good luck.

 

[BadGoat]

so do you recommend flashing back to the old BIOS and then reflashing to see if that clears up the problem?

 

[Harvey]

That won't work if the old BIOS won't support your CPU. Try these steps:

1. Set the CMOS for Default setting.

2. If that doesn't help, try the Fail Safe setting.

3. If that doesn't help, try clearing the CMOS with the jumper on the motherboard.

4. If that doesn't work, try flashing it again.

I may have to go out in a few. If so, I won't be able to reply again right away.

 

[BadGoat]

Well I have this thread over on HardForum as well....

One guy told me this:

"The hostclock msg on post sounds like the Mobo may be getting ready to clock that last cycle. The msg is probably being fired due to a timer or signal that isn't syncing or coming up fast enough to meet the parameters set in the bios. When it decides to go it will most likely do so without any warning."

Any input would be greatly appreciated! All you techies out there take a look at this and give me some input, I would sure hate to RMA a perfectly good chip when the problem was something I overlooked in my BIOS settings....thx alot y'all!

 

[BadGoat]

*bump* anyone????

 

[Jeff7181]

Did you reset everything to defaults as suggested?

 

[VisableAssassin]

only time i ever got a CPU anything error on my KD7-RAID (i know different mobo but im trying) was that i was gooing around and tried to runt he CPU at 133fsb and it didnt like that one bit. other than the possibility of the wrong FSB im at a loss its really weird, sorry i couldnt help much more

 

[BadGoat]

yup, everything has been set right back to default. And I made doubly sure I was running the correct FSB. Some guy advised me to take settings off of SPD or Auto in the CMOS and just set them to manual. He said sometimes that can cause goofy problems as far as timings go...guess I'll put back in the 2500+ and take out my 2000+ pali and give it a try...guess it can't hurt, lol.

Well, thx for the suggestions. Keep them coming please...seems like I am stumping a lot of people on this one including myself.