NotebookForums.com › Forums › NVIDIA ForceWare & NBF MobileForce Drivers › NBF MobileForce Drivers › NBF MobileForce XP 175.16 (32-Bit/64-Bit)
New Posts  All Forums:Forum Nav:

NBF MobileForce XP 175.16 (32-Bit/64-Bit)

Poll Results: Are you satisfied with this driver and recommend it for other users?

 
  • 66% (12)
    Yes
  • 33% (6)
    No
18 Total Votes  
post #1 of 36
5/17/08 at 8:45pm
Thread Starter 
NBF MobileForce XP 175.16 (32-Bit/64-Bit)
DIRECT DOWNLOAD (32-Bit) DIRECT DOWNLOAD (64-Bit) MIRROR 1 (32-Bit) (NOT AVAILABLE, TO BE ADDED LATER) MIRROR 1 (64-Bit) (NOT AVAILABLE, TO BE ADDED LATER) Operating System: Microsoft Windows 2000/XP 32-Bit/64-Bit Driver Version: 6.14.11.7516 NBF MobileForce Custom INF Tweaks Version: 5.10.110 Driver Date: 05/02/2008 Driver Size (32-Bit): 41,607,835 bytes (39.6MB) MD5 Hash (32-Bit): DF8C337349E33FD42CD9FA0ADFBE3B8E Driver Size (64-Bit): 47,912,947 bytes (45.6MB) MD5 Hash (64-Bit): 197D852B16761807C170778BC9E9A92F Please make sure you compare the MD5 Hash and Driver Size of the file you've downloaded to make sure you are getting a Genuine NBF MobileForce Driver, and not one that has been tampered with! ---Release Notes--- It's been a couple of months since the last release of a MobileForce driver, following our change of pace to only release good, solid drivers, rather than rushing every driver out there into MobileForce "garb". This new driver has recently been made official by NVIDIA for many cards, but as always, we at the MobileForce camp bring them directly to you laptop users. There have been several minor changes to the MobileForce TweakSet, but nothing worth directly mentioning here. However, thanks to the MobileForce BetaCircle's testers, we avoided a huge boo-boo with these drivers that was quickly fixed. Performance seems to be up across the board when compared to 174.31, and users of the "safe" 169.xx series drivers can probably update to this new driver, as it seems to be extremely solid. As always, have some fun, follow the guide for updating your drivers (posted in the NBF MobileForce forum) and report back with your findings!!! ---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. All issues and/or concerns regarding this particular MobileForce driver are to be confined to this thread. Any other topics created regarding issues with this or any other driver will be REMOVED. Please, confine all discussion and feedback to this thread. It makes our job easier, and it makes it easier for others to view feedback on the driver release. ---Supported Video Devices---
Code:
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_0533.1  = "NVIDIA GeForce 7000M / nForce 610M  "
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_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_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_0405.1  = "NVIDIA GeForce 9500M GS  "
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 370M  "
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_G86.DEV_042E.1  = "NVIDIA GeForce 9300M G  "
NVIDIA_G92.DEV_0608.1  = "NVIDIA GeForce 9800M GTX  "
NVIDIA_G92.DEV_0609.1  = "NVIDIA GeForce 8800M GTS  "
NVIDIA_G92.DEV_060C.1  = "NVIDIA GeForce 8800M GTX  "
NVIDIA_G92.DEV_061C.1  = "NVIDIA Quadro FX 3600M  "
NVIDIA_G92.DEV_061E.1  = "NVIDIA Quadro FX 3700M  "
NVIDIA_G94.DEV_062A.1  = "NVIDIA GeForce 9800M GS  "
NVIDIA_G94.DEV_0628.1  = "NVIDIA GeForce 9800M GTS  "
NVIDIA_G96.DEV_0648.1  = "NVIDIA GeForce 9600M GS  "
NVIDIA_G96.DEV_0649.1  = "NVIDIA GeForce 9600M GT  "
NVIDIA_G96.DEV_064A.1  = "NVIDIA GeForce 9700M GS  "
NVIDIA_G96.DEV_064B.1  = "NVIDIA GeForce 9500M G  "
NVIDIA_G96.DEV_064C.1  = "NVIDIA GeForce 9650M GT  "
NVIDIA_G96.DEV_065C.1  = "NVIDIA Quadro FX 770M  "
NVIDIA_G98.DEV_06E8.1  = "NVIDIA GeForce 9300M GS  "
NVIDIA_G98.DEV_06E9.1  = "NVIDIA GeForce 9400M GS  "
NVIDIA_NV11.DEV_0112.1 = "NVIDIA GeForce2 Go   "
NVIDIA_NV17.DEV_0174.1 = "NVIDIA GeForce4 440 Go   "
NVIDIA_NV17.DEV_0175.1 = "NVIDIA GeForce4 420 Go   "
NVIDIA_NV17.DEV_0176.1 = "NVIDIA GeForce4 420 Go 32M  "
NVIDIA_NV17.DEV_0177.1 = "NVIDIA GeForce4 460 Go   "
NVIDIA_NV17.DEV_0179.1 = "NVIDIA GeForce4 440 Go 64M   "
NVIDIA_NV17.DEV_017C.1 = "NVIDIA Quadro4 500 GoGL   "
NVIDIA_NV17.DEV_017D.1 = "NVIDIA GeForce4 410 Go 16M   "
NVIDIA_NV18.DEV_0186.1 = "NVIDIA GeForce4 448 Go   "
NVIDIA_NV18.DEV_0187.1 = "NVIDIA GeForce4 488 Go   "
NVIDIA_NV18.DEV_018D.1 = "NVIDIA GeForce4 448 Go    "
NVIDIA_NV28.DEV_0286.1 = "NVIDIA GeForce4 4200 Go   "
NVIDIA_NV28.DEV_028C.1 = "NVIDIA Quadro4 700 GoGL   "
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_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_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   "
MobileForce Driver Thread Layout v1.30
Reply
Reply
post #2 of 36
5/18/08 at 3:06am
been using the beta for some time now, updated to these public set and so far so good

installed perfectly
very smooth running and IQ excellent, gonna be sticking to these for sometime yet.

and i like your pholisophy on releasing your tweaks to only "good" drivers, it keeps quality insurance to a high standard. And tbh you've chosen a preety darn good driver to tweak on
Reply
Reply
post #3 of 36
5/19/08 at 8:11pm
installed over 169.09 from laptopvideo2go... i was getting freezing problems in WoW ... so far its been cleared up and driver stable. (as of now will post again in a few days) thanks tony
Reply
Reply
post #4 of 36
5/21/08 at 1:18am
This driver is completely borked on my system. The Nvidia driver never actually installs. I tried to install it both in safe mode and in normal mode, and it looks like it's installing, but after the restart, my display adapter isn't detected and there are no indications that any drivers have been installed at all. I'm going back to the 174.31 driver, which worked fine.
Reply
Reply
post #5 of 36
5/21/08 at 4:23am
sounds like you had the same probs i had with the beta, which should've ben fixed...
Reply
Reply
post #6 of 36
5/21/08 at 5:09am
Ironically, when I re-installed the 174.31 version, it said that I was loading an older driver than what was currently in use, which indicates that something loaded, even though there was no Nvidia CP, Windows did not detect any display adapter, the screen resolution couldn't go to default (1680x1050), etc.

Anyway, now I've got the 174.31 version back and everything's fine again.
Reply
Reply
post #7 of 36
5/21/08 at 10:14am
Hmmm - I had a minor issue (similar to DJ's) last night installing in Vista. Only because Vista starting installing VGA drivers faster than I could. So - I uninstalled (agian), did a CC and DC run, rebooted, and started 175.16 install as soon as Windows booted. When on without a hitch from there.

Hopefully get a chance to play some in the next night or two....will post if I encounter any probs.
Reply
Reply
post #8 of 36
5/21/08 at 2:31pm
@ Tony: I tried it again after using Driver Sweeper instead of Driver Cleaner Pro, with the same results. Totally borked.
Reply
Reply
post #9 of 36
5/21/08 at 5:27pm
Thread Starter 
The weirdest part about the whole thing is that you're the only one who's had issues.

Buck tried them as well, and it works fine for him, as it does for me and 4 of my friends, and d0x! and Ganzonomy, etc.

It's got to be something specific with your computer.
Reply
Reply
post #10 of 36
5/21/08 at 6:59pm
try to install via Have Disk Method?
Reply
Reply
post #11 of 36
5/22/08 at 8:57pm
Tony:

Didn't think I'd ever be able to leave your 169.04. Your new driver is purrrrrring in my M1730. Faultless install and no probs with programs (mostly 3D graphics) and temps are as cool as 169.04 or better!

Great job. Many thanks for your return.
Reply
Reply
post #12 of 36
6/3/08 at 6:39am
with this driver, after a while svchost.exe begins to use more and more of the processor,
if I restart the nvidia-service it goes back to (almost) no processor use.

I had this problem once before with another driver and I changed back to the dell driver which didn't have this problem.

if I leave my laptop on for a night it leaps up to 30% processor usage :s

laptop: XPS M1710, cpu: intel core 2 duo T7200 2GHz, gpu: 7900GTX 512mB
Reply
Reply
post #13 of 36
6/3/08 at 6:50am
Quote:
Originally Posted by SyRiNx0 View Post
with this driver, after a while svchost.exe begins to use more and more of the processor,
if I restart the nvidia-service it goes back to (almost) no processor use.

I had this problem once before with another driver and I changed back to the dell driver which didn't have this problem.

if I leave my laptop on for a night it leaps up to 30% processor usage :s

laptop: XPS M1710, cpu: intel core 2 duo T7200 2GHz, gpu: 7900GTX 512mB
Do you also have Dell's Creative HD audio software installed?
Reply
Reply
post #14 of 36
6/3/08 at 7:54am
Quote:
Originally Posted by Buck View Post
Do you also have Dell's Creative HD audio software installed?
yes, is that the problem?
if so, what is the solution
Reply
Reply
post #15 of 36
6/3/08 at 8:04am
Well - I know the exact problem you're talking about. I tracked mine down w/the E1705 by using Process ExplorerXP.

One of the svchost files was eating exactly 50% of my CPU (one core was pegged). After installing Process Explorer, I tracked down the offender....in my case the Creative HD drivers.

I unstalled all of the Creative software, then reinstalled. Everything seemed to work fine after that.

I suggest you track down the offending program similarly. It may or may not be the Creative software package....
Reply
Reply
post #16 of 36
6/3/08 at 9:00am
with process explorer I can find the svchost.exe but what can I do with it?
in properties the only service connected to this is the remote procedure call :s
it can be that it is the wrong one, because now it still is only 3% cpu

but are you sure it is the same one, because mine happens very slowly,
I have restarted the nvidia service a couple of hours ago and still 3%,
and the problem is (temporarily) over when I restart the nvidia service,

so I think that the problem is purely the (mobileforce) nvidia driver,
because it didn't happen when I use the dell driver
Reply
Reply
post #17 of 36
6/3/08 at 10:40am
I used process explorer to sniff out the root. In my case, it was the Creative crap. I then uninstalled/reinstalled drivers (without the HD package).

If it ends up not being Creative drivers in your particular scenario, you will still be able to see what the root cause is. After you find it, you'll be able to determine whether or not it's safe to kill/unload the process (via "services.msc" command).

I had to wait for my CPU to load up (to 50%) before I was able to track down the problem.

http://www.microsoft.com/technet/sys...sexplorer.mspx


Edit: Also make sure you follow Fenuxx's driver install instructions HERE
Reply
Reply
post #18 of 36
6/3/08 at 10:57am
Quote:
Originally Posted by Buck View Post
I used process explorer to sniff out the root. In my case, it was the Creative crap. I then uninstalled/reinstalled drivers (without the HD package).

If it ends up not being Creative drivers in your particular scenario, you will still be able to see what the root cause is. After you find it, you'll be able to determine whether or not it's safe to kill/unload the process (via "services.msc" command).

I had to wait for my CPU to load up (to 50%) before I was able to track down the problem.

http://www.microsoft.com/technet/sys...sexplorer.mspx


Edit: Also make sure you follow Fenuxx's driver install instructions HERE

ok, thnx for the fast answers
I didn't exactly follow the guide but I did run drivercleaner pro after the first reboot
and I was planning to do it exactly like the guide says sometime later
but for now I will let svchost claim more cpu and then I will use process explorer again
so that will be a while because it did +-30% in 12 hours :s and now it is 5-6% :s
Reply
Reply
post #19 of 36
6/3/08 at 11:13am
You're welcome. And FWIW...I've yet to encounter serious issues with any of the full release versions of MobileForce drivers.

The only 'hiccup' I've seen is with Vista's UAC and driver signing....but there are ways around that.
Reply
Reply
post #20 of 36
6/3/08 at 11:49am
Quote:
Originally Posted by Buck View Post
You're welcome. And FWIW...I've yet to encounter serious issues with any of the full release versions of MobileForce drivers.

The only 'hiccup' I've seen is with Vista's UAC and driver signing....but there are ways around that.

that's why I put brackets round "mobileforce" it could entirely nvidia's fault
but I will see later what the fault is with process explorer
Reply
Reply
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: NBF MobileForce Drivers
NotebookForums.com › Forums › NVIDIA ForceWare & NBF MobileForce Drivers › NBF MobileForce Drivers › NBF MobileForce XP 175.16 (32-Bit/64-Bit)