Can't stable "Elpida Hyper" With i7-2600K

[3oh6]

My chip is decent,too bad it will do 32M and vantage at 5520 with 1.5,but it wont scale 10 mhz more even with 1.65

looks like we have the same chip. 06/vantage/11/wprime with all cores enabled & HT at 5522MHz with 1.51v vCORE all day long. cannot validate 5530MHz. at least mine can run 108.5 BCLK all day long too, so it is a very valuable chip for maxing out efficiency.

oh, and i just received a UD7 yesterday, so after some work today/tomorrow, i will see if my chip is at fault for the lack of high memory clocks on the M4E

[chew*]

Yeap,seems board dependent hyper problems with SB.My hypers won't boot 1866 cas 6,2133 cas 7 on Asrock P67 Extreme6,will run 1866 decently,but 2133 is stable only for S-pi 1M and some 3d benchmarks,at 8-8-8,no matter voltage(give them up to 1.8,no results).Some G.skill will arrive today,i'll test them to see what's going on,so far i reached for S-pi 32M 1866 7-7-6 32M stable at 1.75(same mem worked like charm on P55,memtest stable at 1.6 ).

My chip is decent,too bad it will do 32M and vantage at 5520 with 1.5,but it wont scale 10 mhz more even with 1.65

Alex mind shooting me the batch info of that chip?

Not all to impressed with HT on performance of 2600K so just looking for a 2500K thats decent.

[1Day]

Dinos that with 1.8 dram ? Also has there been a fix with the ud7 running ram past 2133+ or is that only with hypers?? I got a UD7 on the way atm, and yes i know about the sata 2 incident but doesnt phase me as i use a raid card..

UD7 goes past 2133 even with hypers. I think it is only certain hyper chips that are problems. The two sets I have have gone past 2133 and not really blinked.

[dinos22]

I'll share my experience with Giga boards

I think you wont be able to boot at high bclock i think with UD7 from my experience with 3 chips, best to boot at 100-104 somewhere whatever it likes and push it up with ET6 (must install Intel Management Engine Interface or ET6 will not work properly in windows)

make sure you also flash to a new bios(like F7E i used above) with @BIOS app and then copy that bios to backup bios > ALT+F12 during bootup

easiest way to get up to speed when tuning and crashing is to have battery out, flick PSU off and reload profile after clearing cmos, you'll get the max out in 20 minutes pretty much


johnny i put GTX3 ram and it went past 1100, GT2000C7 same thing, cheap corsair vengeance 1600 sticks bench up to 2133 even for me but it takes a bit of patience and fine tuning. There are some SPDs from wath ive seen that dont seem to agree well and IMCs that just arent up to par which could be Jody's case but personally all chips i stuck in UD5 and UD7 i have here are doing the same. Jody certainly has plenty of decent ram that works for me so ram shouldnt be an issue . All my chips respond to VTT raised up to about 1.24v and they also scale with vdimm, also try Marvel SATA3 port on the HDD and PCH bump if you get some stability issues with higher bclock

Looking forward to it Jody, 32M and 3DMARK01 baby


man cheapseats put the hammer down early, i gotta start doing some proper runs it looks awful now doesnt it

[1Day]

I'll share my experience with Giga boards

I think you wont be able to boot at high bclock i think with UD7 from my experience with 3 chips, best to boot at 100-104 somewhere whatever it likes and push it up with ET6

OK that is something I have not done yet. I tend to only overclock within the BIOS. Guess I need to move with the times.

[Johnny87au]

I'll share my experience with Giga boards

I think you wont be able to boot at high bclock i think with UD7 from my experience with 3 chips, best to boot at 100-104 somewhere whatever it likes and push it up with ET6 (must install Intel Management Engine Interface or ET6 will not work properly in windows)

make sure you also flash to a new bios(like F7E i used above) with @BIOS app and then copy that bios to backup bios > ALT+F12 during bootup

easiest way to get up to speed when tuning and crashing is to have battery out, flick PSU off and reload profile after clearing cmos, you'll get the max out in 20 minutes pretty much


johnny i put GTX3 ram and it went past 1100, GT2000C7 same thing, cheap corsair vengeance 1600 sticks bench up to 2133 even for me but it takes a bit of patience and fine tuning. There are some SPDs from wath ive seen that dont seem to agree well and IMCs that just arent up to par which could be Jody's case but personally all chips i stuck in UD5 and UD7 i have here are doing the same. Jody certainly has plenty of decent ram that works for me so ram shouldnt be an issue . All my chips respond to VTT raised up to about 1.24v and they also scale with vdimm, also try Marvel SATA3 port on the HDD and PCH bump if you get some stability issues with higher bclock

Looking forward to it Jody, 32M and 3DMARK01 baby


man cheapseats put the hammer down early, i gotta start doing some proper runs it looks awful now doesnt it

Thanks dino seems like its IMC related then because GTX2's PSC right? Works fine here but when i use Hypers cant seem to push past 2100, then again not much difference from 2100-2200... Ill try bump the pch voltage and increase vtt a bit more, already at 1.2 though..

[dinos22]

GT2000 cas7 - hyper
GTX2 - hyper
GTX3 - PSC i think

[Johnny87au]

YEAH! that probaly explains it lol, dam ud7 hates my hypers and likes PSC

[Dumo]

I gotta try this UD7

Newegg voided my MIVE order yesterday

[PatRaceTin]

yes my UD7 hate MGH-E

[chew*]

yes my UD7 hate MGH-E

MGH-E...............

Nothing wrong with UD7 or MGH-E.......

[Johnny87au]

@ chew my Corsair gx2 dont clock very well, but when you run some BBSE'S dimms seems to find that sweet spot without any hassle.. I cant push past 2133 on my eplidas but can push beyond it with my bbses.. I thought it would of been IMC related or bios related but so far nothing seems to fix it.. im guessing compatibility issue? I know it sounds silly but out of options ha

[chew*]

@ chew my Corsair gx2 dont clock very well, but when you run some BBSE'S dimms seems to find that sweet spot without any hassle.. I cant push past 2133 on my eplidas but can push beyond it with my bbses.. I thought it would of been IMC related or bios related but so far nothing seems to fix it.. im guessing compatibility issue? I know it sounds silly but out of options ha

just crappy set of elpida is all it is man.

no compatibility issues.

the max ram speed i can do with hypers is max i can do with PSC.

Same wall for my chip.

[PatRaceTin]

Strange Problem when i use Elpida Hyper @1866 i can bench at 5.4Ghz

When i change to G.Skill 2133 C9 (PSC40nm) i got BSOD at 5.4Ghz

[Johnny87au]

just crappy set of elpida is all it is man.

no compatibility issues.

the max ram speed i can do with hypers is max i can do with PSC.

Same wall for my chip.

Might try some Super talents, just gotta find some grr

[chew*]

Might try some Super talents, just gotta find some grr

yah maybe they will work if you get a good bin.

I tested from 1600 C6 SPD bin to 2250 c8 spd bin.

like 1 set 1600 c6 MHG-e, 2 sets 1866 c7 mhn and mgh, 2 sets 2000 c7 mhn and mhg and one set 2250 mgh.

All could run 2166, not all could do 7-7-6 however, voltage required to do XXX speed scaled linear, the lower bins needed alot more voltage.

[TASOS]

Well , i've stopped blaming the boards and bioses (at least in my case).
For me , it's clearly a cpu IMC problem.

I cant stabilize my hypers with 1/8.

I can play with 1/7 @933 7-7-6-1T all day ... but when i switch to 1/8 @1066 i can only do spi1M @ 9-10-9-28 nomatter how many volts or trfc i use.

Same behaviour from my Corsair Dominator GT and my Super Talent Speed.
(Both previously tested on X58 and capable of 1066++ @CL7)

I've tried both the Asus P8P67 Pro and Gigabyte P67A-UD4 ... and almost every available bios.

Same results.

[chew*]

Well , i've stopped blaming the boards and bioses (at least in my case).
For me , it's clearly a cpu IMC problem.

I cant stabilize my hypers with 1/8.

I can play with 1/7 @933 7-7-6-1T all day ... but when i switch to 1/8 @1066 i can only do spi1M @ 9-10-9-28 nomatter how many volts or trfc i use.

Same behaviour from my Corsair Dominator GT and my Super Talent Speed.
(Both previously tested on X58 and capable of 1066++ @CL7)

I've tried both the Asus P8P67 Pro and Gigabyte P67A-UD4 ... and almost every available bios.

Same results.

From my testing on PRO, it can't do 2133.......

However with some serious subtiming work it can pass preety high. ( this is with a chip known to pass 2133 )

I will see if i can get the UD4 to cooperate for some testing......it has some vcore issues......

[maxxx]

Are those GTX1/2 still in the market? Or Corsair EOL'ed those already?

[chew*]

Are those GTX1/2 still in the market? Or Corsair EOL'ed those already?

All elpida hyper is EOL'd.

[maxxx]

All elpida hyper is EOL'd.

@chew: thanks for the reply. Any suggestions for a better ram? I have one last kit of the Dominator GT which have Hyper chips. Its going strong so far, but if it dies, am stuck....

[chew*]

@chew: thanks for the reply. Any suggestions for a better ram? I have one last kit of the Dominator GT which have Hyper chips. Its going strong so far, but if it dies, am stuck....

Better no. More flexible? My gskill flare 7-9-7 2000 kit is the easiest set to use with very good performance. Will it beat the best hyper no....but it will give them a run for the money.

[maxxx]

@chew: thanks. have another G.Skill kit (6-9-6-24) but it seems to hate the UD7. 2133 is a no go. The UD7 seems to like the Hypers better.

[chew*]

@chew: thanks. have another G.Skill kit (6-9-6-24) but it seems to hate the UD7. 2133 is a no go. The UD7 seems to like the Hypers better.

really? What speed bin.

I will give it a go in a few see if i can dial in some timings for that board.

[maxxx]

really? What speed bin.

I will give it a go in a few see if i can dial in some timings for that board.

@chew: its actually a triple channel kit (F3-16000CL6T-6GBPID) 2000Mhz. I know am not that good in overclocking and tweaking stuff, but this one is just not stable when running 2133 with the UD7. I have not tried any other board yet.