• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Not Overclocking, Overclocking Error Message

TechKnight

Platinum Member
I was just wondering if it's just me, but I recently just upgraded my Dream Machine with the following specs:

Asus P3V4X Mobo
PIII 667EB Mhz Slot 1
MicroQ (I think, generic?) 128MB PC133 SDRAM
CL TNT2 Ultra 32MB AGP
CL SB Live! Mp3
CL 56K ISA V.90 Speakerphone Modem
CL Encore 2X DVD with Dxr2 Decoder Card
CL CD Writer 8432

Everything works fine except if I leave the computer off for longer than 5 hours and I turn it back on, it goes into the BIOS and displays the following error message:

During the last boot-up, your system hung for an improper CPU speed setting. Your system is now working in safe mode. To optimize the system performance and reliability, make sure the CPU speed conforms to the specifications of your CPU.

Now the strange things:
1. This machine is NOT overclocked.
2. The system did not crash/hung the last time it was shutdown.

Any ideas what may cause this?
 
The CMOS battery? Hmmm... shouldn't it give me a Checksum error instead like when you change batteries or clear the CMOS? So I try replacing it with another one and see if the same occurance comes up?
 
could be the fact that you are running at 133 fsb. does that mobo officially support cpu's which run at 133. I am on an Abit BX6 Rev. 2 and I had to dissable this error message (cpu unworkable) becuase 133 wasn't some official speed. (same CPU as you).
 
I get the Same damned problem on 2 pc's. One a C2 that is overclocked and the other a P3 at 133(not oc'ed) the system doesn't have to crash or even hang. This message pops up sporatically. Otherwise it runs fine. If you look at the newest bios 1005, it says something about changing the way the board checks the fsb, so maybe this fixes this problem.

Brian
 
Back
Top