3500 winchester on a8v

Radiation · 26 Jun 2007 at 19:03

str said:
Yep if your CPU can handle that speed. The labels for the memory settings are:

tCL (CAS Latency): 2.5
tRTC (RAS to CAS Delay): 4
tRP (RAS Precharge): 4
tRAS (Precharge Delay): 10

There are other sub timings but having them all at auto should work fine.

I changed it to that and it runs at 1:1 and 3:2 but fails at 2:1, what should i do?

Core Speed 2500.3 MHz (10.0 x 250.0 MHz)
HT Link speed 1000.1 MHz
Stock frequency 2200 MHz

3:2
Memory Frequency 208.4 MHz (CPU/12)
CAS# 2.5
RAS# to CAS# 4
RAS# Precharge 4
Cycle Time (tRAS) 10
Bank Cycle Time (tRC) 10
DRAM Idle Timer 16
Command Rate 1T

str · 26 Jun 2007 at 19:11

The motherboard could be changing the sub timings when you use a divider and could be why it's not working properly at 2:1.

If it's stable at 1:1 then that's the best if the max HTT you'll be using is 250.

Radiation · 26 Jun 2007 at 19:15

str said:
The motherboard could be changing the sub timings when you use a divider and could be why it's not working properly at 2:1.

If it's stable at 1:1 then that's the best if the max HTT you'll be using is 250.

Your probably right but why is it when 1:1 is set cpuz shows the ram running at 125Mhz with these settings and similarly with the old settings as well?

str · 26 Jun 2007 at 19:23

Is it the latest version of CPU-Z - it could be a bug with an older version? What's the FSB : DRAM in CPU-Z Memory tab? Can you post screenshots of the main CPU-Z screen and the Memory tab too so can see it.

Radiation · 26 Jun 2007 at 19:46

A few posts above is 3:2 setting with the ram changes you pointed me to but i changed the divider again now to 1:1, heres the part from the output of cpuz.

Memory Type DDR
Memory Size 1024 MBytes
Memory Frequency 125.0 MHz (CPU/20)
CAS# 2.5
RAS# to CAS# 4
RAS# Precharge 4
Cycle Time (tRAS) 10
Bank Cycle Time (tRC) 7
DRAM Idle Timer 16
Command Rate 1T

SOLDNER-MOFO64 · 26 Jun 2007 at 20:16

I'd drop my HTx to 3x to ensure stability and rule it out a possible weak link. Winny's ain't especially known for their fantastic OC'ability and they have their fair share of dodgy mem controllers too.

I dug this out in a hurry....

http://s43.photobucket.com/albums/e364/mofo64/?action=view&current=twinmoss484mhz.jpg

This is on air with my old winny 3500+...1.55v in BIOS on my A8N-SLi deluxe. I found booting into windows with close to stock speeds and timings then adjust via windows with either clockgen or a64info beta. You can change virtually any setting desired this way.

str · 26 Jun 2007 at 20:27

I just did a google search on the A8V Deluxe motherboard and for 1:1 meaning DDR400 when at HTT 200 it's actually 2:1 on the A8V Deluxe so that explains why it's at 125 (DDR250) when using 1:1.

So the 2:1 setting is what you need to use.

Your best bet is to go back to default clocks and leave the memory timings as 2.5-4-4-10 and go into Windows. Download A64Info beta (http://www.xtremesystems.org/forums/showthread.php?t=96678) and do a screenshot of the memory settings and post it here. You can screenshot it by having the program as the active window and then pressing alt-print screen. Then open MSPaint and change the canvas to a little block then do Edit menu -> Paste to add the screenshot and then save it as a JPG then upload it via www.imageshack.us or some other place.

It's likely for you to get DDR550 (2:1 at 250 HTT) working you'll need to change some of the sub timings and I'll need to see the current settings at DDR400/200HTT to be able to help with that.

SkeeterUK · 26 Jun 2007 at 21:26

I did tell him to use 2:1 not 1:1 but didnt work for him he said.

SOLDNER-MOFO64 · 26 Jun 2007 at 21:30

Is it perhaps as a result of dropping the cpu multi that the memory dividers are screwy?

It's default is 11. If he boot's at default cpu and memory (with 250mhz timings set manually), he should be able to walk that chip upto 2750mhz on air with decent temps no problem
(memory 250mhz/ht multi x4/200mhz divider)

I'd hazard a guess at 1.450v set in BIOS, maybe 1.475v.

Radiation · 27 Jun 2007 at 14:46

SOLDNER-MOFO64 said:
I'd drop my HTx to 3x to ensure stability and rule it out a possible weak link. Winny's ain't especially known for their fantastic OC'ability and they have their fair share of dodgy mem controllers too.

I dug this out in a hurry....

http://s43.photobucket.com/albums/e364/mofo64/?action=view&current=twinmoss484mhz.jpg

This is on air with my old winny 3500+...1.55v in BIOS on my A8N-SLi deluxe. I found booting into windows with close to stock speeds and timings then adjust via windows with either clockgen or a64info beta. You can change virtually any setting desired this way.

nice overclock there, id be too worried to go anywhere near that, but now im wondering whats a safe overclock then for these cpu's?

I was thinking about 200mhz or 300mhz is ok, i had a crash on boot today with the settings i used last night so im on default atm, im thinking about forgetting the ram and leaving it at around 200mhz and going 11x 220mhz on the cpu at 2.4ghz for now, i only really just want to squeeze a nice bit extra out.

About the ram, yeah seems its 2:1, i was also wondering are lower timings quicker in some way or is slightly higher timings with more mhz faster, was always a bit confused how that works?

SOLDNER-MOFO64 · 27 Jun 2007 at 18:15

Radiation said:
nice overclock there, id be too worried to go anywhere near that, but now im wondering whats a safe overclock then for these cpu's?

Yeah cheers, I took it to 3116mhz Pi 16M stable with WC and 1.600v in BIOS on my ULTRA-D. I'll dig out the pics later tonight. For me, with decent air-cooling.....2800mhz was a piece of cake and ran PRIME stable for 8hr+.

I was thinking about 200mhz or 300mhz is ok, i had a crash on boot today with the settings i used last night so im on default atm, im thinking about forgetting the ram and leaving it at around 200mhz and going 11x 220mhz on the cpu at 2.4ghz for now, i only really just want to squeeze a nice bit extra out.

About the ram, yeah seems its 2:1, i was also wondering are lower timings quicker in some way or is slightly higher timings with more mhz faster, was always a bit confused how that works?

Both, depending on which bench you run. Some apps prefer tight timings and low latency. Some on the other hand prefer higher bandwidth and loose timings. If you can gain an extra 50mhz-100mhz of bandwidth it's usually more beneficial than to have lower bandwidth and tighter timings. If however you find you need to drop a memory divider in order to max your CPU's FSB and can't quite get your memory back up to it's rated speed...then tightening the timings at that lower speed would then be beneficial.

It's trial and error with most configs.

Radiation · 3 Jul 2007 at 11:08

Its now been a while and it seems stable, im running 228MHz fsb at x11 for 2508MHz, ram is 5:3 with quicker timings and running over its default MHz at 209MHz, done memtests and prime now and then, temps no higher than 50c on load, do you think i should leave it be or try to get it up to 2600MHz?