Mark_C
08-03-01, 09:54 PM
Hi all, this is my first post to the board. I'm hoping you can help me out with this frustrating problem i'm having.
I installed my new motherboard and Duron 900 yesterday and upped the FSB to 112 to get 1008Mhz. (My motherboard is cheap and doesn't have any options for clock alterations.) It worked great, no crashes or any problems, and i ran it for a few hours with several games. I had WinMe installed at the time, so i decided to install Win98se and everything went as normal, until there were consistent lock ups during the installer stage when it asks for drivers. I found out it was due to the overclock, and everything ran smooth at the default 9x100.
Now i've found that any fsb changes, even something as low as 2Mhz causes a lockup of the computer. It's consistent, and happens a few seconds after Windows appears. Oddly, if Scandisk loads and delays bootup until it's finished, my computer doesn't lock up. However it does as soon as it's finished and the icons and startup programs begin to appear. (It may have been a one off, i'll check it again later.)
I'm completely lost on what could be the problem, although i have a feeling it could be the memory. It's 133Mhz ram and should run fine, but it doesn't explain why it was working perfectly before and not now. Is it common for ram to behave like that, where it works fine overclocked for the first few hours, then eventually it fails? I've been running it at 133Mhz Cas3.
Could it be anything to do with when i used a pencil on the L1 bridges? I don't think it would seeing as i'm not changing the clock multiplier and i made sure there was space between the bridges.
Thanks all,
Mark
(Update - When i was typing up this message my computer froze with a long beep, i think it was from WinAmp crashing and not from the motherboard. I have a feeling it's the ram that caused the crash. so i've changed the ram to work at 100Mhz Cas2 at the moment.)
I installed my new motherboard and Duron 900 yesterday and upped the FSB to 112 to get 1008Mhz. (My motherboard is cheap and doesn't have any options for clock alterations.) It worked great, no crashes or any problems, and i ran it for a few hours with several games. I had WinMe installed at the time, so i decided to install Win98se and everything went as normal, until there were consistent lock ups during the installer stage when it asks for drivers. I found out it was due to the overclock, and everything ran smooth at the default 9x100.
Now i've found that any fsb changes, even something as low as 2Mhz causes a lockup of the computer. It's consistent, and happens a few seconds after Windows appears. Oddly, if Scandisk loads and delays bootup until it's finished, my computer doesn't lock up. However it does as soon as it's finished and the icons and startup programs begin to appear. (It may have been a one off, i'll check it again later.)
I'm completely lost on what could be the problem, although i have a feeling it could be the memory. It's 133Mhz ram and should run fine, but it doesn't explain why it was working perfectly before and not now. Is it common for ram to behave like that, where it works fine overclocked for the first few hours, then eventually it fails? I've been running it at 133Mhz Cas3.
Could it be anything to do with when i used a pencil on the L1 bridges? I don't think it would seeing as i'm not changing the clock multiplier and i made sure there was space between the bridges.
Thanks all,
Mark
(Update - When i was typing up this message my computer froze with a long beep, i think it was from WinAmp crashing and not from the motherboard. I have a feeling it's the ram that caused the crash. so i've changed the ram to work at 100Mhz Cas2 at the moment.)