• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Problem Overclocking Opteron 165. Please Help.

gozulin

Senior member
First off, here are my SPECS:

LanParty UT SLI-DR (BIOS 06/23/2005)
Opteron 165 @ 2565Mhz
Scythe Ninja HeatSink + 120mm Nexus fan
1x1GB G.Skill PC4000 DDR 500 @ 200 Mhz (Underclocked)
eVGA 7800GT PCIe
2x250Gb + 200Gb SATA (Seagate Barracuda 7200.8)
OnBoard sound
Fortron 550W
Antec P-180
NEC 3500A DVD+RW


I followed the overclocking guide to establish the max o/c values for my CPU and my RAM.

CPU: 2565 Mhz passed 8 hours Prime95 (real max value between this and 2700Mhz)
RAM: 270 Mhz passed 8 hours Memtest86

Now, I obtained the CPU value by using a 1:2 divider on the RAM and I obtained the RAM value by using a 6.0X multiplier on the cpu (As the guide suggests)

My problem is that when I bumped the CPU back to 2565Mhz and tried to get the RAM up to at least 250Mhz , it wouldn't work. Depending on the value, the computer would freeze at any given point between the time I hit the power button and the time the windows desktop is supposed to show up.

While keeping the CPU at 285 x 9.0X , the max divider I can use on my ram so that I can boot up windows is 7:10 which gives me (.7 x 285 = 200Mhz).

As you will understand, I'm not exactly happy with having to run my RAM underclocked by 20%. There has got to be something I'm doing wrong here. And because a picture is worth a thousand words, here are pictures of my Bios settings:


CPU1
CPU2
RAM1
RAM2
MISC
MISC2
MISC3
MISC4
 
I've found Memtest to be horribly unrepresentative of real world stability. Have you tried booting into Windows with the CPU at stock and RAM oced? If that works, try running Prime blend test and see how long you're able to go for. Also, what kind of chips does your RAM use?
 
Originally posted by: mrkun
I've found Memtest to be horribly unrepresentative of real world stability.

Maybe I don't understand what you mean, but I would never consider a computer "stable" that had any errors from memtest. In real world situations, an occasional memory error might cause a blue screen or lock up, but worse, it might not show up as anything except that some of your data is corrupted.

If you have your memory clocked so high that you get memtest errors, either raise your memory voltage to see if the errors stop or back off on the clock rate.
 
Originally posted by: FullRoast
Originally posted by: mrkun
I've found Memtest to be horribly unrepresentative of real world stability.

Maybe I don't understand what you mean, but I would never consider a computer "stable" that had any errors from memtest.

If you have your memory clocked so high that you get memtest errors, either raise your memory voltage to see if the errors stop or back off on the clock rate.

You don't understand what he means. He was saying that EVEN though my memory PASSED memtest at 270Mhz, it didn't mean it would be stable in windows.

What memtest errors? Please re-read my post.
 
So yeah, I just primed the RAM at 260Mhz (with cpu multiplier at 6x) for an hour and there were no errors. (I used 400 mb for each core instance).
 
Originally posted by: gozulin
So yeah, I just primed the RAM at 260Mhz (with cpu multiplier at 6x) for an hour and there were no errors. (I used 400 mb for each core instance).


Ok, now try 270 on Prime and see what happens. Also, what did you mean by the real max value for your CPU being between 2565 and 2700?
 
Back
Top