[mobilenvidia]

NVIDIA driver v196.86 for Windows 7/Vista 64bit

Download Driver | INF Modified | PhysX Drivers | Click for DriverAgent |

Driver Information

---

• Released By: Dell Mobile
  
• Driver Version: 196.86
  
• Operating System: Windows 7/Vista 64bit
  
• Driver Date: 2010-02-27 (YYYY-MM-DD)
  
• Driver Size: 78.27MB (MD5: 01e6cec61bfbc0054ce2ca5910b9295b)
  
• MS WHQL Certificate:
  
• Setup Files Included:

Languages (13)

---

German
Spanish
Latin American Spanish
French
Italian
Japanese
Korean
Dutch
Polish
Portuguese Brazilian
Russian
Simplified Chinese
Traditional Chinese

Information Files (1 files supporting 86 models)

---

* nvdm.inf supports 86 models:
[DEV_0407&SUBSYS_01F11028] NVIDIA GeForce 8600M GT
[DEV_0407&SUBSYS_01F21028] NVIDIA GeForce 8600M GT
[DEV_0407&SUBSYS_02281028] NVIDIA GeForce 8600M GT
[DEV_0407&SUBSYS_02291028] NVIDIA GeForce 8600M GT
[DEV_0407&SUBSYS_022E1028] NVIDIA GeForce 8600M GT
[DEV_0409&SUBSYS_019B1028] NVIDIA GeForce 8700M GT
[DEV_0409&SUBSYS_019C1028] NVIDIA GeForce 8700M GT
[DEV_0409&SUBSYS_01F11028] NVIDIA GeForce 8700M GT
[DEV_040D&SUBSYS_019B1028] NVIDIA Quadro FX 1600M
[DEV_0425&SUBSYS_02751028] NVIDIA GeForce 8600M GS
[DEV_0427&SUBSYS_01F11028] NVIDIA GeForce 8400M GS
[DEV_0427&SUBSYS_01F21028] NVIDIA GeForce 8400M GS
[DEV_0427&SUBSYS_01F31028] NVIDIA GeForce 8400M GS
[DEV_0427&SUBSYS_02091028] NVIDIA GeForce 8400M GS
[DEV_0427&SUBSYS_02271028] NVIDIA GeForce 8400M GS
[DEV_0427&SUBSYS_02281028] NVIDIA GeForce 8400M GS
[DEV_0427&SUBSYS_02291028] NVIDIA GeForce 8400M GS
[DEV_0427&SUBSYS_022E1028] NVIDIA GeForce 8400M GS
[DEV_0427&SUBSYS_026F1028] NVIDIA GeForce 8400M GS
[DEV_0427&SUBSYS_02731028] NVIDIA GeForce 8400M GS
[DEV_0427&SUBSYS_02861028] NVIDIA GeForce 8400M GS
[DEV_0427&SUBSYS_02B51028] NVIDIA GeForce 8400M GS
[DEV_0428&SUBSYS_019B1028] NVIDIA GeForce 8400M G
[DEV_0429&SUBSYS_01FE1028] NVIDIA Quadro NVS 140M
[DEV_042B&SUBSYS_01F91028] NVIDIA Quadro NVS 135M
[DEV_042B&SUBSYS_01FE1028] NVIDIA Quadro NVS 135M
[DEV_042D&SUBSYS_01FF1028] NVIDIA Quadro FX 360M
[DEV_042D&SUBSYS_024A1028] NVIDIA Quadro FX 360M
[DEV_042D&SUBSYS_024B1028] NVIDIA Quadro FX 360M
[DEV_0609&SUBSYS_019B1028] NVIDIA GeForce 8800M GTS
[DEV_060A&SUBSYS_02A11028] NVIDIA GeForce GTX 280M
[DEV_060B&SUBSYS_019C1028] NVIDIA GeForce 9800M GT
[DEV_060C&SUBSYS_019C1028] NVIDIA GeForce 8800M GTX
[DEV_060F&SUBSYS_02A11028] NVIDIA GeForce GTX 285M
[DEV_060F&SUBSYS_043A1028] NVIDIA GeForce GTX 285M
[DEV_0617&SUBSYS_019C1028] NVIDIA GeForce 9800M GTX
[DEV_0618&SUBSYS_02A11028] NVIDIA GeForce GTX 260M
[DEV_0618&SUBSYS_02A21028] NVIDIA GeForce GTX 260M
[DEV_061C&SUBSYS_019B1028] NVIDIA Quadro FX 3600M
[DEV_061D&SUBSYS_02EF1028] NVIDIA Quadro FX 2800M
[DEV_061E&SUBSYS_019C1028] NVIDIA Quadro FX 3700M
[DEV_061E&SUBSYS_02511028] NVIDIA Quadro FX 3700M
[DEV_061E&SUBSYS_02EF1028] NVIDIA Quadro FX 3700M
[DEV_061F&SUBSYS_02EF1028] NVIDIA Quadro FX 3800M
[DEV_063A&SUBSYS_019B1028] NVIDIA Quadro FX 2700M
[DEV_063A&SUBSYS_02511028] NVIDIA Quadro FX 2700M
[DEV_063A&SUBSYS_02EF1028] NVIDIA Quadro FX 2700M
[DEV_0648&SUBSYS_02C01028] NVIDIA GeForce 9600M GS
[DEV_0649&SUBSYS_02501028] NVIDIA GeForce 9600M GT
[DEV_065A&SUBSYS_02501028] NVIDIA Quadro FX 1700M
[DEV_065C&SUBSYS_02501028] NVIDIA Quadro FX 770M
[DEV_06E8&SUBSYS_02621028] NVIDIA GeForce 9200M GS
[DEV_06E8&SUBSYS_02711028] NVIDIA GeForce 9200M GS
[DEV_06E9&SUBSYS_02BB1028] NVIDIA GeForce 9300M GS
[DEV_06E9&SUBSYS_02BC1028] NVIDIA GeForce 9300M GS
[DEV_06E9&SUBSYS_02BD1028] NVIDIA GeForce 9300M GS
[DEV_06E9&SUBSYS_02D91028] NVIDIA GeForce 9300M GS
[DEV_06E9&SUBSYS_02DE1028] NVIDIA GeForce 9300M GS
[DEV_06EB&SUBSYS_02331028] NVIDIA Quadro NVS 160M
[DEV_06EB&SUBSYS_024F1028] NVIDIA Quadro NVS 160M
[DEV_06FB&SUBSYS_02341028] NVIDIA Quadro FX 370M
[DEV_0A29&SUBSYS_04421028] NVIDIA GeForce GT 330M
[DEV_0A34&SUBSYS_02A21028] NVIDIA GeForce GT 240M
[DEV_0A3C&SUBSYS_040C1028] NVIDIA Quadro FX 880M
[DEV_0A69&SUBSYS_04181028] NVIDIA GeForce G105M
[DEV_0A6C&SUBSYS_040A1028] NVIDIA NVS 3100M
[DEV_0A6C&SUBSYS_040B1028] NVIDIA NVS 3100M
[DEV_0A75&SUBSYS_043F1028] NVIDIA GeForce 310M
[DEV_0A75&SUBSYS_04401028] NVIDIA GeForce 310M
[DEV_0A75&SUBSYS_04411028] NVIDIA GeForce 310M
[DEV_0CBC&SUBSYS_040C1028] NVIDIA Quadro FX 1800M
[DEV_0860&SUBSYS_02711028] NVIDIA GeForce 9400
[DEV_0862&SUBSYS_02711028] NVIDIA GeForce 9400M G
[DEV_0862&SUBSYS_02A11028] NVIDIA GeForce 9400M G
[DEV_0866&SUBSYS_02711028] NVIDIA GeForce 9400M G
[DEV_0866&SUBSYS_02BA1028] NVIDIA GeForce 9400M G
[DEV_0867&SUBSYS_02711028] NVIDIA GeForce 9400
[DEV_0868&SUBSYS_02711028] NVIDIA nForce 760i SLI
[DEV_0870&SUBSYS_02711028] NVIDIA GeForce 9400M
[DEV_0407&SUBSYS_019C1028] NVIDIA GeForce 8600M GT
[DEV_0427&SUBSYS_020A1028] NVIDIA GeForce 8400M GS
[DEV_0428&SUBSYS_01F11028] NVIDIA GeForce 8400M G
[DEV_0428&SUBSYS_01F21028] NVIDIA GeForce 8400M G
[DEV_0428&SUBSYS_020A1028] NVIDIA GeForce 8400M G
[DEV_042B&SUBSYS_019C1028] NVIDIA Quadro NVS 135M
[DEV_042D&SUBSYS_019B1028] NVIDIA Quadro FX 360M

Support and Disclaimer

---

Please post any comments, suggestions, questions and other information related to this driver in this thread
Please make use of the Quickstart Guide for installation, the Forums Search function and Frequently Asked Questions before asking any questions.
If you still have a general question and/or problem that is not related with this driver, please post in the Support section.

All NVIDIA drivers hosted at LaptopVideo2Go.com come as a maximum compressed self-extracting 7-ZIP archive for your convenience.
Additionally, reduce the size of your installation by using NVLiTE to rip out unnecessary languages and miscellaneous files without losing any driver features.
Driver size and MD5 numbers may not be accurate due to the driver being repackaged and post not updated.

via if you find what we do useful and would like to help us pay for hosting these files into the future.
LaptopVideo2Go driver thread v2.0.0

[FadeToBlack]

Thank you.
Hope it works.

[FadeToBlack]

It worked for me, though I have only once restarted (the one after the install).
It seems not to run high temps.

[kane3162]

"""Other differences
196.75 includes files needed for Optimus and a slightly newer control panel.
196.86 does not include these files."""

Nautis1100 said that

so i have a few questions!, is it possible to addin Oprimus and the newer cpanel?

additionally, I have stuck with a 186 driver because of the destroyed 2D acceleration (windows slide show anyone?) seemingly introduced starting with 191.xx and i think continuing on to the latest releases (what someone else had posted here on the forums in each release i was looking at switching to)

any comments on any of this?

[samozen]

i have just installed this driver on vaio vgn-ar71m and i noticed that temperature is reduced with 186.82=55-60 c,but with this one =52-55 c,and it work fine without any blue scrren or any error.so thanks mobilenvidia for this realise....

[hovercraftdriver]

On the news post, Galdere wote "I am very impressed with this driver. I was having to use an older one because of stuttering on some games. That problem has gone with these, FPS are up and everything seem that little bit snappier with it.

I did run into problem which requires a change before installing. I was experiencing a BSOD on boot every other time using the previous driver's INF which was annoying, so I edited the original inf instead of using the replacement and changed the hardware ID number to my own. There has been no problem since.

It is fairly simple to do this as long as your GPU is included already (see the link above) and well worth it IMO. If you are already using a Dell or Alienware then you don't need to do any of this it should just work. Extract the driver and open up the nvdm.inf file in the installation directory. Scroll to bottom and find out the device ID for your card, for example mine is "060C" for my 8800M GTX. Scroll up near the top and find the other section that has this, for example "%NVIDIA_DEV.060C.01% = Section008, PCI\VEN_10DE&DEV_060C&SUBSYS_019C1028". Next you need to open up device manager and go into the properties for your display device. Go into the details tab and select Hardware Ids. Note the number after "SUBSYS_", for example mine is "05731558". Finally replace the part in the INF that for me is the "019C1028" to what is for me "05731558". Save the file and run the setup and you should be in business.

Also this installed a small Dell "hotkey driver" in the start up so I just removed that. You can use many progs to do this, for example CCleaner." End


Read his post over at Notebookreview, but thought I would post here. I wasn't getting constant BSOD, just the initial one on install. However, performance sucked in games (dropping FPS) and 3Dmark06(lost 450 points) from previous driver, which was the HP one recently posted. So I made the change to the stock .inf, and everything is rocking. FPS and 3Dmark score back up, temps fine.

Which leads me to my point. ALL OF THE 196.xx drivers have given me issues, and I'm beginning to believe that LV2Go .inf is the culprit. Not due to poor writing, but there is something in the original driver that is not being accounted for in the current series of Pieter's .infs. Or members hybrid versions of the same. Problem is, it's about 50/50 getting errors from following the previous driver posts. If Pieter's rig isn't having problems, well you can't troubleshoot if it ain't broken, know what I mean? I could be wrong, it's only a theory, but the HP driver and the Dell driver loaded fine on my HP HDX.

This is not a bash post, because I truly appreciate all the work done on this site. Only mentioned to raise awareness to a potential issue. Like I said, don't even know if he can fix it if it isn't happening to him (or whoever the particular .inf author is). I just know I don't have the know-how to sort through it. I know how to add my GPU to a given .inf, that's about it.

This post has been edited by hovercraftdriver: 06 March 2010 - 11:08 AM

[Jaitsu]

Hovercraftdriver: I just registered to thank you because I cannot thank you enough. That simple explanation of how to add my card to the INF manually just saved me hours of hair-tearing.

It looks like you're right: The LV2Go .inf seems to be the source of the problem; I had the same exact problem as you with my ASUS G72GX: BSOD during install, bad performance after, but after manually editing the .inf everything's running smooth. It probably just needs to be rewritten to the new inf format, which is hopefully more a matter of "format" than "actually having to muck around in the INF to add each card" and thus not much work.

[hovercraftdriver]

Jaitsu, on 06 March 2010 - 09:15 AM, said:

Hovercraftdriver: I just registered to thank you because I cannot thank you enough. That simple explanation of how to add my card to the INF manually just saved me hours of hair-tearing.

It looks like you're right: The LV2Go .inf seems to be the source of the problem; I had the same exact problem as you with my ASUS G72GX: BSOD during install, bad performance after, but after manually editing the .inf everything's running smooth. It probably just needs to be rewritten to the new inf format, which is hopefully more a matter of "format" than "actually having to muck around in the INF to add each card" and thus not much work.

Thanks and you're welcome, but not sure if you can tell where Galdere's quote ends and mine starts. It's his idea and he gets the credit. Glad it worked though if I was able to bring attention to it. Some people don't know or read when there are two posts on the same subject on this site some times. Original news post and when Mobilenvidia separates the various file downloads in the driver forums. Sometimes important stuff gets lost between the two threads. Cheers

[Galdere]

Thanks Hovercraftdriver.

I forget if something is of use to not just post it in the news threads. If the separate ones have been made it can mean doing it an extra four times.

All amazing explanations by me are officially from Galdere@LV2G and not any other website. Anything else I take little responsibility for.

I'm sure Pieter will be looking into this ASAP.

Welcome to the forum Jaitsu.

[HisDivineOrder]

hovercraftdriver, on 06 March 2010 - 08:27 AM, said:

On the news post, Galdere wote "I am very impressed with this driver. I was having to use an older one because of stuttering on some games. That problem has gone with these, FPS are up and everything seem that little bit snappier with it.

I did run into problem which requires a change before installing. I was experiencing a BSOD on boot every other time using the previous driver's INF which was annoying, so I edited the original inf instead of using the replacement and changed the hardware ID number to my own. There has been no problem since.

It is fairly simple to do this as long as your GPU is included already (see the link above) and well worth it IMO. If you are already using a Dell or Alienware then you don't need to do any of this it should just work. Extract the driver and open up the nvdm.inf file in the installation directory. Scroll to bottom and find out the device ID for your card, for example mine is "060C" for my 8800M GTX. Scroll up near the top and find the other section that has this, for example "%NVIDIA_DEV.060C.01% = Section008, PCI\VEN_10DE&DEV_060C&SUBSYS_019C1028". Next you need to open up device manager and go into the properties for your display device. Go into the details tab and select Hardware Ids. Note the number after "SUBSYS_", for example mine is "05731558". Finally replace the part in the INF that for me is the "019C1028" to what is for me "05731558". Save the file and run the setup and you should be in business.

Also this installed a small Dell "hotkey driver" in the start up so I just removed that. You can use many progs to do this, for example CCleaner." End


Read his post over at Notebookreview, but thought I would post here. I wasn't getting constant BSOD, just the initial one on install. However, performance sucked in games (dropping FPS) and 3Dmark06(lost 450 points) from previous driver, which was the HP one recently posted. So I made the change to the stock .inf, and everything is rocking. FPS and 3Dmark score back up, temps fine.

Which leads me to my point. ALL OF THE 196.xx drivers have given me issues, and I'm beginning to believe that LV2Go .inf is the culprit. Not due to poor writing, but there is something in the original driver that is not being accounted for in the current series of Pieter's .infs. Or members hybrid versions of the same. Problem is, it's about 50/50 getting errors from following the previous driver posts. If Pieter's rig isn't having problems, well you can't troubleshoot if it ain't broken, know what I mean? I could be wrong, it's only a theory, but the HP driver and the Dell driver loaded fine on my HP HDX.

This is not a bash post, because I truly appreciate all the work done on this site. Only mentioned to raise awareness to a potential issue. Like I said, don't even know if he can fix it if it isn't happening to him (or whoever the particular .inf author is). I just know I don't have the know-how to sort through it. I know how to add my GPU to a given .inf, that's about it.

Thanks for the info! Based on what you provided, I started comparing the different inf files that I've used (ie., nvam.inf, nv_disp.inf, nvdm.inf, nv_opencl.inf, etc). Unfortunately, the provided Dell (nvdm.inf) did not include my GPU (9800GS), so I considered copying and pasting the info line of my device from one of my older inf's into this one. Yet that seemed like it would not work because of how "Section"'s seem to work (sections seem to suggest where the driver should derive its installation procedure.

Anyways!

So I compared the inf file from the 195 WHQL notebook drivers (the last complete notebook WHQL drivers from nvidia) to the inf included with these Dell and they both seemed the same, except for the sections (and the proper ID's). So I used that inf (nvam.inf) and renamed it to nvdm.inf.

Why not just use the inf from lv2go? Because there seem to be things in it that are not in either the nVidia-created Official notebook WHQL driver OR the Dell-provided nvdm.inf. Specifically, there is something called, "Mobile Tweaks" near the end of the document (before the device ID's) that do not show up in the official inf's. I was reluctant to just delete that section because I don't know if he's using that to make up for something he did earlier in the file. I couldn't see any differences in the other parts of the file. Also, it appears that the official inf's split the installation procedures between a Win Vista version and a Windows 7 version. In the modified inf from lv2go, it appears the installation procedure is being called from the same "section."

Because of this, I concluded that if there IS something causing this driver not to work properly with the modified inf, then the inf nVidia's provided with its "notebook drivers" should work. I tried it, it seems to.

I love this site, I hope what I've provided helps in some way and, if it doesn't, oh well!

Thanks for everything you guys do here!

PS:

To use the official nvidia inf, I had to throw in a copy of the HD audio driver installation and PhysX installation executables. For mine, I used the latest from the drivers I had on hand.

So far, so good...

[Galdere]

Welcome to the forum HisDivineOrder.

Pieter will probably want to post about the differences between this driver's inf, generic nvidia infs and his own. He can do so far better than I so I won't even attempt to.

You do say though that Pieter's inf calls vista and win7 installations from the same section. It doesn't, they all work in the same way as far as I know that [NVIDIA.Mfg.NTamd64.6.0] is vista and [NVIDIA.Mfg.NTamd64.6.1] is win7. The sectioning is where each gpu is sent to call different settings from.

Glad you got sorted. Personally, because of the incompatibility with the LV2G inf and this, I chose to edit the existing one rather than what you've done, but if it works that's great. You could however had probably have done this:

Under [NVIDIA_SetA_Devices.NTamd64.6.1] add the line %NVIDIA_DEV.062B.01% = Section008, PCI\VEN_062B&DEV_060C&SUBSYS_********. At the end put your hardware id instead of the *s. Then under NVIDIA_A = "NVIDIA" put NVIDIA_DEV.062B.01 = "NVIDIA GeForce 9800M GS".

[mobilenvidia]

So calling 'Section008' fixes the problem ?

I'll have a look at section008 if it is.
I cannot really start to add OEM specific tweaks as it will break other setups.
The modded INF tries to cater for as many folk as possible, but won't work on all setups due to OEM specifics.

Let hope we can get this sorted and the modded INF updated with a fix.

[HisDivineOrder]

Galdere, on 06 March 2010 - 06:41 PM, said:

Welcome to the forum HisDivineOrder.

Pieter will probably want to post about the differences between this driver's inf, generic nvidia infs and his own. He can do so far better than I so I won't even attempt to.

You do say though that Pieter's inf calls vista and win7 installations from the same section. It doesn't, they all work in the same way as far as I know that [NVIDIA.Mfg.NTamd64.6.0] is vista and [NVIDIA.Mfg.NTamd64.6.1] is win7. The sectioning is where each gpu is sent to call different settings from.

Glad you got sorted. Personally, because of the incompatibility with the LV2G inf and this, I chose to edit the existing one rather than what you've done, but if it works that's great. You could however had probably have done this:

Under [NVIDIA_SetA_Devices.NTamd64.6.1] add the line %NVIDIA_DEV.062B.01% = Section008, PCI\VEN_062B&DEV_060C&SUBSYS_********. At the end put your hardware id instead of the *s. Then under NVIDIA_A = "NVIDIA" put NVIDIA_DEV.062B.01 = "NVIDIA GeForce 9800M GS".

Thanks for the welcome!

Like I said, I was just fumbling my way through the whole thing. I am keeping an eye on my temps to make sure nothing "goes wrong," that I can fix or catch, but definitely if something breaks, I'll try it that way next.

When my device was not explicitly listed, I was not confident in my ability to read which section I should be referencing (or understand why Win Vista and Win 7 were listed in different sections in the file even though I thought the same thing ("Why when Win Vista and Win 7 are so close and a Vista install should work in 7?"). At least, that was my understanding!

You guys are the best at what you do, though, I thought others might find it useful if they are not able to find their own device in the listing and they had the older 195.xx WHQL drivers still around.

Also, not to overstate it, but thanks Pieter, your inf files have made being a laptop gamer much easier.

[mobilenvidia]

Attached is an INF to test for those with BSOD's at install.

Not sure how far ranging the problems are.
Let me know you get on.

Attached File(s)

•  nvdm.zip (18.88K)
  Number of downloads: 262

[kennydied23]

Hovercraftdriver, you have my thanks. no BSODs at all so far with my gtx 260m. Once again, I thank you. One love, me brada.

[Nautis1100]

hovercraftdriver, on 06 March 2010 - 08:27 AM, said:

Which leads me to my point. ALL OF THE 196.xx drivers have given me issues, and I'm beginning to believe that LV2Go .inf is the culprit. Not due to poor writing, but there is something in the original driver that is not being accounted for in the current series of Pieter's .infs. Or members hybrid versions of the same. Problem is, it's about 50/50 getting errors from following the previous driver posts. If Pieter's rig isn't having problems, well you can't troubleshoot if it ain't broken, know what I mean? I could be wrong, it's only a theory, but the HP driver and the Dell driver loaded fine on my HP HDX.

This is not a bash post, because I truly appreciate all the work done on this site. Only mentioned to raise awareness to a potential issue. Like I said, don't even know if he can fix it if it isn't happening to him (or whoever the particular .inf author is). I just know I don't have the know-how to sort through it. I know how to add my GPU to a given .inf, that's about it.

Yeah this is one of the extreme complications with modding to support a vast majority of GPUs like Pieter is. There really is no way of testing all potential GPUs or computer configurations with each release. This means if there is complications like the ones you are running into its great to hear your issues and if you could help figure out any issues. Modding IMHO is (or at least should be) a community effort as much as possible. My guess at the issue is rather than something not being included that there is a configuration setting in Pieters INF that could be triggering the BSOD with your GPU or PC configuration.

If you can let me know what brand, model, and GPU your notebook uses/is along with pointing me to the latest "official" working video driver (non LV2G) for your notebook/gpu I can help y'all figure this out.