1. Best Nvidia Sli Drivers

I installed the last official WHQL drivers from NVIDIA which are v15.27 for Vista, and proceeded to enable the RAID mode for SATA in the BIOS. It looks like no need for two same card not sure if it still works just wanted to share.

@ all users with a NVIDIA nForce chipset mainboard: Preliminary notes. Many users with an nForce chipset mainboard, who are running or going to install Vista, Win7, Win8 or Win10 (32/64bit), are searching for nForce chipset drivers, which are suitable for their special chipset and will give them the best possible performance and stability of their system. NVIDIA itself doesn't offer them. As you probably know, NVIDIA had stopped the development and the production of the nForce chipsets already in springtime 2010. That is why there are no newer nForce chipset driver packs available. Unfortunately many nForce chipset drivers packages, which have been officially released by NVIDIA, have not been optimized for all nForce chipsets they were designed for.

Some of them are not even usable with certain nForce chipsets. That is why I started in January 2008 thread at nForcersHQ Forum, where I was offering some especially optimized nForce driverpacks for Vista (and later for Win7). Since the nForce SATA RAID and -if applicable - the nForce SATA AHCI drivers never have been separately released by NVIDIA and always were part of the nForce chipset driverpacks, I decided to put parts of this nForcersHQ Forum thread into this Forum. Question: For whom are these driverpacks suitable?

The installation of my driverpacks makes sense for owners of an nForce chipset mainboard, who ran into problems with NVIDIA's official packs (for example NF4 users) or who are searching for a driverpack combination, which gives them a better performance (owners of all NF4-7 series chipsets). Important:. Only my 'Actual nForce Driverpacks' are optimized for the advanced AHCI features, which are supported by the latest nForce chipsets from MCP65 up. Users, who want to run their SATA hdd(s) in full 'AHCI Mode', but avoid to install any modified driver, may take NVIDIA's official driver sets. All my packages contain the untouched original NVIDIA drivers (that are the files with the extension '.SYS').

The customization of my 'modded' driverpacks concerns just the associated text files (with the extension '.INF') to make the original drivers compatible with other nForce chipsets and has no negative impact regarding the function of the drivers (=.SYS files). If you are running the installer of any nForce driverpack, you must not expect, that all nForce drivers of your OS will be updated by the drivers, which are within the set. Maybe the installer will give you just the option to install 1 or 2 of the set drivers. This is absolutely normal and may have one of the following reasons:. a) not all nForce chipsets will need all included drivers of the package (example: nForce4 chipsets don't have any device, which is supported by the SMU driver) or. b) the installer believes, that the OS has already the 'best' driver for the related device (not always the truth, but you can always try a forced manual driver update from within the Device Manager by using the 'Have Disk.' Option).

Everything is ok, if you look into the Device Manager and verify, that none of the NVIDIA related devices has a yellow mark. You won't find a NAM folder with NVIDIA's 'Network Management Tools' within my packages, because they are useless for nearly everyone and may cause problems. Big advantage: The download is much quicker due to the small package size. Before you are going to install a new nForce Ethernet driver, you should uninstall the previously running one (exception: the in-box drivers cannot be uninstalled).

Manual installation of the nForce drivers: It is no problem to install any special nForce driver, which is part of the related driverpack, manually from within the Device Manager, but nForce RAID users should pay attention: A successful manual update of an already running nForce RAID driver is not as easy as with other drivers. A step-by-step guide can be found. Optimized NVIDIA nForce Driverpacks (32/64bit) Last updated: ) Changelog:. Replaced:.

32/64bit 'Latest nForce Driverpacks for Win7-10' (now v10.4 again, reason: the re-customized SATARAID drivers of the v10.5 Sets didn't really work) A. WHQL certified nForce Driverpacks (do not contain any modified drivers) 1.

'NForce4 WHQL Driverpacks for Vista/Win7' for nForce4 AMD chipset users, who prefer or need WHQL certified drivers (especially for/after a fresh OS installation onto an nForce4 RAID system) Users with an nForce4 RAID system will run into problems, when they try to get any Windows OS from Vista up installed, because neither the in-box nor the latest nForce SataRAID drivers, which were offered by NVIDIA until 2010, do work with 'LEGACY' mode RAID configurations (note: 'LEGACY' mode RAID systems have the ability to support PataRAID and SataRAID arrays simultaneously). This is the reason why I still offer these special WHQL signed Vista/Win7/Win8 driverpacks for users with an nForce4 chipset mainboard. They should work with Win10 as well.

Here are the download links to my 'NForce4 WHQL Driverpacks' (with multilingual installer):. These are the components:. Ethernet Driver (v67.89) WHQL. SATAIDE Driver (v9.98) WHQL.

SATARAID Driver (v9.98) WHQL. RAIDTOOL Application (v9.99) 'Sedona'. SMBus Driver (v4.69) WHQL. Realtek AC'97 Codec Audio Driver (v63.05) WHQL. Installer (v8.36) Informations regarding these driverpacks:. Compatibility:.

Contrary to NVIDIA's officially offered nForce chipset driver sets these packs are fully supporting nForce4 AMD RAID systems. Users with such hardware configuration can use the included WHQL certified nForce IDE drivers v9.98 even from scratch by loading them during the Win7/8/10 installation (look ). For further details you may look into (for Win7) or (for Vista) installation guide. Although these 'NForce4 WHQL Driverpacks' will support all RAID and non-RAID systems with an nForce4 AMD (=CK804), nForce 430/410 (=MCP51), nForce 590/570/550/680i/650i/780i/750i (=MCP55) and nForce 430/405/400 (=MCP61) chipset, I only recommend them for users with an nForce4 RAID system, who are going to do a fresh installation of Win7 or Vista or ran into problems with another nForce driver pack.

Performance:. The included nForce IDE drivers v9.98 will give you a stable system, but not the best possible performance. That is why I do not recommend to take the 'NF4 RAID WHQL Driverpacks' unless you have an nForce4 AMD system and want to get Win7 or Vista installed onto your nForce4 RAID array. Driver update via Windows Update:. It is highly recommended to disable the automatic Windows Update option, because otherwise you risk, that you get nForce drivers installed, which are broken or worse than those you had previously installed yourself. If Windows Update is offering any new nForce chipset driver, you should only accept it, if you are sure, that the update is useful and safe. AC'97 Codec Audio driver:.

Since Win7/Vista do not natively support the Realtek AC'97 Codec Audio chips, which are the most common ones on nForce4 mainboards, I have added the actual AC'97 Codec Audio drivers from Realtek to these special nForce4 driverpacks. The Realtek Audio driver may not be installed automaticly by running the installer of the package. So the users probably have to do a manual driver installation from within the Device Manager.

Mod+signed nForce Driverpacks (do contain modified, but digitally signed drivers) Relevance of the driver's 'Digital Signature' The latest Windows Operating Systems from Win8 up have a feature named 'Driver Signature Enforcement', which does not allow to get any driver installed, which has no valid digital signature. Since any modification of the associated INF file automaticly breaks the digital signature of the driver, there is only one way to get a 'modded' driver installed onto Win8/8.1/10 without the need of disabling the automaticly active 'Driver Signature Enforcement': The modded driver has to be digitally signed by a trustworthy person or Company. Notes:. All modded drivers, which I am offering here, have been digitally signed by me according to mrces2's guide (look ). Consequence: It should be possible to get these drivers installed without any problems (no disabling of the 'Driver Signature Enforcement' required)!.

Nevertheless you may get the message while trying to get any 'mod+signed' driver installed, that 'the best driver is already running'. This always will happen, when you want to replace a) a WHQL certified driver or b) a newer driver by an older one.

Solution: Force the installation of the 'mod+signed' drivers by using the 'Have Disk' button. How to benefit from the digital signature of the modded drivers: To get full benefit from the driver's digital signature it is necessary to import the related Certificate and to declare the signer as trustworthy. Important: This procedure has to be done only once, but before you are trying to get the first 'mod+signed' driver installed. You can find all needed informations about how to import the Win-RAID CA certificate. Note: Since the digital signature of the modded drivers has not yet been imported at this stage, they cannot be used from scratch. That means, that they are not suitable for the integration into a Win8/10 image and cannot be loaded during the OS installation.

Here are my 'mod+signed' nForce driverpacks for Vista/Win7 resp. @ grug: Welcome at Win-RAID Forum and thanks for your remark regarding the MEGA link to 'Fernados Actual nForce Driverpack 64bit v9.0'. Zitat von im Beitrag Section 2 above (Actual nForce Drivers for Vista/Win7) x64 download link points to the XP x64 download.

Is this by design or a typo? I see this: 'Fernandos Actual nForce Driverpack for XP 64bit v9.0.7z (18.4 MB)' The SkyDrive (MIRROR) link was correct, but the MEGA link was wrong - my bad. Meanwhile I have corrected the MEGA link. Thank you for the info! Regards Fernando. I want to thank you all the hard work you've put into this project of yours, it is extremely helpful and your knowledge of storage subsystems is impressive.

I have searched the forum for the answers to some questions I have but can't seem to find them, so here it goes: I own a DFI LanParty SLI-DR Expert mainboard with the nForce4 SLI AMD (CK804) chipset and I am wondering if it does support AHCI mode and indeed if so I would like to buy an SSD. There is no mention of AHCI in my BIOS but there is an option to enable the MediaShield RAID ROM, which I am guessing supports AHCI as part of the MediaShield controller? The ROM is v5.50.

My previous BIOS configuration was not optimal as I had my HDD plugged into the nForce SATA-II port but I had not enabled RAID mode and Windows was using the in-box storage driver which was running in ATA mode so I was not getting NCQ or AHCI at all! I am using Windows 7 Service Pack 1 32-bit. I installed the last official WHQL drivers from NVIDIA which are v15.27 for Vista, and proceeded to enable the RAID mode for SATA in the BIOS. After I did this I was unable to boot the system drive, but I managed to fix this by disabling RAID mode in the BIOS. I am assuming I need to enable RAID mode in the BIOS.before. I install Windows and install the drivers as well. So to clarify, could you tell me if I do need to enable the MediaShield RAID mode in my BIOS in order for AHCI to work, if I need to make them part of an array or can I just leave them as JBOD, and what would be the best driver pack (from either yourself or NVIDIA) to get the best performance, stability and AHCI support.

Thanks for your time:-). @ Syst3mSh0ck: Welcome at Win-RAID Forum! Zitat von im Beitrag I own a DFI LanParty SLI-DR Expert mainboard with the nForce4 SLI AMD (CK804) chipset and I am wondering if it does support AHCI mode and indeed if so I would like to buy an SSD. I am sorry, but your nForce4 chipset system doesn't support AHCI. Zitat I installed the last official WHQL drivers from NVIDIA which are v15.27 for Vista, and proceeded to enable the RAID mode for SATA in the BIOS.

After I did this I was unable to boot the system drive, but I managed to fix this by disabling RAID mode in the BIOS. I am assuming I need to enable RAID mode in the BIOS.before. I install Windows and install the drivers as well.

That is correct. You can find a guide about how to get Windows 7 installed onto an nForce4 RAID system within the start post of thread. Zitat So to clarify, could you tell me if I do need to enable the MediaShield RAID mode in my BIOS in order for AHCI to work, if I need to make them part of an array or can I just leave them as JBOD, Since you will not be able to get AHCI enabled, I recommend to run the SSD in IDE mode by using the generic MS IDE driver named PCIIDE.SYS. This is the only way to get TRIM working within the SSD. Zitat and what would be the best driver pack (from either yourself or NVIDIA) to get the best performance, stability and AHCI support.

You will not get AHCI support by any of the nForce driverpacks. Usually I recommend the 'Non-AHCI nForce Performance Pack' for nForce4 chipset users. Regards Fernando. I want to tahnk you, you saved my day:). I have an ASUS P5N32-E SLI PLUS with nForce®650i SLI & nForce®570 SLI chipset. I have one SSD as primary HDD.

I read on some forums that I need to enable RAID mode for SSD. I setup SDD in JBOD. I have also setup a RAID 0 in bios for other two disks in striped mode, but in windows I see one big HDD NDIVIA JBOD 931,52G, and I don´t know if it is normal or not.

In nvidia control panel I see 2 snapping. Fisrt is my SSD and second is with the two HDD. I also want to know if the disks must be identical for RAID 0, because mine aren't:-s.

It have the same size, but is two different disks. I attch you a print screen to see. In bios when I look at aray, it show Striping Mode.

I want to ask if this drivers works with windows 8.1? (old drivers report controler error, and causes BSOD). Now I have Windows 7, and it work good, no error, but I want to know if it work with windows 8.1 or windows 8. What version you recomand for me? I downloaded 'Non-AHCI nForce Performance Packs for Vista/Win7'. I tried to view Clasic NVIDIA Control Panel, and when I select from view - use clasic nvidia control panel, i say that when I start again it will be in clasic mode, but at next start is same control panel, not the clasic one.

Thank you again! @ m1hn3a: Welcome at Win-RAID Forum! I doubt, that you have created a RAID0 array. It seems to me, that you are running your 3 drives in Spanning (JBOD) mode.

JBOD provides a method for combining drives of different sizes into one large disk. For details you may look.

Before I answer your questions, I need some additional informations: 1. Please enter the NVIDIA nForce RAID ('MediaShield') Utility by hitting F10 (or similar) while booting, what do you see? If possible, post a screenshot.

Please give me the HardwareIDs of your NVIDIA nForce RAID Controller (open the Device Manager, do a right click onto the Controller 'Properties' Details' 'Property' 'HardwareIDs'). Regards Fernando. @ m1hn3a: Thanks for the screenshots. According to the HardwareIDs your system has an MCP55 Soutbridge.

By the way: I wanted to see the NVIDIA 'MediaShield' Utility (running in DOS mode) and not the NVIDIA Control Panel. Zitat von im Beitrag 2. I have an ASUS P5N32-E SLI PLUS with nForce®650i SLI & nForce®570 SLI chipset. I have one SSD as primary HDD. I read on some forums that I need to enable RAID mode for SSD. I setup SDD in JBOD. I have also setup a RAID 0 in bios for other two disks in striped mode, but in windows I see one big HDD NDIVIA JBOD 931,52G, and I don´t know if it is normal or not.

In nvidia control panel I see 2 snapping. Fisrt is my SSD and second is with the two HDD. I also want to know if the disks must be identical for RAID 0, because mine aren't:-s.

It have the same size, but is two different disks. I attch you a print screen to see. In bios when I look at aray, it show Striping Mode. You should check the SATA ports. It was not a good idea to connect the Raided HDDs to the SATA ports 1.1 and 3.0. The HDD manufacturer usually doesn't matter, that means can be different, when you create a RAID0 array.

I want to ask if this drivers works with windows 8.1? (old drivers report controler error, and causes BSOD). Now I have Windows 7, and it work good, no error, but I want to know if it work with windows 8.1 or windows 8. The Win8 and Win8.1 on-board NVIDIA nForce drivers should work with your system, but you will not be able to install any of my modified driverpacks unless you have disabled the Win8/Win8.1 driver security check. What version you recomand for me? I downloaded 'Non-AHCI nForce Performance Packs for Vista/Win7'. Yes, but only for Vista or Win7.

If you want to run Win8/Win8.1, I would use the on-board nForce drivers. I tried to view Clasic NVIDIA Control Panel, and when I select from view - use clasic nvidia control panel, i say that when I start again it will be in clasic mode, but at next start is same control panel, not the clasic one.

I don't know the reason for that behaviour. Hello, I have attached you 3 screenshot from MediaShield Utility. A also changed port from 1.1 to 3.1, but afrer restart I was not able to use my raid array, until I reinstall Srorage Driver in windows. MediaShield see my array, but in windows says that one drive (that I changed port) is missing. After I reinstaled drivers, my array work like a charm.:-). I also have one problem with network card, after I reinstalled drivers from pack and I set up IP to manual, after restart, it doesn't take my manual IP. I deleted driver and install again manualy (form pack, with have a disk option) and nou I see that it works, for the moment (I will see after more restarts).

I used on-board drivers for windows 8.1 and it report errors from controller in event view and it gives me BSOD, that is the reason I installed windows 7, to see if really controller is the isue or the drivers. I will try again with your drivers, and if is not working I will try with windows 8 but maybe next weekend:).

I changed ports, and it's better now,:) 1. 3.0 and 3.1 I have 168 MB R/W 2. 2.0 and 2.1 I have 179 MB R/W 3 1.1 snd 3.0 I think a little more something arownd 185 MB, why? I think 1.0 and 1.1 is one controller, 2.0 and 2.1 another and 3.0 and 3.1 another?

It's better to be on same controller or different one?:)You suggest to leave on 2.0 and 2.1? I made tests with Crystal Disk Mark. In weekend I hope to have some time and try again with windows 8.1. What pack of drivers you suggest tot try?

The built in drivers are not good:). If I have any question I wrtite here.

Nvidia INF driver modding how to mod the nvidia geforce inf file - Modded drivers will NEVER transform your GPU to another one, and will NEVER add features that you do not already have. The only reasons you might want to install a driver that you need to modify the INF for is because: One, newer then what is currently available and you simply want to try it. This is less common with Quadro, but iCafe and laptop OEM's often leak out early builds. It can be interesting to see if fixes or other announced features are included. I remember we were able to try driver NVCP FXAA before it was officially included in the driver.

We also got to test the shader cache option a few days before it was officially added. And just pure fun/experimentation. Maybe NVIDIA did something really cool in a new branch that we don't have yet.

Also, it can be used to force installation of newer drivers on OEM locked GPU's. Thus the existence of laptopvideo2go. And two, you need an older driver that is not officially supported for your GPU because you have a specific application that is broken in newer ones and you cannot wait for a fix.

Number one covers 99% of the reasons, but every so often some old game or deprecated program. The guide may look lengthy, but once you do it the first time, modding future drivers should be simpler. CTRL+F is your friend.

1 - Opening the INF Extract the drivers you want to modify using something like 7zip. (with 7zip installed, just rightclick and press 'Extract to '/File name here') Inside the extracted driver folder open Display.Driver. The 'nvdispi.inf' in that folder is what we need to modify. If you can't find nvdispi.inf, look for 'nvts.inf', 'nvdispwi.inf', or 'nv4dispi.inf' instead. 2 - Your GPU string Search (CTRL+F) for your GPU (for myself it's GTX 470) in the pastebin link below. Copy the line your GPU is listed with (for myself it's NVIDIADEV.06CD = 'NVIDIA GeForce GTX 470') and paste it in the Strings section located toward the bottom of the INF you are modifying.

3 - Adding support for your GPU to the OS Take the device string for your GPU (for myself it's NVIDIADEV.06CD, aka the first part of your GPU string) and search (CTRL+F) for it in the pastebin link below. Copy the line you find it in. (for myself it's%NVIDIADEV.06CD% = Section023, PCI VEN10DE&DEV06CD) Now, in the INF you are modding, paste that line in the section for your OS; (CTRL+F for searching in notepad) -Search 'NTx86.5.1' for XP -Search 'NTamd64.6.0' for Vista -Search 'NTamd64.6.1' for 7 -Search 'NTamd64.6.2' for 8 -Search 'NTamd64.6.3' for 8.1 -Search 'NTamd64.10.0' for 10 -Search 'NTamd64.10.0.14310' for updated 10 Save it and you're done. Launch the 'setup.exe' from the driver folder and it should start perfectly. If you are using Windows 8 or 10, you need to disable Driver Signature Enforcement (you need to do this for any unsigned driver -aka beta drivers- also.). Windows 10 Click the Start Start menu and select Settings. Go to Update and Security.

Go to Recovery. OR Hold down Left Shift while clicking Restart from the Startmenu Under Advanced Startup, Go to Troubleshoot.

Go to Advanced options. Go to Startup Settings. On the Startup Settings screen press 7 or F7 to disable driver signature enforcement.

Once in Windows, continue with driver installer. Now, for future drivers you need to modify, you already should know the string you need put in the string section, and you already know what line to put where to add support for your GPU on your OS (I suggest you keep that information in a txt file) So to summarize: (this is using myself as an example) NVIDIADEV.06CD = 'NVIDIA GeForce GTX 470' goes in the Strings section of new driver%NVIDIADEV.06CD% = Section023, PCI VEN10DE&DEV06CD goes in the Ntamd64.6.1 section of new driver That's it. It's really only copy and pasting two things. When people make modded INFs for drivers (aka leaked/quadro threads), they simply paste all the strings in the strings section, and paste all the device ID's in all three OS's sections. If you cannot find your GPU in the stings or device ID links above, you can always grab your GPU's code from a drive that already supports your GPU. If something needs clarifying or needs more work, let me know.-Pictures of certain things, or really if you tried the guide and it did not work tell me what part confused you. +1 for sticky.

There are at least a few requests for modded.infs each time a new driver is released. This should help a lot of people out. I should add that if you're using Windows 8 you must disable Driver Signature Enforcement if you want to install a Quadro driver. I see that question come up a lot along with the inf requests.

Best Nvidia Sli Drivers

Move the mouse to the right hand side of the screen then: Settings - Change PC settings - General - Advanced Startup/Restart Now - Troubleshoot - Startup Settings - Restart - 7 on Keyboard -OR- Right click bottom left hand side of the screen and select ' Command Prompt (Admin)' and enter ' shutdown -o -r -t 0' Then: Troubleshoot - Startup Settings - Restart - 7 on Keyboard.