Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I guess the OS does make a difference here is 10.8.1. The would be 1200 points changing from 10.6.8.:confused:

The reason why I mentioned not using anything above 10.6.7, was because of the under clocking features that you are able to enable without risking stability issues that I had faced many times over with in these past 7 months of trying to force (10.7.X and above) to work, but didn't. Now although I was more referring to the existing EVGA SR-2 mobo setup as oppose to your system, I'm sure that Tutor would agree, since he has been our sensei when it comes to under clocking (UC'ing), that the same would apply to your system when it comes to using the correct OS. That is the reason why I gave you the advice that I did.

I'm glad that you're reaching higher GB scores as a result of you installing 10.8.1. Again, through my experience as well as how the coding has been programmed into the newer OS's, there is really no way to take advantage of what I'm trying (as well as others here) to achieve when it comes UC'ing, at least not yet. I hope with what I shared make sense…
 
The reason why I mentioned not using anything above 10.6.7, was because of the under clocking features that you are able to enable without risking stability issues that I had faced many times over with in these past 7 months of trying to force (10.7.X and above) to work, but didn't. Now although I was more referring to the existing EVGA SR-2 mobo setup as oppose to your system, I'm sure that Tutor would agree, since he has been our sensei when it comes to under clocking (UC'ing), that the same would apply to your system when it comes to using the correct OS. That is the reason why I gave you the advice that I did.

I'm glad that you're reaching higher GB scores as a result of you installing 10.8.1. Again, through my experience as well as how the coding has been programmed into the newer OS's, there is really no way to take advantage of what we're trying to achieve when it comes under clocking, at least not yet. I hope with what I shared make sense…

If you'll read back through this thread you'll find this isn't my first go round in it. 10.7.3 I believe was a MOFO it locked k processors to 1.6. so we moved to MacMans SSDT, that was great and I thank him for it but it stopped at 4.2 Ghz. I was at 4.8 and feeling pretty good and I wanted it back so I had to take MacMans SSDT and recompile it to get me back to 4.8. So I got back to 4.8 then started loosing USB ports and wake from sleep while retaining USB functionality I was not pleased. So I bought a Z77 Motherboard supposedly worked without a DSDT it did but still no USB after wake from sleep. So I put Windows on it sold it, I feel you with the Lion stuff but my 10 minutes of playing on 10.8 tells me it's better. Here is where I was before the lion mess and Apple futzing.
 

Attachments

  • 5Ghz Stable.png
    5Ghz Stable.png
    193 KB · Views: 154
Forgot to mention - at < 166 BCLK, I now keep QPI at 5.8. That's why I sometimes set the QPI voltage as high as I do 1.375 to 1.4, depending on the task at hand. I have fan on rear CPU (CPU 1) because it is set to at least 2 steps less Vcore than is CPU 0 and H80 is on front CPU - CPU 0. Moreover, I've found that system and CPUs stay cooler by bringing in air from the rear to cool H80 and exhausting air from top of front and top of my modified Antec 1200s. I use two 4000+ rpm Sunon fans - one to cool H80 radiator and one on front above DVD drive, to exhaust from top front of case.

That's amazing that you've been able to do that (putting a fan on the rear of the CPU) as well as using an H80 on the CPU as well. I do remember what you mentioned from one of your past posts:

"...so my system temps are in the mid to low 40's C and cores are in the mid 30's when at idle and range from 45 to 68 when running benchmarks and rendering but quickly drop into the mid to high 30's throughout."

By now I think you know my water cooling system setup:

http://www.insanelymac.com/forum/index.php?showtopic=277433

my system temps (even at the current UC settings that I just provided a couple of days ago) are 26 to 30C at idle, but when stress testing the max it's ever reached has been 57C and also quickly drops to 30's during those tests. So I don't think I need it, unless you believe that I need to have more fans put on this system, even at the current temps that they are maxing out on. Also, I know that you mentioned that the current RAM that you're using has the Corsair dual RAM fans blowing on them directly to keep them cooler. With the particular RAM that I have on there now with the high heat sinks they are barely lukewarm to the touch. Plus I have the other fans that are at the base of my case that are blowing up toward the high RAM fins itself, cooling them down even further making them even less than lukewarm to the touch. Pretty much everything including the 4890 GPU that you suggested for me to buy it is also water-cooled as well; as I had recently put a water block on that to keep it even cooler as that was the hottest thing in the system running. Now everything else in the case is much cooler as a result. The 4890 was about as hot as the other GTX 480 that I was using before I switched. But again, the 4890 is running warm to the touch now.

Right now where it stands I'm at 33,400+, but with these CPUs I know this thing can get at least to 37,500+ to 38,500+ stable 24/7. Of course if you had this system with you, I'd bet you would be able to get 42,000+ on it. I hope with time both you and BDF will advise me through it, so I can as close to that score as possible. Honestly, I wish I just could pack it up and drive the 18 hours it would take to get to you and have you do it. I'm only kidding as that would totally defeat the purpose of learning (but it has crossed my mind) - LOL!

VVT (typo) = VTT = QPI. VTT PWM is something different. It is how the signal's wave is massaged or modulated. Changing the wave form's modulation can add to, as well as detract from, stability. So you can try it too so long as you test to see how stability is being affected by the changed setting. CAVEAT: less is more.

For now, I am not going to I just live the VTT PWM as that is not something that I'm familiar with anyway. I'm actually still waiting on BDF to get back to me to let me know whether or not I need to OC my system 1st to make sure it's running stable before I UC, or if that was just a typo on his part and that he actually meant to UC. I'm also waiting to find out where I need to start out on inputting the voltage changes on the Memory, VTT and IOH when I lower the BCLK to 12 to start stress testing it and going from there.

----------

If you'll read back through this thread you'll find this isn't my first go round in it. 10.7.3 I believe was a MOFO it locked k processors to 1.6. so we moved to MacMans SSDT, that was great and I thank him for it but it stopped at 4.2 Ghz. I was at 4.8 and feeling pretty good and I wanted it back so I had to take MacMans SSDT and recompile it to get me back to 4.8. So I got back to 4.8 then started loosing USB ports and wake from sleep while retaining USB functionality I was not pleased. So I bought a Z77 Motherboard supposedly worked without a DSDT it did but still no USB after wake from sleep. So I put Windows on it sold it, I feel you with the Lion stuff but my 10 minutes of playing on 10.8 tells me it's better. Here is where I was before the lion mess and Apple futzing.

I feel ya' man, I too was there. I'm just glad I have a stable Gigabyte UD7 setup that's at the same GB of 18,500+. But I would like to have my newer SR-2 setup stable beyond the 33,000+ that's it's currently giving me. I know this can go higher (beyond 35,000) as Tutor and I know that it can, but those UC render GB scores can really only happen with 10.6.7. Again, I should have been wiser in my decision making. I'm just glad for second chances to make it right now and hope that we can push this SR-2 to it's full potential... :cool:
 
Last edited:
That's amazing that you've been able to do that (putting a fan on the rear of the CPU) as well as using an H80 on the CPU as well. I do remember what you mentioned from one of your past posts:

"...so my system temps are in the mid to low 40's C and cores are in the mid 30's when at idle and range from 45 to 68 when running benchmarks and rendering but quickly drop into the mid to high 30's throughout."

By now I think you know my water cooling system setup:

http://www.insanelymac.com/forum/index.php?showtopic=277433

my system temps (even at the current UC settings that I just provided a couple of days ago) are 26 to 30C at idle, but when stress testing the max it's ever reached has been 57C and also quickly drops to 30's during those tests. So I don't think I need it, unless you believe that I need to have more fans put on this system, even at the current temps that they are maxing out on. Also, I know that you mentioned that the current RAM that you're using has the Corsair dual RAM fans blowing on them directly to keep them cooler. With the particular RAM that I have on there now with the high heat sinks they are barely lukewarm to the touch. Plus I have the other fans that are at the base of my case that are blowing up toward the high RAM fins itself, cooling them down even further making them even less than lukewarm to the touch. Pretty much everything including the 4890 GPU that you suggested for me to buy it is also water-cooled as well; as I had recently put a water block on that to keep it even cooler as that was the hottest thing in the system running. Now everything else in the case is much cooler as a result. The 4890 was about as hot as the other GTX 480 that I was using before I switched. But again, the 4890 is running warm to the touch now.

Right now where it stands I'm at 33,400+, but with these CPUs I know this thing can get at least to 37,500+ to 38,500+ stable 24/7. Of course if you had this system with you, I'd bet you would be able to get 42,000+ on it. I hope with time both you and BDF will advise me through it, so I can as close to that score as possible. Honestly, I wish I just could pack it up and drive the 18 hours it would take to get to you and have you do it. I'm only kidding as that would totally defeat the purpose of learning (but it has crossed my mind) - LOL!



For now, I am not going to I just live the VTT PWM as that is not something that I'm familiar with anyway. I'm actually still waiting on BDF to get back to me to let me know whether or not I need to OC my system 1st to make sure it's running stable before I UC, or if that was just a typo on his part and that he actually meant to UC. I'm also waiting to find out where I need to start out on inputting the voltage changes on the Memory, VTT and IOH when I lower the BCLK to 12 to start stress testing it and going from there.

----------



I feel ya' man, I too was there. I'm just glad I have a stable Gigabyte UD7 setup that's at the same GB of 18,500+. But I would like to have my newer SR-2 setup stable beyond the 33,000+ that's it's currently giving me. I know this can go higher (beyond 35,000) as Tutor and I know that it can, but those UC render GB scores can really only happen with 10.6.7. Again, I should have been wiser in my decision making. I'm just glad for second chances to make it right now and hope that we can push this SR-2 to it's full potential... :cool:

I think you can get more than that..you're on water (at least the picture I saw you were) so keeping it cool won't be an issue.

I think it's time that someone builds and SR-X
 
I think you can get more than that..you're on water (at least the picture I saw you were) so keeping it cool won't be an issue.

I think it's time that someone builds and SR-X

Actually someone has built an SR-X and their scores aren't that high as the CPUs just aren't there to kick in the kind of performance that unlocked CPUs can give. Even if they did, I think according to Tutor's breakdown, you would only see about a 10%-17% boost in performance at best. And even when they come out with the unlocked versions at a 30% boost for the extra $2,700+ that I will cost to get those CPUs and mobo I don't know if it's going to be worth it...
 
Actually someone has built an SR-X and their scores aren't that high as the CPUs just aren't there to kick in the kind of performance that unlocked CPUs can give. Even if they did, I think according to Tutor's breakdown, you would only see about a 10%-17% boost in performance at best. And even when they come out with the unlocked versions at a 30% boost for the extra $2,700+ that I will cost to get those CPUs and mobo I don't know if it's going to be worth it...

I thought they were unlocked..

2690's by the pair are scoring about 40k if they were unlocked 65k would be reachable.
 
I thought they were unlocked..

2690's by the pair are scoring about 40k if they were unlocked 65k would be reachable.

Again, price would (again) be a factor vs. performance. The current price of the 2690 is $2,040 each at a 5% overclock from what I researched (I could be wrong), but I'm sure when their unlocked versions come out they'll be much higher in $$$. Probably in the ballpark of $2,750 to $2,900+ each. Would it still be worth it?...

Right now, I'm just trying to get the SR-2 stable... :cool:
 
Again, price would (again) be a factor vs. performance. The current price of the 2690 is $2,040 each at a 5% overclock from what I researched (I could be wrong), but I'm sure when their unlocked versions come out they'll be much higher in $$$. Probably in the ballpark of $2,750 to $2,900+ each. Would it still be worth it?...

Right now, I'm just trying to get the SR-2 stable... :cool:

I know, and carry on ;)
 
I have fan on rear CPU (CPU 1) because it is set to at least 2 steps less Vcore than is CPU 0 and H80 is on front CPU - CPU 0. Moreover, I've found that system and CPUs stay cooler by bringing in air from the rear to cool H80 and exhausting air from top of front and top of my modified Antec 1200s. I use two 4000+ rpm Sunon fans - one to cool H80 radiator and one on front above DVD drive, to exhaust from top front of case.

Hey Tutor, the description of the system you just gave almost looks like this setup that I saw the other day. :eek: You sure this isn't yours? Just messin'... :p There's about 70 fans on here and they all look like Deltas; not much to top here. A nice bennie to have is, not only can you take this PC case tower with you, it will FLY you there... :D
 

Attachments

  • pcfancase.jpg
    pcfancase.jpg
    23.5 KB · Views: 141
I read everything (as best as I could understand) and I have some questions. Starting with the first step (in Windows 7). I'll shut off SpeedStep & Turbo Boost, then am I to just set everything to it's initial default value (stock) and then set my BCLK (CPU Freq. Multi.) to 12? Because that's as low as it will go. Then will I know what the Memory, VTT and IOH are when I reboot and go back into my BIOS in the Voltage Configuration Menu (VCM)? Because I don't even know where to start to give them the proper voltage to begin with. Also, do I do it with or without VDroop? Once I get this done, then I'lll move onto the next question. Thanks...

PS - In relation to all of this stuff that you gave me, did you understand what Tutor is talking about with what he replied to me about when it came to this:



Just to get this straight, is the "VVT Freq" (or VTT Freq) the same as QPI Freq? Because that's the only place that I can see the range of 4.8GT to 6.4GT anywhere in the BIOS. The only other place that I can see the VTT Freq is in the VCM toward the bottom of the screen that says: CPU0 (and CPU1) VTT PWM Freq and that range is between 240 KHz to 634 KHz. So I don't think that's the right one that he's talking about.



For the rest of the info (above) I'm starting to understand this a little bit better but still need time to absorb this, but will understand it better as I continue to learn this. I look forward to your answers as that will also provide the best clarity for me as I move forward... Again, thanks... :)

Sorry it's taken a couple of days to get back to you. Life got in the way. I can't reboot my machine to look at config screens, it's in a simulation at the moment, so I may get some settings off a bit.

Underclocked or overclocked, you're going to need more VCore for the 5690s to push beyond BCLK 155. Your cpus aren't going to consume less energy when they are being pushed to their max--underclocking only saves energy when the chips are idle.

IOH affects BCLK stability the least of all your voltage parameters. How high you set it will primarily be determined by how many PCI cards you have, and in particular how many graphics cards you have. I have mine set to 1.3V for instance; I started out with 1.2 and worked my way up.

VTT affects the "uncore" stability at a given BCLK--in other words the L3 and memory controller, as well as the QPI link. VTT power requirements go up quickly for the Xeons fairly quickly after 4.2-4.3 GHz. Try to keep it no higher than 1.4. Once you have gotten your memory and BCLK settings stable by using the isolation method I sent you (the techreaction.net link), you should not need to adjust this for your overclocking. My everyday overclock is with BCLK at 164; my VTT settings are 1.325 I think. maybe 1.35. Like VCore, each chip (pair in our case) will be different.

The uncore multiplier can be dropped some as well; it is only required to be 1.5x your memory speed for the 5690 (15x and higher). If you drop it down from from the default (20) to even as low as 15 you won't notice much difference on your geekbench scores.

VCore is the processor power. For a truly stable overclock (using occn, linx or whateverfor 24 hours), I found that I needed significantly higher voltages than what I needed just to boot and get a good Geekbench score. I run somewhere around 1.42V or so, sorry can't look at exact setting. Now I could boot pretty easily at 1.38 or 1.39, but those weren't truly stable settings. I did experiment some with underclocking for a day or so--and I found that I still needed about the same voltage for VCore.

My chips aren't particularly good overclockers, and after BCLK 164 my voltage requirements start climbing dramatically, just not comfortable pushing chips this expensive much higher. I have gone to 170 with acceptable temps, geekbench is about 35700 but voltages were kind of high, like 1.5 or so
 
Sorry it's taken a couple of days to get back to you. Life got in the way. I can't reboot my machine to look at config screens, it's in a simulation at the moment, so I may get some settings off a bit.

Underclocked or overclocked, you're going to need more VCore for the 5690s to push beyond BCLK 155. Your cpus aren't going to consume less energy when they are being pushed to their max--underclocking only saves energy when the chips are idle.

IOH affects BCLK stability the least of all your voltage parameters. How high you set it will primarily be determined by how many PCI cards you have, and in particular how many graphics cards you have. I have mine set to 1.3V for instance; I started out with 1.2 and worked my way up.

VTT affects the "uncore" stability at a given BCLK--in other words the L3 and memory controller, as well as the QPI link. VTT power requirements go up quickly for the Xeons fairly quickly after 4.2-4.3 GHz. Try to keep it no higher than 1.4. Once you have gotten your memory and BCLK settings stable by using the isolation method I sent you (the techreaction.net link), you should not need to adjust this for your overclocking. My everyday overclock is with BCLK at 164; my VTT settings are 1.325 I think. maybe 1.35. Like VCore, each chip (pair in our case) will be different.

The uncore multiplier can be dropped some as well; it is only required to be 1.5x your memory speed for the 5690 (15x and higher). If you drop it down from from the default (20) to even as low as 15 you won't notice much difference on your geekbench scores.

VCore is the processor power. For a truly stable overclock (using occn, linx or whateverfor 24 hours), I found that I needed significantly higher voltages than what I needed just to boot and get a good Geekbench score. I run somewhere around 1.42V or so, sorry can't look at exact setting. Now I could boot pretty easily at 1.38 or 1.39, but those weren't truly stable settings. I did experiment some with underclocking for a day or so--and I found that I still needed about the same voltage for VCore.

My chips aren't particularly good overclockers, and after BCLK 164 my voltage requirements start climbing dramatically, just not comfortable pushing chips this expensive much higher. I have gone to 170 with acceptable temps, geekbench is about 35700 but voltages were kind of high, like 1.5 or so

Thank you for your apology, but actually I have to apologize because I think I misunderstood what you were saying. The reason why is because I think I've confused CPU Freq. Setting with CPU Multi Setting. When someone like you or Tutor say BCLK (Base Clock) it throws me off, because I don't see that in my BIOS. I just see CPU Freq. Setting & CPU Multi Stetting. So again, forgive me. I now understand that BCLK = CPU Freq Setting. From now on I would like to make things easier as I'm going to be stress testing things, so I will defer to this chart (below) as my gauge to keep things simpler so you'll see exactly what I have as I make changes:

These are my current settings (that get me a GB of 33,200+, but locks up from time to time).

Frequency/Voltage Control (main screen)
No Dummy O.C.
Target CPU - 2036 MHz
CPU Freq. - 159
PCIE Freq. - 103
CPU Multi - 13
QPI - 5.866GT
Memory Freq. - 1333

Frequency/Voltage Control
CPU 0 Vcore boot - 1.33125V
CPU 1 Vcore boot - 1.31875V
CPU 0 Vcore eventual - 1.34375V
CPU 1 Vcore eventual - 1.33125V

CPU VTT both boot - 1.375V
CPU VTT both eventual - 1.40V

CPU 0 DIMM Vcore - 1.65V
CPU 1 DIMM Vcore - 1.66V
CPU 0 PLL Voltage - 1.845V
CPU 1 PLL Voltage - 1.845V
IOH - 1.40V
CPU 0 DDR PWM Freq - 1210 KHz
CPU 1 DDR PWM Freq - 1210 KHz

Memory Configuration
DRAM tCL - 8
DRAM tRCD - 10
DRAM tRP - 8
DRAM tRAS - 24
Command Rate - 1

Signal Tweaks
Max Negative settings on everything; except for PCIE Signal 1 & 2 as that's left on AUTO.

______________________________________________________

Now to start from scratch in my stress testing (using OCCN in Windows 7) as I'm UNDERCLOCKING and NOT Overclocking my system (correct?), I loaded up the "default" values and with the adjustments you told me that I need to start with, I think this is how it should look:

Frequency/Voltage Control (main screen)
No Dummy O.C.
Target CPU - 1600 MHz
CPU Freq. - 133 (lowest setting)
PCIE Freq. - 100 (leave this at 100, correct?)
CPU Multi - 12 (should I bring this down to 12 (133x12 = 1600MHz) or should leave it at it's default 26? (133x26 = 3466 Mhz) )
QPI - Auto (auto set @ 6.400GT)
Memory Freq. - 1066 Mhz

Frequency/Voltage Control
Everything's on AUTO so the "greyed out" default settings are as follows:
CPU 0 Vcore boot - 1.24375V
CPU 1 Vcore boot - 1.21875V
CPU 0 Vcore eventual - 1.24375V
CPU 1 Vcore eventual - 1.21875V

CPU VTT both boot - 1.20V
CPU VTT both eventual - 1.20V

CPU 0 DIMM Vcore - 1.50V
CPU 1 DIMM Vcore - 1.50V
CPU 0 PLL Voltage - AUTO
CPU 1 PLL Voltage - AUTO
IOH - AUTO (don't know what that setting is defaulted at, just AUTO)
CPU 0 DDR PWM Freq - 800 KHz (AUTO)
CPU 1 DDR PWM Freq - 800 KHz (AUTO)

Memory Configuration
Now these settings want to default to 7-7-7-20. EVGA told me to call Corsair's and Mushkin's tech support staff to find out from them and both those companies said to put them at the correct settings that are on the RAM sticks themselves. So the proper settings are: 9-11-9-27 and that's where I have them set. Unless you tell me different it should look like this correct?
DRAM tCL - 9
DRAM tRCD - 11
DRAM tRP - 9
DRAM tRAS - 27
Command Rate - 2 (That's on AUTO. Should I change that to 1 instead of 2 or leave it on 2 = AUTO?)

Signal Tweaks
Everything's left on AUTO.

Also, in the CPU Configuration menu you said to ONLY disable SpeedStep; which in turn disables TurboMode tech as well. and to leave everything that is enabled and disabled left at their "default" settings correct? Is there any other thing that I need to disable or enable (like C-STATE tech or anything else in the CPU Config Menu)?

If everything looks fine what I have, then this is where I'll start and go from there. I look forward to your reply BDF as I want to begin this testing (and Tutor if you see anything that I need to change, then please, by all means pitch in your thoughts, because as you said in Post #299 "CAVEAT: less is more." and figure that in the mix of this stress testing). Thanks again for your input... :cool:
 
Last edited:
Thank you for your apology, but actually I have to apologize because I think I misunderstood what you were saying. The reason why is because I think I've confused CPU Freq. Setting with CPU Multi Setting. When someone like you or Tutor say BCLK (Base Clock) it throws me off, because I don't see that in my BIOS. I just see CPU Freq. Setting & CPU Multi Stetting. So again, forgive me. I now understand that BCLK = CPU Freq Setting. From now on I would like to make things easier as I'm going to be stress testing things, so I will defer to this chart (below) as my gauge to keep things simpler so you'll see exactly what I have as I make changes:

These are my current settings (that get me a GB of 33,200+, but locks up from time to time).

Frequency/Voltage Control (main screen)
No Dummy O.C.
Target CPU - 2036 MHz
CPU Freq. - 159
PCIE Freq. - 103
CPU Multi - 13
QPI - 5.866GT
Memory Freq. - 1333

Frequency/Voltage Control
CPU 0 Vcore boot - 1.33125V
CPU 1 Vcore boot - 1.31875V
CPU 0 Vcore eventual - 1.34375V
CPU 1 Vcore eventual - 1.33125V

CPU VTT both boot - 1.375V
CPU VTT both eventual - 1.40V

CPU 0 DIMM Vcore - 1.65V
CPU 1 DIMM Vcore - 1.66V
CPU 0 PLL Voltage - 1.845V
CPU 1 PLL Voltage - 1.845V
IOH - 1.40V
CPU 0 DDR PWM Freq - 1210 KHz
CPU 1 DDR PWM Freq - 1210 KHz

Memory Configuration
DRAM tCL - 8
DRAM tRCD - 10
DRAM tRP - 8
DRAM tRAS - 24
Command Rate - 1

Signal Tweaks
Max Negative settings on everything; except for PCIE Signal 1 & 2 as that's left on AUTO.

______________________________________________________

Now to start from scratch in my stress testing (using OCCN in Windows 7) as I'm UNDERCLOCKING and NOT Overclocking my system (correct?), I loaded up the "default" values and with the adjustments you told me that I need to start with, I think this is how it should look:

Frequency/Voltage Control (main screen)
No Dummy O.C.
Target CPU - 1600 MHz
CPU Freq. - 133 (lowest setting)
PCIE Freq. - 100 (leave this at 100, correct?)
CPU Multi - 12 (should I bring this down to 12 (133x12 = 1600MHz) or should leave it at it's default 26? (133x26 = 3466 Mhz) )
QPI - Auto (auto set @ 6.400GT)
Memory Freq. - 1066 Mhz

Frequency/Voltage Control
Everything's on AUTO so the "greyed out" default settings are as follows:
CPU 0 Vcore boot - 1.24375V
CPU 1 Vcore boot - 1.21875V
CPU 0 Vcore eventual - 1.24375V
CPU 1 Vcore eventual - 1.21875V

CPU VTT both boot - 1.20V
CPU VTT both eventual - 1.20V

CPU 0 DIMM Vcore - 1.50V
CPU 1 DIMM Vcore - 1.50V
CPU 0 PLL Voltage - AUTO
CPU 1 PLL Voltage - AUTO
IOH - AUTO (don't know what that setting is defaulted at, just AUTO)
CPU 0 DDR PWM Freq - 800 KHz (AUTO)
CPU 1 DDR PWM Freq - 800 KHz (AUTO)

Memory Configuration
Now these settings want to default to 7-7-7-20. EVGA told me to call Corsair's and Mushkin's tech support staff to find out from them and both those companies said to put them at the correct settings that are on the RAM sticks themselves. So the proper settings are: 9-11-9-27 and that's where I have them set. Unless you tell me different it should look like this correct?
DRAM tCL - 9
DRAM tRCD - 11
DRAM tRP - 9
DRAM tRAS - 27
Command Rate - 2 (That's on AUTO. Should I change that to 1 instead of 2 or leave it on 2 = AUTO?)

Signal Tweaks
Everything's left on AUTO.

Also, in the CPU Configuration menu you said to ONLY disable SpeedStep; which in turn disables TurboMode tech as well. and to leave everything that is enabled and disabled left at their "default" settings correct? Is there any other thing that I need to disable or enable (like C-STATE tech or anything else in the CPU Config Menu)?

If everything looks fine what I have, then this is where I'll start and go from there. I look forward to your reply BDF as I want to begin this testing (and Tutor if you see anything that I need to change, then please, by all means pitch in your thoughts, because as you said in Post #299 "CAVEAT: less is more." and figure that in the mix of this stress testing). Thanks again for your input... :cool:

I'll try to go through this as thoroughly as possible. If I miss things let me know. Also I can't look at my BIOS settings as I'm in the middle of a simulation that will run for another 48 hours or so.

The purpose of establishing your overclock the way I'm outlining is to do it in a reproducible systematic, logical way. The purpose of this method is first establishing the IOH, VTT, and memory overclock parameters for your target BCLK (=CPU Frequency).

First off, some terminology and things EVGA does a bit differently on the SR-2. You've discovered the first one, the BCLK (or base clock, which evga calls the CPU Frequency). Another is "Without Vdroop" which is "Load Line Calibration" in other BIOSes. Another is "Memory Frequency". There are 3 choices here--800, 1033, and 1333. This corresponds to the system memory multiplier, specifically values of 6x CPU Freq, 8x CPU Freq, and 10x CPU Freq.

The CPU Uncore Frequency should be set to 1.5x your target memory for a Gulftown or later processor, so 15x at a minimum. Higher levels of VTT will be needed to support higher Uncore Frequencies.

The stepwise approach has 3 phases. I'll step through each phase in the next post. It goes backwards from what you see a lot---most people try to max out their overclock and figure out the other stuff--memory, stablity, etc after the fact.

Phase 1: "maximize" bclock and uncore frequency. Now the SR-2 is capable of bclocks of 200 or so, which would put your 5690s at 5.6 Ghz in turbo...but you aren't under liquid nitrogen and don't want to fry your chips, so you aren't getting there. Pick your target--say 165 or 170, still very respectable overclocks.

Phase 2: Optimize Memory Frequency and Uncore
Because you can't dramatically overclock the 5690s and reach really high Memory overclocks, this is pretty straightforward. Tighten the memory timings if you can, but almost all guides I've seen recommend that you try to keep Command Rate = 1.

Phase 3: Maxmize your Underclock (or overclock).
Work your way incrementally to your target BCLK (CPU frequency), titrating VCore voltages only.

Grabbing a bite to eat...will post more in a bit.
 
I'll try to go through this as thoroughly as possible. If I miss things let me know. Also I can't look at my BIOS settings as I'm in the middle of a simulation that will run for another 48 hours or so.

The purpose of establishing your overclock the way I'm outlining is to do it in a reproducible systematic, logical way. The purpose of this method is first establishing the IOH, VTT, and memory overclock parameters for your target BCLK (=CPU Frequency).

First off, some terminology and things EVGA does a bit differently on the SR-2. You've discovered the first one, the BCLK (or base clock, which evga calls the CPU Frequency). Another is "Without Vdroop" which is "Load Line Calibration" in other BIOSes. Another is "Memory Frequency". There are 3 choices here--800, 1033, and 1333. This corresponds to the system memory multiplier, specifically values of 6x CPU Freq, 8x CPU Freq, and 10x CPU Freq.

The CPU Uncore Frequency should be set to 1.5x your target memory for a Gulftown or later processor, so 15x at a minimum. Higher levels of VTT will be needed to support higher Uncore Frequencies.

The stepwise approach has 3 phases. I'll step through each phase in the next post. It goes backwards from what you see a lot---most people try to max out their overclock and figure out the other stuff--memory, stablity, etc after the fact.

Phase 1: "maximize" bclock and uncore frequency. Now the SR-2 is capable of bclocks of 200 or so, which would put your 5690s at 5.6 Ghz in turbo...but you aren't under liquid nitrogen and don't want to fry your chips, so you aren't getting there. Pick your target--say 165 or 170, still very respectable overclocks.

Phase 2: Optimize Memory Frequency and Uncore
Because you can't dramatically overclock the 5690s and reach really high Memory overclocks, this is pretty straightforward. Tighten the memory timings if you can, but almost all guides I've seen recommend that you try to keep Command Rate = 1.

Phase 3: Maxmize your Underclock (or overclock).
Work your way incrementally to your target BCLK (CPU frequency), titrating VCore voltages only.

Grabbing a bite to eat...will post more in a bit.

Thank you so much. I hope you're enjoying your food... :) I will wait for more of the phases that you want to share with me before I start this mission of testing... I am looking forward to this challenge, although guys like you and Tutor have no problems figuring this stuff out, I'm still willing to finally make this happen. I would like to approach this though the under clocking fashion if I could according to Tutor's Post (#286), BUT if you feel that I need to OC instead of UC for now, please tell me so I know what I need to go after. I'm up late tonight, (as I will be every night) so I'd like to bang out as much as I can to learn this stuff over the next few days (in-between my work and wife and kids). Again, thanks...
 
More on the BCLK isolation method

Phase 1: "maximize" bclock and uncore frequency.
Most things can be left on auto at this point. You aren't going to be able to "maximize the bclk" for the SR-2 with the 5690s because they will get too hot. Your goal here is to find the minimal safe values of VTT that will let you get to your target CPU Frequency, say 163 to 167 range.

Memory speed settings should be left on Auto for all. Leave the energy saving features turned on that you will have in final configuration, just turn off Speedstep (and subsequently turbo mode, that's part of Speedstep really).

The key to phase 1 is isolate the BCLK from the memory and CPU overclocks by turing those down all the way. First we remove the CPU effects by forcing a low target CPU frequency by lowering the multiplier and turning off Speedstep. Second, we turn the memory down to it's lowest speed...so timings on auto for all, and select the 6x (800 Mhz) or 8 x (1033 Mhz) memory multiplier.

The QPI link speed is dependent on VTT (it's an uncore function), so you want to have an idea where you want that as yo do this. I fix the value here.

Now you don't have to reinvent the wheel here...you already have an idea about where your voltages need to be from the information available. You also don't need to start at "zero"

Notice I've made some changes

Using the BIOS settings you'll start out with something like this:
Frequency/Voltage Control (main screen)
No Dummy O.C.
Target CPU - calculated value....= cpu multi x CPU freq
CPU Freq. - 150
PCIE Freq. - 100
CPU Multi - some low number, 12 to 15 is fine.
QPI - 5.8666 (or whatever the middle value is...5.something)
Memory Freq. - 800 Mhz (lowest value)

Frequency/Voltage Control
Everything's on AUTO so the "greyed out" default settings are as follows:
CPU 0 Vcore boot - auto
CPU 1 Vcore boot - auto
CPU 0 Vcore eventual - auto
CPU 1 Vcore eventual - auto

CPU VTT both boot - 1.25V
CPU VTT both eventual - 1.25V

CPU 0 DIMM Vcore - 1.65V
CPU 1 DIMM Vcore - 1.65V
CPU 0 PLL Voltage - AUTO
CPU 1 PLL Voltage - AUTO
IOH - AUTO (don't know what that setting is defaulted at, just AUTO)
CPU 0 DDR PWM Freq - 800 KHz (AUTO)
CPU 1 DDR PWM Freq - 800 KHz (AUTO)

Set your Uncore Clock Ratio to your target value---15x is the minimum for Gulftown and later, 20x is the maximum. I don't see a big difference on GB testing here over that range.

On the signal tweaks, leave everything on AUTO but IOH0 and IOH1, which should be somewhere around -75 and -15 or so.
Memory Configuration
just leave this at auto (the default values)--these are conservative, fail safe values that will work fine

So boot with this...it will be fine....if you get an FF, turn the Memory Frequency up to 1033.

Now, boot with these settings. In the unlikely event things go wrong, turn up VTT values.

Now, do a short torture test, say 20 minutes of OCCT Linpack. If stable, then reboot and bump up BCLK (change nothing else) 10 units to 160. If the test failed, bump up the VTT (all values) by one notch (0.0125 V? or 0.025, cant remember), then reboot. Rinse and repeat until you get to your target BCLK, adjusting ONLY the VTT values.

Once you've gotten to your target value, then run a longer torture test, say 2 hours of OCCT Linpack or Intelburntest, whatever. Now you know (more or less) what your VTT settings will be.
 
More foolishness....

Phase 2: Optimize Memory Frequency and Uncore

This part is pretty easy...I don't remember the particulars of your memory, but it doesn't really matter. Overclocking memory doesn't gain you that much performance. As I recall, I think you had well spec'ed memory, so it's kind of a moot point. Your going to basically turn the system memory multiplier all the way up to 10x (1333 Mhz). That means your memory will be running at 10x the BCLK, so 1660 Mhz if you target a 166 CPU frequency.

Set IOH to 1.3V and forget about it. If you add more video cards, go up a notch or two. Really, it's that easy. Or leave it on auto.

Your settings here will be:
Frequency/Voltage Control (main screen)
No Dummy O.C.
Target CPU - calculated value....= cpu multi x CPU freq
CPU Freq. - 166
PCIE Freq. - 100
CPU Multi - same low number you used in phase 1.
QPI - 5.8666 (or whatever the middle value is...5.something)
Memory Freq. - 1333 Mhz (highest value)

Frequency/Voltage Control
Everything's on AUTO so the "greyed out" default settings are as follows:
CPU 0 Vcore boot - auto
CPU 1 Vcore boot - auto
CPU 0 Vcore eventual - auto
CPU 1 Vcore eventual - auto

CPU VTT both boot - whatever value you arrived at....
CPU VTT both eventual - whatever value you arrived at....

CPU 0 DIMM Vcore - 1.65V
CPU 1 DIMM Vcore - 1.65V
CPU 0 PLL Voltage - AUTO
CPU 1 PLL Voltage - AUTO
IOH - 1.30 V
CPU 0 DDR PWM Freq - 800 KHz (AUTO)
CPU 1 DDR PWM Freq - 800 KHz (AUTO)

Leave speed step turned off.

Set your memory voltage to 1.65V for each bank if not already done. Odds are that you are still going to be stable here, but now that you've turned up your memory to "full speed", do a short torture test...
In the event your test fails, then up VTT (all) by one notch and retest.

If you want to tweak your memory here a bit, that's fine. You can easily drop the basic timings of your memory to 8-10-8-26 I suspect, and that will net perhaps a few percentage points improvement on memory intensive work. Now do a longer torture test. But don't spend a lot of effort on this, it's low yield.
 
BTW as I'm doing these settings, I just wanted to let you know, since I changed out my refurbed SR-2 mobo for a brand new SR-2 mobo, I started up my SSD that had my already purchased and installed copy of Windows 7 and for some reason now it's saying on the bottom right hand screen "This copy of Windows is not genuine." When I know it IS, but it's still working but with a black background screen. All the apps work fine but OCCN doesn't work though. It's giving me issues, so I'm using IntelBurnTest v2.5.4 and RealTemp v3.70 to check my temps. So I think I'll be fine unless you thing IBT isn't that good compared to OCCN. Let me know, thanks...
 
Even More Foolishness

Phase 3: The Fun Part. Optimizing your (under)clock.

Whee! You're finally there.
Now you have Memory speeds, Uncore settings, and BCLK all set up. IOH and VTT are at their optimum values.

Again you don't have to reinvent the wheel here. You aren't going to go straight for your overclock goal, but work there incrementally.

Now turn on Speedstep and Turbo modes. All of your adjustments at this point will be made to VCORE, nothing else.

Now, CPU1 does require less voltage for VTT and VCore, but I didn't turn mine down until after I had established a stable overclock at my target BCLK.

Your settings here will initially be:
Frequency/Voltage Control (main screen)
No Dummy O.C.
Target CPU - calculated value....= cpu multi x CPU freq
CPU Freq. - 150 (starting lower than your goal)
PCIE Freq. - 100
CPU Multi - 13 (or whatever you want for your underclock!)
QPI - 5.8666 (or whatever the middle value is...5.something)
Memory Freq. - 1333 Mhz (highest value)

Frequency/Voltage Control
Everything's on AUTO so the "greyed out" default settings are as follows:
CPU 0 Vcore boot - 1.325 (I just picked these because I know they work for you at a higher BCLK, with the occasional freeze)
CPU 1 Vcore boot - 1.325
CPU 0 Vcore eventual - 1.325
CPU 1 Vcore eventual - 1.325

CPU VTT both boot - whatever value you arrived at after phase 1 and 2
CPU VTT both eventual - whatever value you arrived at after phase 1 and 2

CPU 0 DIMM Vcore - 1.65V
CPU 1 DIMM Vcore - 1.65V
CPU 0 PLL Voltage - AUTO
CPU 1 PLL Voltage - AUTO
IOH - 1.30 V
CPU 0 DDR PWM Freq - 800 KHz (AUTO)
CPU 1 DDR PWM Freq - 800 KHz (AUTO)

Memory settings:
whatever values you got to in step 2 without wasting much time.

Now, boot, do a 20 or 30 minute torture test. If stable, up your CPU frequency to 160. Now when it crashes, and it will, you need to up your VCore by one or two notches. Vague rule of thumb, if it crashes early or with a BSOD, up it two notches. Rinse and repeat until you get to your target CPU frequency. As you get close, go up or down by 2 notches in CPU frequency (e.g., 160 to 162).

Important: don't be surprised if your VCore voltages are more than you are using currently, yours aren't high enough. Even underclocking you are going to need VCores in excess of 1.4V for long term stability.

In general, at this point you shouldn't need to increase VTT or IOH, only VCore. Once you get stable settings on short tests at your target BCLK, then do a longer test.

One of the great things about this method is that you can always go back and tweak a bit. For instance if you think you can improve your memory timings in a useful way, just "turn down" the CPU by turning off speedstep, and fiddle with the memory, retest with the cpu turned down, increase VTT if you need to, then retest with the CPU "turned back up".

Hope this helps!

PS, about to embark on my second sr-2 build....

----------

BTW as I'm doing these settings, I just wanted to let you know, since I changed out my refurbed SR-2 mobo for a brand new SR-2 mobo, I started up my SSD that had my already purchased and installed copy of Windows 7 and for some reason now it's saying on the bottom right hand screen "This copy of Windows is not genuine." When I know it IS, but it's still working but with a black background screen. All the apps work fine but OCCN doesn't work though. It's giving me issues, so I'm using IntelBurnTest v2.5.4 and RealTemp v3.70 to check my temps. So I think I'll be fine unless you thing IBT isn't that good compared to OCCN. Let me know, thanks...

IBT is fine. Windows thinks it's been stolen if you switch drive controllers on it--so moving from one mobo to another it will do that. It's pretty easy to fix if you call MessySoft

----------

Thank you so much. I hope you're enjoying your food... :) I will wait for more of the phases that you want to share with me before I start this mission of testing... I am looking forward to this challenge, although guys like you and Tutor have no problems figuring this stuff out, I'm still willing to finally make this happen. I would like to approach this though the under clocking fashion if I could according to Tutor's Post (#286), BUT if you feel that I need to OC instead of UC for now, please tell me so I know what I need to go after. I'm up late tonight, (as I will be every night) so I'd like to bang out as much as I can to learn this stuff over the next few days (in-between my work and wife and kids). Again, thanks...

Underclocking is fine, I actually would if i could, but i 'need' lion/ml for other reasons.
 
Well, so far so good. I got it to work with this setup:

No Dummy O.C.
Target CPU - calculated value....= cpu multi x CPU freq
CPU Freq. - 167
PCIE Freq. - 100
CPU Multi - 15 (13 wouldn't work and I remember Tutor said (some months ago) that 13 was the magic number for the X5690s for UC'ing, but I can't remember mathematically why it was that important? :confused:)
QPI - 5.8666
Memory Freq. - 800 & 1066
CPU Uncore Freq. - 2266 Mhz (17 X)

Frequency/Voltage Control
CPU 0 Vcore boot - AUTO
CPU 1 Vcore boot - AUTO
CPU 0 Vcore eventual - AUTO
CPU 1 Vcore eventual - AUTO

CPU VTT both boot - 1.25
CPU VTT both eventual - 1.25

CPU 0 DIMM Vcore - 1.65V
CPU 1 DIMM Vcore - 1.65V
CPU 0 PLL Voltage - AUTO
CPU 1 PLL Voltage - AUTO
IOH - AUTO
CPU 0 DDR PWM Freq - 800 KHz (AUTO)
CPU 1 DDR PWM Freq - 800 KHz (AUTO)

Signal Tweaks
IOH 0 - -75
IOH 1 - -15
Everything else set at AUTO

I was able to finally use OCCT 4.3.1 and used Linkpack and ran all my tests for 20 min.. It took a few hours to reach the setting above, as everything else I tried FF'd on me when I kept the CPU Multi. at 13. I still need to know the difference between why 15 works better over 13. If you have an answer to that question it would be helpful, thanks... Other than that, I think I'm making progress... :) Now I gotta hit the sack. It's 3:30 AM. Gotta get up early and take the kids to school. Let me know how I did and if I can push this some more... Thanks... :cool:
 
Last edited:
I was able to finally use OCCT 4.3.1 and used Linkpack and ran all my tests for 20 min.. It took a few hours to reach the setting above, as everything else I tried FF'd on me when I kept the CPU Multi. at 13. I still need to know the difference between why 15 works better over 13. If you have an answer to that question it would be helpful, thanks... Other than that, I think I'm making progress... :) Now I gotta hit the sack. It's 3:30 AM. Gotta get up early and take the kids to school. Let me know how I did and if I can push this some more... Thanks... :cool:

With CPU Multiplier at 15, you will get Turbo Boost Ratios of CCCCDD, that's hexadecimal for +12 and +13. At CPU multiplier 13 you will get EEEEFF. Once you move to phase 3 you might try again. The auto voltages for VCore maybe the hangup at this stage. Wouldn't worry about that yet, you aren't trying to underclock yet.
 
With CPU Multiplier at 15, you will get Turbo Boost Ratios of CCCCDD, that's hexadecimal for +12 and +13. At CPU multiplier 13 you will get EEEEFF. Once you move to phase 3 you might try again. The auto voltages for VCore maybe the hangup at this stage. Wouldn't worry about that yet, you aren't trying to underclock yet.

Great. Should I push "phase 1" any further like upping the BCLK to 168 - 170 to see where it fails, or just leave it as is?
 
You'll get to 170 no problem. But you probably won't want to push your chips that hard. I would pick a more modest goal personally, until u know how much power you need. 164 or 165 is good
 
Don't forget to do a longer torture test before moving on. 1 or 2 hours probably good enough.

You got it. Doing it now, and I'll make sure to not go over 165 in my 2 hour test...

Lastly, I was checking through all my settings before I launched the test and noticed that in my Memory Config it's set at this:

Memory Configuration
DRAM tCL - [Auto (6)]
DRAM tRCD - [Auto (6)]
DRAM tRP - [Auto (6)]
DRAM tRAS - [Auto (15)]
Command Rate - 1

Even though it's on AUTO, isn't that kinda low? I mean, I haven't touched it so it's doing it thing, but that's where it's set itself. Because I didn't set it up like that. I'm too scared to jack with the RAM like that. Is that a result of my putting in those all those other settings for the Phase 1 testing?

EDIT: Just to let you know the OCCT: CPU Linpack testing that I'm doing is set on Automatic and not on Infinite. Setting it on Automatic allows me to give it a specific time (i.e.; 20 min, 2 hrs, etc). Plus it's default is set to:

Idle Periods: 1 min (at the beginning) & 5 min (at the end)

Memory: 90% (41409 MB)

64 bits (is checked)
AVX Capable Linpack (is not checked)
Use all Logical Cores (is checked)

I don't know what I should or should not be adjusting so I just left them at their own default settings. Let me know if I have to adjust any of these things. Thanks...
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.