If this stuff continues I may contact evga about a replacement. My 1080ti is a hybrid card and I didnt spend all of that money to have a card that needs to be down clocked just to use. Insanity. I do have evga afterburner installed but I do not use it. I will uninstall that and try another flight and see. 

Try 375.70. Way back in October of 2016. Then work your way forward if you want/need to for other games.

Personally the computer one does P3D.

I'm hoping that tomorrow I can make it to BWI (CLE-BOS-BWI) for my "virtual" layover 🙂

10 hours ago, cj-ibbotson said:

 

I tried about 15 drivers and 4 OS installs, one of which was a March 17 build of W10 and a driver from same period. All Windows and nVidia drivers disabled via Group Policy, fresh install of P3D4.3 and it still crashed exactly as before so it can't be a recent system update. Completely random locations and duration between crashes too

Sorry my fault, I forgot to mention the most important thing, this bug happens with P3D only. 

Only a tiny percentage of users is experiencing this on other games while the vast majority has this issue in P3D only, given by 2018 Nvidia drivers + a modern quick GPU and a random factor.

Anyway, if LM would, it could fix it in many ways, because it happens on hundreds of P3D users and only within P3D.

C’mon LM, do your job please !

 

Edited September 25, 20187 yr by Guest

Welp.... greetings from BWI. I made it without any issues with this older driver. I also tried the power limit and downclock again as well. Next is a newer driver (376.33 since that is FSLabs recommended driver) and going back to stock.

Fixed the error in my sim, latest Nvidia drivers, added the 64bit d-word in the p3d forums, removed old airport scenery and added one by one (FlyTampa Montreal you must disable the files with apprlights in the name), 1 month Nvidia Device Hung free.

Edited September 25, 20187 yr by Boeing or not going

Well so far a -RESET going back to max power and sitting on runway with 376.33

Edited September 25, 20187 yr by garymcginnis

I wonder why LM and Nvidia are silent on this, do they perhaps feel guilty and have no clue / time or willingness to undertake a deep troubleshooting preferring to focus on cosmetic marketing stuff instead ?

Edited September 25, 20187 yr by Guest

22 minutes ago, Mark II said:

I wonder why LM and Nvidia are silent on this, do they perhaps feel guilty and have no clue / time or willingness to undertake a deep troubleshooting preferring to focus on cosmetic marketing stuff instead ?

I'm actually pretty much over this hobby at this point. Yeah I had successful flights but it wasn't as smooth as before and just the hassle to get to that point. In addition the FSL flies like word not allowed compared to the real thing. Sitting out this long from FS really made it sink in. Just thinking it's not worth it.

On 9/25/2018 at 9:18 PM, garymcginnis said:

I'm actually pretty much over this hobby at this point. Yeah I had successful flights but it wasn't as smooth as before and just the hassle to get to that point. In addition the FSL flies like word not allowed compared to the real thing. Sitting out this long from FS really made it sink in. Just thinking it's not worth it.

Regrettably I got complacent, updated my driver from 399.24 to the current 411.63 and within minutes it crashed.  I had also raised my cpu overclock by 50mhz so I set it back to what it was before and restored the previous driver using DDU (though that makes zero difference in the past).  Had also thought perhaps Afterburner hadnt applied the reduced Power Limit after the new driver install, which had seemed to have helped so made sure that was reapplied.  I had thought performance wasnt impacted by reducing power limit but on reviewing it sadly it is.  I flying there in Orbx's Pacific North West and it became a stuttery 24 fps, increasing the power limit to 100 or even 80% resulted in a crash though fps went up to 30. Now got crashes on 399.24 which worked for weeks for hours on end with no crash. All my previous test flights over the past week have been around the UK and Europe.  Quite gutted now, its even worse as I had thought I had solved it and went out and bought a new yoke and additional throttle at £170 so its like a kick in the teeth.  Seriously sick of this word not allowed and LM have still NOT even commented on my original post on their forums.  Serious lack of support!! I had been advising so many on Facebook to try what worked for me.  Guessing many complainants dont use Avsim forums compared to Facebook.

Chris

Edited September 26, 20187 yr by cj-ibbotson

For those experiencing this crash, are you using Nvidia Inspector, or using any GPU monitoring programs while the sim is running?

Edited September 29, 20187 yr by exeodus

39 minutes ago, exeodus said:

For those experiencing this crash, are you using Nvidia Inspector, or using any GPU monitoring programs while the sim is running?

Personally I have never used NI as I do not require it and have also run tests with a new OS install and default SIM installation with no other apps of any sort installed and it still crashed.

 

Chris

Well anything new anyone?

No change on 411.70 for me....still get device removed when using NI frame rate limiter.  Dumped it again.

Giving RivaTuner a try I've read about for frame locking at 48 FPS (1/3 of 144 MHz).

33 minutes ago, CaptKornDog said:

No change on 411.70 for me....still get device removed when using NI frame rate limiter.  Dumped it again.

Giving RivaTuner a try I've read about for frame locking at 48 FPS (1/3 of 144 MHz).

Please advise. I'm curious about another FPS limiter as well!

20 hours ago, CaptKornDog said:

No change on 411.70 for me....still get device removed when using NI frame rate limiter.  Dumped it again.

Besides that, the 411.70 works ok? The first time I fired up P3D with this driver, I had only 50% of my normal FPS (locked at 30 internally). Closing P3D and starting it again restored the FPS. Also had issues with 50% FPS loss in other games, there it was sufficient to force "prefer maximum performance" inside the nVIDIA menue for the specific game.