So this Page File Size will fix the problem.
Good to know.
No guarantees but thatās what MS suggests 
1 Like
Youād think that rather than just allowing the OS memory calls to fail disastrously, theyād have been better sticking a longish timeout or a few repeated tries on it.
Surely a bit of a wait would be better than a CTD?
Basically longer waiting times are accepted in such situations (at least thatās better than letting the system crash because of a pointer exception ) - loading from page in general is slower than from RAM 
With plenty of RAM (like 64GB) this shall not happen anyway as usually unused RAM is freed by the program consuming (āgarbage collectingā) but something seems to be wrong over here regarding this somehow.
Yup. Virtually debugging code on a forum is way easier than doing it for real. 
Never as effective though.
2 Likes
Hey, here is a screenshot of my most recent crash.
1 Like
Just gonna add that the page file workaround did nothing for me, did try that before. Also 16Gb RAM seems to be fine if youāre not running hundreds of mods, never came close to maxing out. Needing 64Gb memory because of a programming error is not a solution
1 Like
I agree, except this is PC gaming, where hardware is almost never used to its full potential. Thatās why our CPUs sit mostly idle.
1 Like
Something I have been doing on Flight Sim PC for literally DECADES !!
Good Advice
Also, ādoes not hurtā to set the relevant Registry values, to CLEAR the Page file on shutdown.
Then next time you start the PC, its clear and not full of old, irrelevant data.
1 Like
Again, overwriting the page file upon every shutdown hurts your SSD with unnecessary write degradation. It doesnāt help anything.
Windows does not reuse old contents of a page file, nor should any page table entries point to erroneous data unless your hardware or software is unstable (which is not the fault of the memory manager nor the paging file).
4 Likes
Here are my last 4 entries I could find, all SU9 (except last one (first listed - 1390877444501819186) which is SU10 Beta). They all seem different.
Fault bucket 1390877444501819186, type 5
Event Name: RADAR_LEAK_64
Response: Not available
Cab Id: 1949797525290733077Problem signature:
P1: FlightSimulator.exe
P2: 0.0.0.0
P3: 10.0.22000.2.0.0
P4: 18
P5: 12
P6: 9
P7:
P8:
P9:
P10:Fault bucket 1299719020749668402, type 5
Event Name: RADAR_PRE_LEAK_64
Response: Not available
Cab Id: 1335173378670903902Problem signature:
P1: FlightSimulator.exe
P2: 0.0.0.0
P3: 10.0.22000.2.0.0
P4:
P5:
P6:
P7:
P8:
P9:
P10:Fault bucket 1823450865895561169, type 5
Event Name: RADAR_LEAK_64
Response: Not available
Cab Id: 2243152611126685892Problem signature:
P1: FlightSimulator.exe
P2: 0.0.0.0
P3: 10.0.22000.2.0.0
P4: 22
P5: 16
P6: 12
P7:
P8:
P9:
P10:Fault bucket 2035219560627479614, type 5
Event Name: MoAppCrash
Response: Not available
Cab Id: 1901246586212786854Problem signature:
P1: Microsoft.FlightSimulator_1.25.7.0_x64__8wekyb3d8bbwe
P2: praid:App
P3: 1.25.7.0
P4: 00000000
P5: CoherentGTCore.dll
P6: 0.0.0.0
P7: 621cebbb
P8: c0000005
P9: 0000000000cd4303
P10:
1 Like
Just a thought but nobody is reporting this (not that Iāve seen) in the beta
yes Ron, we determined already that the error have seemingly nothing to do with the pagefile , also because users with 64GB RAM are affected. And I must so laught if I see the nonsense rule about 1.5x RAM and that within a MS document 
Users just not read the topicā¦
We have recommendations in forum for pagefile size related to users with 16GIG, 32GIG and 64GIGā¦ And I hope no user with 32 or 64GIG RAM now set 1.5xRAM as min pagefile.
PS:: and I also expect a different error message related to that postā¦ eg. somewhat with memory allocationā¦
1 Like
I havenāt had the error since Sunday, having done around 10 flights now, with the SU10 Beta. What did it for me was removing process lasso and restoring my graphics card profiles/settings (not in game). I havenāt meddled with any graphics settings or options outside of MSFS for now, besides undervolting the gpu slightly for efficiency.
Still not sure what triggers the error. Iām tempted to re-install process lasso to see if thatās the cause, but itās running at the moment so Iām not sure if itās smart to mess around with it.
Iāve not had a CTD for a while now, but had previously experienced them without the presence of process lasso.
However, although that might appear to clear process lasso of any involvement, i suppose it is possible that the number and types of tasks running in Windows when you are using MSFS might be involved.
Now that the devs have apparently started to actively research this bug, Iām just going to let them get on with it and hope that my current good run of no CTDs continues.
1 Like
Developer, this bug was here reported on 14.April. This is 3 months now. We dont understand why there is not a hotfix on the way, no words, just nothing. Itās a real shame!
2 Likes
This thread has been flagged with the ābug-loggedā tag which means the developers are aware of the issue and are investigating. Additionally, the CM team has previously posted several times in this topic. We will share additional information with the community when it is available.
Thanks,
MSFS Team
6 Likes
@Jummivana posted 2 days ago, asking for fault bucket IDs, and this should reassure you that this bug hasnāt gone unnoticed.
No guarantees of course, but weāll hopefully have a fix that will be released at or, even better, before the SU10 release in August.
3 Likes
Iāve been posting in here since April. Before April this error never appeared. Has to be something with World update 9. They should revert back to like WU 5 or something. I also find if I fly a flight under 2 hours the error appears once every 5 flights. Anything over 2 hours the error occurs almost every time.
1 Like