[HowTo] SO-DIMMs Extreme: Boost 1600 to 2133 and beyond / JEDEC & XMP

Discussion in 'Hardware Components and Aftermarket Upgrades' started by James D, Jan 4, 2012.

Thread Status:
Not open for further replies.
  1. Zer0 C00l

    Zer0 C00l Notebook Consultant

    Reputations:
    107
    Messages:
    165
    Likes Received:
    8
    Trophy Points:
    31
    So with this taiphoon burner program I can achieve 2133Mhz CL10 with my 4x4GB 1866Mhz CL9 Corsair Vengeance ram in my alienware m18x?

    Is it totally stable?

    Can I go even higher than 2133Mhz?
     
  2. nrat

    nrat Notebook Enthusiast

    Reputations:
    21
    Messages:
    48
    Likes Received:
    0
    Trophy Points:
    15
    has anyone tried the Mushkin Enhanced Essentials 8gb modules? they run at 1.35V it makes me thing that they may be running 30nm tech but i cant find anything on them at all
     
  3. residualvoltage

    residualvoltage Notebook Deity

    Reputations:
    717
    Messages:
    761
    Likes Received:
    21
    Trophy Points:
    31
    It all depends. You need to test your ram individually. None of my corsair vengeance 1866 cl10 run at stable at 2133. Try to check in each post which ram sticks they are using... Model company etc etc.

    The above results I have posted are on Samsung 1600mhz 11-11-11-28 chips at 4gb density and I am using them on Dual Channel at 8gb total. 16gb is possible for 1866 and 2133mhz... It depends on the handling of each ram stick as just one could be not a good overclocker and would then cause errors mixed with the rest atincreased speed. There are sticks operating at 1866 CL9,10 and up. There are ram sticks some of use programmed over their normal speed and some are handling 2133 CL13,12,11,10 and CL9. What kind of volts they need depends on testing individual sticks also. RiRi-FiFi got 10-10-10-24 on 1866 which is a very fast timing. My Samsung chips are handling more than a pair of Hynix, Kingston and Corsair that I have tested.

    For me 2133 CL13-CL10 has only required 1.55v. My 2133 9-10-10-25 requires 1.6v. When memtest was used I passed at that 9 10 10 25 on 1.55v for 35 hours. By using my "pre boot assesment" under diagnosis heading of my boot menu on my Alienware I ran it and allowed the extended memtest to run too which revealed to make my chips fully stable at that I needed 1.6v. For that timing unlike 2133 CL13-10 I need my baseclock at 99.8 or 99.72 via bios whichever makes Windows show 99.6 instead of 99.7.

    As for over 2133mhz me and a few others have ran 2133 mhz and raised our baseclocks. John got 108mhz+ * 2133 he got into 2300mhz+ on his ram. we/he hasn't said that's stable but it was interesting none the less. He stated that 108 baseclock may not be stable but perhaps 107 or 106 could be for him as he wan't sure without testing. So far I started testing again and have stabalized 106.33 * 2133 on my M18x R1 at so far, 13-13-13-36, 12-12-12-36, 11-11-11-36, 11-11-11-33, and currently running tests for 10-11-11-33. I'm running 1.65v though to ensure long term stability inside the ram. So far so good still working my timings down.

    IGP is stable on 2133mhz even my tight timings of 9-10-10-25. I found as long as you use 1.6v or less you can boot and use IGP on even these speeds and timings. For a second I tried 2266 on IGP at 1.65v and causes a shutdown as soon as desktop attempts to load. But I did successfully play for a bit on 2266mhz when I had 1.6v set with no shutdowns. As mentioned long term may not have been fine at 2266mhz on the 1.6v but it allowed it to work with the IGP no probs.
     
  4. residualvoltage

    residualvoltage Notebook Deity

    Reputations:
    717
    Messages:
    761
    Likes Received:
    21
    Trophy Points:
    31
    *double post sorry twas ma phone that did it.
     
  5. Johnksss

    Johnksss .

    Reputations:
    10,642
    Messages:
    19,030
    Likes Received:
    11,498
    Trophy Points:
    931
    was not stable...would crash during gaming.

    but if i ran 2133 or even 2200 it was stable. the 2300 was strictly for speed and to see how high the bclk and ram could go.
     
  6. residualvoltage

    residualvoltage Notebook Deity

    Reputations:
    717
    Messages:
    761
    Likes Received:
    21
    Trophy Points:
    31
    That's what I thought thanks for elaborating John. Good news if you end up testing more as above I am gaming stable at 2266 1.65v 10-11-11-33. Still working down it takes so long to be sure your stable, but you know how it goes John. When I get as far as I get I'll post my THP for you to see how yours does on my Cl9 2133 and wherever I get on the 2266 :) cheers friend here's to the coolest project ever lol.

    I've been testing 7970m during day when I have time and leaving ram tests going overnight when I sleep.
    Cheers this is a lot of fun.
     
  7. funky monk

    funky monk Notebook Deity

    Reputations:
    233
    Messages:
    1,486
    Likes Received:
    1
    Trophy Points:
    55
    You could always do it the other way round (imo a more useful method). What you do is you push it to a point where you know you'll get errors and crashes after a few minutes and then you work down. Once you've found a frequency that works for an hour or so you knock the frequency down a tiny bit more (probably use bclk in this case), or increase the voltage a little bit and then you know it's stable. That way you save hours of validation and you can be pretty damn sure you've got something that won't fail.
     
  8. residualvoltage

    residualvoltage Notebook Deity

    Reputations:
    717
    Messages:
    761
    Likes Received:
    21
    Trophy Points:
    31
    Well lol I am doing that my 2133 won't go tighter. 2267mhz is my limit at CL13. As follows 2133 at 106.54 failed. 2133 at 106.42 via bios is what I am actually on. Giving me what I am testing now 2267 to be exact. I can't use higher mhz. And I have no more than 1.65v to work with. I got here very quickly the way I'm testing. I use memtest and preboot assesment from alienware. it's been faster than it seems but you have to test for hours or you don't know it's stable. I've had them fail out into 10-12 test passes at nearly 12-15 hours in. My 2133 I did the 35 hours on my final testing when I was as far as I go to be absolutely sure only. I test on preboot assesment then memtest. Preboot will throw errors for me and or complete within 15min. Next I test in memtest etc and the next day I bench, stress and game to see how they handle.

    Here is where I am doing what you suggested already. This is how I went up till now. First I set 13-13-13-36 the slowest CL timings my system boots (no 14t ? And up) and tested fastest mhz ie 2267 is where I ended up. Next I tested and passed error free 12-12-12-36. Then 11-11-11-36... Then 10-10-10-36 and hit first wall even losest 10's wouldn't pass without throwing errors. So I moved back up to 11-11-11-33 and that passed. Now I'm on 10-11-11-33 and the 10 is the tightest it can be ie one before CL9. It only took a few days to get to here and this way I can guarantee stability I'm not guessing on anything... I tried that on the beggining and the fastest accurate way has been what I described. You can see how I can go after that. I'll get the first 3 numbers as low as possible but only changing one at a time and confirming stability. Next the 4th and 5th number are tied together... You add the third CL number in nanosecs to the 4th number and that gives you the only value you can use for the 5th number. Now The 6th nimber is the only other one I adjust and I do that one last. So after 1,2,3,4 and dth timong is tightest as possible and mhz and volts are as far as you can I lower the 6th as far as possible in increments till it errors again and set it where it's stable. The tertiary/secondary timings like the whole right side column in Thaiphoon burner timing table editor/XMP editor leave those as is as the wil need to be what they are already set to. 2133,1866 and all other speeds will have a whole different right column. Any change I've done there always causes errors. So for my 2133 I started at CL13 and worked down for a stable 9-10-10-25-(30 something)-(30something)-88T (at 2133 that value defaults to 160T)

    I think if anyone follows the methodolagy above they could find max of their ram without wondering if it's stable.

    Just my opinion and I respect any other methods just the same. I just got into ram overclocking I have no previous experience. I'd say everyone in these ram threads has done outsatanding. Maybe some of you can benefit from this method... Maybe not Cheers though it's plenty fun.
     
  9. Zer0 C00l

    Zer0 C00l Notebook Consultant

    Reputations:
    107
    Messages:
    165
    Likes Received:
    8
    Trophy Points:
    31
    It is interesting but I'm happy with 1866 9-10-10-27. I think the amount of hassle for the amount of performance gained is just not worth it. I dont think I'd even be able to tell the difference between 1866 and 2133 in any everyday apps
     
  10. residualvoltage

    residualvoltage Notebook Deity

    Reputations:
    717
    Messages:
    761
    Likes Received:
    21
    Trophy Points:
    31
    That's a great timing for 1866. I agree the hassle is high when trying to determine ranges. In my benches I've tried when the latency is low enough 2133+ is way faster than 1866. I'm sure your system likes 1866 CL9 and is working fine.
    Interesting your timing is similar to mine. 1866 9-10-10-27 :) vs 2133 9-10-10-25... I think it's pretty cool you found those timings.

    Update for my project: now working on 9-11-11-33 @ 2267 mhz :) just keeps getting lower :)

    I'd say most of us shooting for 2133 are enthusiasts. I didn't post my findings to get everyone to do the same... Just figured my experience with my own fun could help others atleast I hope.

    It's simple for any one else. Pick a already safe Jedec speed and set it and forget it.

    I personally am working to get tightest timings I can because 2267 @ cl13 it is not faster than some 2133 and 1866

    When I tested 2133 at CL13-CL9 the speed goes up by a very large amount. If a ram set can run your 1866 Cl9-10-10-27 but 2133 only runs on CL13 the obvious choice is 1866. For some of use we could run 2133 9-10-10-27 in which case 2133 is well worth it over 1866 etc.

    I hope more keep finding speeds and timings that work good. I am seeing a lot of 1866 Cl9 variations and that's great... My Corsair Vengeance last I tested wouldn't even tighten one latency by one single adjustment without error... So it's nice to see this progress from everyone. Ri-Ri Fi-Fi did a nice job and so did many others.
    Your testing has finished and others testing has just be begun. I'd have to say most people push boundaries because other people inspire and push each other... That's truly what makes the tech community so great.

    Latency and ram speed gohand in hand. I noticed 2267 at CL11-11-11-36 had more bandwith than 2133 CL9-10-10-25 and matched in latency... Maxmem tested around 23gb on 2133 above and 52 latency. 2267 at the timing mentioned received 24gb at 52 latency. As I get it lower that latency will go even lower and bandwith will go up maybe a hair more.

    If you get a chance download if you care to the winrar app and go to tools benchmark and run it for a minute and post pic... That will show what your cpu+ram can average in compression per second. 1866 should get atleast 6mb/s and when I checked my 2266 at the cl11 it was already nearing 10mb/s. This sounds like a little amount but it's a lot compared to other setups. A synthetic bench may not show everything in real world use but it does show a great example of how everyday tasks speed up the higher the speed and lower the latency. So you can imagine the differences in file transfers, bus communications and much more. Latencies for anything your system does would improve. Some people do a lot of work on their comps and what takes a pc a few mins to complete... time is shaved off that. If you have a long term project a faster system could save you maybe a few minutes in a day. Not much individually but out of our lives some sit and wait for everything to complete and when that equates to a few hours in a month it's definately a benefit. I'd rather a rendering project finish early if it can.

    I respect everyone here and that includes what anyone chooses to do with their own system. I do hope though that if others want to try that they feel comfortable doing so and knowing what the benefits are if there are any.
     
Thread Status:
Not open for further replies.

Share This Page