• 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.

Shuttle Ak38/n and Athlon XP 2000+

KizzThiz

Junior Member
System setup:

MoBo: AK38/N
CPU: Athlon XP 2000+
Ram: (2) Crucial PC2100 256Mb (512 total)
OS: Win XP Pro

FSB is currently set to 100Mhz. Boots and works fine BUT the BIOS does not recognized the CPU correctly (it used to). Sometimes the BIOS recognizes the ram as DDR 200, sometimes DDR 266. But it never recognizes the CPU correctly until I set the FSB to 133 and if I do that XP won't boot (always blue screens with varying errors).

I built the system 2 weeks ago and everything worked fine (FSB was set to 100mhz). CPU identified correctly, Ram identified as DDR 200 (which is fine)... everything fine. Went away for a week, came back and now BIOS does not identify things correctly. I have verified all BIOS settings and the only way I can get the CPU to identify correctly is by setting the FSB to 133, then XP will blue screen.

Any ideas on this one ??? Should I try a re-install of XP ???

I have clear CMOS multiple times, always get a CMOS check sum error on 1st boot after reset. Works fine with FSB at 133... next reboot or boot XP will blue screen (always 1 of like 5 different errors)

I just want to know why it stopped working (or possible causing) and how to correct it.

Ok... reinstalled XP... no luck... Purchased Corsair pc2700... awaiting arrival...

Anyone have any ideas ???
 
Back
Top