Jump to content
  • [Alienware] Aftermarket Upgrades Driver Support - Modded INF


    J95

    Instructions for modifying the latest GeForce 361.91 WHQL driver inf to work with Alienware notebooks.

     

    GeForce 361.91 WHQL


        *Install drivers at your own risk* Windows 10 + GeForce Drivers are Killing Samsung and LG Notebook LCD Display Panels
          Uninstall both PrecisionX & MSI Afterburner (Keep RTSS) including screen overclocking tools *Still at risk*

     

           Requirements:

           Due to driver incompatibility (black screens, TDRs, BSODs...) with previous vBIOS versions you must flash latest @Prema's v2 980M & 970M (Please consider donating to Prema)


    • Win10/8.1 'F8' Boot options 'Safe Mode' & 'Disable driver Signing'
      cmd (Admin)
    bcdedit /set {default} bootmenupolicy legacy

     

            -> reboot -> F8 -> select 'Disable Driver Signature Enforcement' -> Install drivers

    • Run DDU "Clean & Shutdown (Safe Mode)
    • Extract driver using 7-Zip
    • Display.Driver folder,  copy/overwrite the proper .inf file
    • Extracted driver package,  run setup.exe  

           -> Keep these folders only <-

    361.75.thumb.PNG.cd5111f39779e9d64f24d39

     

     

        INF MOD v361.91

       

    nv_dispi.inf (including nvdmi.inf) PEG/Dedicated All Models: M15x, M17x, AW17 R1, M18x, AW18 R1 (including Optimus/M17xR4) excluding AW 2015 - GTX 980M , 970M , 965M , 880M , 870M , 860M , 780M , 770M , 765M , 680M , 675MX , 670MX , 660M

     

    nvcvi.inf: Optimus Alienware 17 / 05AA (only) GTX 980M - 970M - 965M

          

    Updated throttle free PEG MODs

     

    GeForce 353.00 PEG MOD Win7/8.1 - Full_Profiles_8_v353.00.txt

     

    GeForce 352.84 PEG MOD Win 10 - Full_Profiles_4_v352.84.txt...soon Done!

     

     

     

    GeForce 361.91 Win 7/8.1

    GeForce 361.91 Win10

     

     

    nv_dispi.inf_v361.91_Win7_8.1_PEG_Dedicated.zip

    nvcvi.inf_v361.91_Win7_8.1_Optimus_Alienware_17.zip

     

    nv_dispi.inf_v361.91_Win10_PEG_Dedicated.zip

    nvcvi.inf_v361.91_Win10_Optimus_Alienware_17.zip

     

     

    @thegh0sts

    120Hz models! NV v361.75 previously installed, set refresh rate to 60Hz before uninstalling drivers. DDU uninstall "Clean and restart",  Options: uncheck "Remove present and non-present monitors"

     

    DDU2.thumb.PNG.4070f614da472125a2264c0cf

     

    Continue original discussion here. 


      Report Article


    User Feedback


    I removed my previous intel drivers in safe mode using ddu. I was running peg with no Intel driver installed at all. After reboot windows comes to black screen and the restore point didn't save with previous working drivers. I am trying to see what's possible as I somehow need to install the drivers in safe mode but without signature verification and I'm not sure if that's possible. I'm guessing maybe installing Intel driver in safe mode may let me boot to start over again though I wanted to avoid that. Windows is also set to neverase update video drivers in Windows 10 as per DDU. Any ideas other than what I stated above? 

    Share this comment


    Link to comment
    Share on other sites

    hi , i cant download the inf files.

     

    I need a  modified driver for Alienware 17x Nvidia GTX260m Card

     

    thanks

    Share this comment


    Link to comment
    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 ounces
      After spending significant time and effort to obtain "DC" screen for 8770w (which is essentially a regular IPS panel with fancy board that converts 8bpc LVDS to 10bpc DP), I have finally got and installed one. All works great, except of the one problem...

      It has pretty bad banding / posterization in lower shadows. I have tried profiling it in different modes (full range, sRGB, rec709) - issue persists, and it indeed shows only in the lowest part of the characteristic curve. Mids and highlights are represented fine and show low deviation from reference values.

      GPU is HP K4000M, Nvidia drivers installed "as it is", video-card is identified without a hitch.
      Banding was not present with the original TN panel using the same GPU.
       
      While checking a software side, I have noticed that Win10 has bit depth set to 8-bit...
       

       
      My initial reaction was, - "Easy, let's change it in `nvidia-settings` and we're all set":

      ...but that would be too easy, right? After selecting 10bpc and clicking "Apply" screen went off and back on, only to show that depth stayed at 8bpc. Repeating the above few times yielded exactly the same result and I'm not in a hurry to meet a cliched (and laymen) definition of insanity.
       
      Let's check GPU-Z. So far so good, nothing unusual. Notice the highlighted BIOS version and subvendor string:
       
      Time to delve into other tabs. We are running WDDDM v2.4 which supports GPU dithering, but hey... BIOS version has changed!
       
      Briefly back to `nvidia-settings` to check what is reported by vendor's own utility:

       
      So far, we have two strings for BIOS version:
      80.04.5A.00.02 (let's call it an "A") 80.4.33.0.37 (let's call it a "B")  
      Notice how 2nd one seems to not follow hexademical notation. Lastly, "NVIDIA BIOS" drop-down, reports "A" version:
       
      ...and monitor section which confirms that rig is indeed capable of 10bpc, but currently running at mere 8bpc:

       
      Windows "Adapter settings", reports version "B". It's 2019, diversity is a must.

       
      "NVidia inspector" is of the same opinion:

       
      Now, let's use some seriously legit tools and check-in exported BIOS file in `nvflash`:

       
      Here we have two three interesting findings:
      Reported vendor is Dell, not an HP. See this link for details. BIOS version is back to "A". Have I already mentioned diversity? MXM module uses MX25L2005 flash storage in WSON-8 packaging. If things go real nasty, we should be able to rescue a patient via Pomona clip and external programmer.  
      Loading the same file in "Kepler BIOS tweaker" confirms the facts:

       
      EDID settings, courtesy of NVidia Control Panel. Hex dump can be found at the bottom of this post.
      ...Shall I be worried about "60.02Hz" refresh rate?
       
      To summarize:
      Why two different BIOS versions are reported? Anything to do with UEFI (e.g. HP is sideloading its own during boot)?.. Why two different vendors reported? As far as I remember, this is branded HP GPU. Where to get "clean" BIOS of K4000M for future experiments? Ideally from 8770w equipped with "DreamColor" panel from a factory.  
      Link to the dumps, BIOS ROM and monitor EDID: https://mega.nz/#F!zGgRmQIL!9q2QFZtHuK2RQ-WHXMA4Mg (also attached to this post)
      K4000M.zip
    • By Blocker35
      Hi guys, bit of a rookie to the whole EGPU scene. Currently I have:
       
      - MacBook Pro 2015 13inch (3.1GHz Core i7 16GB RAM)
      - Razer X Core 
      - Apple TB3 to TB2 Adapter
      -  TB2 Cable (Cable Matters)
      - 23inch AOC External Monitor
       
      I am wonder about what graphics card to get to run X-Plane11 with high graphic settings?
      I have purgewrangler set up and ready to use with an AMD graphics card, but am also open to the idea of an Nvidia graphics card.
      Any advice appreciated. I did not buy a Windows PC as I need a Mac for various other things and wanted an all-in-one laptop.
    • By danger007
      Well I am back, sort of.
       
      Reminder of Stats
      *Alienware M17x R4 (bought June 2012) w/ Intel i7 3720QM@2.6ghz (Ivy Bridge) including the igpu Intel 4000 HD series
      8GB Ram, 17 Inch, SoundBlaster software only Recon 3DI, and the normal stuff that comes with it
      *Graphics Card:  Originally shipped 660m, upgraded to 7970m, 7970m died early, with community help moved to MSI 4GB 680M (flashed to Dell thanks to @svl7) and installed I think 314.xx drivers with help from many (sorry can't remember everyone but notable was @J95), was running 7970m in whatever they called their hybrid drivers, the 680m is run in Optimus)
      *OS:  Windows 7 64bit Service Pack 1
      *Storage:  Msata 1tb Samsung 850 Evo, 2 Hitachi 1TB 7200 rpm 2.5" drives (yes I used all 3 GB or will)
       
      So what will you read.  What got me started on this project and then using all the resources on the net, from @J95 and legions of others I owe all credit for the project too.  Please note I take no credit, take no rights, this is simply something to help others out based on working with what has already been laid down for us.   Installing the latest Nvidia 417.67 mobile/notebook drivers for a 680m for Windows 7 Service Pack 1 on Alienware M17x R4
       
      When I got things up and running back in 2016/2017 with the noted people above I saw a new driver and with the STO game having a driver issue I upgraded to it.  Now I didn't notice anything wrong, the game worked and so paid no attention.  When I started to get unable to eject 680m error messages I thought great who got this, ejecting a gpu, wrong.  I then tried the uninstall Intel, Nvidia, use DDU in Safe Mode, disable AV/Firewall, disable driver enforcement, etc then reinstall intel, nvidia (removing certain folders) with the modified inf but now the game said it couldn't find any feature set and wouldn't let me play.  Finally removing the Nvidia drivers allowed at least the iGPU to run the game.  Used Unigine Heaven 4.0 to encounter more errors with Nvidia.
       
      I moved back to my msata install of windows 7 that I haven't had a chance to work on since 2017 (i know pathetic) that only had system drivers, expired Norton, and not yet registered/activation.  Seems fine.  Tried to run Heaven, same error.  Well after 3 days of trying to duplicate what I had been instructed to do, I finally sat down with a nice big bottle of Fiji Water (courtesy of lovely lady at the Oscars in almost every background pic) and decided I was determined to fix things.   I downloaded the 419.67, copied the nv_dispi.inf & nvdmi.inf to get to work.  After reading the content and using comparisons once again from the noted individuals and the legions of other, I had them modified and decided to give it a try on the clean win 7 install from 2 years ago.  After the uninstall, ddu, deleting folders, copying mod. inf to their directory (also included the change to setup.cfg - credit once again goes to individuals like @J95), gyrxiur, DeathAngel , creator of Notepad++, sora and many others) I was able to launch the Heaven 4.0 Benchmark.  So I am assuming that I have the new 419.67 working on my system.  I did a benchmark of the 680m in 419.67 with unigine Heaven 4 to go with the files I am posting.  Please note the bios was provided by I believe @svl7 (sorry if I got wrong person) and no overclocking of it other than what the changed vbios did.
       
      I am attaching below the following:
      Nvidia 419.67 modified inf and config - nvdmi.inf, nv_dispi.inf, setup.cfg (no credit to me all credit belongs to others)
      The Unigine benchmark results (txt file).
       
      Now the shortened legalize warning
      Please remember you are to take all risk when using modified inf files, I take no responsibility (no virus or other dildrus included) if they don't work with your GPU.  The usual.
       
      This was tested and used on Alienware M17x R4 running the last bios they released A12 or A13 and so it the system bios is not modified at all, the card is a MSI 680m 4Gb flashed vbios to Dell 680m 4GB, and installed in Windows 7 64bit Service Pack 1.  Hopefully if you have only a different card you can make any minor adjustments you need to.  
       
      Please let me know how they work.  I will also be reporting back on the reinstall on my other laptop install I use to play Neverwinter/ Star Trek Online - was suppose to be a temp solution till new install was finished, and if they worked on it as well.
      Alienware M17x R4 680m 419.67 Mod Inf and Setup and Heaven 4 Benchmark.zip
    • By Edrc
      Hello,
       
      I am new on this forum, so I am sorry if posting at the wrong place. It's been 2 weeks that I am searching how to make my GTX 980M 8GB working Inside my Alienware 17 R1 (June 2014, i7 4710MQ, 60 Herts Display, OPTIMUS and the GTX 880M Inside died.)
      After "quickly" looking some forums, I saw that a 980M would easily fit Inside … but maybe I was wrong.
       
      Hardware wasn't a problem. I've also could install drivers by modding the nvdmi or nvcvi. inf files. The card was recognied BUT :
      the clock speed is locked a 135 or 405 Mherts and fan is not runing when booted up.
      I tried to flash vBios with nvflash and some ROM I found on vBios collection … but no way to get this working properly.
       
      So, i'm coming here. I've seen many people talking about Prema or svl7 or other big boss in the place … but ? how ? where ? when ?
       
      Inside the peripherial manager I have this in remote acces path : PCI\VEN_10DE&DEV_1617&SUBSYS_05AA1028&REV_A1\4&D590A51&0&0008
      So I assume my GTX 980M card ID is 1617 and vendor and PC Model are 05AA 1028.
      But near the "Standard Microsoft Video Card" there is a yellow exclamation point and Inside details it says "this peripherial doesn't work properly" when no Nvidia drivers installed.
      I could find some vBios with 1617 (Asus) but black screen at boot up. Since laptop model where not the same .. probably.
      And I wasn't able to find 1617 with the existing 05AA 1028 … as the GTX 980M was not an option for my model. (AW 17 R1 2014 ,60Herts)
      I tried 353.60, 382.33 and 419.35 drivers. The latest one seems easier to install but longer.
       
      BIOS is A16 from Dell. And I am using Windows 10. Got a Dell 330W brick. 
       
      I saw a guy with the exact model as me, he gets a modded vBios especially for his configuration, then everything worked easily … but can't find the topic again
       
      I guess depending on the card info and the laptop model … a dedicated vBios is required … 
       
      So, If anyone here got some informations or any kind of help for me, it would be very nice.
       
      Thanks for reading and help.  
       
      PS: there are a lot of files, pictures and links that I can't see on this forum .. even after registration …. 
       
×

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.