Jump to content

Search the Community

Showing results for tags 'driver'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Forum Introduction & Feedback
    • Site Announcements, Rules & New Member Intros
    • TechInferno Forum Feedback
  • Tech News & Reviews
    • News & Reviews
  • Notebook Discussion
    • General Notebook Discussions
    • Notebook OEM Subforums
    • What Notebook Best Fits My Needs?
    • Legacy Articles
  • Desktop & General Hardware
    • General Desktops Discussion
    • Desktop Hardware
    • Overclocking, Cooling & Build Logs
  • Software, Networking & Gaming
    • PC & Console Gaming
    • Video Driver Releases & Discussion
    • Networking
    • General Software Discussion
  • Everything Else
    • Off Topic
  • Legacy Section (Not Actively Supported)
    • DIY e-GPU Projects

Categories

  • SVL7 & Klem VBIOS Mods
    • AMD
    • Alienware M11x R3
    • Alienware M14x R2
    • Alienware M17x R4
    • Alienware M18x R1
    • Alienware M18x R2
    • Kepler VBIOS
    • Lenovo Y400-Y500
    • Lenovo Y410p-Y510p
    • Lenovo Y580-Y480
    • Legacy BIOS/VBIOS
    • Maxwell VBIOS
    • Sony Vaio SVS13 / SVS15 series
  • BAKED BIOS Mods
    • Clevo
  • Utilities

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Steam


AIM


MSN


Website URL


Yahoo


Jabber


Skype


Location


Interests


Occupation

  1. I installed an NVIDIA Quadro P4000 Max-Q in a Clevo P750DM-G. Device manager hardware ID shows: PCI\VEN_10DE&DEV_1BB7&SUBSYS_75021558&REV_A1 I have done the standard inf file mod, then disabled driver enforcement as I have done successfully in the past, but it's not working this time. The install starts, then fails less than half way through. I have tried the DCH version, standard version, and studio versions and none of them will work. I am probably missing something. Could it be the result of the vBIOS? Below are screenshots starting with GPUz
  2. 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 ; [email protected].荈.<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. Okay here is what's going. I have a alienware m18x r1 running an amd 8970m, I wanted to upgrade it to crossfire but I could see a 8970m was more expensive than a r9 m290x So I decided to buy a r9 m290x and see if I could make it work in my alienware and also run crossfire. Even though many shops refused to sell me one because the didn't think it would work in an alienware m18x r1 only in the r2. Here is the whole process. 19/08/17 23:15 No post bios showing when booting, so impossible to enter bios menu, but can boot into windows 10 with no problems. 19/08/17 23:20 Because I haven't deleted the old AMD 8970m the r9 m290x shows as a 8970m with no problems. 19/08/17 23:34 First performance test was a success. The r9 m290x changed p-state normally. The gpu fan start spinning normally. But because of no thermal paste, the test lasted 20 seconds because the temperature raised fast. 20/08/17 00:00 Created a backup of the vbios version 015.032.000.004.044450 20/08/17 00:10 Flashed a new clevo vbios version 015.032.000.003.044465 Caused the card to be corrupted and resulted the 8 beep code. 20/08/17 00:35 Finally managed to flash the back and return the graphics card to its original state. 20/08/17 00:50 Flashed a new dell vbios version 015.046.000.014.045579 No change in behavior 20/08/17 01:07 After trying multiple vbios with no luck I finally found one. Dell vbios Version 015.041.000.000.044966 Brings back the post bios screen and I can now enter the bios menu through the r9 m290x. Note: This vbios reduce the cards performance from 900 mhz to 850 mhz 20/08/17 01:21 After more testing I found one that is working with no limits. Clevo vbios version 015.036.000.005.044618 Brings back the post bios screen and I can now enter the bios menu through the r9 m290x. This will be the vbios I will keep at the moment. 20/08/17 01:56 I completely uninstalled the previous driver and installed the newest driver. The graphics card is recognized as a 8970m but works normal. 21/08/17 20:15 I have inserted my old 8970m in the secondary slot and will start testing crossfire. 21/08/17 21:45 I have found out that the fan for the secondary fan did not spin. The is a cable that have felt out. I will fix it now. 21/08/17 22:00 In my try to test crossfire compatibility, I installed the newest AMD driver 17.7.2 but as soon it installed the driver for the secondary card it caused black screen. Only booting the computer in safe mode brings the screen back. 21/08/17 23:02 After many frustrating hours I finally managed to get crossfire working with the r9 m290x as the primary card and my old 8970m as the secondary. I have flashed the same vbios on both cards so the r9 m290x shows up I device manager as a 8970m. I first installed AMD driver version 16.2.1 Then installed AMD driver version 16.6.1 in order to play battlefield 21/08/17 23:20 First test run in battlefield 1 21/08/17 23:40 Battlefield 1 is flickering bad, this can maybe be solved with a new patch or driver. Other games I have tried is working perfect with crossfire on. Now what I would like to try is somehow force the r9 m290x driver to be installed and see if it will make it possible to run the latest AMD driver without getting a blackscreen. I have tried to edit the .inf file like you would do with nvidia but no luck. I have also tried to figure out how to edit the device id in the vbios, but I find it too complex.
  4. This new Game Ready Driver provides the best day-0 gaming experience for the latest new games supporting NVIDIA DLSS 3 technology including Conqueror’s Blade and Dakar Desert Rally.Gaming Technology Introduces support for the GeForce RTX 4070 Ti Fixed Bugs Portal RTX hang during resolution/mode change and GFE recording [3894168] [DirectX 12] Shadowplay recordings may appear over exposed when Use HDR is enabled from the Windows display settings. [200742937] AVS4You monochrome video preview [3890225] Players report black/grey screens in Outer Wilds with 522.25 driver [3841593] Lumion Pro 12.3 - Heavy corruption observed on app window.[3784371] Fixed brightness issue on some Notebooks [3765244] Windows 10 & 11 x64 Desktop https://us.download.nvidia.com/Windows/528.02/528.02-desktop-win10-win11-64bit-international-dch-whql.exe x64 Notebook https://ru.download.nvidia.com/Windows/528.02/528.02-notebook-win10-win11-64bit-international-dch-whql.exe
  5. Hello everyone! First of all sorry if this isn't the correct forum to post this. I bought a laptop few days ago. The laptop is Sager P150EM. Cpu:i7 3610qm Gpu: amd hd 7970m Ram: 8gb Os: windows 8.1 pro So my problem is that everytime i install the amd driver after the intel driver my laptop freezes or gets a bsod or something that stops it from working. Any help would be appreciated. I saw somewhere something about vbios does this matter anywhere?
  6. Well that didn't take long for NVIDIA to respond to Navi. The new 436.02 Game Ready Driver adds the following features: Game Ready Provides increased performance and the optimal gaming experience for Apex Legends, Battlefield V, Forza Horizon 4, Strange Brigade, and World War Z Gaming Technology Adds Beta support for GPU Integer Scaling Adds Beta support for Ultra-Low Latency Mode Adds support for new Freestyle Sharpen Filter Adds support for new G-SYNC compatible monitors Driver release notes: https://us.download.nvidia.com/Windows/436.02/436.02-win10-win8-win7-release-notes.pdf This isn't the old max pre-rendered frames setting, its supposedly a new improved algorithm that matches AMDs anti-lag feature for Navi. Next up is support for integer scaling which Intel recently announced but it seems NVIDIA beat everyone to the punch. Unfortunately, this is only for Turing for now: Additionally NVIDIA has created a new filter for FreeStyle simply called "Sharpen" which improves performance and visual clarity that is supposed to be on par with RSI but with much broader support and granular adjustment. According to Eurogamer, "They also point out that the amount of sharpening can be adjusted from 0 to 100 per cent, applied on a per-game basis and works with games across all major graphics APIs: DX9, DX11, DX12 and Vulkan". Finally, the driver brings with it some game performance improvement, including very popular titles like Apex Legends which sees up to 23% boost at 1080p: Overall a pretty solid release, it had some issues earlier when it was released with GeForce Experience being force installed but it should be remedied by now. View full article
  7. Following the release of NVIDIAs new 436.02 driver which I mentioned in an earlier article here, I've decided to make a quick and dirty video showing off NVIDIAs new Sharpen filter which is part of their Game Filter feature. It works with the most popular APIs including DX 9, 11, 12 and Vulkan and can be set on a per-game basis with granular settings of 0-100 unlike AMDs RIS which is limited to Navi and lacks DX 11 support. View full article
  8. Following the release of NVIDIAs new 436.02 driver which I mentioned in an earlier article here, I've decided to make a quick and dirty video showing off NVIDIAs new Sharpen filter which is part of their Game Filter feature. It works with the most popular APIs including DX 9, 11, 12 and Vulkan and can be set on a per-game basis with granular settings of 0-100 unlike AMDs RIS which is limited to Navi and lacks DX 11 support. View full article
  9. I got the exp gdc beast 8.5 got all the connections right... laptop boots up... fans turn on the gpu.... device manager detects gtx 1060 with a “ ! “ in a yellow triangle. Now what to do.... i tried to do the bios mod.... but realised that i have 3.07 version. Questions- 1 is there any way to get this done without the mod?? 2 if mod is the only way... kindly help me with step by step instruction in laymans terms... i m not a techy... so i might not understand technical terms.... altho i am interested... but learning yet. Please help.
  10. Hi everyone, I have an AW 17 (2013) on which i installed a gtx970m. So far I have always been able to mod the drivers and play with no major issue. After driver 373.06 (Yeah it got out a while ago, i started playing again recently) all the drivers i tried to mod and install do not work. I mod the inf file (nvdmi) with the subsys, then remove driver signature enforcement and install them, they install and everything looks fine on paper: nvidia control panes correctly states the number of the driver, in the control panel i read the hardware has no problem and the driver is updated. I set the options so that every game is run with the graphic processor, but for every game i run (I tried with several different ones) the computer always uses the shitty integrated graphic card. Does anyone have an idea on how i can fix this? thank you all for your help.
  11. 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 (15.45.19.4678) 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???
  12. My issue: one of the two 680M GPUs started displaying an "Windows has stopped this device because it has reported problems. (Code 43)". My hardware: Clevo P37EM / Sager NP9370 My OS: Windows 10 Enterprise 2016 LTSB x64 I keep the OS always up-to-date (Windows LTSB only ships security and fix updates). I also have very few softwares installed. Basically, my computer was working normally, but today I was playing Overwatch (which I always play) and after some hours, I suddenly heard a Windows beep, the game froze and the computer restarted. When I was back at the desktop, I noticed the resolution was not right and then I opened the Device Manager to see that one of the 680M was giving a Error Code 43. Both GPUs appear on my BIOS setup, the BIOS correctly identifies them as 680M. I found it strange, so I check my GPU VBIOS and noticed something odd, one of them was at 80.04.33.00.10 and the other was at 80.04.67.00.01 (I get these drivers here). I know for a fact that since some older NVIDIA Driver, the VBIOS must be 80.04.33.00.10 or else I got some errors on this SAGER model, so I flash 33 on both a while back. I then proceeded to flash the correct version again. When I run DDU I notice it only detects the VBIOS version for one of the GPUs, the other one doesn't show the VBIOS version. My results are: NV Driver 398.36 ROM 33 PCI BUS 2 working PCI BUS 1 error code 43 ROM 67 PCI BUS 2 working PCI BUS 1 error code 43 NV Driver 391.35 ROM 33 PCI BUS 2 working PCI BUS 1 error code 43 ROM 67 PCI BUS 2 working PCI BUS 1 error code 43 Can a Nvidia update or Windows update brick a GPU? How can I know if it's a software or hardware issue? I'm afraid that one GPU died as I don't have the money to replace it now and it would be difficult to find a spare new 680M (which is now old hardware) where I live. I'm panicking a little...
  13. 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 (15.45.19.4678) 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???
  14. Hello im new to owning an alienware laptop and i got some problems with that custom nvidia drivers for my model. There is no Dell driver for the 765m, i´ve read about changing the nvdmi.inf and i sucessfully installed the driver already by doing that. The problem i have is that i got no clue how to find out which section is the right for mine. I run into some weird error as my laptop freezes on restarting or shut down, or i get the message that UxdService needs to be stopped in order to shutdown. I tried to download the Dell Driver for the old 680m and find the right section from there but i guess im to stupid to understand as there are a lot of numbers. This is my hardware ID. I tried using section 62. Section 64 was also already tried. PCI\VEN_10DE&DEV_11E1&SUBSYS_05801028 I can play games just fine but it annoys me not to be able to shutdown without pressing the power button for a few secs. Very thankful if anyone could help. Also if anyone would explain me how to do it right i´d be glad to help other members.
  15. Hi, Masters, i m trying to let my egpu working through modding the inf file. My 660ti's device number is this PCI\VEN_10DE&DEV_1183&SUBSYS_2843 1462&REV_A1 and i manged to add a few lines in the nvlti.inf file, cause my laptop is thinkpad... i m not sure if i should mod this file or others either way it didnt work. i added line below [NVIDIA_Devices.NTamd64.10.0...14310] ... %NVIDIA_DEV.1183.2843.1462% = Section021, PCI\VEN_10DE&DEV_1183&SUBSYS_28431462 %NVIDIA_DEV.1183.2843.1462% = Section022, PCI\VEN_10DE&DEV_1183&SUBSYS_28431462 [Strings] ... NVIDIA_DEV.1183.2843.1462 = "NVIDIA GeForce GTX 660 Ti" for some unknown reason it just didnt work........ Could you guys help me out, this EXP thing is driving me crazy...
  16. Got a Alienware 17 R3 with GTX 970 M. Trying to overclock the GPU and need to download a VBIOS. Tried to download the file: Nvidia GTX 970m - 'OC edition' rev0.zip 1.0.0 from techinferno site but it would not let me. Can anyone point out a site that can get me going? Thx
  17. chidoughboy

    15.12 Crimson

    I didn't see any thread for the latest stable AMD drivers so I figured I'd chime in on my experience with them. They installed successfully and I was able to reboot but the whole system locked up after 10 min of browsing the web and I was forced to hard restart. I kept getting blue screens and was never able to load windows. I have prema v2 bios but does anyone else with an AMD mobility card have problems with this driver? I noticed AMD Overdrive is finally available for my GPU (8970M) but never had a chance to use it.
  18. Title. I'm experiencing a few problems including P-state drops when playing mid game and it really hurts my FPS. Thanks in advance. (Y510P SLI 755m) EDIT: I'm on Windows 10
  19. Hi, I have a Clevo P170EM with an AMD 7970M. Last year I tried to change the vBIOS of my 7970M, a friend of my tried to change it because he wanted to ''overlock'' the card. He said no worries I said okay do it, then later on he returned my laptop and bricked both my card and the normal BIOS. I had to repair the laptop trough a repair company in the city. They only could repair the BIOS by doing another BIOS on it. They said to try everything with the card but my laptop wouldn't accept it. The problem: After the Windows 10 installation I installed all the drivers from the manufacters site (http://www.eurocom.com/ec/drivers(226)ec). Including the SSD driver, then I FIRST installed and fully updated the Intel HD Graphics. After that I installed the AMD videocard drivers (crimsons edition), the weird part is, AMD autodetect sees my card and so does Windows. Then the driver ask me to restart my laptop, after restarting the Windows logo appears then the screen goes black with a blinking cursor left upper screen. I believe it has someting to do with the vBIOS of the card and I also believe that the card is not bricked but just wrong BIOS. I asked the manufacter and they say that the card may be bricked, when I ask for the BIOS they would not provide it for free (bastards). I asked for both the motherboard and AMD card BIOS, they said I have to pay for it. Question: Can someone provide information and files for the right vBIOS? I mean the vBIOS that is standard. Greetz, Jamie P.s I have some pictures and screenshot of Windows and the BIOS detecting the graphic card, the weird thing is both OS and BIOS detect the card but when I install the drivers it goes black P.s.s I already tried everything AMD support provided so I have no use for comments like ''Try unistall with DDU'' or try with second monitor etc. As you can see I've disabled the card because when I enable, Windows freezes and screen goes black.
  20. Hello, I have a msi GEFORCE gtx 980 ti going into the AKITIO thunderbolt 2. I have a 600w power supply with both of the PCI E (6+2)pin power cables going into the card. I am now on 10.9.5 after upgrading from mountain lion. (15' Late 2011 macbook pro i7 2.2ghz 16GB RAM . AMD Radeon hd 6750m 512mb) Whenever i run the script curl -o ~/Desktop/automate-eGPU.sh https://raw.githubusercontent.com/goalque/automate-eGPU/master/automate-eGPU.sh 2) chmod +x ~/Desktop/automate-eGPU.sh 3) cd ~/Desktop 4) sudo ./automate-eGPU.sh I get the response of "Only Kepler architecture cards are supported on OS X 10.9.5." I also have tried to run a modes driver i found a mirror link of and it states after the installer starts that "Mac OS X version 10.9.5 (13F34) is not supported with this package. Please see NVIDIA’s website for further driver information." I am a video editor and have my first big shoot in Los Angeles in two weeks, I would greatly appreciate any help I can get. Thomas, www.iamThomasDaniel.com
  21. M18X R2 Drivers Windows 7 x64 Dell's website isn't showing drivers for the M18X R2. Here is the backup off my thumb drive for those who need them until the show back up, Win 7 x64 https://www.dropbox.com/s/fmue5c9dweeqfnu/M18X R2 Drivers.7z?dl=0
  22. I've had this issue a while ago on my Alienware m17x R4 with 7970m and windows 7 Ultimate x64 and I've been trying to fix this since, but I've found a solution :DIt's probably more simple then you thought it would be :PBasically, what you do is you switch to iGPU Intel HD4000 first (FN+F7),then you have to install this audio driver (A01, 4/30/12, Creative Labs CT9570, Audio_Creative_W74_5NJ7K_A01-Setup_ZPE.exe), 6.0.100.2033 driver from their website,Switch back into dGPU again,there you go :DHope this helps
  23. NVIDIA earlier today released the 361.43 WHQL driver which comes with some long awaited fixes that cover power usage when idle at 144 Hz as well as SLI issues with Star Wars Battlefront. In addition, the driver adds support for GameWorks VR 1.1 as well as support for Oculus VR's latest SDK. Some highlights from the 361.43 release notes: Gaming Technology Support added for GameWorks VR 1.1 including VR SLI support for OpenGL applications and support for the latest Oculus SDK. Application SLI Profiles Added or updated the following SLI profiles: Bless - DirectX 9 SLI profile added DayZ - SLI AA and NVIDIA Control Panel AA enhance disabled Dungeon Defenders 2 - DirectX 9 SLI profile added Elite Dangerous - 64-bit EXE added • Hard West - DirectX 11 SLI profile added Windows 10 Fixed Issues Cleaned up flip timing and event notification bugs. [200151547] Fixed a driver bug where if the output is active, hot unplugging a device will cause any following hot plug device to be ignored. [1707505] Cleaned up unexpected behavior related to the multi-HMD (helmet-mounted device) use case. [200152110] Return NVAPI_NO_CONNECTOR_FOUND from the NVAPI_GPU_GetAllDisplayIds() when headless GPUs are detected to allow for identification of the unsupported use case. [200155835] [GM20x] Clock speeds remain above idle at 144 Hz on desktop. [1631144]  Lag in Star Wars Battlefront with SLI enabled after updating to driver 359.06. [1709067] Windows 8.1/Windows 8/Windows 7/Windows Vista Fixed Issues Prevented an extra hotplug/unplug for unconnected devices in escapeDirectModeEnable\DisableVRDirectMode(). [1707485] Fixed windowed G-SYNC not being totally disabled at the UMD (user-mode display) when the VR display is active. [200146036] Updated the whitelist entry regkey to allow multiple entries at once. [200155690] [GM20x] Clock speeds remain above idle at 144 Hz on desktop. [1631144] Other Fixed Issues Increased robustness of the VR SLI queued present implementation to mitigate flickering and tearing related to rendering to the scanout surface. This is not operating system specific. [200151843] View full article
  24. Good Day, My egpu driver is already installed and device manager requires to restart, but after restarting the egpu driver is undetected again. I'm using hotswap or hotplug trick while in sleep mode. Once the driver is detected and reinstalled again, it requires to restart the os. I'm trapped... Can someone please help and give me suggestions? thank you My setup: Toshiba l630 core i5 2nd gen 2.53ghz 4gb ram Pe4c 3.0 mpcie gtx 960 generic psu 600w driver installed dsdt override done win7 64bit ultimate
  25. NVIDIA released the GeForce 361.60 hotfix driver which addresses crashes in photoshop and illustrator as well as installing and clocking related issues. You can grab the driver from below. Windows 7 and 8 64 bit Version 32 bit Version Windows 10 64 bit - Win10 32 bit - Win 10 View full article
×
×
  • Create New...

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.