New Posts  All Forums:Forum Nav:

NBF MobileForce VS 156.65 M6

post #1 of 13
10/12/07 at 12:09pm
Thread Starter 
NBF MobileForce VS 156.65 M6 32/64-Bit
DIRECT DOWNLOAD (32-Bit) (NOT AVAILABLE) DIRECT DOWNLOAD (64-Bit) (NOT AVAILABLE) MIRROR 1 (32-Bit) (NOT AVAILABLE) MIRROR 1 (64-Bit) (NOT AVAILABLE) Operating System: Microsoft Windows Vista 32/64-Bit Driver Version: 6.14.11.5665 NBF MobileForce Custom INF Tweaks Version: 6.03.45 Driver Date: 09/19/2007 Driver Size (32-Bit): 33,123,749 bytes MD5 Hash (32-Bit): 2F1B21CCB47C8A42BA2F8BFB6833AF25 Driver Size (64-Bit): 40,038,565 bytes MD5 Hash (64-Bit): 53DEED3DB31B75A0D81697A027BC963A Please make sure you compare the MD5 Hash of the file you're downloading to make sure you are getting a Genuine MobileForce Driver, and not one that has been tampered with! ---Release Notes--- Here we have something of an anomaly in the surge of ForceWare drivers released, one that actually is a true MOBILE driver. This driver natively supported many of the popular mobile GPUs, but with the MobileForce version, supports all mobile devices from the GeForce FX Go-Series and upward, including Quadro FX products. This driver, in the testing done by the newly-reformed MobileForce BetaCircle, consisting of several people with different hardware configurations and OSes, found this driver to be pretty stable and providing solid performance. Unfortunately, this driver, while a mobile driver, still does not have the PowerMizer Control Panel. However, in our testing, it was evident that PowerMizer works, it just can't be configured with the NVIDIA Control Panel. However, as in all MobileForce drivers, we've included the best "all-around" PowerMizer tweaks that should work decently for everyone. On behalf of the rest of the MobileForce Team, including the BetaCircle, we'd like to thank NotebookForums.com for giving us a new home, and an awesome community to work with! As always, have fun, and report back! ---Other Information--- If you are updating your driver, please follow the directions in THIS THREAD. If you don't use follow these directions, and whine about problems with the driver not working properly, we're going to ask you to use follow these directions anyways, so please, update your driver properly . . . We will thank you later. Please post RESPONSIBLY!!! We will answer your question as soon as possible. ---Supported Video Devices---
Code:
NVIDIA_C51.DEV_0243.1  = "NVIDIA C51"
NVIDIA_C51.DEV_0244.1  = "NVIDIA GeForce Go 6150"
NVIDIA_C51.DEV_0247.1  = "NVIDIA GeForce Go 6100"
NVIDIA_C67.DEV_0530.1  = "NVIDIA GeForce 7190M / nForce 650M"
NVIDIA_C67.DEV_0531.1  = "NVIDIA GeForce 7150M / nForce 630M"
NVIDIA_C67.DEV_0532.1  = "NVIDIA MCP67M"
NVIDIA_C67.DEV_0533.1  = "NVIDIA GeForce 7000M / nForce 610M"
NVIDIA_C67.DEV_053F.1  = "NVIDIA MCP67M "
NVIDIA_G70.DEV_0098.1  = "NVIDIA GeForce Go 7800"
NVIDIA_G70.DEV_0099.1  = "NVIDIA GeForce Go 7800 GTX"
NVIDIA_G71.DEV_0297.1  = "NVIDIA GeForce Go 7950 GTX"
NVIDIA_G71.DEV_0298.1  = "NVIDIA GeForce Go 7900 GS"
NVIDIA_G71.DEV_0299.1  = "NVIDIA GeForce Go 7900 GTX"
NVIDIA_G71.DEV_029A.1  = "NVIDIA Quadro FX 2500M"
NVIDIA_G71.DEV_029B.1  = "NVIDIA Quadro FX 1500M"
NVIDIA_G71.DEV_029C.1  = "NVIDIA G71GLM"
NVIDIA_G71.DEV_029D.1  = "NVIDIA Quadro FX 3500M"
NVIDIA_G72.DEV_01D4.1  = "NVIDIA GeForce Go 7350"
NVIDIA_G72.DEV_01D6.1  = "NVIDIA GeForce Go 7200"
NVIDIA_G72.DEV_01D7.1  = "NVIDIA GeForce Go 7300"
NVIDIA_G72.DEV_01D8.1  = "NVIDIA GeForce Go 7400"
NVIDIA_G72.DEV_01D9.1  = "NVIDIA GeForce Go 7450"
NVIDIA_G72.DEV_01DA.1  = "NVIDIA Quadro NVS 110M"
NVIDIA_G72.DEV_01DB.1  = "NVIDIA Quadro NVS 120M"
NVIDIA_G72.DEV_01DC.1  = "NVIDIA Quadro FX 350M"
NVIDIA_G73.DEV_038B.1  = "NVIDIA G73M-X"
NVIDIA_G73.DEV_0397.1  = "NVIDIA GeForce Go 7700"
NVIDIA_G73.DEV_0398.1  = "NVIDIA GeForce Go 7600"
NVIDIA_G73.DEV_0399.1  = "NVIDIA GeForce Go 7600 GT"
NVIDIA_G73.DEV_039A.1  = "NVIDIA Quadro NVS 300M"
NVIDIA_G73.DEV_039B.1  = "NVIDIA GeForce Go 7900 SE"
NVIDIA_G73.DEV_039C.1  = "NVIDIA Quadro FX 550M"
NVIDIA_G84.DEV_0407.1  = "NVIDIA GeForce 8600M GT"
NVIDIA_G84.DEV_0408.1  = "NVIDIA GeForce 8600M GTS"
NVIDIA_G84.DEV_0409.1  = "NVIDIA GeForce 8700M GT"
NVIDIA_G84.DEV_040A.1  = "NVIDIA Quadro NVS 310M"
NVIDIA_G84.DEV_040B.1  = "NVIDIA Quadro NVS 320M"
NVIDIA_G84.DEV_040C.1  = "NVIDIA Quadro FX 570M"
NVIDIA_G84.DEV_040D.1  = "NVIDIA Quadro FX 1600M"
NVIDIA_G86.DEV_0425.1  = "NVIDIA GeForce 8600M GS"
NVIDIA_G86.DEV_0426.1  = "NVIDIA GeForce 8400M GT"
NVIDIA_G86.DEV_0427.1  = "NVIDIA GeForce 8400M GS"
NVIDIA_G86.DEV_0428.1  = "NVIDIA GeForce 8400M G"
NVIDIA_G86.DEV_0429.1  = "NVIDIA Quadro NVS 140M"
NVIDIA_G86.DEV_042A.1  = "NVIDIA Quadro NVS 130M"
NVIDIA_G86.DEV_042B.1  = "NVIDIA Quadro NVS 135M"
NVIDIA_G86.DEV_042D.1  = "NVIDIA Quadro FX 360M"
NVIDIA_NV31.DEV_0316.1 = "NVIDIA NV31M "
NVIDIA_NV31.DEV_0317.1 = "NVIDIA NV31M Pro "
NVIDIA_NV31.DEV_031A.1 = "NVIDIA GeForce FX Go 5600 "
NVIDIA_NV31.DEV_031B.1 = "NVIDIA GeForce FX Go 5650 "
NVIDIA_NV31.DEV_031C.1 = "NVIDIA Quadro FX Go 700 "
NVIDIA_NV31.DEV_031D.1 = "NVIDIA NV31GLM "
NVIDIA_NV31.DEV_031E.1 = "NVIDIA NV31GLM Pro"
NVIDIA_NV31.DEV_031F.1 = "NVIDIA NV31GLM Pro "
NVIDIA_NV34.DEV_0324.1 = "NVIDIA GeForce FX Go 5200 64MB"
NVIDIA_NV34.DEV_0325.1 = "NVIDIA GeForce FX Go 5250/5500 "
NVIDIA_NV34.DEV_0328.1 = "NVIDIA GeForce FX Go 5200 32/64M "
NVIDIA_NV34.DEV_032C.1 = "NVIDIA GeForce FX Go 53x0 "
NVIDIA_NV34.DEV_032D.1 = "NVIDIA GeForce FX Go 5100 "
NVIDIA_NV36.DEV_0347.1 = "NVIDIA GeForce FX Go 5700 "
NVIDIA_NV36.DEV_0348.1 = "NVIDIA GeForce FX Go 5700  "
NVIDIA_NV36.DEV_0349.1 = "NVIDIA NV36M Pro "
NVIDIA_NV36.DEV_034B.1 = "NVIDIA NV36MAP "
NVIDIA_NV36.DEV_034C.1 = "NVIDIA Quadro FX Go 1000 "
NVIDIA_NV41.DEV_00C8.1 = "NVIDIA GeForce Go 6800"
NVIDIA_NV41.DEV_00C9.1 = "NVIDIA GeForce Go 6800 Ultra"
NVIDIA_NV41.DEV_00CC.1 = "NVIDIA Quadro FX Go 1400 "
NVIDIA_NV43.DEV_0144.1 = "NVIDIA GeForce Go 6600"
NVIDIA_NV43.DEV_0146.1 = "NVIDIA GeForce Go 6600 TE/6200 TE"
NVIDIA_NV43.DEV_0148.1 = "NVIDIA GeForce Go 6600 "
NVIDIA_NV43.DEV_0149.1 = "NVIDIA GeForce Go 6600 GT"
NVIDIA_NV44.DEV_0164.1 = "NVIDIA GeForce Go 6200"
NVIDIA_NV44.DEV_0166.1 = "NVIDIA GeForce Go 6400"
NVIDIA_NV44.DEV_0167.1 = "NVIDIA GeForce Go 6200 "
NVIDIA_NV44.DEV_0168.1 = "NVIDIA GeForce Go 6400 "
NVIDIA_NV44.DEV_016B.1 = "NVIDIA NV44GLM"
NVIDIA_NV44.DEV_016C.1 = "NVIDIA NV44GLM "
NVIDIA_NV44.DEV_016D.1 = "NVIDIA NV44GLM  "
NVIDIA_NV44.DEV_0228.1 = "NVIDIA NV44M"
MobileForce Driver Thread Layout v1.10
Reply
Reply
post #2 of 13
10/12/07 at 3:17pm
THANK YOU!

Can't wait to install
Reply
Reply
post #3 of 13
10/13/07 at 3:36am
Hmm, I may be mistaken but weren't these supposed to have powermizer settings for vista?

I ask because I just installed these to test and there is still NO powermizer options.

TIA

D.
Reply
Reply
post #4 of 13
10/13/07 at 5:21am
Thread Starter 
Quote:
Originally Posted by NBF MobileForce VS 156.65 M6 Release Notes
"Unfortunately, this driver, while a mobile driver, still does not have the PowerMizer Control Panel. However, in our testing, it was evident that PowerMizer works, it just can't be configured with the NVIDIA Control Panel."
PowerMizer is there......
Reply
Reply
post #5 of 13
10/13/07 at 5:28am
Ok, missed that in the release notes.
I have ati tool running and it says that the card never downclocks from default high power 3d settings (ie... 500core600mem on a 2500M) that and not seeing the settings in the control panel is what makes me wonder about powermizer.
I also checked with RivaTuner 2.05 and the clocks havn't changed, nor the vid.

I will do some more monitoring/testing and see what happens with the clocks.

D.
Reply
Reply
post #6 of 13
10/13/07 at 9:28am
Thanks for the drivers! will try them later tonight.

But before that, the driver sizes and MD5 hash don't match with the files from the mirror, instead they are identical to the ones for 163.76 XP.

I'm sure it's just a copy/paste mistake but just in case if the files have been tampered with.
Reply
Reply
post #7 of 13
10/14/07 at 2:54am
Ok, just my results.
These will NOT change from default 3D performance settings.
ie... there is no low power 3D or 2D.
This is really bad on battery as I am running in full performance mode and this cuts my battery life in half.

As for performance, they seem to do pretty well... but no better than previous releases which would at least do some type of clock speed changing.

I also reinstalled these drivers 5x just to be sure.

OH, and as the previous poster mentioned... the MD5 checksums don't match.
D.
Reply
Reply
post #8 of 13
10/14/07 at 3:05am
Thread Starter 
OK, fixed the MD5 hashes and the size of the drivers. You're right, it was a copy/paste error... D'OH!



You're the first one to have noticed that the power states don't change Debaucher. There was testing done in the MobileForce BetaCircle (our Beta Testers) and we did confirm that PowerMizer works. It is entirely possible that it could be something to do with your computer. The fact that it doesn't change states at ALL with these drivers tips me off to that. With ALL of the newer drivers, including the 163.75 I also released, there IS PowerMizer activity, just with these, there are 3 states active instead of the two (full power, and low power) in most other drivers.

It may be asking alot, and its entirely up to you if you want to give it a try, but see if reinstalling Windows Vista has any effect on the PowerMizer states or not.
Reply
Reply
post #9 of 13
10/14/07 at 4:50am
Well, I know that powemizer is functional on my computer (as I tried 156.66 from LV2GO) but with that driver once it goes into 2D mode, I get screen corruption (3D performance and 3D low power are fine).
SO... I guess it could either be a driver problem or a problem with my install.

If I get the bug-in-bonnet symptoms tonight, I may just give a reinstall a shot (have to wait until the little one is in bed) but I am not looking forward to that. (I usually just redo a backup image I have saved on my external HD... but would have to start from scratch to rule anything else out).

Will get back to you with my results.

D.
Reply
Reply
post #10 of 13
10/15/07 at 4:13am
Well, did a complete reinstall and still doesn't work with this driver.
I am now using 163.75 from LV2GO and with a few inf tweaks I am able to get powermizer to work correctly with vista but without the entry in nvcontrol panel.
(You can check out LV2GO home page and the resulting forum post for more info if you are interested)

D.
Reply
Reply
post #11 of 13
10/25/07 at 3:55am
I used the 156.65, 156.66, and 156.73 drivers off of laptopvideo2go and ran into overheating with all of them. Less than an hour of Team Fortress 2 or Portal is sufficient to make my laptop shut down; the latest Valve games seem to run my 7800 GTX Go hot.

So, if your laptop shuts down and tells you it overheated when you boot back up, that's why. i9kfangui reported my max GPU temp was at 112 C when I alt-tabbed once. Dell should throw us 7800 users an update here.

The 84.63 and 84.69 drivers do not do this, but they have flashing textures in Half-Life 2: Episode 2 and seem to hitch randomly for some reason. They often hitch when I turn the flashlight on, which is very annoying.

The 156 drivers fix these problems and definitely run Bioshock smoother too, so it's really a shame they cause overheating.
Reply
Reply
post #12 of 13
10/25/07 at 5:32am
Thread Starter 
Have you tried 163.75 at all?

On another point, drivers usually don't cause that huge of a change in temperatures. You should clean out the laptop's air vents if you haven't already. There could be another issue here besides the drivers themselves.
Reply
Reply
post #13 of 13
10/25/07 at 8:40pm
Quote:
Originally Posted by GeForceTony View Post
Have you tried 163.75 at all? On another point, drivers usually don't cause that huge of a change in temperatures. You should clean out the laptop's air vents if you haven't already. There could be another issue here besides the drivers themselves.
I'm aware that many factors influence temperature. My air vents are good to go though. My conclusion that these drivers run hotter is based on a sequence of driver installs including 156.xx, 84.xx, 97.92, and 163.xx drivers. All of these driver installs occurred over the past week. Here's what I found, for the benefit of others. Method for changing drivers. 1. Uninstall using Add/Remove. Reboot to Safe Mode. 2. In Safe Mode, run Driver Cleaner Pro 1.5 Build 14 with the NVIDIA filter. Reboot to regular windows. 3. Install the new driver, using the LV2G .inf for versions 84.63, 97.92, 163.71, and 163.76. Reboot to regular windows. My computer only shut down due to overheating when I had 156.xx drivers installed. In addition, i9kfangui reported a max GPU temperature 5-7 C warmer for the 156.xx drivers compared to versions 84.63 and 84.69. 84.63- Flashing textures and random hitching in HL2: Episode 2. A hitch often occurs whenever I turn the flashlight on. 84.69 (Dell's latest for the M170 with a 7800 GTX Go)- Desktop icons and windows are moved/fit to 800x600 equivalent space on my desktop when I close and open my laptop lid or when my screen turns off for power saving. Flashing textures and random hitching in HL2: Episode 2. A hitch often occurs whenever I turn the flashlight on. 156.65, 66, 73- HL2: Episode 2, Team Fortress 2, and Portal all cause my laptop to shut down due to overheating. The hitching and flashing texture issues are solved, and the performance was technically 1 frame per second less than the 84.xx drivers. The .inf these drivers come with lacks support for 1440x900, 1680x1050, and 1600x1000 resolutions. Changing the NV_MODES line to the LV2G .inf's solved that issue. Finally, with these drivers I also noticed the Bioshock demo ran smoother. I don't know if it's related to the hitching issue or whether I was seeing more frames per second. The Unreal Tournament 3 MP beta did not run the temperature up much more than 90 C, and the Crysis MP beta did not cause overheating. 97.92 - HL2: Episode runs 10% slower. I did not test for the flashing textures or temperature since the 10% already eliminates this driver as a choice for me. 163.71 and 163.76 - HL2: Episode runs 10% slower. I did not test for the flashing textures or temperature. Team Fortress 2 also ran noticeably slower (which led me to test it in more detail using Episode 2). The NVidia Control Panel crashes any way I try to access it. The taskbar icon provides access to some options and does not crash. When my Windows desktop boots up, I experience 5-10 second periods where my laptop does not respond to anything, including mouse movements and keystrokes. That's all I've learned so far. I'm currently using the 84.63 driver, but I don't plan on playing HL2: Episode 2 until I find better drivers, or it gets cold indoors so I can switch to a 156 series driver without overheating. I hope Dell doesn't think they're off the hook for driver updates, they'll be hearing from me soon if I don't find a suitable driver.
Reply
Reply
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: NBF MobileForce Drivers