Newest Nvidia driver 378.49 causes memory leak

[kikigey89]

Could also confirm this with 378.49, their latest official release and with the hotfix (so the hotfix did not fix my issue).
376.33 solved it. Using a GTX 970 BTW. Thanks!

[Dumpcore]

I confirm the same problem. Tha latest Nvidia driver (378.66) causes OOMs with Prepar3D 3.4 HF3 in long flights. I have reverted back to 376.33 driver, and the problem have been fixed. I am not using very hungry addons, and haven't maxed out the Prepar3D graphical settings.

My graphic card is a single GTX 970 (no SLI), 8 GB RAM, Intel 2600K OC 4.8 GHZ. Windows 10 64 bit.

[FireRx]

Guys,
Did you know a hotfix was release last week. 378.72 for this issue?
Sseems to work okay here so far except for my TDFI B717. That one needs a few more tweaks and is a work in progress/ :)

[MikeFlight]

378.72 didn't work for me.

After a roll back to 376.33 no more VAS problems. Working fine for me.
i4790K, GTX970, 16 GB RAM, P3Dv3.4 HF2.

[FireRx]

yeah, Im going to roll back too

would be just flying along no problem theyn BAM CTD. not error message in event viewer or anything

[uksnapper]

I too had issues with latest driver - it was like filling a bath tub full of VAS and pulling the plug and watch it disappear. I did roll back to an earlier driver and really it didn't make a difference. I was watching a video from "Froogle" and stumbled upon his Nvidea Inspector setting and after changing a couple of my settings I now seem to have a sim that works the way it should -1.52GB available. With the issues it went as low as -0.35GB before it CTD.

[bcrawley57]

Any chance of a link to the video? I am at my wits end with VAS issues?

[Airwolf]

I too had issues with latest driver - it was like filling a bath tub full of VAS and pulling the plug and watch it disappear. I did roll back to an earlier driver and really it didn't make a difference. I was watching a video from "Froogle" and stumbled upon his Nvidea Inspector setting and after changing a couple of my settings I now seem to have a sim that works the way it should -1.52GB available. With the issues it went as low as -0.35GB before it CTD.

Which video is this?

[Hanse]

I just changed back as proposed to 376.33 and can confirm that the behaviour in connection with VAS is much better. During the flight there is nearly no buildup of memory used and just before landing I had several hundred MB more of free VAS than with version 376.66. So it is a try worth.

Maybe if we get the link for Froogles video on using the NVIDIA INSPECTOR with P3D v3 settings then we are able to free some more VAS......

Rolf

[MikeB54]

I don't have the link handy but if you just go to YouTube and search for Froogle you will find it.

Mike

[zap737]

I too had issues with latest driver - it was like filling a bath tub full of VAS and pulling the plug and watch it disappear. I did roll back to an earlier driver and really it didn't make a difference. I was watching a video from "Froogle" and stumbled upon his Nvidea Inspector setting and after changing a couple of my settings I now seem to have a sim that works the way it should -1.52GB available. With the issues it went as low as -0.35GB before it CTD.

Could you please confirm which driver version you are referring to.

Also could you please post a link to that video or at least advise what settings you changed.

[uksnapper]

I too had issues with latest driver - it was like filling a bath tub full of VAS and pulling the plug and watch it disappear. I did roll back to an earlier driver and really it didn't make a difference. I was watching a video from "Froogle" and stumbled upon his Nvidea Inspector setting and after changing a couple of my settings I now seem to have a sim that works the way it should -1.52GB available. With the issues it went as low as -0.35GB before it CTD.

Could you please confirm which driver version you are referring to.

Also could you please post a link to that video or at least advise what settings you changed.

I updated to 378.66 - had the VAS issue - as reverting back made no difference I re-updated to 378.66. Stumbled upon Froogles video (that makes no claim this sorts out VAS issue) and after applying changes - i am now having no issues since. I changed everything to mirror the Froogle settings apart from Antialiasing I kept at 4x opposed to Froogles 32x.
Here is the link to the video - 7:30 in https://www.youtube.com/watch?v=M04WZ9gw0Sk

[zap737]

I updated to 378.66 - had the VAS issue - as reverting back made no difference I re-updated to 378.66. Stumbled upon Froogles video (that makes no claim this sorts out VAS issue) and after applying changes - i am now having no issues since. I changed everything to mirror the Froogle settings apart from Antialiasing I kept at 4x opposed to Froogles 32x.
Here is the link to the video - 7:30 in https://www.youtube.com/watch?v=M04WZ9gw0Sk

OK Thanks. That's weird though, because those settings you changed in Nvidia inspector shouldn'treally affect VAS.

[marcon8122]

Preparing popcorns to see all people buying new 1080ti forced to use 378 series with vas leak and start crying. But they can't simply contact nvidia and tell them with 378 you have broken something...

[tonaz]

Hello! Anybody tried latest 378.78?
Same mem leak? Better to stick with 376.33?
Thanks!