any program that unlocks my fsb and core speeds on amd64 3200+ winchester? I want to OC but not using some newbish 5%, 7%, 11% system. we all know higher fsb is better than equa-raise fsb and multiplier, so i want to muck around in that department.
tired of MSI dynamic overclocking program
- Thread starter mdchesne
- Start date
Disable it in the BIOS,... along with any spread spectrum, cool n' quiet, or aggressive timings. Also set your memory timings / latency manually.
Yeah, everything should be there in BIOS. I know it is for me, and my board is older than yours, so you should have those options available.
Pr0d1gy
Diamond Member
- Jan 30, 2005
- 7,774
- 0
- 76
Is there anything that will tell us what each of the settings actually is, since they call them odd names? I need to adjust the timings on my RAM just to make it run correctly.
-Hey did either of you MSI mobo users have to install SATA drivers for your hard drives? I am trying to use a Raptor on my Neo4 SLI mobo, but it doesn't want to take...?
-Hey did either of you MSI mobo users have to install SATA drivers for your hard drives? I am trying to use a Raptor on my Neo4 SLI mobo, but it doesn't want to take...?
Jeff7181
Lifer
- Aug 21, 2002
- 18,368
- 11
- 81
Disabling Cool 'n' Quiet isn't a necessity. I have mine overclocked and I leave Cool 'n' Quiet enabled. As long as the CPU is getting enough voltage to run at the speed it throttles down to, there's no reason you can't use Cool 'n' Quiet. With mine, it runs 1125 MHz on 1.2V and idles between 30 and 33 C depending on room temp... as opposed to 44-46 with Cool 'n' quiet disabled running 2475 MHz on 1.45V.
Well, I'm not using SATA, but here's what I understand. If you're doing RAID, then yeah, you'll need to use the drivers (good ol' "F6" thing). If not, then I really don't think you do, however, I am not certain, as I don't use SATA. The best advice I can give is to use different ports, and configure your BIOS to NOT use RAID (mine has an option). Hope this helps, and I wish I could be of more help.
Sure not a problem. Here is usually how RAM timings look like. You normally have:
Cas Latency
Ras Precharge (TRP)
Ras To Cas Delay (TRCD)
Motherboard Cycle Time (TRAS)
When people and manufacturers report RAM timings it goes in this order:
(CAS) - (TRP) - (TRCD) - (TRAS)
For example, my OCZ PC4000 Rev2 uses the latest Hynix DT-D50 chips. Its timings are 2.5-3-3-7 with 2.80v @ DDR500 speeds. In your BIOS it looks like this:
http://www.tbreak.com/reviews/imageview.php?image=8987
Taken from here ill intereperate em for you...
First as the picture suggests switch to manual mode.
The Memclock refers to the divider. 200 is 1:1. 166 is 5:4 etc etc. setting the RAM to 1:1 will synch it with the CPU's HTT speed. At a CPU HTT of 250 your ram will also be 250. When using 5:4 at 250 your RAM would be at 200. These ratios are used to allow for overclcoking on slower RAM.
First timing is as I said earlier. CAS Latency (TCL) set that to what you want or what your RAM is rated for
Next is the TRAS. That is the motherboard's Cycle time. The way you configure TRAS is as follows. You add the TRCD and TRP together and add 1. As the picture suggests 2+2 (TRCD + TRP) + 1 = 5. Which is why TRAS = 5
Next is the TRCD. Set that to what you want. Just as a note of caution, lower numbers mean lower latency which increases speed. Also note that TRCD is the most stressful timing on most RAM. Unless you have TCCD or a BH/UTT varient, it will not boot with a TRCD lower than 3.
Next is the TRP. This is the second most stressful timing. While some RAM can use TRP of 2 most cannot.
The following timings are a mystery to me. Those deal specifically with the A64's ondie memory controller. Generally speaking lower numbers are better but I personally would leave those on auto.
The next timing of interest is 1T/2T Memory timing. This is commly known as CPC or Command Per Clock rate. Setting this to 1T is FAR better than 2T. Unlike Intel, AMD takes a serious peformance hit with 2T. You can tell quite clearly which one you are using if you look at Sisoft Sandra's memory bandwith benchmark.
If your memory efficiency is less than 80% you are using 2T if it is higher than 80% you are using 1T. Common bandwith for 2T is around mid 70%....which is horrible.
The next 3 timings I have no clue what to do with them. The Read Preamble and Asynch Latency both use 6ns which refers to the memory access time. DDR333 uses 6ns (nano-seconds) while DDR400 uses 5ns. Not sure what those 2's purpose is. I would leave them alone or on AUTO if possible.
Just as a walkthrough on this board here is what my timings would look like in order:
Manual
200mhz
2.5
7T
3T
3T
AUTO
AUTO
AUTO
AUTO
AUTO
AUTO
AUTO
MANUAL
D0 (or auto if possible)
1T
6ns (or auto if possible)
6ns (or auto if possible)
Disabled
With such timings and settings at stock it would boot to DDR400 with the timings of 2.5-3-3-7. From there I would raise the vdimm to 2.80 or 2.85v and push the HTT multiplier from 5 (1000) to 4 (800). Finally I would raise the bus speed to 250 which would give me my DDR500 speed and stock timings.
**be aware that I am assuming you are using a reasonable multiplier like 9 or 10X**
____
Did that help any?
Why would anyone bother useing clockgen?
It would be equally as buggy as he is already using and lacks key features his BIOS has. He's gotta learn how to do it the right way at some pointI just installed everything that came on the packaged CD. my HDs work fine. the sata drivers came on that cd, i remember that
Originally posted by: Sentential
Why would anyone bother useing clockgen?
FWIW
I have found Clockgen to be a useful tool in determining your maximum OC. I originally started using the Bios directly... after the second time my system wouldn't boot without reseting the CMOS I decided there must be a better way.
I go into my Bios and set memory timings, voltages and then hypertransport multiplier (LDT). Leaving the other settings (the ones I can adjust using clockgen) at stock levels.
Then I know I can always boot without opening the case to reset the CMOS. I then proceed to vary the FSB and multiplier until the system hangs. Then I can reboot, backoff and retry looking for a stable combination.
Once you have found an acceptable stable OC, then you can set it in Bios without worrying about the system failing to Boot and the need to reset the CMOS.
Maybe there is a better way (if there is please post how), but I found this to be very helpful when trying to determine your maximum FSB and max CPU freq.
- Aug 22, 2001
- 30,422
- 27,053
- 146
Pr0d1gy
Diamond Member
- Jan 30, 2005
- 7,774
- 0
- 76
OK, that means my Raptor probably is damaged & needs an RMA.
Sentential, thanks you so much for taking time out of your day to explain the BIOS to me step by step. That really helps alot. I have TCCD chipped Patriot XBL, and I have heard that 2-2-2-10 is the best setting for them latency-wise. I guess it will just be a matter of getting the right settings built around that.
HeroOfPellinor
Lifer
- Dec 27, 2001
- 11,272
- 1
- 0
I had to use the NVidia SATA ports instead of the two SI ports. Maybe Ill figure out why someday, but, for now, it's fine for me.
I did try the insert key, but I couldn't get the system to respond. I usually use a wireless USB keboard... next time I'll make sure to use the wired PS2 keyboard.
Either way I still find it easier to boot into Windows and step slowly up to a maxium FSB from one boot rather than rebooting half a dozen or more times using the bios directly.
I don't disagree that clockgen can cause crashes. I have found that as long as I don't increase the FSB by more than 10 to 15 Mhz in a single jump, the system does not hang.
I was able to take my system on a single boot and find my max FSB of 340 Mhz using clockgen. Seems efficient to me.
Not a problem
222 is considered low latency so what you said was indeed correct. As for the 10 cycle time for the most part only applied to earlier Nforce2 Ultra (athlonXP) boards. For the Neo4 you really ought to use the standard 5 with 222. It will provide the best bandwith.For TCCD most part, people prefer to have better bandwith/speed with the timings of 2.5-3-3-7. With those timings TCCD tends to clock to PC4400 and PC4800 speeds. The 222 on TCCD tends to max out *very* quickly, often before reaching PC3500 speeds (216). If I were you I would use 2.5-3-3-7 and scale the bus speed past DDR550 speeds.
just make sure that you're actually getting better performance with the higher bus speed. A64s like the tight timings of 2225, so if you can get them up there with the tight timings, you're going to have the best of both worlds.
TRENDING THREADS
-
Discussion Zen 5 Speculation (EPYC Turin and Strix Point/Granite Ridge - Ryzen 9000)- Started by DisEnchantment
- Replies: 23K
-
Discussion Intel Meteor, Arrow, Lunar & Panther Lakes Discussion Threads
- Started by Tigerick
- Replies: 19K
-
-
-
Intel processors crashing Unreal engine games (and others)- Started by BFG10K
- Replies: 2K
Facebook
Twitter