Word not allowed, it happened again!! After couple of hours of flight, CTD without any warnings. First time it was CoherentUIGT.dll file which crashed the sim, this second time it was RenoirCore.WindowsDesktop.dll. Both times I was flying with FBW A32NX in South America. Lesson learned: apparently I have to fly just some short flights, maybe an hour or hour and half at the most. Great stuff indeed…
Try without using the FBW A320. I too had crashes using that plane, but none so far using the CRJ. Also, are you using external liveries? I was advised to delete those too.
I do have ivao_x-csl folder in my community folder. I use it to show other planes when I´m flying on vatsim. I do not own the CRJ…
Had a CTD with Asobo A320.
Interesting, I will try this also.
How many hours of flight did you do an experiment?
Mine was crashing 100% of the time at the end of the loading before the flight.
Now I disabled virtual memory and it seem to be fixed.
To check if this is your issue to, in windows open Event Vier → windows logs → system
If your getting screwd by virtual memory there will be a WARNING like this:
“Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: FlightSimulator.exe (15936) consumed 23888822272 bytes, chrome.exe (2460) consumed 458981376 bytes, and MsMpEng.exe (3240) consumed 400093184 bytes.”
I disabled my virtual memory because I have 32GB of RAM.
If you have less than 32gigs, you should increase your virtual memory, not disable.
To disable virtual memory, it’s no enough to set it to zero in advanced system settings you have to use the cmd command:
fsutil behavior set encryptpagingfile 0
1 Like
I’ll try, it’s the only thing I haven’t tested, with virtual memory.
Make sure to report the crash to desktop to the FBW team as i’m also getting a CTD with CoherentUIGT.dll. It seems to be the FBW A320 causing the crashes. I was doing a flight from Los Angeles to Vancouver and then experienced a crash so I checked my event viewer and sure enough CoherentUIGT.dll file was the cause, this is the second time now today on the same flight with the FBW A320.
Yesterday’s tests:
-
Tried to launch MSFS, crashed with GPU driver timeout and vcruntime140.dll at the millisecond where the initial loading screens fade to the main menu.
-
Second attempt, same crash.
-
Third attempt, managed to reach the main menu, CTD 5 seconds later with the same errors.
-
Fourth attempt, success. Call me crazy, but I have the feeling that if I click the mouse wildly and move it around while MSFS is ready to transition from the loading screens to main menu, then it usually doesn’t crash. It doesn’t make sense but I’ve seen it happening so many times that I use it as a placebo “workaround”.
So I loaded the JustFlight Piper Arrow and literally let it there parked at the apron for 12 consecutive hours, while I was writing new improved checklists and programming my Bravo with spad-next. I knew that MSFS wouldn’t crash no matter what I did, how many apps I launched or how many times I switched back and forth to Windows.
Then I restarted the flight session, completed a 1-hour flight, returned back to the main menu and… CTD.
- Another attempt to load MSFS, worked OK. Loaded Asobo default Diamond DA40 to test some things at a different location, 2 minutes into the session while I was preparing to start up the engine and… CTD.
So it seems that some aircraft CTD all the time, from default types to CJ4 WT. While with some others I’ve never seen a crash, e.g. default C152/172, Piper Arrow and so on.
I seriously have no idea what’s going on. It can’t be the addons or the community folder or the hardware itself, because I’m not changing anything between these attempts. It’s gotta be the software. Today I’ll try to replicate using the same location for both aircraft that CTD and those that don’t.
ps: spad-next takes mapping configs to a whole new different level, I’ve managed to map almost every important function of the Piper Arrow via LVARs and it works like a charm. No more mouse clicking left and right.
1 Like
I also suffers from crash to windows without error message.
Happens now from time to time, have no clue on whats going on.
Checked the temperatur and work load of the computer but it feels just great 
Upgraded to 32gb of RAM (from 16) but no diffrens.
Intel I7 with a 2080 so It should work just fine…
What do you mean by “crash to windows without error message.”
Because after each crisis there is usually a message in Windows Event Viewer. This not because there are no messages that appear, when you come back to the desktop, that there are no messages
I CRASH two times after 15 minutes, with the two same error messages… GPU driver timeout and vcruntime140.dll
6800XT, 5800X, 32gb ram,1TO nvme specially for msfs, i m disppointed. is windows10 update last night ?
Don´t know what is happening.
Today I was about 1h in to my 1h 20 min flight… it kind of sucks.
No error messege for me, “just like that” i´m back in windows.
My CTD’s seem to be dependent on the aircraft I’m trying to fly. Whenever I try to startup from EHRD with either the Aerosoft CRJ or the Aermachi I crash back to the desktop during loading. I’m planning to fly in VR, so I have the Oculus Desktop app running as well as the Oculus Tray tool (but I did not switch to VR mode yet). If I choose the Robin then everything is a-ok. Didn’t try other aircraft or location combo’s yet as my time is pretty sparse right now. Never had CTD’s before the last few updates.
Hi! I’ve gotten this error message before. Maybe 4 months ago. For me, it was related to an overclock I had on my GPU. Removing the overclock stopped these from occurring.
I hope this helps you. If not, maybe try reinstalling your GPU driver and reset all GPU settings back to default.
I’ve been reluctant to post this because it seemed like it was hit or miss on the fix. However, I’m up to at least 20 cases with friends who’ve had CTDs randomly while trying to start a new flight OR while flying somewhere, but the crash is in a specific region.
Also - this only applies if you have mods in your Community folder.
What I’ve learned is that MSFS is being pickier with mods. Two cases:
-
If the layout.json file does not match the actual addon contents, MSFS can crash. Run the MSFSLayoutGenerator.exe tool to update your layout.json.
-
if the addon has a “modellib” folder and the folder under that is “mytextures”, then you need to rename “mytextures” to something unique. And then rerun MSFSLayoutGenerator.exe to update your layout.json.
I wish I could say this will solve all your problems, but for those who need to have their addons, this is what got me flying again.
2 Likes
no oc. i don t install last radeon driver, because precedent version make fps fall… i ll wait the sim update 4…
Ok. I’m sorry I couldn’t help you. But that error definitely indicates a GPU hardware or software issue of some kind.