superfrank
n00b
- Joined
- Sep 12, 2007
- Messages
- 3
I have a Gigabyte GA-965P-DS4 motherboard and the E6600 (2.4GHz core 2 duo). Last night I was fiddling in BIOS settings trying to find a setting that would make Linux recognise the IDE controller. During the process I inadvertently caused the machine to boot up with a clock speed of ~1.6GHz instead of 2.4GHz. Due to a failure of mental arithmetic and common sense (and partly due to the fact I had drunk a beer or two), my solution was to set the multiplier to 8 and the FSB to 400MHz. Yes yes, in hindsight its very obvious that I don't have a 3.2GHz chip with 600MHz RAM!
Anyway as you may be able to guess, when I rebooted the machine with these idiotic settings, it failed to boot, and the lights on the front panel were flashing on and off. I quickly realised my mistake and knew that I would have to reset the CMOS to get it working again. Well after I did this the machine still would not boot up - instead, it switches on for about 10s then switches off for about 5s and repeats this ad infinitum.
At this stage I expect that I have fried either the CPU, the RAM or the motherboard......its gonna be a pain working out which one is dead though!
Anyway as you may be able to guess, when I rebooted the machine with these idiotic settings, it failed to boot, and the lights on the front panel were flashing on and off. I quickly realised my mistake and knew that I would have to reset the CMOS to get it working again. Well after I did this the machine still would not boot up - instead, it switches on for about 10s then switches off for about 5s and repeats this ad infinitum.
At this stage I expect that I have fried either the CPU, the RAM or the motherboard......its gonna be a pain working out which one is dead though!