Name: dean_brfc Date: February 18, 2007 at 18:47:22 Pacific Subject: Monitor (?) problems after OCing OS: Windows XP Home CPU/Ram: 512
Comment:
Hi,
I recently tried to overclock my Intel Celeron 2.4ghz via the BIOS settings. I initially did it to 2.6, which showed up fine in the System Information in Windows. I then proceeded to try 3ghz. When I saved and exited from the BIOS, the power cable was knocked out before the computer started to boot up.
Since then my monitor (and another spare) has failed to recognise anything is connected when the computer is turned on. I get the bleeping sound from the computer although the hard-disk activity light stays constantly on after a few seconds. The CD drive light flashes for a while too.
Does anyone have any ideas what may have happened or how I can get something back on my monitor screen? I'm quite desperate so help would be greatly appreciated.
Sorry I forgot to add: I 'THINK' the computer had shut down fully before the cable came out, I'm sure it was almost exactly in the gap between shutting down and restarting.
If you didn't lock the PCI/AGP at their defaults (33/66MHz) or don't have a BIOS option that allows you to lock them, you've raised the FSB too high & the PCI/AGP have gone too far out of spec. 112MHz is the safe max...
I figured the default was 100MHz. Regardless, there are several BIOS settings that need to be addressed when overclocking, not just the CPU freq. There's the PCI/AGP bus, RAM freq, RAM timings, Spread Spectrum (which should always be disabled), CPU & RAM voltages, etc.
You haven't listed the make/model of your board or what speed RAM you're running, so it's difficult to give any suggestions.
Ah sorry, I should have mentioned that. It's an MSI motherboard, model number MS-6787 VER:2. I have two sticks of 256 RAM, one DDR400 and one DDR333, both are CL2.5. I don't know if this makes any difference, but both the graphics and sound are on-board.
You can try clearing the CMOS and reset everything to default values - usually there's a motherboard jumper, but briefly removing the CMOS battery (while unplugged) should accomplish the same thing
I'm not one of those who think Bill Gates is the devil. I simply suspect that if Microsoft ever met up with the devil, it wouldn't need an interpreter.
Thank you everyone for helping, I didn't actually think there was any chance of fixing it after reading horror stories about failed overclocking on the internet. There were indeed some reset jumpers in there, I wouldn't have had a clue had I not asked here though.
That's good - sure, all you'd need to do in most cases would be to reset the CMOS values - those 'horror stories' are no doubt cases where the CPU was damaged.
Now you can start over...
I'm not one of those who think Bill Gates is the devil. I simply suspect that if Microsoft ever met up with the devil, it wouldn't need an interpreter.
The information on Computing.Net is the opinions of its users. Such
opinions may not be accurate and they are to be used at your own risk.
Computing.Net cannot verify the validity of the statements made on this site. Computing.Net and Computing.Net, LLC hereby disclaim all responsibility and liability for the content of Computing.Net and its accuracy.
PLEASE READ THE FULL DISCLAIMER AND LEGAL TERMS BY CLICKING HERE