Leaderboard

It's not about me, it's about you. Why June though? I understand that you want to get a new GDC adapter, but I'm not sure if you actually need it. What makes you think that's the faulty component, if you also doubt your PSU? Unless there is something you didn't write here, I suggest to get PSU and GPU checked and try again. Don't worry, it won't be easy. There is a ton of software errors and malfunctions you can meet later.

Well, my PSU fan only works when it's under heavy load, which is never with just eGPU. I have only done this wiring once, which makes me no expert on troubleshooting. I would say that you should verify if your components work before any other action. Maybe you can use some other PC or PC maintenance shop to have your components checked.

Black screen because nvidia changed something in the drivers a few years ago. Sent from my SM-T560NU using Tapatalk

Hi. I would start investigating why is PSU not working. How can you tell if it's working? If you have everything wired right and laptop running, there is a green diod on GDC (at least on mine). You could also post the full spec, including eGPU and PSU.

Got a old-specced (LVDs screen) iGPU E6440 for my brother and an i7-4700MQ off ebay. He wans't interested in crazy performance so I didn't opt for a pricier 4800/4900MQ. I didn't have much time yesterday to test, but I can confirm that changing the multiplier using NVRAM works for the E6440 too. You can set the i7-4700MQ to run with the extra 2 multipliers turbo (x34 4C - x35 2C - x36 1C) confirmed with Throttlestop too. It will be possibly TDP throttled, but didn't have enough time to test extensively. Saddly enough BIOS version A06 (that came originally with the laptop) seems to have corrected the microcode issue that would allow the 4700MQ to run like an XM chip. When I have time with his laptop (not soon probably since he is hardly here) I am probably going to try to downgrade BIOS to A01 or A02 if possible and check if they have the older microcode which will let me to unlock the multiplier!

Finally, i reached "adult" status on this board, and now i can post by myself I successfully upgraded the SB i3, to an IB i5-3230M for 15$. Since my HyperX 2133Mhz kit is already migrated to the Dell, the first boot revealed that the memory controller of the i5 cant cope with the PnP (JEDEC) 2133Mhz @CL11. I locked the memory speed down to 1600Mhz CL11 , replacing one of the kingstons with a samsung module, just to be able to check the new CPU is working properly. Yes it does, and a little bit of TSBench revealed that it does outperform my Haswell-ULV on the same clock not only with lower power consumption (15.1W thanks to the Haswells IVR and integrated PCH VS 10.9W) but a 32M TSBench completes almost a second faster. The Haswell system has a very lean w8.1 x64 install, and the Ivy has a bloated w7 x64. (no throttling occurs, both cpus are running @2.4Ghz during the whole bench) The other thing which makes me very happy that when C-states are disabled in the bios, i can still toggle C1E using Throttlestop for the Battery profile(I was able to do the same on 1st gen. Core i anno, but unable to do it with 4th.gen.), and although it does not enable C3, C6 and C7, but still has a substantial impact in idle power consumption (3.1W vs 7.1W). And the advantages of disabled C states in my usage scenario is huge, so the ~+1W power consumption when idling is a fair trade-off for me.(This i5 idles around 2.5W with all C states enabled, although i have not tinkered with the settings so far to see if this can be reduced) The next thing on my list is finding the limit of the memory controller, but i'll have to dig into the topic deeper... My kit is a Kingston HX321LS11IB2K2/16, if anybody with the same kit would share their settings that would be great. UPDATE: Using EFI variables (Thanks timohour for the extract of A16 BIOS), i was able to lock the memory freq. to 1866, so my kit is running in dual channel 1866Mhz 10-11-12-30 CR1. This could be useful for some other folks too, when the automatic freq. configuration makes the system unusable, but one can get into the one-time boot menu (F12 during Dell logo). Unfortunately my machine wont even get to POST when the auto memory frequency configures the sticks to run @ 2133. Also, changing boot mode from Legacy to UEFI when one wants to mangle with EFI vars is unnecessary, because even in Legacy mode there is option to boot into the EFI shell from the USB drive. I guess SecureBoot still has to be disabled, but i will check. Setting: Memory Frequency, Variable: 0x1E6 {05 A6 12 04 13 04 D1 01 02 00 E6 01 10 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00} 0x60BA3 Option: Auto, Value: 0x0 {09 0E BE 02 30 00 00 00 00 00 00 00 00 00} 0x60BB1 Option: 1067, Value: 0x1 {09 0E 14 04 00 00 01 00 00 00 00 00 00 00} 0x60BBF Option: 1333, Value: 0x2 {09 0E 15 04 00 00 02 00 00 00 00 00 00 00} 0x60BCD Option: 1600, Value: 0x3 {09 0E 16 04 00 00 03 00 00 00 00 00 00 00} 0x60BDB Option: 1867, Value: 0x4 {09 0E 17 04 00 00 04 00 00 00 00 00 00 00} 0x60BE9 Option: 2133, Value: 0x5 {09 0E 18 04 00 00 05 00 00 00 00 00 00 00} 0x60BF7 Option: 2400, Value: 0x6 {09 0E 19 04 00 00 06 00 00 00 00 00 00 00} 0x60C05 Option: 2667, Value: 0x7 {09 0E 1A 04 00 00 07 00 00 00 00 00 00 00} There is another EFI var that for DIMM2 (the top slot) but it does not need to be modified if running dual chanel, because the freq, and timings will be determined by the module with the worst capabilities. I've also noticed that there is something wrong with the values, because this should be only 8 bit, instead of 12 (?!) Setting: Memory Frequency, Variable: 0x1E7 {05 A6 12 04 13 04 D2 01 02 00 E7 01 10 11 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00} 0x60C3B Option: 1067, Value: 0x42B {09 0E 14 04 00 01 2B 04 00 00 00 00 00 00} 0x60C49 Option: 1333, Value: 0x535 {09 0E 15 04 30 01 35 05 00 00 00 00 00 00} 0x60C57 Option: 1600, Value: 0x640 {09 0E 16 04 00 01 40 06 00 00 00 00 00 00} 0x60C65 Option: 1867, Value: 0x74B {09 0E 17 04 00 01 4B 07 00 00 00 00 00 00} 0x60C73 Option: 2133, Value: 0x855 {09 0E 18 04 00 01 55 08 00 00 00 00 00 00} 0x60C81 Option: 2400, Value: 0x960 {09 0E 19 04 00 01 60 09 00 00 00 00 00 00} 0x60C8F Option: 2667, Value: 0xA75 {09 0E 1A 04 00 01 75 0A 00 00 00 00 00 00} UPDATE2: I was also able to boot into windows @2133 CL11-12-13(factory) , when manually setting EFI var 0x1EF (Nmode) to 2N instead of auto. Using 2N mode improves stability, but 1N offers the maximum performance. Memory bandwith R/W/C was around 28k/30k/28k Mb/s. Before running a GFX bench to check for iGPU instability, i've restarted the system. Tried to restart, to be exact, because this functionality is lost, but there are some other settings available in the bios at the memory section, so maybe this could work out better than loosening the timings. I will continue to experiment tomorrow, until then i've reverted back to 1866, which is stable with the factory (tight) timings.

If you know your way around tweaking memory there are a bunch of variables that you could try (never tried them myself): Numeric: tCL , Variable: 0x1FE Default: 8 Bit, Value: 0x4EndNumeric: tRCD , Variable: 0x1FF Default: 8 Bit, Value: 0x3EndNumeric: tRP , Variable: 0x200 Default: 8 Bit, Value: 0x3 End Numeric: tRAS , Variable: 0x201 Default: 16 Bit, Value: 0x9 EndNumeric: tWR , Variable: 0x203 Default: 8 Bit, Value: 0x5End Numeric: tRFC , Variable: 0x204 Default: 16 Bit, Value: 0xFEndNumeric: tRRD , Variable: 0x206Default: 8 Bit, Value: 0x4End Numeric: tWTR , Variable: 0x207 Default: 8 Bit, Value: 0x3 End Numeric: tRTP , Variable: 0x208Default: 8 Bit, Value: 0x4 EndNumeric: tRC , Variable: 0x209 Default: 16 Bit, Value: 0xF End Numeric: tFAW , Variable: 0x20B Default: 16 Bit, Value: 0xAEnd Setting: NMode Support, Variable: 0x1EFOption: Auto, Value: 0x10Option: 1N Mode, Value: 0x0Option: 2N Mode, Value: 0x2 End For 8bit values you probably set from 0x0 to 0xFF (256) and for 16 bit values from 0x0 to 0xFFFF (65536). For example if you want to set tCL 13 you should set variable 0x1FE to 0xD etc. NMode seems to be the Command Rate use 1N for 1T or 2N for 2T.But you should probably also set Setting: DIMM profile, Variable: 0x1EE Option: Default DIMM profile, Value: 0x0Option: Custom profile, Value: 0x1Option: XMP profile 1, Value: 0x2 Option: XMP profile 2, Value: 0x3to Custom Profile.What kit?

If I am right the 3740QM has maximum unlocked bins x41 for 1 core x40 for 2 core x39 for 3/4 core. You should set the hexadecimal of these multipliers in every var. For example 0x25 (which is 1 core ration limit) you should set the value 0x29 which is the HxD of 41. At 0x26 you set 0x28 etc. Generally you can set the highest in every variable and your chip would go as far as it can. Regarding JEDEC I suspect that you can set the JEDEC profile spd with variable 0x1e6. Never tried it since there was no use for it. DO NOT USE THE VARIABLE 0x228 to flash an OC ME FW: It is possible that this mod causes bios corruption. I had problems after a flash since I couldn't reenable the ME FW flash through UEFI variables and I had to use the hardware mod to unlock the Descryptor region again. Unlock your descriptor like described here and flash a modified ME FW as described here. Unless you are interested in OC your RAM a little more than 2133, I wouldn't recomment to BCLK OC an [email protected] since you would definetely face Temperature Throttle. I faced some TDP throttling my self during the tests. I think that you should try the highest core frequency without additional voltage (it should be stable at 1350-1400MHz) plus dual channel high-speed RAM (2133MHz) if you haven't already. Keep in mind that dual rank chips have generally better performance than single rank chips and the faster the RAM the better the iGPU performance. Check http://forum.techinferno.com/general-notebook-discussions/6063-all-memory-not-created-equal-hyperx-2133-cl12-versus-ripjaws-2133-cl11.html thread for more info on RAM.

I'm always happy to contribute 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. A simple Windows 8.1 restart doesn't change the Ram settings. I was unable to get the laptop to boot with any of the Ram modules at 2133 (tested 4 different modules). All of them were 1,50v and manufactured before 2014. The 8GB modules are from 2012. 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. Here is a picture of the weak Ram module. @sagemaru The UEFI variables stick until you remove both the laptops battery and CMOS battery. Please check my post at the top of the previous page for more details about that.

Thanks timohour. I forgot that I also own a PE4L-PM060A. Maybe this one is easier to mod? I can provide photos if you think that helps. Already have my Dell E6430 (iGPU only/900p/Bios A16) I had to use uefi variables to unlock raid0 . As expected the variable that needs to be changed is different from the one of the E6440 = "0x19D". So in my case E6430 = "0x12D". And had to use them again to set up TOLUD in order to use eGPU. Using Thaiphoon Burner I've purchased Thaiphoon Burner but I was unlucky. 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. At 1866 the E6430 wont boot, even with another module installed and with different CAS settings. The other module has no problems with 1866. I can set XMP profiles for both of them or even JEDEC. Some other modules I've tested only allow me to create XMP profiles. With other Ram modules (2x4GB) I managed to get 1866 working in dual channel. 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. So I had to set them all again, including the one that allows me to use Raid0. Once this was done I got my system back and running without any more problems. Keep in mind that this was in my case. I can't be made responsible if this doesn't work with another system. I want to play with the other uefi variables when I get a chance, and I will update this post with my progress. Thanks to everyone that made this mods possible.

Hi timohour, Thanks for your reply. Its a iGPU model. I will probably keep this system for two or tree years. I don't think I will be able to afford a new system anytime soon. I have a good desktop for gaming. Its not the latest thing but Its still very capable. I7 990x, Rampage 3 Gene and 12GB DDR3 1600. I get a kick at playing around with this eGPU stuff, I like it better than actually playing games. Soldering skills wouldn't be a problem as they are a requirement at my current job and I need to practice. If I manage to sell my 3630QM locally I will try to buy a 3720QM or higher. Would a 3920XM make any sense in a E6430 or is the max recommend cpu a 3840QM due to its lower TDP? I have a EXP GDC v.6 and a Beast, both of them EC. The Beast can be turned into mPCIe. The cable is reasonably cheap and easy to get. Would that help in any way? Thanks for your input.

Answering your questions: * You wouldn't know what the ideal core limit is. On the i7-37x0/38x0QMs though you can set only 4 more bins for each turbo. Even if you set a bigger number you can't surpass your chip's maximum. e.g. an OEM i7-3720QM would have the following original Turbo Boosts: 1-core --> 3.6GHz --> (x36) 2-core --> 3.5GHz --> (x35) 3-core --> 3.4GHz --> (x34) 4-core --> 3.4GHz --> (x34) Using the maximum 4 more multipliers Intel unlocked on 37x0/38x0 on the 3720QM you can get 1-core --> 4.0GHz --> (x40) 2-core --> 3.9GHz --> (x39) 3-core --> 3.8GHz --> (x38) 4-core --> 3.8GHz --> (x38) That's how I chose the multipliers. On your situation with the i7-3840QM your maximum multiplier would be 1-core --> 4.2GHz --> (x42) 2-core --> 4.1GHz --> (x41) 3-core --> 4.0GHz --> (x40) 4-core --> 4.0GHz --> (x40) I can't tell if it would boot with these settings though so I would suggest that you use BCLK OC on lower multipliers to make sure you can use that high clocks because if you don't you may won't be able to boot and you would need a locked CPU (i3,i5 or maybe i7-36x0) to remove the settings on the NVRAM if CMOS reset won't work. * As Khenglish has noticed on another post its best to use as high BCLK OC as possible, since BCLK overclocking does not cause an automatic voltage increase, which multiplier increases do. Less voltage means less heat/less power and maybe higher stability. When i unlocked my CPU highest multi would be x40 for 1 core. When I tried to BCLK OC it would hang for everything above 102,3MHz. This means that with x40 for one core I would have a BCLK as low as 102,3MHz. With 102,3MHz BCLK OC my 2 core Turbo would be 102,3 x 39 = 3,98GHz while my 4 core Turbo would be 102,3 x 38 = 3,89GHz. When I lowered my 1 core Turbo @ x39 and kept 2-core turbo @x39 and 3/4-core turbo @ x38, I could again BCLK OC higher @ 104,7MHz. This means that with x39 for one core I would have a BCLK @104,7MHz. With 104,7MHz BCLK OC my 2 core Turbo would be 104,7 x 39 = 4,08GHz while my 4 core Turbo would be 104,7 x 38 = 3,98GHz. Almost 100MHz higher. Got this? *Yes, you can use the 99% CPU usage setting to prevent the overclock when not needing max performance or you can use Throttlestop to lower the multi or even use XTU to set your multiplier lower than the value you set in NVRAM. (keep in my mind that Throttlestop overrides the settings you have done in XTU). We will be happy to attend your successfull Latitude OC. Feel free to ask anything else you need. It wouldn't go lower than 3.25GB. Maybe I needed to do a thorough boot. I did a CMOS reset(remove cmos battery for a few minutes) and everything is back to default (including CoreRatio and power limits btw). Anyway manual setting was easier and more fun. I may try if this work for me too when I have time. This was a unstable setup that I used with a mini pcie to pcie extender and soldered some cables on a second mini pcie that was modified to check the ODD usage... I could send you a photo of the current setup. Regarding the CPU I am quoting Tech Inferno Fan advice In simple words with the i7-3630QM your max turbo for 4-core would be 3.2GHz while for the 3720QM your max 4-core turbo would be 3.8GHz. Also in my case the memory controller in my i7-3720QM is much better than the one in the 3630QM, since it would be rock stable @2234MHz dual channel memory while the 3630QM would crash even @ 2216MHz. Just for your instance 3DMark06 CPU score difference would be almost 1100 points between a OCed 3630QM and an OCed 3720QM.

Unlocking i7-37x0QM/38x0QM extra 4 multipliers on a Dell Latitude E6430For a full guide on how to do this check the first post.It works!!Just used the NVRAM tool to set my core limits x40 (1C), x39(2C), x38(3-4C) and my 3720QM and it works!!!Only problem is that I have to set my long time TDP a little higher cause after around 40 sec anything above x35 (x36,x37,x38) would throttle down to x34,x35.(Not because of thermal limitatiofns. I could see that my 3630QM would throttle due to thermal reasons when it reached 105C.)UPDATE: Regarding my long power limit I set [ Long duration power limit 0xB40], [Short duration power limit 0xB41] at 100W (0x64) and my [ Long duration maintained Variable 0xB42] at 128sec (0xff) (not sure if the last is necessary). But I can tell that there is no more TDP throttling now. TDP throttling kicks in after ~ 6 minutes OF 100% CPU Utilisation! Only solution as mentioned by Khenglish here is to use an invalid adapter and use Throttle stop to overcome the invalid adapter throttle. Also seems like max VID for this is CPU is limited to 1,2109V starting @ x37.(check the table on the previous post). This means that there is plenty of room for undervolting here. Any ideas?Setting single core @ x40 did significally lower my headroom for BCLK OC. It would BSOD if I set anything over 102.4 in XTU. Highest single core OC 4.09GHz!!!So I decided to limit the CPU up to x39 using XTU for both 1C & 2C, and set my BCLK @ 104.7.This way I can have a 1C/2C Turbo @ 4.08GHz vs 3.98GHz and a 4C Turbo @ 3.98GHz vs 3.88GHz + I can take advantage of raised BCLK and OC my RAM @2234MHz + I would run similar clocks with lower voltage (BCLK OC does not cause an automatic voltage increase)3DMark06 CPU score had a great improvement of almost 1100 points compared to the stock chip or an OCed 3630QM and almost 1500 points compared to my 3630QM @ stock. i7-3720QM stock i7-3720QM OCed I would definetely love an XM CPU but its pricetag for an OEM product is very high and I am sure that it won't provide much better performance until it reaches its thermal limits (especially in my E6430 which is a small 14" laptop).A high binned 3740QM or a 38x0QM that i hope it would have a little more headroom in the highest multipliers' voltages meaning that it could do 4C @ 4,07GHz for i7-3740QM/3820QM and 4C @ 4,18GHz for the i7-3840QM + lower temps provided that it could go over 1.21V, would be much appreciated but won't bring huge improvement.UPDATE: Seems like the highest voltage for all i7-3XX0QMs is limited to 1.2109V. So Practically no actual gain if you go to a 3740QM or an 38x0QM unless it is a superior chip regarding thermal performance. It is possible that every 4C i7 won't be able to do more than 4,1GHz due to insufficient voltage but this needs more testing...I am very happy with the upgrade. These Latitudes are rare laptops and they provide gaming machine rate capabilities for their pricetag.I don't think that I have to envy my brothers Haswell Y50-70 and his 4720HQ that he got for 1000€...I didn't spend more than 400€ (including 3720QM, 8GB 2133MHz, and used laptop) and I got better performance and portability...There is a guide here on how to overclock your BCLK using XTU.

The i7-37xxQM/i7-38xxQM better the i7-36xxQM with their +400Mhz locked turbo bins which some bios/uefi vars unlock. The i7-39xxXM have fully unlockable multipliers but you'll be TDP throttled and temp throttled to much lower multis than they are capable unless can increase TDP and improve cooling. Hence why the i7-37xxQMs might be a good one to look at. Would suggest skipping the i7-38xxQMs. They get a bit more cache than the i7-37xxQMs. Hardly worth paying a premium for. We do not have any data on whether the E6530/E6430 can have those extra turbo bins unlocked with UEFI vars. Though Khenglish's mods on the opening page would suggest you are more likely than not of being able to do that. If I had one of these machines then I'd be certainly up to giving it a go with a i7-3740QM. You can see that a i7-39xxXM is not such a cost effective solution to getting a bit more performance over your i7-3630QM. A i7-37xxQM/i7-38xxQM with unlocked turbo bins being the sweet spot for maximum performance at a reasonable price on these systems.