Another Opteron 165 thread

[smokeyjoe]

I posted this in another thread that seems to have died so..

I've got a 165 CCBBE that I can run on ORTHOS for an hour with no problems at 315*9 and 1.35v on my ASUS premium. This is with my RAM set at 200 mhz divider 3-5-5-8 2T in BIOS - basically the largest/slowest divider and really loose timings.

I have tried changing the divider to 266 mhz which would put me at 2835/14 = 202.50 Mhz with the same loose timings, but I can't even get into windows. Kind of bummed about that, I thought this RAM would be ok with a 2.5 Mhz increase?

I just copied and pasted the above.. I now have my 165 at 300*9 and still cannot run my RAM at anything above the 200 divider. My RAM should be able to run at the 266 divider which would slightly under clock it to 192 mhz, shouldn't it? I must be missing something here..

I am still new at overclocking, anyone have any suggestions on what to set my RAM?

 

[lopri]

There are timings that needs to be adjusted and then there are timings that are hidden from users. In your board's BIOS, check the memory timing section and see if there are 'Max Async latency' and 'read preamable'. If their values are adjustable, try loosening them by 1~2 ns.

 

[smokeyjoe]

I don't have these options on my ASUS board.. currently using 1009 Bios. Anyone running an updated bios for this board that has more memory options?

 

[myocardia]

You definitely need to update your BIOS, if it's more than 9 or 10 months old, because you should be able to run your RAM @ it's default timings, including 1T command rate, using the 133/266 DDR divider. Have you tried the 166/333 DDR divider, with the timings you're using, and 2.70v of vdimm?

 

[JustAnAverageGuy]

The latest a8n-sli premium bios (1302 beta) doesn't offer any more options, but then again, nobody knows what it does.

Asus's changelogs are nowhere to be found :roll:

1302 is a stable release though. Used it for months with no problems

- JaAG

 

[smokeyjoe]

Originally posted by: JustAnAverageGuy
The latest a8n-sli premium bios (1302 beta) doesn't offer any more options, but then again, nobody knows what it does.

that's pretty much why I haven't updated since 1009..

Originally posted by: myocardia
You definitely need to update your BIOS, if it's more than 9 or 10 months old, because you should be able to run your RAM @ it's default timings, including 1T command rate, using the 133/266 DDR divider. Have you tried the 166/333 DDR divider, with the timings you're using, and 2.70v of vdimm?

I just now was able to get the 266 and 333 divider to work at cpu speed of 266*9=2394.. haven't tested stability at all. Currently on 333 divider, RAM at 218mhz, 3-4-4-8 1T. I don't see why the 266 divider won't work at 2700? ( Is it common for a divider not to work at a higher cpu clock speed?

Also, my vdimm is 2.75

 

[smokeyjoe]

Well.. I updated my BIOS to 1302 and I still can't use the 266 divider with my clock speed at 2700 >< I have it set to the 200 divider now and my ram is running at 150 Mhz

If I could just hit 3.6 with this cpu then I would be ok with that divider hehe

Any help, suggestions or similar experiences is greatly appreciated

Thanks and Merry Christmas

 

[smokeyjoe]

Well.. I'm bumping my old thread since I still can't figure this out

Right now I am running at 300*8 on the 266 divider with no problems at all. I can't seem to wrap my head around why I can't run at 300*9 on the 266 divider It would be under clocking my RAM slightly to 192 mhz.. whereas now I am right at 200 mhz at the same FSB.

I didn't think the higher clock speed would matter as long as my RAM ran at or around its rated speed??

 

[inveterate]

fuk bioses,, I haven't updated in a YEAR and it's runnign STRONG

 

[Regalk]

smokey - did you ever get the OC going? I have the Asus A8N-E and
my opty 144 maxed out to around 303 with OCZ gold PC4000 (166 mem)
swapped out to a 3200+ and changed RAM to PC3200 OCZ and maxed out at 320 X 9 (133 mem)
In both cases i had to up my voltages to around 1.55 vcore and DDR volts at 2.85
I had to manually set the timings for the RAM
I do not hink updating bioses will help at this stage as the Socket 939 is pretty much mature now so new bioses may only be for the 5000+ or higher

 

[smokeyjoe]

no, the max I can run the 266 divider on is apparently 2.4 mhz. I don't get it.. and I haven't given up searching for an anser, at least for tonight haha

 

[rogue1979]

I have a Biostar Tforce running a sempron 2800+ at 312 (2500MHz). I had to set the ram divider to 100MHz, it should run 133 at that fsb.

Just cranked the memory timings to cas 2, 10-2-2-2 1T. It benchmarks just fine, I don't worry about it.

 

[smokeyjoe]

yea, it should run on the 266 Divider at 300*9.. but, she doesn't want to

 

[TheFamilyMan]

I had the same issue as you at first but went into BIOS and set it to 'Auto' and now it goes into 266 mode. I tried manually setting it to 266 with timings recommended by GSkill at that speed and it wouldn't get past post. Once I set it to 'Auto', not only did it set to 266 but the timings were actually being set tighter than GSkill was indicating on their spec sheets. Booted into Windows and verified via CPUz memory.

My setup is as follows:

Opteron 165 w/ Zalman 330*9 ~2.97gHz
Asus A8N-SLI Premium
2gb GSkill DDR400 @ 2.5-3-3-5-2T @ ~433mHz DDR

The CPU is at 1.40v idling around 38C and maxing out ~49C full load. I'm thinking of picking up the Vigor CLT-M2A TEC cooling solution to get the temps down. I can get into Windows at 350mHz but temps are too high for me to be comfortable with just utilizing air and the ram isn't stable running near DDR500 specs.

 

[smokeyjoe]

Nice, thanks for the input. We have similar setups. I haven't fooled with it too much over the holidays but will again soon. That's a nice over clock on air too.

I noticed your ram is at 2T.. do you have just 2 sticks? Have you tried running in 1t?

 

[TheFamilyMan]

I haven't tried the ram @ 1T yet but will. I wanted to get it completely stable first and use it for a bit at the stable settings. I'll start monkeying with the details this week probably.