My system (FIC AD11 mobo) won't post at 133MHz FSB setting, no matter what I do. It works fine at 100MHz and it DID work perfectly at 133 for several months!!!
- Here is the LONG story:
I have been using my system happily for months now (no overclocking, or anything) when it slowly degraded and died last week. I don't recall doing anything weird, no hardware/software upgrades, no patches, no driver changes, for at least a week. I woke it up from the sleep mode two days ago, opened Outlook to check my mail and bam! - got BSOD followed by a prompt reboot.
From that point on, it would never complete booting again, usually BSOD-ing at, or right after Win2000 login window. I swithced to the SafeMode - it worked fine with no problems. All devices were reported to work properly in the Device Manager. I have even been surfing the web for at least an hour with no problems.
Now is where it gets interesting: Rebooted again - system froze at the PCI card screen. Reboot - now it froze at the FIC splash screen. Reboot - DEAD - no post, no beeps, no video signals. Reboot... Reboot... same...
- End of story.
I have stripped everything to the basics:
AD11 1.2 M00604
BIOS: ABA42 (I had to clear the BIOS with the CLR_CMOS jumper, so everything should be set to default)
Athlon TB 1333MHz with fan
256MB CORSAIR XMS 2400 (CM64SD256-2400 C2)
Nvidia Riva TNT AGP (I had tried several other video boards to no avail, so the video card is not the problem)
Only one thing seemed to work: I moved the FSB jumper (FS) to 100MHz and cleared CMOS - it booted with no problems. After making it work at 100MHz, I had tried switching to 133 either by just moving the jumper (with power off, of course), or by first selecting 133/33 setting in BIOS and then moving the jumper. Both result in system not positing and giving no beeps.
Sometimes the AD11 will still power the bridge and CPU fans (one of them or both), but not always.
When I switch using the second method (by setting 133/33 in BIOS), I need to clear CMOS to make the system boot in 100MHz again (even if jumper is set to 100MHz).
As I said, the system worked fine at 133MHz for several months (with no overclocking).
Why is it refusing now???
- Here is the LONG story:
I have been using my system happily for months now (no overclocking, or anything) when it slowly degraded and died last week. I don't recall doing anything weird, no hardware/software upgrades, no patches, no driver changes, for at least a week. I woke it up from the sleep mode two days ago, opened Outlook to check my mail and bam! - got BSOD followed by a prompt reboot.
From that point on, it would never complete booting again, usually BSOD-ing at, or right after Win2000 login window. I swithced to the SafeMode - it worked fine with no problems. All devices were reported to work properly in the Device Manager. I have even been surfing the web for at least an hour with no problems.
Now is where it gets interesting: Rebooted again - system froze at the PCI card screen. Reboot - now it froze at the FIC splash screen. Reboot - DEAD - no post, no beeps, no video signals. Reboot... Reboot... same...
- End of story.
I have stripped everything to the basics:
AD11 1.2 M00604
BIOS: ABA42 (I had to clear the BIOS with the CLR_CMOS jumper, so everything should be set to default)
Athlon TB 1333MHz with fan
256MB CORSAIR XMS 2400 (CM64SD256-2400 C2)
Nvidia Riva TNT AGP (I had tried several other video boards to no avail, so the video card is not the problem)
Only one thing seemed to work: I moved the FSB jumper (FS) to 100MHz and cleared CMOS - it booted with no problems. After making it work at 100MHz, I had tried switching to 133 either by just moving the jumper (with power off, of course), or by first selecting 133/33 setting in BIOS and then moving the jumper. Both result in system not positing and giving no beeps.
Sometimes the AD11 will still power the bridge and CPU fans (one of them or both), but not always.
When I switch using the second method (by setting 133/33 in BIOS), I need to clear CMOS to make the system boot in 100MHz again (even if jumper is set to 100MHz).
As I said, the system worked fine at 133MHz for several months (with no overclocking).
Why is it refusing now???
Facebook
Twitter