SU2 keeps crashing to desktop when I approach large cities, e.g. São Paulo, London, LA. It happens at seemingly randomly moments, but it happens basically on every flight at some point. I only fly VR, but I’m not sure if it would occur in 2D mode as well. I don’t know what to do…
This post has two objectives: first I wanna find out if anybody else has that problem. And secondly, I want to find out if there’s any way for me to narrow down a reason. I have seen other people mention crash logs. How do I access them? What do I look for in them to narrow down the reason for crashes?
I have a high-end system, and when the crashes happen, as far as I can tell, I’m not overheating the GPU or hitting any memory limits.
Thanks for your answers. I have not deleted the SceneryIndex folder, but I did uninstall and reinstall MSFS 2024. I will delete this folder and see what happens.
I have not cleared the DX folder. Didn’t know there was such a thing. Will have to google how to do that. Is there a folder called DX cache?
I am on the latest NVidia driver.
I am not using OpenXR toolkit.
I don’t know if I have rebar set to on or off. I generally avoid messing with bios since I’m not much of a computer expert, but I will check.
This is the virtual memory (paging file) setting on the Windows side.
If the physical memory is 64GB, the committed memory may be exceeded and CTD may occur. In that case, the paging file must be set to a sufficient amount.
If there is enough physical memory + paging file space reserved, the cause of the CTD may be something else.
Same issue here in 2D. Approaching Los Angeles, New York, etc. CTDs every time. 64 GB of RAM and 4080 Super. Trying some of the recommendations posted previously, but so far no luck.
I spent a few hours trying different fixes. I was getting CTD 100% of the time when flying from Palm Springs to LAX or Islip into JFK. It would CTD at pretty much the exact same location each time, about 20 miles out. I finally decided to try updating my BIOS, and that turned out to be the fix for me. I’ve done both of the test flights 2-3 times now with not one CTD.
Coincidently, KPSP to KLAX is what I fly most of the time, too.
I will update my BIOS. I have to admit I’m not well versed in all things BIOS. Is there a good link you recommend to a youtube video that explains how to update the BIOS?
Another question: I’m trying to make sure I’m on the latest windows version. So, I checked “windows updater”, it says I’m up to date. But I’m on 23H2, isn’t the latest version 24H2?
BIOS update depends on motherboard manufacturer. If you click on Settings in windows you should see Home at the top, then the name of your PC and the name of the motherboard directly beneath that. For example, mine says “Z790 AORUS ELITE AX” From there, you should be able to find some YouTube videos explaining how to update the BIOS. Mine also says 24H2
.
Thanks, I found some YouTube videos. I have not yet updated my bios, but took a look at my BIOS settings. I turned off rebar, as recommended by a poster above. I have had one successful flight. So either it was coincidence or that fixed it. Do you think your BIOS update happened to turn off rebar?
Let us know if updating the BIOS worked. I get CTD inMS2024 every time within 30 minutes of flying with 13900 CPU and 4090 card. I tried every fix out there (except for updating BIOS) , MS2020 works great with not 1 CTD and over 70 add on airports. InMSFS2024, my community folder is empty, and I get CTD 100% of the time. Sometime when I pause the game for 5 minutes, sometime when stopped on a runway, sometimes during cruise in the middle of nowhere, sometimes during start-up. MSFS2024 is completely unstable for me. My event looks the same as above with LIMITLESS mentioned. My CPU seems to be running at 85-93 deg C and Iam not sure if temps are an issue??? I was going to re-install MSFS2024.
Did another test flight from KPSP to KLAX, got another CTD on approach into LA. So, I guess simply switching from rebar on to rebar off didn’t fix it. Will have to update the BIOS, I guess.
I just updated my BIOS, and according to my first tests I didn’t have a crash flying into LA on a plane/route where I would get 100% CTD before. More tests are necessary, but it looks promising right now. The effects of a BIOS update are presumably dependent on the motherboard you have. I happen to have an ASUS prime z790 p Wi-Fi board, similar to the person that posted above. So your mileage may vary, but imo it is worth considering a BIOS update.
I updated BIOS and no difference. CTD every time. I have very high end machine and been using Microsoft Flight Simulator since 1990 -I consider myself a loyal fan and somewhat an expert, but I simply can’t solve the daily MSFS2024 CTD’s Asobo, fix your mess. You are failing is.
Really sorry to hear this. I had CTDs on every flight, starting some time half way through SU2 beta. Now that I have updated my bios, I haven’t had a single CTD, not one. Would be interesting to find out what exactly the bios update changed. Do you overclock anything? Have you tried without overclocking?
I’m this this exact same issue and been for a while. I have tried flying into Toronto, LA, Las Vegas, New York, and within about 10-15 miles of the city my whole system crashes. Not just a CTD but an entire system crash requiring a HARD reboot.
Flying into smaller cities, like Victoria, Astoria, and the like, not an issue, but the larger ones. Everytime.
I have done all the suggestions, including reloading the sim, empty community folder, stock 172. Doesn’t matter… is this a VRAM issue or something worse???