Latest Nvidia drivers 381.65 causes memory leak

[Rob McCarthy]

We were able to reproduce the leak by leaving Prepar3D running over the course of three days at the default starting location. We saw an increase of roughly 300mb during this time. After this the VAS stabilized and no longer increased. We still have this instance running and memory usage has been stable since Monday. We sent Nvidia the information they requested including sytem logs and are currently waiting on a response.

Regards,
Rob McCarthy

[marcon8122]

Thank you Rob consider that over water and with thunderstorm the vas will raise more and also will be not purged like older driver version after some miles

[ahuimanu]

Hi Rob,

Thank you for your inquiry into this matter. I would add that a somewhat more useful test would also subject the sim to scenery loading by way of cross-country travel (not just sitting still). Some have suggested issues with travelling over water and I've noticed this to be an issue as well.

Thanks again for your attention. It was regrettable that the previous thread was closed as a single thread allows for a running dialog. I hope this tread may remain open until some resolution is found.

[jsbryner]

Rob,
I can tell you I had been plagued with this issue since I deployed my new sim rig earlier this year. Long hauls, transoceanic and high density scenery (ORBX, etc) eventually became no-flys for me.
Resolving it turned out to be getting the combination of Prepar3D version and NVidia driver correct. The only NVidia driver version / Prepar3D Version combination which does not cause problems with memory leaks (for me) is Prepar3D Professional 3.4.22.19868 with NVidia Driver 376.33. Any other combination of the 2 (older versions of Prepar3D and newer versions of NVidia driver) seem to present the memory leak problem in some form or other. It is my understanding that Prepar3D 3.4.22.19868 incorporated a change to release memory more aggressively to address VAS problems reported by users. So, that's the version of P3D I finally settled on. I had read a post where users noticed VAS issues after NVidia drver version 376.33, so I went back to that. It's been reliable ever since. Hope this reply helps.

My specs:
Prepar3D Professional 3.4.22.19868
Windows 10 Professional
NVIDIA GeForce GTX 1080
Intel i7-6900K 3.2GHz

---
Jeffrey S. Bryner

[abd40110a]

Have you tried this last one: http://nvidia.custhelp.com/app/answers/ ... ver-381.78

It is a release taking into account comments published on the forum Nvidia.

It woks for me and my GTX 1080 Ti.

[BRAUS]

It is a release taking into account comments published on the forum Nvidia.

It woks for me and my GTX 1080 Ti.

Could you point us to where it says this release takes into account comments published on the Nvidia forum Please?

As far as I can see the only thing this is the only thing this hotfix is supposed to fix:

"GeForce Hotfix driver 381.78
Answer ID 4453 Updated 04/17/2017 09:37 AM
This is GeForce Hot Fix driver version 381.78 that addresses the following:
-Fixes Windows 10 Creators Update booting to a black screen on certain notebooks"

But it also fixed some black screen issues that some desktop users were experiencing.

Although I can say I have done one quick test with this driver on my 1080ti and it still produces one big VAS hit during the flight but at least it appears to sit still after that which is somewhat better than a continuous leak. It was only a quick test so I can't say 100% the leak doesn't continue.

Bruno

Edited a typo.

[Poppet]

Hello

I have Removed all "Off Topic" posts. Please stay on topic

[BRAUS]

Ok so after further testing with 381.78 I get a spike at the start as previously mentioned but I am no longer seeing the 70-80MB per hour increase during flight that I was experiencing before. Now it is more like 10-15MB per hour and Prepar3D is actually trying to release VAS where before it was a steady increase with no return.

As for the sudden spike it was approximately 600-700MB with 378.92 and 381.65 but with 381.78 it is only about 250MB. Another user I was in contact with replicated the spike on his system using 381.65 flying from YSSY to YPPH a few nm from CB. Route: DCT TESAT H65 WOL J42 CB J142 BORTO Q188 CANDY Q158 PH
Neither of us had ORBX YSCB or Canberra City activated so that was ruled out.

The spike for me was occurring at any point during the flight with 378.92, however with either 381.65 or 381.78 it happens somewhere between takeoff and TOC.

Anyway I suggest anyone with a 1080ti like me to go with 381.78 as it is a vast improvement but anyone who can roll back to 376.33 to go back to it. Hopefully Nvidia will get back to Rob and we get some good news.

Andrew - I am running Prepar3D on 3 monitors full screen and did not experience the same issue you are having with 381.78

Cheers,

Bruno

[Twistgrip]

Hi Braus,

I have a GTX 1060 with 381.65 and am experiencing repeated crashes also. Most of my flying is in AUS and just now did a flight in PMDG 738 from YMML ML-H129-DOSEL-Y59-NONUP-J142-CB-YSCB and it came up with out of memory just as I intercepted the glide slope, I run Active Sky 16 and ASCA weather was overcast. Ive also been trying to adjust sliders to not much avail.

I will try rolling back to 376.33

Cheers
Steve

[marcon8122]

Would be interesting to know what cause those 15 mb spike and why the sim is no more able to unload vas as previous

[FireRx]

I went back to 376.33. Smooth as silk with no issues. Nvdia needs to step up their game.

[georgio52]

New Driver Release Date: 2017.4.25 Version: 381.89  


PC INFORMATION :

GPU: EVGA GeForce GTX 1060 Superclocked 6GB GDDR5
Memory: 8GB 3000 MHz DDR4
Motherboard: GIGABYTE GA-Z170X Gaming G1

[maca12]

Hello,
any tests and experience with nvidia 381.89 ?
imporvement with OOMs, or still the same ?
many thanks