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

Any FIC AD11 owners experiencing this problem?

It's not so much a problem as it is a minor annoyance. I couldn't resist the urge to stretch the legs of my new rig, but I was having problems getting the FSB to o/c. I have a 1GHz Athlon-C, and it's unlocked. I kept the multiplier at 7.5x while I tried bumping the FSB, and it simply won't go past 133MHz.

The AD11 offers 138/140/... increments, but I can't boot into Windows at anything beyond 133MHz. Is this an issue with my RAM? I tried Vcore at 1.475 (default) and then at 1.75, and both times it would get to the Win2K loading screen and then hang. On the other hand, I bumped the multiplier up to 10 x 133MHz quite easily last night, and only stopped b/c I needed some sleep, and b/c I didn't quite feel like running the chip at 55C (I'm in Florida, so the high ambient is giving my lapped Taisol 740 all it can handle right now).

Anyway, I'm assuming my memory is the hindrance, but I was hoping maybe there was something I could do to help that. It's Crucial PC2100 unbuffered DDR SDRAM. The default bios CAS setting is 2, and I didn't quite get around to trying 2.5 to test stability at the higher clock. I also had a hunch that it might be my IBM 75GXP that isn't handling the o/c too well, but that's probably a bad conclusion.

Anyway, I haven't been able to get it online yet, so drivers are pretty much stock for everything I have. Is there a more recent bios that I should upgrade to? Am I just going to have to accept a 133MHz FSB, and stop complaining? Thanks for any help/advice. PEACE.
 
Back
Top