- LATITUDE E6440 RAM UPGRADE UPDATE
- LATITUDE E6440 RAM UPGRADE MODS
- LATITUDE E6440 RAM UPGRADE WINDOWS 8.1
The irony of this system is that with overclocking and high-speed ram, the dGPU becomes redundant and you can get better battery life and comfortably use eGPU.
Please check my post at the top of the previous page for more details about that. Here is a picture of the weak Ram The UEFI variables stick until you remove both the laptops battery and CMOS battery. Maybe that's why I can't get more than 1866 dual or single channel? Or its my 3630QMs memory controller? This was tested using bios A16. All of them were 1,50v and manufactured before 2014. I was unable to get the laptop to boot with any of the Ram modules at 2133 (tested 4 different modules).
LATITUDE E6440 RAM UPGRADE WINDOWS 8.1
A simple Windows 8.1 restart doesn't change the Ram settings. My cpu is a 3630QM and I can confirm that once I add JEDEC timmings 1866, all I have to do is shutdown and start again and the memory automatically runs at 1866. Could you elaborate on your ram module (s/n and/or a photo of the memory chips) so we can avoid them in the feature?Īlso could you add your CPU? I have been thinking to build a table on the first post with user configurations and mods.Ĭan you confirm that memories with JEDEC timings 1866MHz or 2133MHz will automatically speed 1866MHz or 2133MHz respectively? Rereading your edited post, I say nicely done.
LATITUDE E6440 RAM UPGRADE MODS
Thanks to everyone that made this mods possible.
LATITUDE E6440 RAM UPGRADE UPDATE
I want to play with the other uefi variables when I get a chance, and I will update this post with my progress. I can't be made responsible if this doesn't work with another system. Once this was done I got my system back and running without any more problems. So I had to set them all again, including the one that allows me to use Raid0. Thaipoon Burner is very easy to use and at least in my case if I use uefi variables to load a XMP profile that the Ram cannot handle, all I had to do was remove the battery and disconnect the CMOS battery, reconnect after a few seconds and the uefi variables revert to their default values, as would the bios settings. With other Ram modules (2x4GB) I managed to get 1866 working in dual channel. Some other modules I've tested only allow me to create XMP profiles. I can set XMP profiles for both of them or even JEDEC. The other module has no problems with 1866. At 1866 the E6430 wont boot, even with another module installed and with different CAS settings. It turns out that one of my "cheap" Ram modules from 2012 (8GB Kingston 1600 CAS11) is a bit weak and only lets me lower the CAS to 10. I've purchased Thaiphoon Burner but I was unlucky. And had to use them again to set up TOLUD in order to use eGPU. As expected the variable that needs to be changed is different from the one of the E6440 = "0x19D". I had to use uefi variables to unlock raid0. I can provide photos if you think that helps.Īlready have my Dell E6430 (iGPU only/900p/Bios A16)
In case this isn't feasible you would be able to use a riser but there would be a toll on signal's integrity. (where we can see if there is a possiblity to solder cables)
Check this out or if possible upload a close photo of the bottom of your GDC product. I don't know the structure of the EXP GDC v.6 or the Beast (I never bought GDC products), but I guess that you would be able to solder the 2nd lane's pcie signals from your gear to a mini pcie adapter. This means that you won't be able to use your EC gear. As noted on previews posts you would need two of the internal mini pcie ports to run x2 2.0.
0 kommentar(er)
