Reply to this thread
Forum question
Started by misfitkid86 | | 2 answers
hello, i was interested in overclocking my memory but have no clue how to do so! i have two lane 8gb gskills ripjaws there stock at 1600, really i'd just like to get them up to 1866 but as i said i have no idea how to begin. the mobo is a asus sabertooth z77 and the cpu is a 3570k running at 4.4 if that matters, thanks!
thebrain360
October 13, 2014 12:02:42 AM
well its a complicated story really but heres a quick guide
Go into your BIOS and set the most aggressive memory timings available to you. I’m running 2-2-5-2 on my Corsair 3000 CAS 2. (See Lostcircuits.com or Speed Demonz
radiativenz – my favorite – should you need help with the meaning of such things as 2-2-5-2.) Start at a stock FSB speed (133 should be stock on new mobos) and also make sure Vcore and Vdimm are set to default voltages.
While in the BIOS, also lower the multiplier on your CPU (when the CPU is locked, the multiplier is fixed and cannot be changed) – maybe 8. Yes, this is low but you want the CPU to be stable as you increase the FSB, so you make sure it is running slow. (By the way, CPU speed is FSB x multiplier. You probably know that, but just making sure.) You’ll reset the CPU multiplier higher later.
Run an application that really exercises the memory at each FSB speed to see if you’re stable (see Testing below). Sandra doesn’t cut it for this test. After you know this initial setup is stable, start increasing the FSB speed and retest each time. Yes, this takes a lot of time!You may wish to jump to 166 FSB once you’ve tested stock. (I believe that that is the point at which one or more multipliers change and you’ll want them at the higher levels of the FSB anyway.)
When the test results are unstable, increase the Vdimm and try again. Continue increasing the Vdimm till stable or you don’t want to go any higher in voltage.
Using this process of increasing the FSB speed, testing and increasing the Vdimm as needed, work your way up to the highest FSB you can reach for the max Vdimm voltage you’re willing to run.Be careful to keep the CPU near stock speed – or lower – by lowering the CPU multiplier should your FSB speeds reach high levels. This will keep the CPU stable without having to increase its voltage {Vcore), an operation that we wish to delay and keep independent from the memory overclock.
There are various strategies about how to minimize the time you spend reaching a maximum FSB but I’ll not take up space to suggest those — I’m sure you can figure several others out.
You can reduce your aggressive memory setting (2-2-5-2) to get higher FSB speeds, but it has been noted several times by others that “In general, you can get better memory performance out of a lower clock speed and better timings than out of a faster clock speed but worse timings.”Often, your memory performance is more important to overall performance than your overclock, so a good approach is to overclock as far as your memory can operate at its most aggressive settings.
You can have problems (unstable behavior) with video, networking and other cards, as the FSB gets high. The FSB speed at which the multipliers change is critical to these problems.
You would work next on the CPU speed, but that isn’t part of this guide – at least not for now. Basically, you start increasing the CPU multiplier and increase the Vcore as needed for stability in this case. And test, test, test… always watching your CPU temperatures!!! The CPU you save maybe your own.
Go into your BIOS and set the most aggressive memory timings available to you. I’m running 2-2-5-2 on my Corsair 3000 CAS 2. (See Lostcircuits.com or Speed Demonz
radiativenz – my favorite – should you need help with the meaning of such things as 2-2-5-2.) Start at a stock FSB speed (133 should be stock on new mobos) and also make sure Vcore and Vdimm are set to default voltages.
While in the BIOS, also lower the multiplier on your CPU (when the CPU is locked, the multiplier is fixed and cannot be changed) – maybe 8. Yes, this is low but you want the CPU to be stable as you increase the FSB, so you make sure it is running slow. (By the way, CPU speed is FSB x multiplier. You probably know that, but just making sure.) You’ll reset the CPU multiplier higher later.
Run an application that really exercises the memory at each FSB speed to see if you’re stable (see Testing below). Sandra doesn’t cut it for this test. After you know this initial setup is stable, start increasing the FSB speed and retest each time. Yes, this takes a lot of time!You may wish to jump to 166 FSB once you’ve tested stock. (I believe that that is the point at which one or more multipliers change and you’ll want them at the higher levels of the FSB anyway.)
When the test results are unstable, increase the Vdimm and try again. Continue increasing the Vdimm till stable or you don’t want to go any higher in voltage.
Using this process of increasing the FSB speed, testing and increasing the Vdimm as needed, work your way up to the highest FSB you can reach for the max Vdimm voltage you’re willing to run.Be careful to keep the CPU near stock speed – or lower – by lowering the CPU multiplier should your FSB speeds reach high levels. This will keep the CPU stable without having to increase its voltage {Vcore), an operation that we wish to delay and keep independent from the memory overclock.
There are various strategies about how to minimize the time you spend reaching a maximum FSB but I’ll not take up space to suggest those — I’m sure you can figure several others out.
You can reduce your aggressive memory setting (2-2-5-2) to get higher FSB speeds, but it has been noted several times by others that “In general, you can get better memory performance out of a lower clock speed and better timings than out of a faster clock speed but worse timings.”Often, your memory performance is more important to overall performance than your overclock, so a good approach is to overclock as far as your memory can operate at its most aggressive settings.
You can have problems (unstable behavior) with video, networking and other cards, as the FSB gets high. The FSB speed at which the multipliers change is critical to these problems.
You would work next on the CPU speed, but that isn’t part of this guide – at least not for now. Basically, you start increasing the CPU multiplier and increase the Vcore as needed for stability in this case. And test, test, test… always watching your CPU temperatures!!! The CPU you save maybe your own.
argeru
October 12, 2014 11:53:40 PM
See all answers