v1ral, what is the highest v-core you have tried so far?

Setting "MCH strap" to "auto" would loosen all the RAM timings not specifically set.

techno-mancer

BTW, you get that BR yet for all your help?

Aw I've got enough of those. They've been giving them out like lollypops in the past year. I remember when they were really something to be proud of (hard to get).

okay as i wait for my block to get here.. been dialing in my 4.1 baseclock. and i stumbled upon this kind boggling situation i am in. i lowered vcore to 1.21875
...droop off.. and testing now..
i dont know what does this mean.. was my vcore way high when i started.. i wonder what vcore i use to 4.2..

sorry i made no sense..anyways..it passed lowering it again..
vcore at 1.2125

That's just amazing. I would like to see the rest of your settings (CPU PLL, QPI PLL, and did you change any DIMM settings), or are they the same as the template at post #287 page 10? Wow, how could that happen? Yeah just mind-boggling.
 
Oh, congrats on the new block, I hope it does wonders for you.

on load your vcore prob gets up to around 1.25ish......when you had your vcore higher with vdroop your vcore dropped to around 1.25ish

@ Halloweenwhatever, you need to re-think some of your so-called knowledgeable posting here, where it seems you have taken license to criticize me and a "flaw in your thinking" as you wrote...something about a different kind of motherboard? Sorry, it's the SAME KIND of board I own you class-clown windbag! WE BOTH HAVE CLASSIFIED E-760's.
 
So there's a flaw IN YOUR THINKING my man, now stay OUT of my posts if you can't do or say something constuctive or beneficial here, that is my recommendation to you! 
 
@ the OP Viral, you are doing fine, now why don't you take the new H20 block and let's get going on up to 201 QPI and let's stop ****footing around with all the numbers in-between there. If you are having success by LOWERING the VCore then you've been too high all along, it turns out. That means the success or failure of your CPU and RAM has all along meant that the RAM needed to be addressed more than the CPU...or so I feel 'bout it, and that's what is important now that you are having success at the lower QPI settings...with decreased VCore, a good thing to have going for your program.
 
I will get in touch with you tomorrow, even if I'm at work, by sending you an IM and you can tell me all about the situation that you're in once you install the new H20 block, another good thing. Look for me to be messaging you sometime in the middle of the afternoon, 3-4 o'clock or thereabouts. If I don't get you then I'll get you in the early evening tomorrow, with any luck.  
 
You're doing great, continue discovering things you can lower, because lower is always better and I am very pleased to see you working the "low side of the street"...these are great CPU's, the B203's, and they have always run at low voltages, the ones I have known about do that...if you look at the old Stability thread there are several of them at 4.3Ghz and higher, and it shows a consistent pattern of low VCore for all those CPU's, no matter where they ended up with their Mhz...go look for yourself if you have to, it's  true as true can be. 
 
I'll talk with you tomorrow, and good show on experimenting with lower VCore, as that is always a good thing to be doing-- if it works, especially! 
 
rexrzer77 
 
 
 
 

v1ral

upadate..
installed block bench today with 4.1 ghz temps dropped hardcore from 86 to like 74ish.. wow..now its time to play.

 
Wow, so it was your block all along!!
 

Fail..
Errors again and again right after the first pass completes

Yes I have gone up to +250 and I tried 1.4 vcore...

Bios ( 82 ) Trying 77 no Seems I get lower temps from 82 with 197 bclock like 3c                                                                                                
 CPU ( 920 D0 ) ( Batch #3849B203 )                   
CPU Cooler ( D. Teck Fuzion v2 )
Memory ( G.Skill P.I Blue 8-8-8-21 1600mhz )
PSU ( Corsair HX850W )
GPU ( EVGA GTX 470 SC+ )
Drivers ( Latest )                                                                                                 
Operating System ( Windows 7 64 Ultimate )


Frequency Control
CPU Clock Ratio ( 20*+1 )                                                                                        
CPU Host Frequency (Mhz) ( 201 )                                                                     
MCH Strap ( Auto )
CPU Uncore Frequency ( ??Mhz ) ( x16 )                                               
CPU Clock Skew ( 0 ps )
Spread Spectrum ( Disabled )
PCIE Frequency (Mhz) ( Auto )  

Memory Feature       
Memory Speed ( Standard )
Memory Control Setting ( Enabled )
Memory Frequency ( 1610mhz / 2:8 )                                                               
Channel Interleave Setting ( 6 Way )
Rank Interleave Setting ( 4 Way )
Memory Low Gap ( Auto )
tCL Setting ( 8 )
tRCD Setting ( 8 )
tRP Setting ( 8 )
tRAS Setting ( 21 )
tRFC Setting ( 59 )
Command Rate ( 1t )


Voltage Control
EVGA VDroop Control ( w/o VDroop )
CPU VCore ( 1.25625 ) Lowest I've tried with no Bsod's                                                                                               
CPU VTT Voltage ( +200 )  Where should I go from here? I've tried from +100~+250
CPU PLL VCore ( Auto )( 1.8)
**IOH PLL VCore ( Auto ) ( 1.8)
DIMM Voltage ( 1.7 ) I've went this high to be .5 of Vtt *I've calculated my minumum/maximum req.
DIMM DQ Vref ( Auto )
QPI PLL VCore ( 1.3 ) Tried from 1.1*default to 1.2... 1.3.. 1.325
IOH VCore ( 1.3 ) Tried from 1.1*default to 1.2... 1.3.. 1.325
IOH/ICH I/O Voltage ( Auto )( 1.5 )
**VTT PWM Frequency ( Highest Values )
**CPU PWM Frequency ( Highest Values )
**CPU Impedance ( Less )
**QPI Signal Compensation ( Less )
ICH VCore ( Auto )( 1.05)



CPU Feature
Intel SpeedStep ( Disabled )
Turbo Mode Function ( Enabled )
CxE Function ( Disabled )
Execute Disable Bit ( Disabled )
Virtualization Technology ( Disabled )
Intel HT Technology ( Enabled )
Active Processor Cores ( All )
QPI Control Settings ( Enabled )
QPI Link Fast Mode ( Enabled )
QPI Frequency Selection ( 4.8 )
OC Recovery ( Disabled )

PnP/PCI     PCI Express
Maximum Payload Size ( Auto )
 
Power Management Setup
ACPI Suspend Type ( S3 ) ? 
HPET Support ( Enabled )?    
HPET Mode ( 64-bit )?

thanks for the pm.. ill try it out when i get home.. but if linx doesnt budge then..?... ram jacked up..?

Drop your mem multi to 2:6 next.

v1ral

been tinkering again and cant get anyting to.work at ALL..
my ram wont work pass 1600..with what ever i throw at it. which is weird.. i passed memtest at 1600 1.68 vdimm.

First, if it took 1.68 to get your RAM to pass memtest @1600, you shouldn't run your RAM at 1.68 and 1600. You should increase the V to run at 1600, like at least 5%. This means 1.77V. My guess is your board is putting out at least 5% less VDIMM than you are setting, if not even maybe a full 10% less. The specifics of your actual board output don't matter much bc you just need to do what works. Never run things right on the cusp of failure, unless you accept failures in your daily computing routine. You only need to keep VTT at least +75 to do that, and since you have determined that your VTT needs +150 then that's not an issue. And when you drop to 2:6 you should be able to drop your RAM V back down near 1.65. When you posted your mem timings from AIDA64, you didn't post the 666MHz voltage, so I can't do the calculation; but it goes like this:
 
You need 1.77V (board setting, not actual) to be stable at 1600. That's an increase of 10.625% above the 1.6V spec.
So if 666MHz (DDR3 1333) says 1.5V, then you should set 1.5 * 1.10625 = 1.66V for anything up to 1333 (201-222 Bclock).
 
 
Don't try to OC your RAM right now, it may be pointless. Mine would only OC to about 1652, but I did not try to overvolt actual V measurement past RAM specs either. I could've tried that, but at that time it would've been pointless to me since I do not run >4GHz 24/7, I did so only for the club. I may still try that sometime since I run 171-175 Bclock 24/7, and at 2:10 that means DDR3 1710-1750. But I digress. This gives me something to play with in the future when my business slows down again.
 
The point for you is, worry about your CPU OC first, so I recommend you drop your RAM multi to 2:6 and if that spec was 1.5V then set your DIMM V to 1.66. Then when you achieve your acceptable CPU OC you can fiddle around with 2:8 again to see if you can get it to work - if your Bclock is close enough to 205. It's entirely possible that you could be up >216 and getting your RAM over 1730 just might be impossible for you. You can always backtrack your OC, if you make good records, and try the same stuff that worked earlier with higher RAM speed and play with timings/V to try to get your RAM speed up.
 
 
OK now for the next issue. Many ppls have reported Bclock "holes". These are Bclock settings at which your OC just will not work. Some reported that they could not achieve >200, but when they tried >210 they were successful. This is something we don't recommend early in an OC, nor even in the middle of an OC, but only after exhaustive tries at inching the Bclock up; bc only at that time do you know your chip well enough to guess the proper V settings to achieve this. It also was probably impossible with your previous CPU block, but now with the new block your temps should be acceptable, watch that Vreg (keep <96). By the proper V settings, I mean you may need a tiny bit more VTT, and a moderate bump in Vcore, but the same or nearly the same other Vs. I think you should try it, like 211 or so, try 211 then 209 then 215. Of course you should watch those temps like a hawk when you do this, and expect to maybe need to reset CMOS a few times just to get into BIOS again; just don't let it scare you off from trying. GL.
 
 
Oh yeah, Kudos to you, V1ral, for your tenacity on your OC too.  Most ppls would have given up long ago, you stuck with it as you should have. It's very refreshing to coach someone like you once more.

corsair dom gt are in my future.!