128MB PC133 RAM
Abit BH6 rev 1.1 w/latest bios
iwill pro66 w/ibm 15GB/66 HD (DJNA-351520)
soundblaster live value
matrox millennium g400 dual-head 32MB AGP
linksys lne100tx (w/wake on lan plugged into the mobo)
on mobo controllers:
ibm 6.4gb hd DTTA-350540 (the boot drive) (pm)
maxtor 541MB hd 7541AP (ps)
btc 36xh cd-rom (sm)
wd 341MB hd WDC-AC2340 (ss)
Normal Floppy Drive (mitsumi)
So I had a PII 266 w/128MB sdram(66) and upgraded to the PIII 533B w/128MB pc133 sdram(133) and when I booted up I got the blue stop screen after the video check during win2k startup. I tried all versions of startup and I pulled sound and nics with the same result.
I verified all settings in the bios and verified that the 133mhz bus is being cut 1/4 for the pci bus (after a bios upgrade). The board actually supports a 150mhz bus so I have confidence in the board. All peripherals were working fine pre-upgrade. It comes down to the processor and ram. Unfortunately, I don't have any other pc133 memory or another pentium that does 100mhz bus let alone 133.
So here is the information I need help with:
I underclocked the system. Running at 100MHz (1/3 cut to pci bus) the system works fine. No errors, no hangups, no boot problems. The inaccessable boot device (let me rephrase, the only boot device) is the 6.4GB hard drive which is the primary master in the system and is obviously accessable.
How does the 133MHz bus interract with the IDE controller onboard the motherboard such that it becomes inaccessable to windows?
Does it actually try running at 133MHz or is it cut back like the PCI bus?
Even stranger, as stated before, I ran bootup to command prompt only so it shows you the progress of bootup. Windows was loading device drivers from the 6.4GB Hard Drive. After the Video loaded (agp.sys or something simmilar) is when the system froze on the bootup. When booting normally or in safemode of any type, the screen flickers half-way through the progress bar (when it usually does), then the keyboard lights flash (per norm) then boom, the inaccessable boot device stop screen.
Any help in understanding this would be appreciated.
Microsoft's knowledge base had no information on this error.
Other information that may be useful:
The iwill card does not have any updates available.
The linksys nics are using the latest drivers from linksys certified by Microsoft, as is the video card.
Sound card was not present for the testing so is not an issue.
The case has a 300Watt power supply.
Motherboard Monitoring states the temperature of the CPU never exceeded 93 degreese F.
The case is cooled with 4 fans, the hard drives have a fan, and the processor has a dual-fan supersink cooler.
The device manager has no ! anywhere at 100MHz.
Points will be awarded to partial and complete answers. I have plenty of points to give away, i'd just like to get this system running the way it should. Any and all help is appreciated. If you need to contact me directly, use: email@example.com
The ultimate question that needs answering in this questions is "What do I need to do to get this system running (and working) at 133MHz bus?" Part of my computers-experience is building systems so I don't need a step-by-step procedure.
On a side note, and probably a different question...
on both systems I have (this and an amd 400 k6-III) when I go to shutdown the system, the last thing that happens gives me a driver_state_failure bluescreen. This ONLY happens on shutdown or restart. The only two things in common on both systems are the linksys lne100tx (plugged into w-o-l on mobo) and the power supply (deer computer co., LTD model LC-300ATX). Not an issue since it only happens on shutdown but if anyone has clues why this oand how to fix it, I'll post another question for it to award points. Again, the knowledge base was no help.