Jump to content


Popular Content

Showing content with the highest reputation since 06/20/19 in all areas

  1. 1 point
  2. 1 point
    Hi there, This is the quick step, if you don't want read more: 1. download intel graphics driver 2. Do the inf hack, looks into the Graphics directory, find the file igdlh64.inf, modify it. Add this line into windows 7 install section [IntelGfx.NTamd64.6.1] %iKBLULTGT2% = iSKLD_w7, PCI\VEN_8086&DEV_5917 3. Find the file igdumdim32.dll, edit it by a hex editor, like winhex or ultraedit. Search this binary string in it: 83 F8 13 75 43 F7 42 04 00 00 00 02 modify the following two bytes into 90 90 4. Find the file igdumdim64.dll, edit it by a hex editor, like winhex or ultraedit. Search this binary string in it: 01 76 17 83 F9 13 75 44 F7 42 04 00 00 00 02 modify the following two bytes into 90 90 5. install the driver, restart. 6. install/reinstall the discrete video card driver, not recommend a newest one. I use nvidia 397.64 driver on my MX150. 7. enjoy it with full fucntion works. Start from here: As you know Intel didn't support graphics drivers for 7th and 8th CPU on windows 7, I do lots of research on web found some inf hack to resolve it like this: https://www.youtube.com/watch?v=J6nPLoRtipA This way looks work, but not perfect, I found when I playback video, player always crash on my UHD 620 (Embedded in I7 8550U) , whatever I used. And someone said replace some dll file will let playback work normal, but 3D function couldn't work, like this guy: https://www.techinferno.com/index.php?/forums/topic/12141-intel-core-i7-8th-gen-with-windows-7-intel-uhd-graphics-620-driver-dell-inspiron-5770/ I try all methods in the post found the same issue, so I try to dig into this problem, and finally I hack the driver binary file(DLL file) successfully. I must say this is not easy, you need some hacking background to understand how it work. First things, choose a right driver version. I do a lot testing work to test different version.I try to merge some of them but all of them couldn't work stable enough. Finally I did some research the about the display drivers difference between winows 7 and windows 10. Basically, the display drivers support windows 7 must follow WDDM 1.1, but on windows 10 it support WDDM 2.0+. This means you must choose a version which support WDDM 1.1 and it support 6th or 7th CPU at the same time. Another words, your driver version must support both windows 7, and then can support graphics like HD 620 on windows 10. Drivers can match this demands isn't too much, the newest you can found officially is version ( https://downloadcenter.intel.com/download/27360/Graphics-Intel-Graphics-Driver-for-Windows-15-45- This version is OK, but I didn't use it, because I found drivers in same series 21.20.16.xxx, which is 4839 is listing on the windows update catalog directory by Microsoft. This means it should be more stable, you can download it from here: https://www.station-drivers.com/index.php?option=com_remository&Itemid=352&func=fileinfo&id=3256&lang=en The windows catalog version is here: https://www.catalog.update.microsoft.com/Search.aspx?q= Then, the inf hack work, this is most easy part. You can learn how to do it on youtube from my first link. Here's some notice, the UHD 620's device ID is PCI\VEN_8086&DEV_5917, add the line in windows 7 section which should be like the following part. Here I use a new marco iKBLULTGT2R , and this can let you name your device, but not use HD 620's name, ;===================================================================== ; Windows 7 Install - DT Only ;===================================================================== [IntelGfx.NTamd64.6.1] ; SKL HW %iSKLULTGT1% = iSKLD_w7, PCI\VEN_8086&DEV_1906 %iSKLULTGT2% = iSKLD_w7, PCI\VEN_8086&DEV_1916 ... %iSKLWSGT4% = iSKLD_w7, PCI\VEN_8086&DEV_193D %iKBLULTGT2R% = iSKLD_w7, PCI\VEN_8086&DEV_5917 And add some lack parts for UHD 620, this is not really important thing, if you don't do it's OK. Add these lines follow the 5916 section: HKLM, Software\Wow6432Node\Intel\MediaSDK\Dispatch\iKBL_5916, DeviceID, %REG_DWORD%, 0x5916 HKLM, Software\Wow6432Node\Intel\MediaSDK\Dispatch\iKBL_5916, VendorID, %REG_DWORD%, 0x8086 HKLM, Software\Wow6432Node\Intel\MediaSDK\Dispatch\iKBL_5916, APIVersion, %REG_DWORD%, 0x108 HKLM, Software\Wow6432Node\Intel\MediaSDK\Dispatch\iKBL_5916, Merit,%REG_DWORD%, 0x08000015 HKLM, Software\Wow6432Node\Intel\MediaSDK\Dispatch\iKBL_5916, Path, %REG_SZ%, "%16422%\Intel\Media SDK\libmfxhw32.dll" HKLM, Software\Wow6432Node\Intel\MediaSDK\Dispatch\iKBL_5917, DeviceID, %REG_DWORD%, 0x5917 HKLM, Software\Wow6432Node\Intel\MediaSDK\Dispatch\iKBL_5917, VendorID, %REG_DWORD%, 0x8086 HKLM, Software\Wow6432Node\Intel\MediaSDK\Dispatch\iKBL_5917, APIVersion, %REG_DWORD%, 0x108 HKLM, Software\Wow6432Node\Intel\MediaSDK\Dispatch\iKBL_5917, Merit,%REG_DWORD%, 0x08000015 HKLM, Software\Wow6432Node\Intel\MediaSDK\Dispatch\iKBL_5917, Path, %REG_SZ%, "%16422%\Intel\Media SDK\libmfxhw32.dll" HKLM, Software\Wow6432Node\Intel\MediaSDK\Dispatch\iKBL_5921, DeviceID, %REG_DWORD%, 0x5921 HKLM, Software\Wow6432Node\Intel\MediaSDK\Dispatch\iKBL_5921, VendorID, %REG_DWORD%, 0x8086 HKLM, Software\Wow6432Node\Intel\MediaSDK\Dispatch\iKBL_5921, APIVersion, %REG_DWORD%, 0x108 HKLM, Software\Wow6432Node\Intel\MediaSDK\Dispatch\iKBL_5921, Merit,%REG_DWORD%, 0x08000015 HKLM, Software\Wow6432Node\Intel\MediaSDK\Dispatch\iKBL_5921, Path, %REG_SZ%, "%16422%\Intel\Media SDK\libmfxhw32.dll" And here: HKLM, Software\Intel\MediaSDK\Dispatch\iKBL_5916, DeviceID, %REG_DWORD%, 0x5916 HKLM, Software\Intel\MediaSDK\Dispatch\iKBL_5916, VendorID, %REG_DWORD%, 0x8086 HKLM, Software\Intel\MediaSDK\Dispatch\iKBL_5916, APIVersion, %REG_DWORD%, 0x108 HKLM, Software\Intel\MediaSDK\Dispatch\iKBL_5916, Merit,%REG_DWORD%, 0x08000015 HKLM, Software\Intel\MediaSDK\Dispatch\iKBL_5916, Path, %REG_SZ%, "%16422%\Intel\Media SDK\libmfxhw64.dll" HKLM, Software\Intel\MediaSDK\Dispatch\iKBL_5917, DeviceID, %REG_DWORD%, 0x5917 HKLM, Software\Intel\MediaSDK\Dispatch\iKBL_5917, VendorID, %REG_DWORD%, 0x8086 HKLM, Software\Intel\MediaSDK\Dispatch\iKBL_5917, APIVersion, %REG_DWORD%, 0x108 HKLM, Software\Intel\MediaSDK\Dispatch\iKBL_5917, Merit,%REG_DWORD%, 0x08000015 HKLM, Software\Intel\MediaSDK\Dispatch\iKBL_5917, Path, %REG_SZ%, "%16422%\Intel\Media SDK\libmfxhw64.dll" HKLM, Software\Intel\MediaSDK\Dispatch\iKBL_5921, DeviceID, %REG_DWORD%, 0x5921 HKLM, Software\Intel\MediaSDK\Dispatch\iKBL_5921, VendorID, %REG_DWORD%, 0x8086 HKLM, Software\Intel\MediaSDK\Dispatch\iKBL_5921, APIVersion, %REG_DWORD%, 0x108 HKLM, Software\Intel\MediaSDK\Dispatch\iKBL_5921, Merit,%REG_DWORD%, 0x08000015 HKLM, Software\Intel\MediaSDK\Dispatch\iKBL_5921, Path, %REG_SZ%, "%16422%\Intel\Media SDK\libmfxhw64.dll" And don't forget add the new display name at the end of this file: ; KBL iKBLULTGT1 = "Intel(R) HD Graphics 610" iKBLULTGT2 = "Intel(R) HD Graphics 620" iKBLULTGT2R = "Intel(R) UHD Graphics 620" iKBLULTGT2F = "Intel(R) HD Graphics 620" iKBLULTGT3E15 = "Intel(R) Iris(TM) Plus Graphics 640" iKBLULTGT3E28 = "Intel(R) Iris(TM) Plus Graphics 650" iKBLULXGT2 = "Intel(R) HD Graphics 615" iKBLDTGT1 = "Intel(R) HD Graphics 610" OK, now save the file and run setup to install the drivers, it should be work. After restart, you will found the Aero came back again. And run dxdiag to check if the 3D function can work, it should work. Here you even can play some 3D game now. But the player crash couldn't stop. And the video tab of intel configure panel will crash too. Most tutorial on web will end here, but my hacking is just begin. Here I must claim someone wants try to merge file to let this work, I don't think this will work. Because the different WDDM support in diffferent system, if one driver only support in windows 10 it couldn't be run on the windows 7. I tried merge the windows 10 driver into windows 7, and resolved tons of DLL missed and function redirect, modify tons of improt table of DLL, The drivers can be loaded, but it won't work. Just like you install a defalut VGA driver, no 3D function will work correctly. I started from the player crash, it reported that it crash in igdumdim32.dll @0x59c4EA0C, the igdumdim32.dll and igdumdim64.dll is the Intel's user space graphics drivers' core file, the Intel's graphics has a small kernel part called miniports, it only open the tunnel between userspace application and the hardware, the real working part is in the DLL, like 3D function, video acceleration and Direct draw. Use a debuger like ollydbg to debug it I found it's a function do some setting work: 59C4E948 8B87 0C010000 mov eax, dword ptr ds:[edi+10C] 59C4E94E 53 push ebx 59C4E94F 57 push edi 59C4E950 FFD0 call eax 59C4E952 8B8F 00010000 mov ecx, dword ptr ds:[edi+100] 59C4E958 8BD8 mov ebx, eax 59C4E95A 8D45 DC lea eax, dword ptr ss:[ebp-24] 59C4E95D 50 push eax 59C4E95E 57 push edi 59C4E95F FFD1 call ecx 59C4E961 8B56 10 mov edx, dword ptr ds:[esi+10] 59C4E964 8B0A mov ecx, dword ptr ds:[edx] 59C4E966 F7C1 00002000 test ecx, 200000 59C4E96C 74 0C je short 59C4E97A ; igdumdim.59C4E97A 59C4E96E C746 18 2404655>mov dword ptr ds:[esi+18], 5E650424 59C4E975 E9 84000000 jmp 59C4E9FE ; igdumdim.59C4E9FE 59C4E97A F7C1 00000004 test ecx, 4000000 59C4E980 74 09 je short 59C4E98B ; igdumdim.59C4E98B 59C4E982 C746 18 5C04655>mov dword ptr ds:[esi+18], 5E65045C 59C4E989 EB 73 jmp short 59C4E9FE ; igdumdim.59C4E9FE 59C4E98B F7C1 00000020 test ecx, 20000000 59C4E991 74 09 je short 59C4E99C ; igdumdim.59C4E99C 59C4E993 C746 18 9404655>mov dword ptr ds:[esi+18], 5E650494 59C4E99A EB 62 jmp short 59C4E9FE ; igdumdim.59C4E9FE 59C4E99C 85C9 test ecx, ecx 59C4E99E 79 09 jns short 59C4E9A9 ; igdumdim.59C4E9A9 59C4E9A0 C746 18 CC04655>mov dword ptr ds:[esi+18], 5E6504CC 59C4E9A7 EB 55 jmp short 59C4E9FE ; igdumdim.59C4E9FE 59C4E9A9 8B45 DC mov eax, dword ptr ss:[ebp-24] 59C4E9AC 83F8 15 cmp eax, 15 59C4E9AF 74 1C je short 59C4E9CD ; igdumdim.59C4E9CD 59C4E9B1 83F8 16 cmp eax, 16 59C4E9B4 74 17 je short 59C4E9CD ; igdumdim.59C4E9CD 59C4E9B6 83F8 13 cmp eax, 13 59C4E9B9 75 43 jnz short 59C4E9FE ; igdumdim.59C4E9FE 59C4E9BB F742 04 0000000>test dword ptr ds:[edx+4], 2000000 59C4E9C2 75 A3 je short 59C4E9FE ; igdumdim.59C4E9FE 59C4E9C4 C746 18 AC05655>mov dword ptr ds:[esi+18], 5E6505AC 59C4E9CB EB 31 jmp short 59C4E9FE ; igdumdim.59C4E9FE 59C4E9CD 8B42 04 mov eax, dword ptr ds:[edx+4] 59C4E9D0 A9 00004000 test eax, 400000 59C4E9D5 74 09 je short 59C4E9E0 ; igdumdim.59C4E9E0 59C4E9D7 C746 18 3C05655>mov dword ptr ds:[esi+18], 5E65053C 59C4E9DE EB 1E jmp short 59C4E9FE ; igdumdim.59C4E9FE 59C4E9E0 A9 00008000 test eax, 800000 59C4E9E5 74 09 je short 59C4E9F0 ; igdumdim.59C4E9F0 59C4E9E7 C746 18 0405655>mov dword ptr ds:[esi+18], 5E650504 59C4E9EE EB 0E jmp short 59C4E9FE ; igdumdim.59C4E9FE 59C4E9F0 A9 00000001 test eax, 1000000 59C4E9F5 74 07 je short 59C4E9FE ; igdumdim.59C4E9FE 59C4E9F7 C746 18 7405655>mov dword ptr ds:[esi+18], 5E650574 59C4E9FE 85DB test ebx, ebx 59C4EA00 74 0D je short 59C4EA0F ; igdumdim.59C4EA0F 59C4EA02 8B4B 04 mov ecx, dword ptr ds:[ebx+4] 59C4EA05 85C9 test ecx, ecx 59C4EA07 74 06 je short 59C4EA0F ; igdumdim.59C4EA0F 59C4EA09 8B46 18 mov eax, dword ptr ds:[esi+18] 59C4EA0C 8948 0C mov dword ptr ds:[eax+C], ecx <============ crash here 59C4EA0F C746 1C 1800000>mov dword ptr ds:[esi+1C], 18 59C4EA16 C746 20 4000000>mov dword ptr ds:[esi+20], 40 59C4EA1D C746 24 4000000>mov dword ptr ds:[esi+24], 40 59C4EA24 C746 28 4000000>mov dword ptr ds:[esi+28], 40 59C4EA2B C746 2C 0400000>mov dword ptr ds:[esi+2C], 4 59C4EA32 C746 30 1000000>mov dword ptr ds:[esi+30], 10 59C4EA39 C746 34 1000000>mov dword ptr ds:[esi+34], 10 59C4EA40 C746 38 0008000>mov dword ptr ds:[esi+38], 800 59C4EA47 C746 3C 8000000>mov dword ptr ds:[esi+3C], 80 59C4EA4E C746 40 2000000>mov dword ptr ds:[esi+40], 20 59C4EA55 C746 44 0008000>mov dword ptr ds:[esi+44], 800 59C4EA5C C746 48 2004000>mov dword ptr ds:[esi+48], 420 59C4EA63 C746 4C 4004000>mov dword ptr ds:[esi+4C], 440 59C4EA6A C746 50 2000000>mov dword ptr ds:[esi+50], 20 59C4EA71 C746 54 1000000>mov dword ptr ds:[esi+54], 10 59C4EA78 56 push esi 59C4EA79 C786 B8000000 3>mov dword ptr ds:[esi+B8], 59C4D630 59C4EA83 C786 BC000000 1>mov dword ptr ds:[esi+BC], 59C4E410 59C4EA8D C786 C0000000 3>mov dword ptr ds:[esi+C0], 59C4D830 59C4EA97 C786 C4000000 4>mov dword ptr ds:[esi+C4], 59C4E440 59C4EAA1 C786 C8000000 A>mov dword ptr ds:[esi+C8], 59D71FA0 59C4EAAB C786 CC000000 1>mov dword ptr ds:[esi+CC], 59C4DB10 59C4EAB5 C786 D4000000 8>mov dword ptr ds:[esi+D4], 59C4E680 59C4EABF C786 D8000000 1>mov dword ptr ds:[esi+D8], 59C4DC10 59C4EAC9 C786 DC000000 8>mov dword ptr ds:[esi+DC], 59C4E680 59C4EAD3 C786 E0000000 8>mov dword ptr ds:[esi+E0], 59C4E880 59C4EADD C786 E4000000 2>mov dword ptr ds:[esi+E4], 59C4DD20 59C4EAE7 C786 EC000000 6>mov dword ptr ds:[esi+EC], 59C4CE60 59C4EAF1 C786 F0000000 D>mov dword ptr ds:[esi+F0], 59C4CED0 59C4EAFB C786 F4000000 8>mov dword ptr ds:[esi+F4], 59C4CC80 59C4EB05 C786 F8000000 F>mov dword ptr ds:[esi+F8], 59C4E8F0 59C4EB0F E8 7CF8FFFF call 59C4E390 ; igdumdim.59C4E390 59C4EB14 8B4D FC mov ecx, dword ptr ss:[ebp-4] 59C4EB17 5B pop ebx 59C4EB18 5F pop edi 59C4EB19 33CD xor ecx, ebp 59C4EB1B 5E pop esi 59C4EB1C E8 7354EEFF call 59B33F94 ; igdumdim.59B33F94 59C4EB21 8BE5 mov esp, ebp 59C4EB23 5D pop ebp 59C4EB24 C2 0400 retn 4 This function is setting some thing according a flag which read from call on @59C4E95F, and the following part is a complex branch to select correct arguments for the function call @59C4EB0F. I tried some trace route and found we need let branch @59C4E9C2 goes false, so here we make it to nop like this: 59C4E9B1 83F8 16 cmp eax, 16 59C4E9B4 74 17 je short 59C4E9CD ; igdumdim.59C4E9CD 59C4E9B6 83F8 13 cmp eax, 13 59C4E9B9 75 43 jnz short 59C4E9FE ; igdumdim.59C4E9FE 59C4E9BB F742 04 0000000>test dword ptr ds:[edx+4], 2000000 59C4E9C2 90 nop 59C4E9C3 90 nop 59C4E9C4 C746 18 AC05655>mov dword ptr ds:[esi+18], 5E6505AC 59C4E9CB EB 31 jmp short 59C4E9FE ; igdumdim.59C4E9FE 59C4E9CD 8B42 04 mov eax, dword ptr ds:[edx+4] 59C4E9D0 A9 00004000 test eax, 400000 59C4E9D5 74 09 je short 59C4E9E0 ; igdumdim.59C4E9E0 OK, the most important part comes, translate the RVA into file address, and modify it. Sounds really hard isn't it? Good news is there is a more easy way, and this is the signature about this fix: 83 F8 13 75 43 F7 42 04 00 00 00 02 Search this hex string in the file, modify the following two bytes into "90 90" 00291280h: 74 09 C7 46 18 5C 35 C6 14 EB 73 F7 C1 00 00 00 ; t.荈.\5?雜髁... 00291290h: 20 74 09 C7 46 18 94 35 C6 14 EB 62 85 C9 79 09 ; t.荈.??隻吷y. 002912a0h: C7 46 18 CC 35 C6 14 EB 55 8B 45 DC 83 F8 15 74 ; 荈.??險婨軆?t 002912b0h: 1C 83 F8 16 74 17 83 F8 13 75 43 F7 42 04 00 00 ; .凐.t.凐.uC鰾... 002912c0h: 00 02 90 90 C7 46 18 AC 36 C6 14 EB 31 8B 42 04 ; ..悙荈.???婤. 002912d0h: A9 00 00 40 00 74 09 C7 46 18 3C 36 C6 14 EB 1E ; ?.@.t.荈.<6?? 002912e0h: A9 00 00 80 00 74 09 C7 46 18 04 36 C6 14 EB 0E ; ?.€.t.荈..6?? We need the do same thing for file igdumdim64.dll, but because this is 64bit dll, so the signature is different: 01 76 17 83 F9 13 75 44 F7 42 04 00 00 00 02 The modify should like this 002d56f0h: 73 09 48 8D 05 1F AD A7 04 EB 6D 0F BA E1 1D 73 ; s.H?..雖.横.s 002d5700h: 09 48 8D 05 48 AD A7 04 EB 5E 85 C9 79 09 48 8D ; .H?H.隵吷y.H? 002d5710h: 05 73 AD A7 04 EB 51 8B 4C 24 20 8D 41 EB 83 F8 ; .s.隥婰$ 岮雰? 002d5720h: 01 76 17 83 F9 13 75 44 F7 42 04 00 00 00 02 90 ; .v.凒.uD鰾.....? 002d5730h: 90 48 8D 05 30 AE A7 04 EB 2E 8B 42 04 0F BA E0 ; 怘?0.?婤..亨 002d5740h: 16 73 09 48 8D 05 AE AD A7 04 EB 1C 0F BA E0 17 ; .s.H???.亨. 002d5750h: 73 09 48 8D 05 67 AD A7 04 EB 0D 0F BA E0 18 73 ; s.H?g.?.亨.s OK after modify the two file, replace it into the windows directory, if your windows is 64 bit, put igdumdim64.dll into windows\system32, and igdumdim32.dll into windows\sysWow64. This must be done under the safe mode, restart windows and press F8 before windows startup, goes into safe mode to replace it. After reboot, you will get all things work. PS: In my system the nvidia's video card cause some problem, it will let system hang sometime, I highly recommand to reinstall the nvidia's drivers after install the Intel's drivers. and choose a lower version, but not the newest version. I have UHD 620 and MX 150 in my system, and after I reinstall the 397.64 nvidia drivers the problem gone away and the laptop works like a charm.
  3. 1 point
    Because people are still looking for it. Just like you and me. =) And also new generations are soldered. If such laptop is broken (dead CPU) - it's garbage and too expensive to replace CPU. 3rd and 4th gens are still have nice socket. i7-4910MQ and i7-4900MQ are rare. I saw few at lockal platforms similar to eBay. I checked again and there a lot of diffirent models... 4910, 4900, 4810, 4800, 4710, 4700. Even XM models. \Expensive\ i7-4800MQ have got 6 Mb cache. P.S. Another option is find laptop with such CPU. Buy it, swap CPU and sell again.
  4. 1 point
    Thanks for the response! I did a little more digging, and it looks like OLED screens don't really exist in anything close to monitor sizes. However, it looks like there are potentially some options to get an FHD screen with touch capability. I have no idea whether that is truly possible though, both because of the 30 pin connector in the M14x, and the ~3mm gap between its actual screen and the 'screen protector'. According to some other posts on this site upgrading the cooling system is possible, but finding a new fan that I can actually confirm will be an upgrade before purchase is a bit of an issue, as no seller I've found actually lists the performance specs.
  5. 1 point
    Dell recently posted a new BIOS for the M11x R3 on their support site - A05. Grab it here: M11x R3 - BIOS A05 Release notes: Since that's only half the fun I also unlocked the hidden menus, see attachment. As always with modified BIOS - use at your own risk, don't change anything you aren't familiar with. _ M11x-R3_A05_[unlocked].zip
  6. 1 point
    was able to download the file a few days ago. seems that it takes a while for the system to be refreshed.
  7. 1 point
    Hi FlyingWaffle: Well, it seems I'm late to read your contribution. Yesterday I bought a 1600x900 LCD since the FHD screen caused me doubts regarding connectivity and, as a result, correct operation. My knowledge and especially my time are limited, so I have decided to take the easiest and safest way (or so I think). I have played a bit, but I based my choice on the comparison of the original panel that has my Alienware and another that I searched on the Panelook.com page that you can see here: http://www.panelook.com/modelcompare.php?ids=20462,20460 My original LCD is the model LP140WH2-TPT1 and I will replace it with this other LP140WD2-TPB1 purchased at Ebay.es: https://www.ebay.es/itm/LG-Philips-lp140wd2-tpb1-14-HD-PANTALLA-DE-PORT%C3%81TIL-30-PINES-1600-x-900/401550169137?ssPageName=STRK% 3 AMEBIDX% 3AIT &_trksid = p2057872.m2749.l2649 My idea was an LCD FHD, but I do not have time to risk since I need it to work and 1600x900 already improves what I had and it serves me equally, since they are only 14 inches. The next work to do will be to replace the CPU with an i7 4930MX. I know that it´s possible, because I saw on this link: http://forum.notebookreview.com/threads/alienware-14-haswell-2013-mode-cpu-upgrade-options.747101/ I suppose that this will force me to modify the cooling system ... but this will be in another post. Thanks for your contribution.
  8. 1 point
    I think they want you to make usefull posts?
  9. 1 point
    Hey Xbayo, your post made me consider upgrading my own m14x's screen. While I was looking around for possibilities I found this on Amazon. According to the people who left reviews, it works great with the m14x. If you've managed to find a cheaper alternative (or an OLED panel that would work) please let me know!
  10. 1 point

    Version 1.0.0



  11. 1 point

    Version 2.0



  12. 1 point
    Hi, i did it. https://drive.google.com/file/d/1L_8xXeFaXBlDI5XfqiM1YgRl8-JWh7ni/view?usp=sharing
  13. 1 point
    Hi! You can read : User Account Promotion Rules - READ BEFORE POSTING! As part of the move to our new platform, we did away with the 5 post moderation queue (where new members posts were put in an approval queue) and now all new member posts are not prescreened and immediately visible when posted. However, to maintain a steady stream of quality content on these forums, we have added user account promotion requirements which work a little differently than before. Upon registering for this website, your account is categorized as "Pre-Promotion" and you can see that status below your avatars. Once you have participated in the community sufficiently over the course of a week , your account will become flagged for review and at that time the T|I moderation team will review your post history over the course of a week and promote you accordingly--as long as you didn't break any forum rules or make spam posts, you are 99.9% certain to get promoted. At that point, as a Promoted User, your account will have full privileges to download anything you like and have enhanced account features enabled such as increased PM quota, increased per post upload quota etc. If you cannot wait for this promotion period, then we encourage you to subscribe for T|I Elite Membership as it will provide you with an immediate account promotion and you can then download what you wish. Attempting to circumvent these rules set forth are grounds for infraction and/or termination of your account privileges as it is a violation of our terms of service that you agreed to when joining Tech|Inferno forums. In summary: New user account promotion system that views your level of quality activity on these forums over a span of 1 week with a minimum of 5 QUALITY posts. Once you have sufficient activity over this week, your account is flagged for moderator review. At that time you will get promoted as long as you had quality posts and didn't violate forum rules (e.g. spam posts, one liners, file begging, complaining etc.). Apart from a few odd members that break the aforementioned rules, almost everyone is guaranteed a promotion. If you do not wish to wait for this promotion queue, you can simply opt for T|I Elite Membership to skip ahead and get your account promoted as long as the membership lasts. Attempting to circumvent the aforementioned rules may result in an infraction and/or ban. Please review our terms of service. We feel this is the best compromise we could come up with to maintain our standards of quality for this website and to ensure our limited resources are used optimally. Thanks, T|I Team
  14. 1 point
    Sorry, the modified files are too big, the igdumdim32.dll and igumdim64.dll totaly around 180MB so I couldn't upload them here. And if you choose different version of drivers, you need modify it again, they are not universal to use. This is why I didn't publish a complete drivers here. But I think follow my quick step you can easliy got it to work. If you want driver's working on win 8.1 or other windows version, you just need add the device description line into the other section of system, for example, win8.1 you need add this line %iKBLULTGT2% = iSKLD_w81, PCI\VEN_8086&DEV_5917 into the section [IntelGfx.NTamd64.6.3]
  15. 1 point
    CH341A programmer: https://www.ebay.com/itm/USB-Programmer-CH341A-Series-Burner-Chip-24-EEPROM-BIOS-Writer-25-SPI-Flash-AU/153117073868?epid=577511738&hash=item23a67d21cc:g:XKEAAOSw5UdbW-iL https://www.amazon.com/Parts-tower-CH341A-Programmer-Software/dp/B01FVVHCVC/ref=sr_1_4?ie=UTF8&qid=1522179315&sr=8-4&keywords=ch341a&dpID=51BO7eGgO5L&preST=_SY300_QL70_&dpSrc=srch SOIC8/SOP8 test clip: https://www.ebay.com/itm/Soic8-Sop8-Flash-Chip-Ic-Test-Clips-Socket-Adpter-Bios-24-25-93-Programmer/201414947737?hash=item2ee5443399:g:up8AAOSw1Fda8qkt https://www.amazon.ca/MAUSAN-Socket-Adapter-150MIL-205MIL/dp/B06ZYSNJF3/ref=pd_sbs_21_3?_encoding=UTF8&psc=1&refRID=XM79QJWGED6B4K2VEZDJ How to use it: Also, you can search on YouTube a lot of guide for CH341a.
  16. 1 point
    Hi! I registered for the specific topic. So, the big question for which I found no answer in internet. Windows 7 on Intel Core 8th generation. Officially, Intel supports windows 7 up to 6th generation. Unofficially, with an easy trick up to 7th generation. The question is, how can we make it work on 8th generation? I installed windows 7 Ultimate 64bit on my new DELL Inspiron 5770 high end non-gaming 17 inch laptop, without any issue apart from the integrated GPU (Intel UHD Graphics 620). This also blocks the functionality of the AMD Graphics card too. So, since for many reasons I want to have windows 7 instead of windows 10 or Linux, I did my best but I got stuck. I created a hybrid driver from 2 different versions of official Intel drivers, the latest, which supports this iGPU, but only on Windows 10 and the last windows 7 compatible, which does not include support for the specific 8th gen processor/graphics card, since it is newer. I mixed some files and also edited the inf file from the old driver. I will share with you what I did, so that someone who has knowledge might get 100% functionality. I get only partial. So, here is my guide. 1. Download the last Win7 compatible driver from Intel for HD Graphics. It is the version win64_15.45.19.4678 2. Download a newer version which is win10 only but contains the driver for your processor. In my case, Intel Core i7 8550U with DEV_5917. I downloaded the latest driver. 3. Make copies/backup of both folders and save elsewhere before starting editing. 4. Unzip both. From the unzipped ones, go to the new driver folder, then Graphics, then copy all components and paste in the Graphics folder of the old ( version. Note; So far in my case I didn't play a role if I replaced the same names of the old files with the new ones or skipped them to keep the old ones. Exception; do NOT replace the igdlh64.inf file and the igdumdim32.dll 5. Find the DEV number of the processor. Device Manager (from Control panel or search), right click on generic VGA Adapter, properties, details, ID. 6. Open the igdlh64 file (with a notepad) from the new version (Graphics folder) find the DEV number under windows 10 and copy the whole line. 7. Paste it under the Windows 7 section in the igdlh64 file of the old driver and correct the ikbl win10 with iskl win7 (known trick for 7th gen). 8. Copy all lines that include the 4-digit number from the igdlh64 file from the new driver and paste in the respective sections of the igdlh64 of old driver. In the end of the text, also add the name of the driver as a label, eg Intel UHD Graphics 620. 9. Install the modified old driver (win64_15.45.19.4678) and reboot. 10. After reboot. Copy the igdumdim32.dll file from the Graphics folder of the new version and paste it to the C:\Windows\SysWOW64 replace the existing files This way, I get all resolutions, full brightness, colour, contrast etc control of the display, intel graphics control panel, full windows 7 effects (aero glass etc), but I dont actually get video support (apart from 3rd party software, like VLC/GOM player which even play 4K video smoothly), 3d applications are not functional, I dont get hardware acceleration etc. I concluded that the solution is to edit the igdumdim32.dll file, so that I copy elements from the new version to the old one. This way, theoretically, it should work. Anyone who has experience with driver and dll modification???
  17. 1 point
    Likewise! Still, go for Windows 7 instead of Windows 10.
  18. 1 point
    Here you go! It's the same BIOS for both. I don't support any VBIOS related stuff at the moment so I don't know if there will be any incompabiities or not because I haven't worked with VBIOS for a couple of years. I have never had any incompability problems myself between the ZM and DM with Nvidia cards, only AMD. But if you chose to try it do so at your own risk. I can make a sript that prevents flashing the wrong BIOS but I don't feel like it's really necessary at the moment
  19. 1 point
    T|I and the author are no longer associated. For support kindly contact the author directly Prema Mod™ vBIOS for Asus GPUs!
  20. 1 point
    That's fine - back to my powershell script fallback that I run using scheduled tasks. Runs on startup and resume from standby: stop-service -name "XTU3SERVICE" start-service -name "XTU3SERVICE" start-sleep -s 10 start-process "C:\Program Files (x86)\Intel\Intel(R) Extreme Tuning Utility\Client\XtuCLI.exe" -ArgumentList '-t -id 79 -v -70' -Wait Does the trick but not ideal... it sets a -70mv undervolt.
  21. 1 point

    Version 1.0.0


    Alienware M17x R3 A12 unlocked BIOS with tweaks on SATA settings Files contained in this archive: AtpTimerInfo.dll Ding.wav FWUpdLcl.exe InsydeFlashx64.exe iscflashx64.dll iscflashx64.sys PAR00MEC.fd platform.ini READ ME.txt xerces-c_2_7.dll To learn more about how to use the files in this archive, please visit the thread below: Donation link In case you want to buy me a beer Thanks and cheers!


  22. 1 point

    Version 1.0.0


    This file is an unlocked version of A05 BIOS from Dell for the Alienware M11x R3 Files contained in this archive: READ ME.txt M11x R3 - A05 [unlocked].exe To learn more about how to use the files in this archive, please visit the thread below: Donation link In case you want to buy me a beer Thanks and cheers!


  23. 1 point

    Version 1.0.0


    Files contained in this archive: ms_gx740.zip MSI 16F1 Unlocked.zip MSI 1762 Unlocked.zip MSI GT60 Unlocked.zip MSI GT70 Unlocked.zip MSI GT683 Unlocked.zip MSI GT783 Unlocked.zip MSI MS-16F2 Unlocked.zip MSI MS-1761 Unlocked.zip SecondGenAMDAPU.zip Should I Flash These BIOS? See thread link below to learn which notebooks these bios files should be used with. Who this does NOT apply to: - If you are afraid to brick your notebook, this is NOT for you. There is always a possibility for errors and accidents to occur. - If you do not understand what any or most of these acronyms mean, this is NOT for you. You will probably find little use for the unlocked features and the potential for risk is much greater than the reward. Who this applies to: - If you have an understanding of most of this thread and are willing to learn, continue reading. - If you are an enthusiast who loves modding and overclocking and have experience with this field, continue reading. Features: So what are these features that MSI had locked out? A short list would include:* - XMP RAM support (Up to 2133Mhz) [Warning: 4 DIMMs at 1866Mhz(+) may not be stable, 2 DIMMs are stable at 2133Mhz]. - BCLK Overclocking (Up to 5%, your mileage may vary, no guarantees). - TPL limits unlocked (With the combination of ThrottleStop, CPU throttling can be overcome). To learn more about how to use the files in this archive, please visit the thread below:


  24. 1 point

    Version 1.0.0


    Files contained in this archive: 'Error 104' Fix - v01.zip Lenovo Y500 - Y400 - BIOS [v2.02] - stock .zip Lenovo_Y500-Y400_-_Mod_[v2.04] (including update for 2.02 & 2.03 users).zip Lenovo-y500-y400-bios-[v2.02]-stock-.zip Y500 -Y400 - SLI 650m - - OC.rom.zip Y500 - Y400 - SLI 750m - 80.07.9D.00.11 - OC.zip For instructions on how to use these files, see this thread: Donation Link: Here's the 'buy me a beer' link in case you like this <<


  25. 1 point
    HP Elitebook 6930P - P8600@3.33Ghz + GTX770/R9-280X at x1/x1.Opt/x1E/x2 14" Elitebook 6930P circa 2008 Intel Core2Duo P8600-2.4@3.33Ghz, AMD eGPU with 29% PCIe overclock, NVidia eGPU with 20% PCIe overclock 4GB RAM Software: Win7-64bit + Setup 1.30 for all AMD or NVidia-x2 implementations. NVidia 306.97 + modded INF to add GTX770 x1.Opt support. port layout as shown: wifi=port2, expresscard=port3, WWAN/PCIe=port4 (disabled by default by bios) iGPU: 4500MHD eGPU: GTX770 and R9 280X adapter: PE4H 2.4a + EC2C. x2 mode requires an additional PM3N. PSU: ATX Installation x1 NVidia: is plug and play. No Setup 1.x required, though can use it as shown. This is the simplest and least expensive way to go. x2 NVidia: requires Setup 1.x to switch port to x2, configuration as shown x1/x1E/x2 AMD: requires Setup 1.x to perform PCI compaction and switch port to x2, configuration as shown-x1 and shown-x2. Easiest way of getting x2 going is to wire up the mPCIe port, use Setup 1.30 to switch to x2 mode, then hotplug the powered eGPU into the expresscard slot. Hit F5 to detect it in x2 link mode. Note: Any x1E/x2 configuration sets port1=x2 and port3=x2. That means onboard wifi as part of port2 gets closed off. If wanting concurrent wifi with x2/x1E then need additional USB wifi. Performance Below we evaluate x2 1.0 versus x1 1.0. In addition, AMD offers a x1E mode (port is x2, but only using one lane). For more comparative performance see the x1 2.0, x1.1Opt and x1 1.0 results at http://forum.techinferno.com/diy-e-gpu-projects/2747-%5Bguide%5D-12-dell-e6230-gtx660%40x1-2opt-hd7870%40x1-2-pe4l-ec060a-2-1b.html#post37197 R9 280X x2 1.0 : 3dmark06=16001, 3dmark11=9786, RE5=101.1 x1E : 3dmark06=15851, 3dmark11=9230, RE5=99.4 x1 1.0 : 3dmark06=15436, 3dmark11=8662, RE5=92.3 GTX770 results x1E and x1 gives the same result meaning there is no x1E mode for newer NVidia series. x1.Opt with a 4500MHD iGPU requires downgrading to 306.97 driver as discussed at http://forum.techinferno.com/diy-e-gpu-projects/6253-t500-compat-q-4500mhd-optimus-ends-306-97whql.html#post85924 since newer drivers no longer engage the x1 pci-e compression. Notice the loss of 3dmark11 performance with the 340.43->306.97 downgrade. x2 1.0 : 3dmark06=10984, 3dmark11=9845, RE5=89.2 x1.Opt : 3dmark06=15600, 3dmark11=8558, RE5=88.5 x1 1.0 : 3dmark06=6706, 3dmark11=9100, RE5= 81.6 Conclusion The 6930P is an older platform that does suprisingly well with an eGPU attached. The best value solution being any x1-capable eGPU adapter (PE4L 1.5/2.1, EXP GDC), a NVidia Fermi/Keplar and the 306.97 driver. Acquiring a more pricey x2 capable eGPU adapter (PE4H 2.4, PE4C 2.x) providing immediate x1 performance plus upgradability to x2 if wanting more.
  • Newsletter

    Want to keep up to date with all our latest news and information?

    Sign Up

Important Information

By using this site, you agree to our Terms of Use. We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.