March 31, 20233 yr 2 hours ago, altenae said: 4 online friends got the same error around the SAME time with all different version drivers. (also some had 531.29). So think how can this be … All had the error on the same time. You really think this is a driver issue when all 4 online players have all different driver versions and encountered the same issue at the same time reverted with DDU on 531.29 and working as before , maybe you are right , I didn't know this issue happens on 531.29 version ...will see
March 31, 20233 yr 2 hours ago, altenae said: 4 online friends got the same error around the SAME time with all different version drivers. (also some had 531.29). So think how can this be … All had the error on the same time. You really think this is a driver issue when all 4 online players have all different driver versions and encountered the same issue at the same time and did they all do a clean install, important !!! leftovers of drivers can cause problems too. but there has been too many issues with nvidia drivers lately
March 31, 20233 yr This NOT a new problem - I was getting the error fairly consistently in early fall 2022. Temps were always low, VRAM and system memory usage was low. Tried DX11 / DX12 / several different drivers. Nothing fixed it - just kept happening. Sometimes frequently sometimes only once every couple days. The problem persisted for several weeks and then stopped occurring and has never reoccurred. I did nothing to try to resolve it. Edited March 31, 20233 yr by TacomaSailor AMD Ryzen 7 9800X3D / MSI X870 Tomahawk Mobo / 64 GB DDR5 memory / RTX 4070 Super with 12 GB VRAM / AORUS FO48U 4k display NVMe for Drive C, an NVMe device dedicated to Flight Sim 2024 and a separate NVMe device for Flight Sim 2020 and an NVMe dedicated to 500GB of addons managed by AddonsLinker / 1 GB Comcast Xfinity Internet connection / HP Reverb G2 / Tobii 5 Head & Eye Tracking
April 1, 20233 yr Just had this error for the first time. Super frustrating, because I get the free time to play MSFS once every month or so. We'll see if it happens again in May... 😒 High end system, no overclocking. It's lying about running out of memory. Take-offs are optional, landings are mandatory.The only time you have too much fuel is when you're on fire. To make a small fortune in aviation you must start with a large fortune.There's nothing less important than the runway behind you and the altitude above you. It's better to be on the ground wishing you were in the air, than in the air wishing you were on the ground.
April 1, 20233 yr 20 hours ago, wim123 said: and did they all do a clean install, important !!! leftovers of drivers can cause problems too. but there has been too many issues with nvidia drivers lately I think he means that some of his friends were already using the 531.29 drivers, and had not installed the new ones. Christopher Low AMD Ryzen 7 9800X3D CPU / 64GB DDR5-6000 RAM / 12GB Nvidia RTX 4070 Super GPU / Gigabyte X870E Aorus Elite Wifi 7 / 1+2TB Samsung Evo Plus M2 Nvme UK2000 Beta Tester
April 1, 20233 yr 1 hour ago, Christopher Low said: I think he means that some of his friends were already using the 531.29 drivers, and had not installed the new ones. i got that yes...still could be leftover stuff, but it seems it is something very random, not everyone has got it.
April 1, 20233 yr 10 hours ago, WestAir said: Just had this error for the first time. Super frustrating, because I get the free time to play MSFS once every month or so. We'll see if it happens again in May... 😒 High end system, no overclocking. It's lying about running out of memory. I took a personal day from work today and tried again. This time I rolled back to 531.29. Then I upped my graphics settings to Ultra everything, 4K. As high as the bars let me go. Flew the same flight / route as before, except made it to my destination without any issues. I'm going to take a shot in the dark and say the latest NVidia Driver is the cause of this crash. Take-offs are optional, landings are mandatory.The only time you have too much fuel is when you're on fire. To make a small fortune in aviation you must start with a large fortune.There's nothing less important than the runway behind you and the altitude above you. It's better to be on the ground wishing you were in the air, than in the air wishing you were on the ground.
April 1, 20233 yr 19 minutes ago, WestAir said: I took a personal day from work today and tried again. This time I rolled back to 531.29. Then I upped my graphics settings to Ultra everything, 4K. As high as the bars let me go. Flew the same flight / route as before, except made it to my destination without any issues. I'm going to take a shot in the dark and say the latest NVidia Driver is the cause of this crash. Look at he date when this issue started !!https://forums.flightsimulator.com/t/warning-your-graphics-device-has-encountered-a-problem/541301/2573 Before 531.xx was there. I had the error with 531.29 so ?? How can that be ? It's not only an issue with the lastes Nvidia Drivers. Edited April 1, 20233 yr by altenae MSI Tomahawk Z790, I7-13700K, DDR5 6000mhz, MSI 4090, 3x SSD 980 PRO, Corsair 360 Liguid CPU cooler, Corsair H1200V2 power.
April 1, 20233 yr 1 hour ago, altenae said: Look at he date when this issue started !!https://forums.flightsimulator.com/t/warning-your-graphics-device-has-encountered-a-problem/541301/2573 Before 531.xx was there. I had the error with 531.29 so ?? How can that be ? It's not only an issue with the lastes Nvidia Drivers. It could be there is more than one event that can cause this particular CTD, but to an individual user there is almost always only one cause. I mean the number of people who suddenly got this for the first time with this driver, and then could not reproduce after rolling back, is not a minor thing that can be brushed off as coincidence. Though of course I am only guessing and have no evidence to back up my presumption. I would ask: If anyone who got this for the first time after updating to the latest driver, then gets this again after having rolled back, it would be great if they could post here. Take-offs are optional, landings are mandatory.The only time you have too much fuel is when you're on fire. To make a small fortune in aviation you must start with a large fortune.There's nothing less important than the runway behind you and the altitude above you. It's better to be on the ground wishing you were in the air, than in the air wishing you were on the ground.
April 1, 20233 yr I just got it yesterday for the first time as well. Reverted back to the previous driver and no issues. Jeff D. Nielsen (KMCI) https://www.twitch.tv/pilotskcx https://discord.io/MaxDutyDay VENGEANCE a8200 Gaming PC: AMD Ryzen 9 9950X3D, GeForce RTX 5080, 64GB DDR5, 4TB (2TB/2TB) M.2 SSD, Win11 Pro
April 2, 20233 yr I never had this issue until yesterday when it happened twice. I also had upgraded to the latest driver, but oddly enough..........it happened while I was taking off from KDFW, Runway 35L and during takeoff roll I hit some invisible object and CRASH. I have taken off from this runway countless times since this is my home airport, and never had this issue. I wonder if it's an Asobo server / scenery loading issue?? My specs are below - I never had an issue until now. Dennis Sincerely, Dennis D. Müllert System Specs: MoBo: MSI MAG X870 Tomahawk WiFi ATX AM5. CPU: AMD Ryzen 7 9800X3D. Memory: 128GB Corsair Vengeance DDR5-5600 CL-40. GPU: 24GB Asus TUF Gaming OC GeForce RTX 4090. Monitor: LG UltraGear+ 45" curved OLED. Power Supply: Corsair 1500 Watt 80+ Platinum ATX. HD: 2TB Sabrent Rocket NVME SSD. Windows 11 Pro. Flight Sim Hardware: Joystick: Thrustmaster T16000M. Rudder Pedals: Thrustmaster TPR Pendular Pedals. Yoke: Honeycomb Alpha. Throttles: Honeycomb Bravo. Controller: XBox Controller
April 2, 20233 yr Author 12 hours ago, WestAir said: ... I would ask: If anyone who got this for the first time after updating to the latest driver, then gets this again after having rolled back, it would be great if they could post here. Old Nvidia driver (version unknown) working for months (maybe even a year) and after the last SU update ---> error Upgraded to version 531.41 ---> error Downgraded to version 528.49 ---> worked a couple of times and now getting the same graphics related error again Result: CTD before MSFS completely loads and MSFS is now unavailable to me. A re-install may not be an option if it automatically updates and if the update is what is causing the error. P3D and DCS flightsims working fine. Edited April 2, 20233 yr by bofhlusr Hardware: i7-8700k, GTX 1070-ti, 32GB ram, NVMe/SSD drives with lots of free space. Software: latest Windows 10 Pro, P3Dv4.5+, FSX Steam, and lots of addons (100+ mostly Orbx stuff).
April 2, 20233 yr On 3/31/2023 at 4:30 AM, polosim said: Remove addons that could be causing this error I've never heard this one before! HowardMSI Mag B650 Tomahawk MB, Ryzen7-7800X3D CPU@5ghz, Arctic AIO II 360 cooler, Nvidia RTX4090 GPU, 32gb DDR5@6000Mhz, SSD/2Tb+SSD/500Gb+OS, Corsair 1000W PSU, LG Ultragear 48"4K, MFG Crosswinds, TQ6 Throttle, Fulcrum One YokeMy FlightSim YouTube Channel: https://www.youtube.com/@skyhigh776
April 2, 20233 yr 14 minutes ago, Rockliffe said: I've never heard this one before! Every day, there is something new to be learned. There are three pages of guesses, so far. The reason for this is clearly that no one knows the answer and as well as that, it is highly likely that there is not one answer, but several. The easiest trap to fall into is to make the assumption that the last thing that was done must be the cause of a problem. The quickest way to rule out all Community addons is to rename the Community folder and restart MSFS. The quickest way to rule out a driver is to "roll back" to the version that was there before. Ruling out Marketplace addons is a far more lengthy process that is probably not necessary in any case. Then there is the vast array of hardware combinations and the even more vast array of possible user-induced errors to be considered.
Archived
This topic is now archived and is closed to further replies.