nforce2 200 FSB???

[krypptic]

I have a quick question,

If i can run my cpu asynch @ 200 fsb with ram at 333 stable and
I can run my cpu asynch @166 with ram at 400 stable shouldn't
I be able to run them synched at 200?

I know nforce2 boards should be run at 1:1 fsb/ram ratio.
I just thought if it was possible asynch, it would be possible synched.

I have been able to run 11 x 185 stable in prime95 (synched)
but any higher the fsb causes an error in the 1st minute.

And 200 FSB won't post at any multiplier. I couldn't figure that one out.

Temps don't appear to be an issue since at stock speed cpu temp is 36
and oc'd it goes up 1 or 2 degrees.

I have tried raising vcore, but this has no effect until I hit 1.75 which only
raises temps to 40.

Anyone have any ideas?

 

[ianching]

I have had this problem before with the 8RDA. It does 225FSB only with a 5x multiplier but it won't even do 210FSB at 2.1GHz (10*210). However, after some BIOS tweaking, it's now doing 220FSB (10*220) with a 1700+, I simply changed the "Optimal" settings in the CPU Interface (under Adanced Chipset Features) to "Aggressive".

Not sure if it works on your board or not but worth a try. Also, is your board a nForce2 400 Ultra?

 

[bgeh]

Originally posted by: krypptic
I have a quick question,

If i can run my cpu asynch @ 200 fsb with ram at 333 stable and
I can run my cpu asynch @166 with ram at 400 stable shouldn't
I be able to run them synched at 200?

I know nforce2 boards should be run at 1:1 fsb/ram ratio.
I just thought if it was possible asynch, it would be possible synched.

I have been able to run 11 x 185 stable in prime95 (synched)
but any higher the fsb causes an error in the 1st minute.

And 200 FSB won't post at any multiplier. I couldn't figure that one out.

Temps don't appear to be an issue since at stock speed cpu temp is 36
and oc'd it goes up 1 or 2 degrees.

I have tried raising vcore, but this has no effect until I hit 1.75 which only
raises temps to 40.

Anyone have any ideas?

do you have the Nforce 2 Ultra or the A1/C1 chips or is your board a Rev. 2?
the others have difficulty hitting 200FSB

 

[krypptic]

I do have the ultra 400 chipset, with the c1 northbridge.

Still can;t figure it out, I guess I won't be reachin the 200 fsb any time soon.

 

[MatthewF01]

question, slightly off topic:


I have a Chaintech 7NJS Nforce2 motherboard. My chipset is just the original stepping, with the silver circle and everything. My question is, are manufacturers switching to the newer revisions, or even 400 Ultra, without moving to a new model?

For example... if I RMA'ed my board back to Newegg and got a new one, would it be the newer chipset?


Plus what kind of improvements does it yield when moving to the newer revisions? I am running at 217*8.5 on an 1800+ TbredA with Corsair 3200c2 @2.8v

thanks

 

[hans007]

Originally posted by: krypptic
I have a quick question,

If i can run my cpu asynch @ 200 fsb with ram at 333 stable and
I can run my cpu asynch @166 with ram at 400 stable shouldn't
I be able to run them synched at 200?

I know nforce2 boards should be run at 1:1 fsb/ram ratio.
I just thought if it was possible asynch, it would be possible synched.

I have been able to run 11 x 185 stable in prime95 (synched)
but any higher the fsb causes an error in the 1st minute.

And 200 FSB won't post at any multiplier. I couldn't figure that one out.

Temps don't appear to be an issue since at stock speed cpu temp is 36
and oc'd it goes up 1 or 2 degrees.

I have tried raising vcore, but this has no effect until I hit 1.75 which only
raises temps to 40.

Anyone have any ideas?

youve got the msi k7n2 delta -l.

my board... is the k7n2g-l revision A2 igp. i can run 166bus with 400 mhz memory cas3. but when i run 200bus it only runs at 166 cl 2.5 memory. if i run at 200 cas3 it is flakey. granted my ram is only rated at 166bus pc2700 cl2.5.

i tried some other pc2700 ram and it wont even post at 200 memory cl3 200 bus for the cpu. so i guess i need better ram. but you having the newer chipset, on same pcb basically i'm sure its just some ram problem.