I don't know for sure.

I remember having once tried a 1000MHz Coppermine chip in a s370 BX board and it worked just like a normal 750MHz chip. I ended up using a 800MHz Celeron in that build as I wanted a Celeron build 😜

I think it may depend on the BIOS or perhaps some logic chip on the board.

The board has a BX chipset which does not support a 133MHz FSB.
Since the board does not support 133MHz FSB it is unlikely the microcode in the BIOS includes 133MHz FSB CPUs.
The 300A uses a 66MHz FSB.

Make sure your jumpers for FSB are set correctly. Page 18.
http://www.motherboards.org/files/manuals/1/p3bf-104.pdf

The board has jumper settings for 133MHz FSB but that won't necessary allow using a 133MHz FSB CPU. (Not in microcode)
It would (might) allow overclocking a 100MHz FSB CPU to 133MHz FSB. (In microcode)
.

While the BX chipset never officially supported an 133MHz bus, it is perfectly capable of running at 133MHz - but it will OC the AGP bus, so beware. Unless the BIOS has any logic to halt when it detects an unknown processor it should work fine. You can also leave the bus at 100MHz if you prefer to play it safe with the graphics card.

I highly doubt you will have any problem. CPUs like the Pentium III 1000EB have the multiplier built onto the CPU, all they need it the FSB set.

PCBONEZ wrote:

Make sure your jumpers for FSB are set correctly

I tried manual switchers and jumpless mode, auto voltage, manual 2.0V voltage on slotket - 300A does not work. Probably MB and/or slotket or other thing has issues, or BIOS by some reason wants slot1 300A only.
I was able to run slot1 P3 1000EB at 66*7,5 a single time, it entered setup, there was 1.7 V instead of correct 1.75, and then the system has stucked. The MB starts not every time I press power button, I suspect mulfunction (PSU, MB, button, CPU, ...). I think, on operable board 1000EB should to work at 100x7,5 (at least) if it started with 66 MHz FSB, in case such start was not due to possible nonstable malfunction.

Tertz wrote:

The MB starts not every time I press power button, I suspect mulfunction (PSU, MB, button, CPU, ...)

Does it have any bloated or leaking capacitors?
Any OST brand?

Have you tried a different PSU?
.

Also are you using PC133 RAM or something slower?

At one time I had a bunch of P2B and P3B boards. Overclockability improved with later revisions. A P3B-F 1.04 is a later board so it has a very good chance of running reliably at 133FSB, but it's not a sure thing. Sometimes they aren't stable at that speed. When trying to run at 133FSB, you have to be careful that the PCI ratio is set to 1/4 and AGP at 2/3 (the latter is still an overclock, but it's the best you can do and it works fine with lots of video cards).

I didn't have a 1GHz CPU back then, but I know I tested some lower speed 133FSB Coppermines on them. If they didn't run at 133FSB then they would still run at 100.
It's possible the 1GHz is a later core stepping than anything I had at the time. Even so, from all the online discussions I've seen about these boards, I'm about 99% sure it will run happily with any Coppermine as long as the BIOS has been sufficiently updated. The only thing in doubt is whether you'll be able to use the full 133FSB or have to clock it down to 750/100.
The latest beta BIOS for the P2B even supports booting with Tualatins, so I'd be very surprised if the P3B BIOS wasn't at least updated enough to support all Coppermine steppings.

It sounds like there's a stability problem, possibly with the board or PSU, I'm afraid.
Make sure the RAM is known reliable at the required speed as PCBONEZ mentioned, and that the latencies aren't set too aggressive.
Slot-1 can be a bit fiddly - sometimes the CPU just needs to be reseated in the slot and then it works.

Try fully resetting the CMOS and then using the option to load defaults. Sometimes there can be a corrupt setting somewhere that isn't exposed in the setup menus. This can especially happen when updating a BIOS, and the new version doesn't store information the same way as the old version did.

If you have a multimeter, some voltages could be checked that might point to a problem. The slightly low Vcore you saw in the BIOS might suggest a problem, or it might just be inaccurate.

alexanrs wrote:

While the BX chipset never officially supported an 133MHz bus, it is perfectly capable of running at 133MHz ...

And then some.

I'm running a rev 1.04 P3B-F board @ 133Mhz. Had some issues with various AGP cards using the overclocked AGP bus, but finally got it stable running a 1400Mhz Tualatin.
Re: Artex's Build of the Week: Altered Beast

I used P3B-F 1.04 with a P3-933 SL4BT and had no significant problems.

Artex wrote:

I'm running a rev 1.04 P3B-F board @ 133Mhz. Had some issues with various AGP cards using the overclocked AGP bus, but finally got it stable running a 1400Mhz Tualatin.
Re: Artex's Build of the Week: Altered Beast

Can you try to disable Sideband Addressing? I had nothing but good results with my 1400-S@Upgradeware Slot-T/P3B-F 1.04/Spectra x21 Geforce 3 Ti500 setup by disabling it. It looks like it seriously hampers FSB because I couldn't go above 124/133fsb before doing so but now I can easily crank it up to 150 with some sick ram timings (2-2-2-4).

subhuman@xgtx wrote:

Artex wrote:

I'm running a rev 1.04 P3B-F board @ 133Mhz. Had some issues with various AGP cards using the overclocked AGP bus, but finally got it stable running a 1400Mhz Tualatin.
Re: Artex's Build of the Week: Altered Beast

Can you try to disable Sideband Addressing? I had nothing but good results with my 1400-S@Upgradeware Slot-T/P3B-F 1.04/Spectra x21 Geforce 3 Ti500 setup by disabling it. It looks like it seriously hampers FSB because I couldn't go above 124/133fsb before doing so but now I can easily crank it up to 150 with some sick ram timings (2-2-2-4).

I think I tried that using PowerStrip but it just locked up my system.