Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 11/19/18 in all areas

  1. 3 points

    Version 1.0.0

    1403 downloads

    Files contained in this download: Asus 770m (G750JX) - 80.06.54.00.13 'OC edition' rev02.zip Clevo 670mx - 3GB - 80.04.58.00.03 - 'OC edition'_rev02.zip Clevo 675mx (4GB) - 80.04.58.00.05_'OCedition'_rev00.zip Clevo 680m - 80.04.29.00.01 'OCedition' revised_01.zip Clevo 680m - 80.04.33.00.10 'OCedition' revised_01.zip Clevo 680m - 80.04.33.00.10_'OCedition'_revised_01 - OV 1000v.zip Clevo 680m - 80.04.33.00.10_'OCedition'_revised_01 - OV 1025v.zip Clevo 680m - 80.04.33.00.10_'OCedition'_revised_01 - OV 1050v.zip Clevo 680m - 80.04.67.00.01 'OCedition' revised_01.zip Dell 680m - 80.04.5B.00.02_'OCedition'_revised_00.zip Dell 680m - 80.04.33.00.32__'OCedition'_revised_00 - OV 1000v.zip Dell 680m - 80.04.33.00.32__'OCedition'_revised_00 - OV 1025v.zip Dell 680m - 80.04.33.00.32__'OCedition'_revised_00 - OV 1050v.zip Dell 680m - 80.04.33.00.32__'OCedition'_revised_00.zip Dell 765m - 80.06.61.00.01 - 'OC edition' (AW 17) - v00.zip Dell 765m - 80.06.64.00.01 'OC edition' (AW 14).zip Dell K4000m - 80.04.33.00.34_'OC edition'.zip Dell K5000m - 80.04.33.00.05 'OCedition' rev00.zip HP K3000m - 80.04.33.00.2E - 'OC edition'.zip MSI 670mx (1.5GB) - 80.04.5B.00.A5 'OCedition' rev00.zip MSI 675mx (2GB) - 80.04.58.00.14_'OCedition'_rev00.zip MSI 675mx (4GB) - 80.04.58.00.0E_'OCedition'_rev00.zip MSI 680m - 80.04.33.00.24_'OCedition'_revised_02 - OV 1000v.zip MSI 680m - 80.04.33.00.24_'OCedition'_revised_02 - OV 1025v.zip MSI 680m - 80.04.33.00.24_'OCedition'_revised_02 - OV 1050v.zip MSI 680m - 80.04.33.00.24_'OCedition'_revised_02.zip MSI 770m - 80.06.54.00.11 'OC edition' - rev02.zip Nvidia 770m - 80.06.51.00.0F 'OC edition' - rev02.zip Nvidia GTX 780m - 'OC edition' - rev02.zip Nvidia GTX 860m (Kepler) - 'OC edition' - rev00.zip Nvidia GTX 870m - 'OC edition' - rev00.zip Nvidia GTX 880m - 'OC edition' - rev00.zip Nvidia K3000m - 80.04.3A.00.07_'OCedition'_rev00.zip Instructions on how to use these files:

    Free

  2. 2 points
    T|I and the author are no longer associated. For support kindly contact the author directly
  3. 1 point
    In case you own a Lenovo Y410p or Y510p laptop, you might be interested in upgrading its performance by installing an external graphics card. Ultrabay eGPU adapter designed by @gerald was proven to be a convenient plug-and-play option to do exactly that. However, for a long time only an AMD-branded GPUs could be used due to limitations in the Lenovo's stock BIOS. The purpose of the modified firmware presented here is to expand the range of available GPUs by enabling Nvidia support on Gerald's Ultrabay eGPU adapter. Huge thanks to: @MWichni - For efficiently assisting me during the development of this mod. By flashing dozens of BIOS builds over the course of several weeks and thoroughly describing the effects observed (or the lack thereof), he enabled me to fully understand necessary parts in BIOS structure and come up with a final solution. @svl7 - Whose unlocked BIOS / Whitelist mod has served as a basis for this modification. His discovery of a security hole in V2.07 BIOS has provided us with a convenient BIOS flashing method that does not require a physical programmer. The Unlocked BIOS and WLAN whitelist mods originally designed by him are also implemented in this BIOS mod. @gerald - For designing the aforementioned adapter. Without it, all this work would make very little sense. Key features: Resolves the "40-second reboot" issue normally encountered while using Nvidia graphics cards with Ultrabay eGPU adapter, thus allowing all Nvidia cards to be used. Based on the latest V3.08 BIOS. Includes Svl7's WLAN whitelist removal mod - for the convenience of aftermarket WLAN card users. Includes Svl7's BIOS debug menu mod - for the ease of experimentation with newly available features, e.g. attempting to use Nvidia Optimus to pass eGPU video back to laptop's display. NB! Svl7's Debug Menu is not a toy! It contains a lot of options that are either not supported or partially supported by the hardware platform and/or can disturb its normal operation or prevent the PC from booting up at all. Any of the entries not originally present in the stock BIOS should be modified at your own risk! DISCLAIMER: ANY MODIFICATIONS YOU ARE APPLYING TO YOUR HARDWARE ARE PERFORMED AT YOUR OWN RISK! AUTHOR OF THIS MOD DOES NOT HOLD ANY LIABILITY FOR LOSS OR DAMAGE RELATED TO USING THIS SOFTWARE. Screenshots: Installation instructions: If things don't go right: Error 43: If you intend using the GTX10XX-series Nvidia card as the eGPU (which you probably do), you are very likely to encounter the infamous Error 43 in Windows Device Manager. This is a widely known issue in the eGPU community and is not related to this particular mod in any way. Following this guide thoroughly will in most cases resolve the Error 43 issue. Download: Get your copy here! P.S.: Version of this mod for Lenovo Y400/Y500 models is coming soon!
  4. 1 point
    For those who don't like the restrictions Lenovo put on their system, here's a BIOS mod that will get you back at least some of the freedom you should have over your own hardware. Features: WLAN card whitelist removed, any (hardware-wise compatible) card should now work hidden BIOS menus unlocked VBIOS tweaked for more performance and better tuning possibilities Keep in mind that not necessarily all of the BIOS options available with this mod will be fully functional, so use the new available settings with care. If you're unsure about something don't change it and ask here, someone might be able to help. Available for v1.07 / v1.09 / v1.10 and v3.05. v2.04 and v2.07 added (only whitelist removal as for now) If you have a different BIOS (or more specific, a BIOS newer than 3.05) I will need a copy of it in order to make it work for your system. Instructions for flashing the modified BIOS v3.05: You need a USB stick prepared to run DOS, here is a guide you can follow in case you don't know how to do this: Guide by @StamatisX - thanks! >>> Before continuing make sure the AC adapter is connected to your laptop and your battery has at least 20% charge remaining. <<< (0) - NOTE: This step is Only necessary if your system isn't already using BIOS v3.05 Update to the official v3.05 BIOS provided by Lenovo . (1) - Create a backup of your own BIOS (now v3.05) by using Fptw64 tool. Extract the files and run the included .bat file from an admin command prompt. . (2) - Download Lenovo_Y510p-Y410p_[v3.05]_modified.zip and put the files of folder [1] to the root of your prepared USB DOS stick. Let the BiosFixer prepare your BIOS for flashing by drag and dropping your backup file on it. Put the created "v305mod.bin" file to the root of your USB DOS drive as well. . (3) - Now you need to downgrade the firmware back to v2.07 (Y510p-Y410p_v207_[stock].zip) in order to flash the mod. . (4) - Boot from your USB DOS drive, when you see the command prompt type BIOS and hit enter. Wait until the BIOS is flashed (you can safely ignore warnings about non-existing regions). . (5) - Once the BIOS flash completed with no errors, type EC and hit enter. Wait until the EC is flashed. Then reboot. . (6) - Go to the BIOS setup menu, load the default settings, apply and reboot. Done. In case you're using an ultra bay GPU follow the instructions in post #2 and flash the vbios.. NOTE: It's crucial that you flash both, BIOS and EC. Having different EC and BIOS versions can in certain situations lead to issues. IMPORTANT: If you want to go back to stock v3.05 you can do that easily by simply using the official update from Lenovo. That's it, nothing additional required in this case. Old instructions for users with v1.07 / v1.09 / v1.10 or v2.04 / v2.07 who for some reasons don't want to update to v3.05: Video walk-through of bios settings (thanks @allstone): My donation link in case you want to buy me a beer Download link for files referenced in this post:
  5. 1 point
    The Asus N55SF comes with a Nvidia GT 555m, which has already been proven to be highly overclockable by Alienware M14x users. M14x owners have already the possibility to slightly increase the voltage of their GPU by using a slightly -voltage-increase-nvidia-gt-555m-7.html#post12003"]modified VBIOS. Here's a similar mod for N55SF users. The modified VBIOS will increase the voltage of the GPU by about 0.1V which will allow you further overclock your GPU core. (Note: The graphics memory isn't affected by this mod, you won't be able to clock it higher than before) Instructions: Since the VBIOS is part of the system BIOS you need to flash the whole BIOS in order to make use of the mod. Flash the file with your preferred BIOS flashing utility, e.g. with the one provided by Asus (click here). - Only flash with the battery and AC adapter plugged in to your system After flashing I highly recommend to go to the BIOS menu and load the default settings. Then reboot and if you want reset your custom settings. Verify the increased GPU voltage by using GPU-Z or a similar GPU monitoring tool. Note: Only the voltage of the 3d performance profile gets increased, in order to see it your GPU needs to clock up to 3d clocks. Also make sure your system is free of dust and check your temps when you first use this BIOS, the voltage increase will also slightly increase the GPU load temps, but it should be well in the thermal envelope of the system. Credits: Thank goes to the following people: @Saltius for modding the VBIOS @Angelsky for testing the modded BIOS and providing pics @svl7 for locating the VBIOS file and extracting & repacking the BIOS Let me know if you have any questions or encounter some issues. Have fun overclocking your system! If you have questions, let me know! Also if you encounter any issues, please report back. As always with such mods, you are responsible for your system and changes you make. Asus N55SF BIOS [555m volt mod].zip
  6. 1 point
    Hi there, This is the quick step, if you don't want read more: 1. download intel graphics driver 21.20.16.4839 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 15.45.23.4860 (21.20.16.4860): 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=21.20.16.4839 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.
  7. 1 point
    This is continuation of this thread (http://forum.techinferno.com/lenovo-ibm/2690-lenovo-y500-unlocked-bios.html) with all the necessary information in the first post in order to make it easier to find all the stuff. Lenovo Y400 / Y500 - 'unlocked' BIOS / wwan-wlan whitelist removal + modified VBIOS for higher overclocking The Lenovo Y500 comes with a pretty locked down BIOS, and in addition to this with a whitelist which prevents the user from getting 3rd-party wwan/wlan cards to work properly. The modified BIOS versions here will take care of this. Keep in mind that not necessarily all options available in the modified bios will work. Some might not do anything at all, others could possibly leave your system in a state which will prevent it from booting. Use care when changing stuff in the modified bios, don't touch things you're not familiar with. Use all the mods and software posted here on your own risk. Read the instructions carefully. NOTE: This will only flash the bios region. It won't reset the nvars set in the bios. *************** ONLY FLASH A MOD OF THE SAME VERSION AS YOUR CURRENT BIOS VERSION!!! If you're on 2.02 or 2.03 you can safely use the 2.04 update, *************** Attached you'll find modified versions of the Y400 / Y500 BIOS v1.03 and v1.05. Removed as they're outdated. Better updated to v2.02. The bios contains your Windows 8 license, therefore you can't just flash any file, else you'll have issue with your Windows activation. Furthermore the serial numbers, service tags etc. are stored there as well. You don't want to loose them. I wrote a little program that will take care of this issue and personalize the modified bios for you, so that you won't end up with an invalid Windows or no service tags. *************** Preparation to get to BIOS v2.02 (coming from any earlier version): Generally it's a good idea to keep the BIOS up to date. We're luck to have an official BIOS update to v2.02 apparently thanks to a leak on the net. (Lenovo is really bad when it comes to providing firmware updates and fixing issues). The leaked version must be genuine, else it wouldn't flash by using the regular method. If you want to update your system to v2.02 then grab the update here, extract it and flash the bios by executing the included InsydeFlash utility. Once the update is completed you can continue with the instructions below to get a modified version on your system. *************** Instructions for flashing a modified version: As a reminder - the modified BIOS needs to be the same version as you have on your system (2.02 to 2.04 is ok). Prepare an USB stick which can boot DOS. If you don't know how to do this, follow this short guide: Download the flash tool, for flashing you'll need the DOS version, but for creating the backup of your current BIOS the Win64 version will do as well, and it is faster. Get the prr tool as well. Grab the modified BIOS you want to flash, it comes as a tool which will patch the bios for you. Make sure you grab the version that corresponds with your BIOS version. Create a backup of your current BIOS using the flash tool you downloaded (first step) by runing the included backup.bat, or by using the Win or Dos version flash tool with this command: If the .bat doesn't work then open an administrator command prompt in your working directory and run the .bat per command line or type the command written above. In case you get an 'error 104' replace the parts file with the one that can be found in the 'error 104 fix' attachment at the end of the post. And if you still have issues after doing all of the steps above then please leave a reply in the thread and describe your problem. Open the downloaded tool and execute it. Drag and drop your BIOS backup file on it, it will create the mod for you. It will look like this: Put the modified BIOS, the prr.exe tool and the fpt.exe (along with the fparts.txt file) on the root of your prepared DOS bootable USB drive, restart your system and boot from that drive. Execute the prr.exe, if you don't get an error message continue by pressing enter. Then flash the bios by using this command (filename.bin obviously needs to be replaced with the name of the file you want to flash). If you can't remember the name of your file, use the command dir to display all the files on your drive. Flash with this: fpt.exe -f filename.bin -bios NOTE: The name of the BIOS file mustn't exceed eight characters (not counting the extension)! That's a DOS limit, so make sure the name of your file isn't too long. Wait until the process is done. After flashing it will verify the data, in case there's something wrong with the flashed data it will tell you. In that case don't reboot, just flash again. *************** Flashing the ultra bay 650m - only for SLI users with BIOS v2.02: The modified BIOS v2.02 also contains a vbios which will allow you to overclock your 650m past the 135MHz limit. As the ultra bay GPU has it's own vbios module you need to flash it separately. You'll need an USB drive which can boot DOS (just as the one you used for flashing the BIOS). *************** It might look a bit complicated at first, but that's the easiest way I could think of. Let me know if anything is unclear. >> Here's the 'buy me a beer' link in case you like this << Use at your own risk, you are responsible for your system and the changes you make on it. My programs come with absolutely no warranty to the extent permitted by applicable law. Grab file archive here:
  8. 1 point
    I recently got a 2010 27" iMac for free! Some further research concluded that the MXM slot in the iMac has been proven to work with a GTX 880m, including Mac OS! I used to play with a 7970 ghz edition, but ended up selling it for some more projects. I've been lagging along on a 5870 2gb and thought that with my switch to the free iMac, I might as well update my gpu. Heres the problem I was faced with: the 880m is a little underpowered on stock clocks. So, after even more research I discovered that the 980m was around the same as a 7970 performance wise. I ended up grabbing a deal on an 880m for only 160$, but I did want to share my findings with you guys. *WARNING* ONLY 2009, 2010, AND 2011 IMACS HAVE THE MXM SLOT!!!! IF YOU ARE USING A 2012+ YOU CANNOT UPGRADE YOUR GPU So the 980m used to work all the way up to mac os sierra. It's now high sierra, but the fix is still pretty simple. What you will need: -thermal pads -copper ram heatsinks/ one of the specialized backplates that cools MXM memory modules. -Your graphics card -YOU NEED an imac 2011 gpu heatsink -GOOD thermal paste (Preferably liquid metal if youre comfortable with that) -IMAC 2010 power supply *As far as i know the power supply's between these 3 imac's are interchangeable, but the largest one is the 2010 variant, at the 310 watts, and the others are much lower. *Just from tdp we know that the 980m is 115w and the cpu's on these guys are most commonly 95w, thats allready 200 with out hdd, all the other components etc. -nvidia web drivers READ THE FOLLOWING DIRECTIONS CAREFULLY Step 1: You must have all your mac os/ windows partitions set up with bootcamp, and MAKE SURE it boots into Mac OS and wont boot into anything else when you start it up AFTER the upgrade. *Remember nvidia web drivers must be installed before you upgrae Step 2: dremel/ cnc/ remove a couple parts of the VRM section of the imac 2011 heatsink, (You want your card IN HAND so you are able to make sure it fits correctly. step 3: Assemble the gpu assembly step 4: Re assemble the imac, with the new gpu. *This is where is gets slightly harder* step 5: You want to reset your iMac's System Management Controller, otherwise known as SMC. *DO NOT FLASH NVRAM OR PRAM, or you will have to redo the whole process, after you put your old gpu in to fix all the bootcamp problems and such *You can do this by plugging the power cord into your imac, waiting 30 seconds and NOT turning it on, unplug your power cord, wait 30 seconds, then plug it back in. Wait another 30 seconds, then turn it on. (But not before reading the following to be prepared:) step 6: You need to force Mac OS to work with an unsupported card. this is a pretty simple process if you are comfortable with terminal. * I couldn't have found this without this page: https://www.ifixit.com/Story/18646/Successful_iMac_Upgrade_to_GTX_880M " To make a non-apple provided Nvidia graphics card work in macOS Sierra you need to do the following… Start the computer in safe mode by holding shift. Get your BoardID by running this command in terminal echo "<result>$(ioreg -rd1 -c IOPlatformExpertDevice | awk -F'["|"]' '/board-id/{print $4}')</result>" Open the AppleGraphicsControl Kext using this command sudo nano /System/Library/Extensions/AppleGraphicsControl.kext/Contents/PlugIns/AppleGraphicsDevicePolicy.kext/Contents/Info.plist Use the arrow keys to go down until you see <key>ConfigMap</key> followed by a bunch of keys and strings. LOOK FOR YOUR BOARD ID… IF IT IS LISTED: Change the string to <string>none</string> IF IT IS NOT LISTED: Add it in the same format as the ones listed. Save the file by pressing Ctrl+O, then enter. Exit by pressing Ctrl+X Rebuild the kernel cache using the following two commands: sudo kextcache -system-prelinked-kernel AND sudo kextcache -system-caches Have Fun! Theoretically this should work, and I would love for somebody to try as I got an 880m instead. Just keep in mind this is all from research and has not been proven to work. Be sure to research this subject before you try it.
  9. 1 point
    Hi! Create your backup of bios (as described at the first page), I'll take a look.
  10. 1 point
  11. 1 point
    No, I had no issues updating to windows v. 1809. Do your drivers still work after the update?
  12. 1 point
    I don't understand. VLC can't play 4k ? and what device ?
  13. 1 point
    I have your answer, see my post here: https://www.techinferno.com/index.php?/forums/topic/12377-way-to-make-intel-uhd-620-graphics-driver-to-works-in-windows-7-no-crash-in-video-play-back-3d-function-normally/
  14. 1 point

    Version 5.513.0

    298 downloads

    Flashing Overview: - Go to the device manager -> 'Display Adapters' -> chooser your GPU, right click on it and choose disable - Flash the VBIOS with mnvflash, a modified version of nvflash (see attachments). Below are detailed instructions for nvflash in case you aren't familiar with it. - After the flashing is done: Enable the GPU once again in the device manager. - Reboot Detailed Instructions: As soon as you see the command line you're ready to go, write dir and hit enter to display all the files on the USB drive. Display all Nvidia adapters in the system: nvflash -a or alternatively the longer version of the command: nvflash --list This command will return you a list with all Nvidia adapters present in your system. Here's an example output of this command run on my M15x with a 680m in it: NVIDIA Firmware Update Utility (Version 5.117) NVIDIA display adapters present in system: <0> N13E-GTX (10DE,11A0,1028,02A2) H:--:NRM B:02,PCI,D:00,F:00 The number in the <> brackets is the index of the corresponding device. SLI users will have more than one entry and flash each card separately. Backup your current VBIOS: Never forget to keep a backup of your original VBIOS before you flash anything non-stock. Use this command to save a copy of the firmware to your USB drive: nvflash -b filename.rom or with nvflash --save filename.rom Flash the VBIOS to your card(s): For a single card it's really straight forward, you don't need to worry about the adapter indices. Just use this command: nvflash -6 vbiosname.rom -6 will allow you to override mismatches of the PCI subsystem ID. In case of a mismatch you'll need to confirm the flash with 'y'. NOTE: Users with a non-US keyboard might need to press 'z' or similar, because the 'y' isn't at the same location for all keyboard layouts. SLI users will need to flash each card separately. The concept stays the same, but you will need to use the corresponding adapter index to flash a card. How to figure out the adapter nr. is described above. Flashing goes like this: nvflash -i[index] -6 vbios.rom [index] represents a number, namely the index you found with the 'nvflash -a' command. So a command example to flash a card which has index 0 is: 'nvflash -i0 -6 vbios.rom' Donation link In case you want to buy me a beer Thanks and cheers!

    Free

  15. 1 point
    PM - it's Private Messages. Just check your Private Messages.
  16. 1 point

    Version 1.0.0

    6 downloads

    BIOS for P65XHP3/HP6G only. If you like my work DONATE

    Free

  17. 1 point
    Brvao, man. This is exactly what I'm looking 4 4 all these years. And it seems like u got stuck on the Nvidia Card won't start up problem. Tesla said that he has asked an experienced bios modder, and I think the modder pointed out that the motherboard soldered hardware Nvidia SLI bridge is one of the points. Have u tried remove all SLI-link on that interface to avoid it try to start SLI??? On the other hand, I do believe there's a whitelist in the BIOS on UltraBay interface part just like Mini PCI-E. Cuz u can't start up with an AMD card when u r using higher version bios, and u just Cannot start with GT755M and GT650M SLI. I asked someone who can contact with an Lenovo Customer Service guy, and he told me that when Bios start up, Bios Do need to read sth like Hardware ID which Write in VBIOS on the 2nd Card to start up. (By the way I remember that back to the time Win8.1 came out with WDDM1.3, SLI Just Failed cuz Nvidia Driver cannot update the 2nd card VBIOS to support WDDM1.3, it sucks.) And I do believe the omnipotent svl7 can remove it just like Mini PCI-E too , but unfortunately it says that he is 'Retired Staff' at this time. Is there anybody who can contact him to have a look into this problem??? I think that masquerading a desktop card such as GTX1080 etc. by modified VBIOS into a GT650M/750M/755M is not the corrcet way to solve this problem. A totally remove of the start up check whitelist and a totally remove of all SLI-link on UltraBay may be the correct way. Any way, just plz don't give up bringing Nvidia Card to this project. F*ck the Lenovo for betraying all the customer who believed in its Ultrabay Module, and thank godness your project came out. And forgive my English 4 any grammatical error or misuse of words, I'm not a native English-speaker.
  18. 1 point
    Project is live!!! https://www.kickstarter.com/projects/290597041/lenovo-y410p-y510p-ultrabay-adapter-for-graphic-ca pls support this project.
  19. 1 point

    Version 1.0.0

    47 downloads

    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!

    Free

  20. 1 point

    Version 1.0.0

    8 downloads

    Files contained in this archive: flash.bat READ ME.txt SVS_13-15_seriesFixer.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!

    Free

  21. 1 point

    Version 1.0.0

    786 downloads

    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 - 80.07.27.00.33 - 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 <<

    Free

  22. 1 point
    Introduction The RAID_0 was very easy to setup thanks to Mr.Fox's "windows installation guide", I've only made these instructions custom for 2570P users. What do I need? · 2 x SSD drives: I used 2 x 256GB Sandisk Ultra Plus · 9.5mm HDD caddy: $11 eBay · A knife · Some sturdy glue, I used LocTite Super Glue. · 4GB+ USB thumbdrive Instruction RAID_0 Setup for Win 7 Make an WIN7 USB installation with Windows USB/DVD download Tool and a Win7 ISO (fully legal) NOTE: If can't find Home edition of your language you can download Pro edition and delete \sources\ei.cfg to be able to choose home edition later on in the installation. In bios: Set ‘Sata Device Mode’ to RAID In bios: Set USB-boot in top of the list of BOOT Devices Boot up Win7 installation from the USB-drive Inside installation make sure to delete all partitions so that you end up with two unallocated disks (disk 0 and disk 1) Install Windows 7 one of the unallocated drives, for me disk 1 worked whilst disk 0 didn't (can’t explain why, but I guess it has to do with the RAID setting from BIOS). Windows should now be installed. Since we only have allocated space on one disk we need to enter Disk Management in Windows: type “partition” in start menu search field (no quotes) press enter. Inside Disk Management: Extend the allocated disk (C:\) with unallocated space of the second disk by choosing “Extend Volume”. Now it's time to create our RAID-array. Install RTS (Intel’s Rapid Storage Technology) from HP or Intel website. I took my RTS from HP's 2570P drivers archive. Under “Create” tab: You can create the RAID-array, choose RAID 0. Setting Stripe size? This is something I forgot to do and had to settle with default 32KB. I’m happy with it so I don’t really care. In other words, I have no clue what's preferred. Press next and wait some 30 minutes or so in order to migrate data from (in my case) disk 1 to disk 0. You’re done! Now it should look something like my "Darth_Raider" =) ODD Face Plate mod (text instructions only) 1. Remove the optical drive (one screw under the notebook's back cover) 2. Take pictures of how the original bezel is attached to the optical drive 3. Pry of the bezel off of your optical drive (no point of being careful) 4. Cut off all ‘hinges’ from the bezel so it’s then flat and nice 5. Remove the (very useless) bezel from the eBay caddy by removing two screws under the sticker. 6. Use a light touch of glue (or tape) to test-fit the odd bezel on the eBay caddy. I7. f you're happy (nothing is sticking out?), glue it on permanently! Results RAID_0 Benchmarks: AS SSD & CrystalDiskMark Boot-up Time (Video): ~16s from power on to desktop
  23. 1 point
    Hello all, first post! I'm John from Washington. This seemed as good a place as any to introduce myself; thanks to Xonar for making the thread. I've lurked NBR for awhile but this seems to be more my type of environment. Now if you'll excuse me, I'm headed over to the 420 thread.
  24. 1 point
    There you go If anyone sees something promising or wants to see the sub menus or selection options let me know as there is a lot of stuff in there that I don't know what it is. The one thing that could be promising that I wish I hadn't sold my 120hz screen for is if the IGP is disabled it may make the 120hz screen+AMD combo possible. If Nvidia's 580 wasn't so ridiculously priced it wouldn't matter, but let's face it, $600 for one card is asinine.
  25. 1 point
  • 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.