Newest Nvidia driver 378.49 causes memory leak

[Kosta]

To my disbelief, Windows10 promptly updated to their 376.54 version and I thought WTF!!!
Is the only way of combating this auto update, to use the process you used where you add the hardware ID's in the GPE to exclude any driver update? I wasn't sure about using this process because of the possibility of screwing it up, especially if you lose the hardware ID's.
Appreciate your advice mate.

Hmm, not sure why it isn't working on your computer.
Might be some reason that policy isn't applying. Check via gpresult /r if local group policy applied recently, most likely with the last reboot. Make sure you have set the setting and THEN rebooted. Also might do gpudpate /force before restart - doesn't hurt.
Then try the DDU process and all that.
Install driver, go to updates and check for windows updates. It shouldn't download the driver.

[tonaz]

BTW for windows 10 HOME users, the only working way is to disable windows update service in services.
This is because HOME can't set group policies.
This implies that you can't DL any other updates, ofcourse.
And first time you reactivate updates and check... Boom, driver autoupdate jumps in.

[Kosta]

BTW for windows 10 HOME users, the only working way is to disable windows update service in services.

Are you sure?
There have been reports of registry settings and also someone said there is a way you can let windows update the driver and then revert, supposedly windows will not ask again to install the update. Of course, not the optimal solution, as updating might bring something that reverting doesn't remove.

[tonaz]

True, sorry.
Btw to back ontopic, for me it is 378.92 + fsSpotlights to make OOM.
Without fsSpotlights it does not OOM.
After a lot of testing.

So the problem FOR ME is FsSpotlights + 378.93 = OOM
378.92 without FsS = Ok
376.33 with FsS = Ok as well.

So it is the combination of two.

[Martyson]

Just info:

Nvidia 378.92 (Clean install, just the driver / no Physx etc.)
No problems with:

Win7-64 PC, GTX 550Ti, FS9.1

Win7-64 PC, GTX 960, FSX Accel, P3D V3.4 HF3, Xplane10

[rubster]

Just tested the latest nvidia drivers 378.92. These drivers also have a memory leak. Tested it setting up the real air turbine duke on a not so heavy airport in Denmark. Left it there for about 1,5 a 2 hours. And memory was drained from -1.5 gig to 0.11 gig. Reverted back to 376.33. Did the same thing and it's stable at -1.76 for 2 hours long.

I have a 10 series gpu btw

[Martyson]

Just tested the latest nvidia drivers 378.92. These drivers also have a memory leak. Tested it setting up the real air turbine duke on a not so heavy airport in Denmark. Left it there for about 1,5 a 2 hours. And memory was drained from -1.5 gig to 0.11 gig. Reverted back to 376.33. Did the same thing and it's stable at -1.76 for 2 hours long.

I have a 10 series gpu btw

Installed Nvidia 376.33
Note: Last time I used this driver was Dec 22, 2016
I installed now just for a test to see if VAS was being used.

Clean driver only install
Win7-64 PC
P3Dv3.4 HF3


KDTW
RAduke
Runway and takeoff VAS test

2492408 VAS ready for takeoff
2462080 VAS departing


VAS usage (small leak) is the same a all previous Nvidia drivers and newer drivers I tested up to 378.92.

[maca11]

Hello,
can 376.33 be installed back if I have already newest windows 10 updates ?
many thanks
JM

[Bluefinn]

Anybody tested 381.65 yet?

[MurisSaab]

Hello,
can 376.33 be installed back if I have already newest windows 10 updates ?
many thanks
JM

Yes, I am running Windows 10 Enterprise 1703 (Creators Update) with Nvidia 376.33

I have disabled the update of the Nvidia drivers via GPO and everything else is updating normally

So far no issues

[tonaz]

i tested 381.65
and IT LOOKS LIKE they fixed the mem leak!!!
At least for me, they works very good.
376.33 was the last version working, so i did my usual test.
First with 376.33: VAS was 1.486mb starting. Passed new york it was 1.270mb stable.
Then with 381.65: VAS was 1.542mb starting. Passed new york it was 1.375mb stable.
So for my system, a better vas usage.
But i hope i am not cheering too fast.

[joefackel]

Did i read your numbers wrong or had you lower VAS with the old driver? ;-)

[tonaz]

correct, but i talked too fast :-\
did another more consistent test and i was with just 40mb vas after taking off, then imminent OOM, naturally.
:-\
meh. the will never fix this.
going back .33

[evaamo]

Sad thing for those of us with 1080TI cards. Going back to .33 isn't an option.

I hope they fix this soon.

cheers
-E

[MurisSaab]

Anybody tested 381.65 yet?

I tested it and it failed for me. Staying with 376.33 for now