M378B5773DH0-CH9
It should be 30nm if I am correct.
M378B5773DH0-CH9
It should be 30nm if I am correct.
Guys, tell me it is normal with USPS:
Why nothing during Jan the 2nd? :(Quote:
Last event
Date Time Location Event Details
December 31, 2011 08:13:00 AM Miami FL US Arrival Scan
http://skinflint.co.uk/eu/531278
This should be Samsung 30nm aswell. However they are not idenctical low profile ones.
Factory code: M378B5273DH0-CH9 or -CH900
Just ordered 4 sticks for my p67 deluxe and 2600K. Lets see if i can have 2133 CL9.
Same chips posted in one russian forum
http://occlub.ru/forum/showthread.php?t=1813
first try on the MIVE
wont boot at 2400 i tried till 1,55 and CL12 i get ERROR 59 wich is CPU microcode error
so i pushed bclk this mobo goes to 108 so its not an issue
here first screenie
http://img38.imageshack.us/img38/293...amsungram1.jpg
Uploaded with ImageShack.us
if you spot the everest screen i just realize that it says MOBILE CPU lmao i dont know if its 2105 BIOS cauz other versions of everest shows the same
so far this is what i got for now
*thanks OC nub for posting volts as it was a nice start
i have some doubts maybe someone can clear them
as its very low volt BIOS detects perfect 1,35v just i dont know how much VTT to use as i remember there was a rule like VTT - VDIMM must not go out of 0,5 range but this was on other I7's
cheers to all
Sergio
well after some tests i conclude that def not a mem for MIVE or MIVE needs a BIOS update
Why is that?
Didnt think 2400 worked on SB? Dont you need SB-E for the 2400 ratio?
yeah guys even that i got 2400 for select on the mobo i get CODE 59 wich means CPU MICROCODE ERROR as manual states, and closer divider is 2133, so i need to push bclk for anything above 2133
i did a nice 2200 CL10 pushing 103 x 49 but i need to redo my OC as needs more VCore etc---
So far good mem but i went back to my patriots 2133 9-11-9-27 16GB 1T
cheers to all
Sergio
I tried these out as well on my R3E, I did manage 2400Mhz... 11,11,11,28 , had to run dimms at 1.6v though, I ran a couple or Linx runs ok. but not really stable
I just used 2 sticks, to see if I could get a boost on the latency while getting 8 gig over the tri 6 gig.
In the end I didnt see any real performance gain overall over my current set up, I guess cos i could not get timing tight enough so went back to the corsairs ..
I tried 2133/ 2175 on 10,10,10 .. 1.5v.. but again.. performance not great, I can get 2133 8,8,8 24 with the corsairs.. but even these timings are slightly less performance than the tighter 7,7,7,20 .
@ Andressergio
With your VTT at 1.1v you are good/safe up to 1.6vdimm, meaning 1.6vdimm or less, if your Patriot kit is 1.65v, you are outside that range by .05v, to stay within the range just raise VTT to 1.15v or higher with the 1.65v memory kits if you are concerned. Im not sure if anyone follows this rule with SB, I havent and have had no issues.
I never run vccio at anything over 1.0875 as it usually caused instability with my cpus and always 1.65v, and while benching 1.8v all the time for 224X 6-9-6-20 on the GSkill RipjawX BBSE sticks I have, no degradation or problems here.
I think the whole 0.5v vtt/vdimm rule was more so for Bloomfield and Gulftown.
why u say im a failure ? i just didnt know this issue of SB mate at least im here on this forum to learn everyday more and help other ppl, i can be mistaken but i aint no failure
i just been told by some friends here that only ES had the divider
2133 9-10-10 i only tested mem till 1,5vdimm and its not stable at those timmings, best it was 2133 10-10-10-30 1T @ 1,5
talking about the 2400 divider i really dont know why mem goes easy to 2250+ and we on MIVE dont have nothing between 2133 and 2400 to select, im sure this mem will go easy at 2200 or more at CL10