- Feb 2, 2008
- 2,219
- 221
- 101
Power supply
bad RAM
CPU voltage set too low
RAM voltage set too low
overheating northbridge
northbridge voltage too low
I'm using a DS3L 2.0 with an e2140 and I've been having buggy behavior in XP (like incorrect time clock after reboot) and OS X (strange behavior in Garageband). However, I've done quite a bit of stability testing and nothing came up Memtest, Orthos, Prime95, etc. My temps are low according to the latest Speedfan beta (as well as CoreTemp). Cores never got above 50 and the rest of the temps were low. My PSU voltages appear to be stable, although the 12 volt reading has never worked.
I dropped my BIOS voltage from 1.350 to one notch down and did some more stability testing. After three hours of Prime95 running at High priority, the system abruptly rebooted. I've had issues with random spontaneous rebooting since I first put the system together, although this is the first time it's happened in a long time. I assume that lowering the CPU voltage did the trick and that the problem only reared its head once the CPU was sufficiently hot (as it's more sensitive to insufficient voltage when hot as far as I've read).
However, I'm also concerned that perhaps my northbridge voltage is too low. Is stock OK for 375 FSB speed? I've read posts saying it's OK to run at 400 at the stock voltage, but that seems odd since it's such an increase over the 333 reference limit of the chipset.
I have raised the voltage back to 1.350 but wonder if hours of stability testing won't uncover the actual issue. Any tips? Is it perhaps a flaky PSU? I have a Seasonic S-12 II 380 watt unit.
What could be causing the incorrect time clock issue? Maybe I need to check the BIOS to make sure it's set correctly. I have both operating systems set to Eastern and net synching.
bad RAM
CPU voltage set too low
RAM voltage set too low
overheating northbridge
northbridge voltage too low
I'm using a DS3L 2.0 with an e2140 and I've been having buggy behavior in XP (like incorrect time clock after reboot) and OS X (strange behavior in Garageband). However, I've done quite a bit of stability testing and nothing came up Memtest, Orthos, Prime95, etc. My temps are low according to the latest Speedfan beta (as well as CoreTemp). Cores never got above 50 and the rest of the temps were low. My PSU voltages appear to be stable, although the 12 volt reading has never worked.
I dropped my BIOS voltage from 1.350 to one notch down and did some more stability testing. After three hours of Prime95 running at High priority, the system abruptly rebooted. I've had issues with random spontaneous rebooting since I first put the system together, although this is the first time it's happened in a long time. I assume that lowering the CPU voltage did the trick and that the problem only reared its head once the CPU was sufficiently hot (as it's more sensitive to insufficient voltage when hot as far as I've read).
However, I'm also concerned that perhaps my northbridge voltage is too low. Is stock OK for 375 FSB speed? I've read posts saying it's OK to run at 400 at the stock voltage, but that seems odd since it's such an increase over the 333 reference limit of the chipset.
I have raised the voltage back to 1.350 but wonder if hours of stability testing won't uncover the actual issue. Any tips? Is it perhaps a flaky PSU? I have a Seasonic S-12 II 380 watt unit.
What could be causing the incorrect time clock issue? Maybe I need to check the BIOS to make sure it's set correctly. I have both operating systems set to Eastern and net synching.
Facebook
Twitter