Heh so my Nforce2 arrived last night. After much trouble and headache and lack of sleep, I have windows up and running again, and am beginning to get everything back in order (to see what I had to do, check out this: http://forums.anandtech.com/messageview.cfm?catid=34&threadid=936303 )
so then I tried to overclock a little.
To begin, my processor is an 1800+ Palo, LOCKED. The bios currently on this board (11/18) HAS the multiplier adjustments so ill unlock soon, but that shouldnt be holding me back here for now.
Im running 2 sticks of 256MB Samsung PC2100 in the DualChan. configuration. These arent great sticks of RAM, I cant even ever change the CAS Latency without having issues. Same way when I ran them on my K7S5A.
Now, I know these sticks have a LIL headroom in them, cuz when i used to run a 1.2 Tbird, I had my FSB at 150 and they ran FINE. I then ran then at 138 stable with my 1800+ on the K7S5A.
NOTE this board was preloaded with the 11/18 or whatever BIOS.
So I went into the BIOS here, took up the Vcore voltage, tried 1.775, 1.8, and 1.85.
Also, I raised the VDimm voltage to 2.7 but noticed that upon reentering BIOS, the setting did NOT STICK. Anyone have a solution on that?
Next I put the FSB at just 135 to see if it would even do that. I put CPU interface to Aggressive, RAM to Sync, and left RAM timings at optimal. Locked AGP at 66mhz.
Reboot. Nothing.
It will take 134, but when it reboots it says memory frequency=133mhz.
What gives? Is this ram just holding out on me? I have a stick of Corsair XMS 3200 on the way, but still. What is the problem here? I do not at all think the ram is the problem.
suggestions?
thanks.
so then I tried to overclock a little.
To begin, my processor is an 1800+ Palo, LOCKED. The bios currently on this board (11/18) HAS the multiplier adjustments so ill unlock soon, but that shouldnt be holding me back here for now.
Im running 2 sticks of 256MB Samsung PC2100 in the DualChan. configuration. These arent great sticks of RAM, I cant even ever change the CAS Latency without having issues. Same way when I ran them on my K7S5A.
Now, I know these sticks have a LIL headroom in them, cuz when i used to run a 1.2 Tbird, I had my FSB at 150 and they ran FINE. I then ran then at 138 stable with my 1800+ on the K7S5A.
NOTE this board was preloaded with the 11/18 or whatever BIOS.
So I went into the BIOS here, took up the Vcore voltage, tried 1.775, 1.8, and 1.85.
Also, I raised the VDimm voltage to 2.7 but noticed that upon reentering BIOS, the setting did NOT STICK. Anyone have a solution on that?
Next I put the FSB at just 135 to see if it would even do that. I put CPU interface to Aggressive, RAM to Sync, and left RAM timings at optimal. Locked AGP at 66mhz.
Reboot. Nothing.
It will take 134, but when it reboots it says memory frequency=133mhz.
What gives? Is this ram just holding out on me? I have a stick of Corsair XMS 3200 on the way, but still. What is the problem here? I do not at all think the ram is the problem.
suggestions?
thanks.
Facebook
Twitter