OC Help

[gvblake22]

Orthos should just say there was an error of some kind and stop the test. If your computer is freezing up, you can consider that very unstable and the same as an error.

[Yellowhello]

Originally Posted by gvblake22

Orthos should just say there was an error of some kind and stop the test. If your computer is freezing up, you can consider that very unstable and the same as an error.

OK, so that means that a BIOS update did nothing to help my OC. Thanks for the info, though.

[Yellowhello]

Final OC:

CPU-Z Validator Database
__________________________________________________ __

How I got this (to help with other peoples problems):
I set the multiplier to 6 (x6, for 1.2GHz) and restarted.

Set the FSB to 1400QDR (350FSB, for 2.1GHz) and 1.4V and restarted.

Set multiplier to 7 (x7, for 2.45GHz) and restarted.

Booted into Windows sucessfully and ran Orthos for 15 min, no errors and restarted.

Set multiplier to 8 (x8, for 2.8GHz) and restarted.

Set brought FSB down to 1333QDR (333FSB) and multiplier to 9 (x9, for 3.0GHz) and restarted.

Booted into Windows, ran Orthos for 15 min, no errors, and restarted.

Temps were too high, so brought voltage down to 1.375V and restarted.

Booted into Windows and ran Orthos for 2 hours, no errors.
___________________________________________

For some reason, lowering the multiplier and raising the FSB, then slowly raising the multplier works for me. RAM is running in 1:1 with FSB, for 667DDR2, almost stock on stock voltage.

Hope this helps for anyone having trouble OCing an E4300 on an ASUS P5N32-E SLI Plus. I'm happy though!!

[KillingField]

That's not a bad OC, but the E4300's should do much better on your board, maybe you jst got unlucky and got a weak chip.
Mine will run that at all default settings, it'll do 3.2 with a small bump in vcore (1.36) and up to 3.4 at 1.47. Water cooling does help out a little though.