May 23, 20233 yr Driver Version 531.79 Crashes my MSFS Edited May 23, 20233 yr by SierraHotel AMD Ryzen 7 3700X 4.2 32 gig ram, Nvidia RTX3060 12 gig, Intel 760 SSD M2 NVMe 512 gig, M2NVMe 1Tbt (OS) M2NVMe 2Tbt (MSFS) Crucial MX500 SSD (Backup OS). VR Oculus Quest 2 Windows 11 25H2 YouTube:- https://www.youtube.com/channel/UC96wsF3D_h5GzNNJnuDH3WQ 2k+ Videos & Streams BATC and FSFO FB Group:- https://www.facebook.com/groups/1571953959750565 Flight Sim First Officer (FSFOv6) and SoFly Beta Tester Reality Is For People Who Can't Handle Simulation!
May 23, 20233 yr 11 minutes ago, SierraHotel said: It's a new one on me! It's a message that pops up in the AAU2 beta I believe: https://forums.flightsimulator.com/t/driver-warning-to-lower-than-531-30/591706. I think another thread was started on this in the MSFS forum here in Avsim, you can search for it. The reason is, there is some bug with the newest NVidia drivers and MSFS. The MSFS team and NVidia are working together to figure out the bug in the newest NVidia driver. Edited May 23, 20233 yr by abrams_tank i5-12400, RTX 3060 Ti, 32 GB RAM
May 23, 20233 yr 27 minutes ago, SierraHotel said: Driver Version 531.79 Crashes MSFS Been running 531.79 since it's release. No issues whatsoever. You should change that to "Driver version 531.79 may under some very specific circumstances that no ones actually managed to put their finger on cause a CTD but there's a good chance you'll be absolutely fine"
May 23, 20233 yr Thread title is misleading. No crashes here. It's an Asobo/Microsoft "recommendation", nothing more, and can be permanently disabled in the latest version of the beta.
May 23, 20233 yr Commercial Member 6 minutes ago, The Moose said: Been running 531.79 since it's release. No issues whatsoever. You are likely using DX11, in that case even the latest drivers works just fine. The crashes happens only in DX12, which is a bummer if you have a 4000-series card, since DX12 is required to enable Frame generation. Before the alert, I couldn't use MSFS on my laptop with a 4090 chip for more than a few minutes without crashing, but I could use it for hours straight in DX11. Going back to the recommended version, 531.29.0 (531.30.0 has never been released, that's why MS used the wording "lower", so it's clear you must use 531.29 at most), all crashes are gone, and I could use DX12 as well DX11 with no issues whatsoever. Umberto Colapicchioni http://www.fsdreamteam.com FSDT on Facebook
May 23, 20233 yr 4 minutes ago, virtuali said: You are likely using DX11, in that case even the latest drivers works just fine. The crashes happens only in DX12, which is a bummer if you have a 4000-series card, since DX12 is required to enable Frame generation. Exactly. I had CTDs with all more recent NVIDIA-Drivers after 45 min into the flight - until I switched back from DX12 to DX11. No single CTD since. I sincerely hope they will be able to exchange this boring message by a working DX12 soon. Kind regards, Michael Intel i7-13700K / AsRock Z790 / Crucial 32 GB DDR 5 / ASUS RTX 4080OC 16GB / BeQuiet ATX 1000W / WD m.2 NVMe 2TB (System) / WD m.2 NVMe 4 TB (MSFS) / WD HDD 10 TB / XTOP+Saitek hardware panel / LG 34UM95 3440 x 1440 / HP Reverb 1 (2160x2160 per eye) / Win 11
May 23, 20233 yr https://www.avsim.com/forums/topic/633931-asobo-releases-driver-warning-to-lower-than-53130/ Edited May 23, 20233 yr by rutrA AMD Ryzen 9 9950X3D, MSI RTX 5090, 64GB RAM 6000MHz DDR5, Tuf Gaming X870Plus, 1200W PSU English is not my first language.
May 23, 20233 yr 1 hour ago, The Moose said: Been running 531.79 since it's release. No issues whatsoever. You should change that to "Driver version 531.79 may under some very specific circumstances that no ones actually managed to put their finger on cause a CTD but there's a good chance you'll be absolutely fine" Same here. Even rolled back to the latest recommended driver and it made no difference in either stability or performance. I'm running i711700k with GTX 1080ti DX12. Pretty smooth with only v few stutters...
May 23, 20233 yr 1 hour ago, virtuali said: You are likely using DX11, in that case even the latest drivers works just fine. The crashes happens only in DX12, which is a bummer if you have a 4000-series card, since DX12 is required to enable Frame generation. Before the alert, I couldn't use MSFS on my laptop with a 4090 chip for more than a few minutes without crashing, but I could use it for hours straight in DX11. Going back to the recommended version, 531.29.0 (531.30.0 has never been released, that's why MS used the wording "lower", so it's clear you must use 531.29 at most), all crashes are gone, and I could use DX12 as well DX11 with no issues whatsoever. I'm using DX12 and I also don't have crashes with 531.79, but I was having some stutters. So went back to 531.29 and it fixed the stutters. Alvega CPU: AMD 7800X3D | COOLER: Cooler Master MasterLiquid 240L Core ARGB | GPU: RTX 4070 TI Super 16GB OC | Mobo: ASUS TUF GAMING X670E-PLUS WIFI |RAM: 32 GB Corsair Vengeance RGB DDR5 6000MHz PC5-48000 2x16GB CL36 | SSDs: WD Black SN770 2TB NVMe SSD (WIN11), WD Black SN850X SSD 2 TB M.2 2280 PCIe Gen4 NVMe (MSFS), Crucial MX500 2TB (Other stuff) | CASE: Forgeon Arcanite ARGB Mesh Tower ATX White | Power Supply: Forgeon Bolt PSU 850W 80+ Gold Full Modular White
May 23, 20233 yr Same here. 531.29 is the driver I use because it eliminates stutters for me. i9-14900K / DDR6 / 4090 / 64 GB RAM
May 23, 20233 yr I've always thought that everybody should be better off by never using the latest video drivers. The only exception, as far as I remember, was just after SU10 when Nvidia and MS worked together on a driver that was released together with SU10 (pardon me if it wasn't SU10, but you get the idea). Cheers, Ed MSFS2020 Steam // Rig: Corsair Graphite 760T Full Tower - ASUS MBoard Maximus XII Hero Z490 - CPU Intel i9-10900K - 64GB RAM - MSI RTX2080 Super 8GB - [1xNVMe M.2 1TB + 1xNVMe M.2 2TB (Samsung)] + [1xSSD 1TB + 1xSSD 2TB (Crucial)] + [1xSSD 1TB (Samsung)] + 1 HDD Seagate 2TB + 1 HDD Seagate External 4TB - Monitor LG 29UC97C UWHD Curved - PSU Corsair RM1000x // Thrustmaster FCS & MS XBOX Controllers
May 23, 20233 yr No issues with this driver on my 4080 as long as I do not use GF Experience filters. With them, crash latest 5min into a flight. Known issue, its even in the release notes. What also helps: set the shader cache to 10GB or more specifically for MSFS (you need nVIDIA Inspector to do this). Greetings, Chris AMD Ryzen 7 9800X3D, 2x32GB DDR5 6000MT/s RAM, MSI RTX 4090 Ventus 3X, Windows 11 Home, MSFS2024
May 23, 20233 yr 10 minutes ago, edpatino said: I've always thought that everybody should be better off by never using the latest video drivers. The only exception, as far as I remember, was just after SU10 when Nvidia and MS worked together on a driver that was released together with SU10 (pardon me if it wasn't SU10, but you get the idea). Most people play other games too and need the latest drivers for them. Alvega CPU: AMD 7800X3D | COOLER: Cooler Master MasterLiquid 240L Core ARGB | GPU: RTX 4070 TI Super 16GB OC | Mobo: ASUS TUF GAMING X670E-PLUS WIFI |RAM: 32 GB Corsair Vengeance RGB DDR5 6000MHz PC5-48000 2x16GB CL36 | SSDs: WD Black SN770 2TB NVMe SSD (WIN11), WD Black SN850X SSD 2 TB M.2 2280 PCIe Gen4 NVMe (MSFS), Crucial MX500 2TB (Other stuff) | CASE: Forgeon Arcanite ARGB Mesh Tower ATX White | Power Supply: Forgeon Bolt PSU 850W 80+ Gold Full Modular White
May 23, 20233 yr I have had the "graphics error" CTD constantly since SU12 was released, even with the 531.29 driver, using DX-11. Never had this problem before. I believe I am not alone. Looking forward to a fix from Asobo, hopefully with the next SU.
May 23, 20233 yr saw sudden increase in "graphic/overheat error" messages with the latest driver(s) and went back to 528.49. no issues since then. On DX12 with TAA. Phil Leaven i5 10600KF, 32 GB 3200 RAM, ASUS 4070 12GB EVO, Asus ROG Z490-H, 2 WD Black NVME for each Win11 (500GB) and MSFS (1TB), Rolling Cache 16GB, Photogrammetry always OFF, Live Weather and Live Traffic always ON, Res 2560x1440 on 27"
Archived
This topic is now archived and is closed to further replies.