I'm not having very good success with my attempts at overclocking, so I'm looking for some help.
I have:
Asus P5B Deluxe, BIOS rev 0507
Intel E6400 with Scythe Ninja Plus w/a 120mm fan
1 GB stick of Corsair PC 6400 9set to 5-5-5-12 initially, 5-5-5-18 later on)
480w Antec power supply
PCI video card (for a Folding at Home machine a nice video card is not necessary)
6.4gb IDE hard drive
Initially, I had success in getting it running at 2.6ghz stable Folding (350x8, vcore 1.375v). I let it go overnight with no problems. Once I got up to 2.8ghz, it would boot to desktop, but would crash when I ran Orthos. I tried Orthos on small units (stress CPU only, and it was stable, whereas blend/mixed units crashed it; this led me to think memory/chipset volts). I finally got it fairly stable by upping the memory voltage to 2.25 and raising CPU voltage to 1.4v.
When I tried to go up to 3ghz (376x8), the system bluescreened, and upon attempting to reboot, I got a message saying that Windows\system32\confg or some such was corrupted/missing. I was unable to get back into Windows despite numerous attempts, and had to reformat and reload everything.
This time I got it up to 2.8ghz, using different settings: auto on all voltages, and Orthos crashed again. In frustration, I upped the chipset voltages one notch, and got it stable enough to run Orthos for a little while.
I then upped it to 3.2ghz (400x8 @ 1.4v CPU voltage), and found that the temps were 57 idle (too high), so I said forget that, and went back to 3.0ghz, I upped the chipset voltages again. It hard locked up when I ran Orthos. Upon reboot, I got the dreaded corrupted system files again. Luckily I was able to lower it to 2.8ghz and start back up in safe mode, where I was able to do a system restore and get it running again.
I'm a noob at this, but it seems that there is some sort of data corruption issue going on here. I have PCI-E bus set to 100, and PCI bus set to 33mhz. Memory was set to 533mhz/266 (I think this runs it at 1:1, right?). If I had memory at (auto), the system would hard lock up past 2.6ghz.
Or am I missing something obvious?
I have:
Asus P5B Deluxe, BIOS rev 0507
Intel E6400 with Scythe Ninja Plus w/a 120mm fan
1 GB stick of Corsair PC 6400 9set to 5-5-5-12 initially, 5-5-5-18 later on)
480w Antec power supply
PCI video card (for a Folding at Home machine a nice video card is not necessary)
6.4gb IDE hard drive
Initially, I had success in getting it running at 2.6ghz stable Folding (350x8, vcore 1.375v). I let it go overnight with no problems. Once I got up to 2.8ghz, it would boot to desktop, but would crash when I ran Orthos. I tried Orthos on small units (stress CPU only, and it was stable, whereas blend/mixed units crashed it; this led me to think memory/chipset volts). I finally got it fairly stable by upping the memory voltage to 2.25 and raising CPU voltage to 1.4v.
When I tried to go up to 3ghz (376x8), the system bluescreened, and upon attempting to reboot, I got a message saying that Windows\system32\confg or some such was corrupted/missing. I was unable to get back into Windows despite numerous attempts, and had to reformat and reload everything.
This time I got it up to 2.8ghz, using different settings: auto on all voltages, and Orthos crashed again. In frustration, I upped the chipset voltages one notch, and got it stable enough to run Orthos for a little while.
I then upped it to 3.2ghz (400x8 @ 1.4v CPU voltage), and found that the temps were 57 idle (too high), so I said forget that, and went back to 3.0ghz, I upped the chipset voltages again. It hard locked up when I ran Orthos. Upon reboot, I got the dreaded corrupted system files again. Luckily I was able to lower it to 2.8ghz and start back up in safe mode, where I was able to do a system restore and get it running again.
I'm a noob at this, but it seems that there is some sort of data corruption issue going on here. I have PCI-E bus set to 100, and PCI bus set to 33mhz. Memory was set to 533mhz/266 (I think this runs it at 1:1, right?). If I had memory at (auto), the system would hard lock up past 2.6ghz.
Or am I missing something obvious?