squirtle24
Senior member
Hallo! I've been struggling with this on and off for a couple of days, but no luck. I could use some advice for this problem. Here are the essential system specs:
Abit BE6-2(BIOS flashed to XU)
PC133 RAM
P3-700@933(just upgraded the CPU from a Celeron366@550)
IBM 75GXP (30 gigs)
Generic PCI video card for testing purposes
Windows 2000, running with latest HighPoint drivers from Abit's website
Win2k will load and be stable under these conditions:
1. 100MHz FSB, P3 running at 700Mhz, HDD connected to the onboard UDMA66 interface.
2. 133MHz FSB, P3 running at 933MHz, HDD connected to the standard IDE interface.
Win2k will not even start to load when I'm running:
1. 133MHz FSB, P3 running at 933MHz, HDD connected to the onboard UDMA66 interface.
For this situation, the system gets to the second screen(where it shows IRQ info), and then hangs the instant it tries to boot Win2k. Basically, I think the HighPoint controller is having problems at 133MHz FSB. I find this odd, since the latest BIOS for this board supports that FSB speed. All of the other components appear to be okay.
I also tried changing the mode of the HDD. This gives me blue screens during Win2k's boot process at both 100MHz FSB and 133MHz FSB.
Has anyone ever encountered this problem with the BE6-2? I'd greatly appreciate any constructive advice.
Abit BE6-2(BIOS flashed to XU)
PC133 RAM
P3-700@933(just upgraded the CPU from a Celeron366@550)
IBM 75GXP (30 gigs)
Generic PCI video card for testing purposes
Windows 2000, running with latest HighPoint drivers from Abit's website
Win2k will load and be stable under these conditions:
1. 100MHz FSB, P3 running at 700Mhz, HDD connected to the onboard UDMA66 interface.
2. 133MHz FSB, P3 running at 933MHz, HDD connected to the standard IDE interface.
Win2k will not even start to load when I'm running:
1. 133MHz FSB, P3 running at 933MHz, HDD connected to the onboard UDMA66 interface.
For this situation, the system gets to the second screen(where it shows IRQ info), and then hangs the instant it tries to boot Win2k. Basically, I think the HighPoint controller is having problems at 133MHz FSB. I find this odd, since the latest BIOS for this board supports that FSB speed. All of the other components appear to be okay.
I also tried changing the mode of the HDD. This gives me blue screens during Win2k's boot process at both 100MHz FSB and 133MHz FSB.
Has anyone ever encountered this problem with the BE6-2? I'd greatly appreciate any constructive advice.