Jump to content
JChristian

One of the 680M SLi might be dead after an update?

Recommended Posts

Posted (edited)
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...
Edited by JChristian

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Similar Content

    • By thechillhacker
      Hello all
       
      I have a Clevo P370EM3 laptop with a pair of GTX 680Ms in SLI mode and have never been able to get Linux to work properly with full acceleration and without tearing. I have tried every xorg config I can find, and even all the modifications from the nvidia configurator to no avail. Has anyone been able to get these things to work 100% in Linux? I have typically used ubuntu based distros, including Mint, and every available driver version from the repositories, but can never get it to work quite right.
       
      Thanks for any help anyone can provide. It is killing me to run Windows on this machine because of these issues, and I am almost to the point of installing the inferior 7970 cards.
       
      Have a great day
      -TCH
    • By jhsd1124013561
      Help! I created a BOS BOOT DISK and use legacy to boot in DOS.   But it is saying that "An operating system wasn't found".   I have extracted all the files (the alienware m18x r2 a11 unlocked bios) into my external hard drive (format: NTFS)
    • By Mengqin
      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.
         
       
    • By Psycha
      Hello, I'm on an alienware m17 r4 and am trying mod my vbios for a 970m 3GB msi. I've managed to get the max boost with an increase in voltage, however I believe my voltage settings maybe unstable. When attempting to load programs capable of high gpu usage capabilities, the gpu begins to become pretty unstable. would anyone be able to provide assistance? I have both my edited and original roms as well.
       
      *update
       
      I'm not sure how to delete this thread but disregard this please. I've figured out the issue.
    • By Say
      Wlc,
      I want to create an afermarket diy cooling solution for my laptop.
×

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.