I have a DFI CA-63SN. In the BIOS (award) there is a setting for the CPU FSB speed (also has jumpers) and there is a setting for ther DRAM Clock (no jumpers).
When i set the CPU to "auto" via jumpers, it correctly detects the Intel 600EB to be 133MHz FSB. The DRAM Clock sits at "HCLK-33". This made sense, when I had PC100 memory installed. I recently tried using PC133 (certified, from Micron) and the setting remained at "HCLK-33". Ok, I say, and i double check the RAM specs on Micron's site, as well as using a utility to snoop the SPD chips to confirm it's PC133 (it is).
So, I figure, what the heck and I set the DRAM Clock setting to "HCLK" (when FSB is at 133, there is an "HCLK" and "HCLK-33
). Now, upon reboot, I get a steady series of beeps (believed to indicate no memory). I've tried clearing CMOS using jumper and popping battery and shorting the battery holder contacts. The only way I can get this thing to boot, now, is to manually strap the CPU FSB to 100Mhz, which allows the RAM to run also at 100MHz (recall the HCLK setting I made in BIOS). Nothing I do seems to clear the HCLK setting and when booted up at 100MHz FSB there is not an option to drop DRAM Clock back to "-33". That setting appears to be an option only when FSB is set to 133, which I can no longer boot with because of the damn HCLK setting which causes this PC133 RAM to fail or the mobo to fail in detecting it.
I realize this is most likely an issue with the PC133 RAM and Mobo not getting along, but the bottom line at this point is:
HOW can I get my BIOS to a) REALLY clear itself and reconfigure everything on reboot or b) Get that setting in BIOS back to "HCLK-33" so it'll boot with 133MHz FSB again?
Any help is appreciated. I must be missing something obvious here, because it just shouldn't be this difficult (ya, right).
Thanks,
-LB
When i set the CPU to "auto" via jumpers, it correctly detects the Intel 600EB to be 133MHz FSB. The DRAM Clock sits at "HCLK-33". This made sense, when I had PC100 memory installed. I recently tried using PC133 (certified, from Micron) and the setting remained at "HCLK-33". Ok, I say, and i double check the RAM specs on Micron's site, as well as using a utility to snoop the SPD chips to confirm it's PC133 (it is).
So, I figure, what the heck and I set the DRAM Clock setting to "HCLK" (when FSB is at 133, there is an "HCLK" and "HCLK-33
). Now, upon reboot, I get a steady series of beeps (believed to indicate no memory). I've tried clearing CMOS using jumper and popping battery and shorting the battery holder contacts. The only way I can get this thing to boot, now, is to manually strap the CPU FSB to 100Mhz, which allows the RAM to run also at 100MHz (recall the HCLK setting I made in BIOS). Nothing I do seems to clear the HCLK setting and when booted up at 100MHz FSB there is not an option to drop DRAM Clock back to "-33". That setting appears to be an option only when FSB is set to 133, which I can no longer boot with because of the damn HCLK setting which causes this PC133 RAM to fail or the mobo to fail in detecting it.
I realize this is most likely an issue with the PC133 RAM and Mobo not getting along, but the bottom line at this point is:
HOW can I get my BIOS to a) REALLY clear itself and reconfigure everything on reboot or b) Get that setting in BIOS back to "HCLK-33" so it'll boot with 133MHz FSB again?
Any help is appreciated. I must be missing something obvious here, because it just shouldn't be this difficult (ya, right).
Thanks,
-LB