If everything stayed the way it was described above, except CPU frequency is set to 400 and DRAM @ 800, it will boot successfully into Windows, then be very unstable. If I let my system run for a while (surf a bit, chat a bit), I will eventually get a BSOD. When I start to run SuperPI or Memtest, the system will immediately freeze.
I do not know how to reach a stable 3.2GHz, so I call on this wonderful community's expertise to help me. What other settings do I need to adjust to achieve 3.2GHz? Help is very much appreciated and I will be glad to answer questions that will assist you in helping me Thanks a ton.
If it helps, I tried running my CPU @ 266 and ram @ 400, 4-5-4-15, 2.1V today and it was memtest 7h stable. I need to be pointed in the right direction of what settings to change to get stable 3.2GHz =/
I tried to set ram to 4-5-4-15 with all the other settings the same, but it won't boot into BIOS @ 370-400FSB. I have to enable timing by SPD to boot into windows.
Gee, really do hope its not a northbridge cooling problem. I've read some stuff about the mobo over @ xtremesystems http://www.xtremesystems.org/forums/showthread.php?t=11... and I doubt its the northbridge overheating. However, it's been speculated...so I'll put a fan over there just in case.
I've disabled DRAM throttling @ 400FSB, and I get the same behavior as before.
I've gone all the way up to 1.5Vcore, but I get the same thing.
If 3.0GHz is the ceiling with this, i'm gonna I'll try every single combination in BIOS till it works.
I have a Seagate Barracuda 7200.10 SATA 3.0Gb/s 320-GB Hard Drive
Thanks for the reply mugz. What calculation do I need to make to synch the PCI-E clock to the FSB? At 3.2GHz, I tried 105-115MHz PCI-E frequency. It would BSOD the instant I got into windows with a 0x0000007E or 0x0000007F or 0x0000008F or win2k.sys error.