I've been running an FX 53 at 2600 Mhz using 13x200 and I thought I would give a stab at some FSB tinkering and look into this DDR 500 thing. Problem is I'm using dual WD740s in RAID0 on the nvidia SATA controller.
Ive heard of FSB OC problems with SATA drives before...
On my FX-53, K8N Neo2, and 2x512 Corsair XL, I am able to run a 250 Mhz FSB and get DDR500, using a CPU multiplier of 10 (grrr cmon MSI , I need 10.5!) and HT at 4x250 = 1000, AGP at 66.
Now I know this isnt a memory problem, because I can boot from an IDE DVD drive with a memory test program and let it run all day without problems. I had some problems with bad hardware that had to be RMA'ed (ie: first stab at the XL ram gave errors even at stock speeds at 2-2-2-5-1T @ DDR400 @ 2.75v)
so I've held up on running anything beyond spec until I can be sure the hardware runs ok AT spec.
But now that I have Windows installed and everything set up with working components I looked into setting up the 10x250 for DDR 500 operation.
The POST hangs on the nvidia SATA bios, after reporting the array is healthy, etc. Normally it proceeds to the device listing and the XP bootstrap, but it hangs here, and eventually reboots in MSI BIOS safe mode or requires a hard reset.
I know its not the CPU, it can run fine at 13x200, and even setting to 9x250 still doesnt help.
AGP and PCI should be locked at 66 Mhz, and HT is set as 4x250 = 1000, the only thing that should be running at 250 is the DDR interface on the CPU right? How is this affecting the SATA controller on the nVidia chip? I thought it might be something to do with the SATA DMA so I disabled that, no change. Is there some other relationship between the FSB and the nForce3 that would cause a higher FSB to affect the SATA controller?
It's not a big deal, Id rather have SATA RAID, but it's puzzling me.
Ive heard of FSB OC problems with SATA drives before...
On my FX-53, K8N Neo2, and 2x512 Corsair XL, I am able to run a 250 Mhz FSB and get DDR500, using a CPU multiplier of 10 (grrr cmon MSI , I need 10.5!) and HT at 4x250 = 1000, AGP at 66.
Now I know this isnt a memory problem, because I can boot from an IDE DVD drive with a memory test program and let it run all day without problems. I had some problems with bad hardware that had to be RMA'ed (ie: first stab at the XL ram gave errors even at stock speeds at 2-2-2-5-1T @ DDR400 @ 2.75v)
so I've held up on running anything beyond spec until I can be sure the hardware runs ok AT spec.
But now that I have Windows installed and everything set up with working components I looked into setting up the 10x250 for DDR 500 operation.
The POST hangs on the nvidia SATA bios, after reporting the array is healthy, etc. Normally it proceeds to the device listing and the XP bootstrap, but it hangs here, and eventually reboots in MSI BIOS safe mode or requires a hard reset.
I know its not the CPU, it can run fine at 13x200, and even setting to 9x250 still doesnt help.
AGP and PCI should be locked at 66 Mhz, and HT is set as 4x250 = 1000, the only thing that should be running at 250 is the DDR interface on the CPU right? How is this affecting the SATA controller on the nVidia chip? I thought it might be something to do with the SATA DMA so I disabled that, no change. Is there some other relationship between the FSB and the nForce3 that would cause a higher FSB to affect the SATA controller?
It's not a big deal, Id rather have SATA RAID, but it's puzzling me.