Jump to content

Skyl3r

Registered User
  • Posts

    26
  • Joined

  • Last visited

Everything posted by Skyl3r

  1. Hello all, I purchased a Clevo 980m to upgrade my current system as described below: Alienware m17x r4 24GB (8+8+4+4) i7-3920xm GTX 680m SVL7 A11v2 Unlocked BIOS Windows 10 Professional I was able to install the GPU with no major issues. (Had to remove the clevo backplate, and use the clevo screws instead of the Dell screws). What I attempted to do to make the GPU work was the following: Before install, I set laptop to UEFI, disabled legacy ROM, enabled Windows 8 Fast Boot. I also left switchable graphics on, because I am fine with Optimus I booted the laptop and did a clean install of Windows 10 Windows 10 automagically detected my hardware, including the 980m. So I tried just downloading 980m drivers from NVidia and installing them The 980m does not work. It shows in Device manager with the yellow exclamation point saying "Windows has detected a problem with this device ..." So I tried running DDU, then modifying the INF by following the guide here https://null-src.com/posts/nvidia-notebook-driver-inf-mod/post.php (I searched for a device in the Dell/Alienware .inf that had a PC model code of 0551 which I obtained from the hardware ID of the 980m, then cloned that line, changing the GPU model code to reflect the 980m's GPU model code. Then added an entry into the [Strings] section for it.) I had the same results after installing the drivers with my (perhaps incorrectly?) modified INF. I tried rebooting with PEG only and Integrated disabled, then running DDU and reinstalling using the same modified .INF and had the same results. Windows loads fine, and ONLY shows the 980m in device manager, but still says it has an issue. Above is what I did in the order I did it. Does anyone have an idea if I did something completely wrong or I missed a step or anything? I heard this was the best place to ask EDIT: This has been solved now. Thanks much to naightmehr. The solution was a correctly modified .inf file with the right driver version. If you find yourself in the same situation try installing some old driver verisons. The one that worked for me was 352.84! Rock on fellas!
×
×
  • 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.