Can confirm after setting the sound to my headphones instead of the default I was able to fly 2 flights in a row with 7 hours in the sim without stopping. Strange if that was the issue.
I was finally able to get a full flight in with a complex aircraft, MD-80. I updated my bios, it was on the original bios and that might have been the difference. I will test more later. UPDATE>>> After 3 flights tried the new A320 from Fenix. Made it about an hour into the flight and got the error. So it is not happening as much, but it is still happening.
Well luckily this appeared as I was taxing into stand and I was able to continue to use MSFS.
My previous flights have been successful the only setting I changed today was my headphones - I chose to use my headphone rather than my desktop speakers.
So I see a lot of users flying around on Vatsim and Volanta. Are they not having the issues we are? How does Asobo and Microsoft not know about this memory crash issue? This issue was not happening with earlier MSFS Versions. Whatās even more frustrating is you donāt know when the crash is going to happen. Itās completely random. I had one today when I was loading my flight plan in the FMS. It was a no big deal at that time of my flight but gee wiz Asobo address this with a hot fix!
3 Likes
I was finally able to make a few flights without ctd or memory error message.
I havenāt changed anything except maybe my sound output device, but Iām not sure.
In my case I noticed that in the configuration menu of FS the choice of sound output was not always possible, I had to modify in W10 before.
Either there has been a modification at Asobo level, or my sound setup has changed things.
To be continuedā¦
guys, I think I have fixed this issue. it turns out to be sound setting in windows. Yes, many people mentioned before, but what I have done is set default output device AND default communication device (something like this, canāt recall exact naming) to your current use speaker/headphone/whatever.
You can find those settings in advanced sound settings by right click on the volume icon. My initial setting is default output device is my speaker but default communication device is my monitor loud speaker. This mismatch might cause the issue. So, hope this finding help you as well.
The point is, Always make sure your default device is the same as your default communication device.
1 Like
done that, still had memory read errors. tbh fixing external sound output devices makes little sense in rectifying internal functions in the application making calls to non existent memory locations. But I tried it and have had several memory read crashes since.
2 Likes
I too am seeing these errors since SU 9 and would really appreciate a hotfix. They have become consistent enough to be bothersome.
Thanks for any engineering support you can devote to this issue. We are as important as the XBox community.
C
I followed your youtube, your instructional videos are very good, I learned how to fly a Boeing 737-700, I also have the same problem as you, it bothers me so much that I canāt complete a perfect flight almost a day now, however Asobo didnāt respond, which was really disappointing.
1 Like
One issue Iām having now is with long hauls. Previously I had no issues, and now Iām getting a ābreak point exceptionā error around the 9 - 10 hour mark. Iāve reached out to several others who are experiencing the same thing. Iāve yet to complete a long haul with the PMDG 737 BBJ because of this.
So since i changed the sound stettings, i was able to flight 4 hours. Iāve got the error once i restartet my VR Headset in the main menu of MSFS. But i was not able to reproduce it.
I see there are problems too with the World Update. I canāt even download it. There is a buggy connection issue.
As i know, after i lost a connection it crashed too. Got huge FPS drops before.
Maybe i can reproduce it, if i lose connection.
thanks!
oddly enough yesterday I was able to complete a full flight but today after take-off, I began to spin around in the external drone camera whilst the aircraft fly the LNAV/VNAV elements of the SID for screenshots/streaming and it froze and instantly CTDādā¦ perhaps it is something very broken in the sim we are unable to fix without Asobo addressing it.
Iām Ā£270 down personally having purchased new RAM due to the āmemory could not be readā making me run MemTest86 resulting in me then buying new RAM all for nothing and itās meant I cannot fly IRL this month because of it! thanks Asobo
3 Likes
so, you do not state ā Did Memtest86 PASS or FAIL
If it failed, then yes, you may well have needed new ram
If it did NOT fail, then new ram was most likely not going help.
In any case, the Application Error- memory could not be read is 99.99 % most likely to be a software error, with a NULL POINTER, as opposed to a bad ram issue
1 Like
I also thought it was a RAM problem at first, so I replaced it with a new one, and it didnāt solve it, if you play other games, you will find that you canāt go wrong at all, thatās the MSFS problem.
It did fail the memtest 3 times across 12 tests running at once so there was an issue there but it didnāt solve the MSFS ctd issue for me.
Problem is, I like many others arenāt that techy and donāt understand what half of it means, so we try our best yet everything keeps pointing back to issues in the sim instead somewhere
Soā¦Iām not sure if upgrading my bios or avoiding Italy did the trick or if I was just more lucky, but the last 4 flights went through without a problem for me.
Just adding my two pennies - been flying from EGCC to EHAM to test, starting at runway 23L and following an FMC f-plan through DESIG and LAMSO - CTD has been occurring since SU9 and no solution has worked so far:
- tried setting sound options correctly
- removed all content from community folder and deleted content.xml
- already have page file set up
- saw one tip to delete and reinstall Xbox app
- set fps limit to 30
- ran in DX12
- removed all non-essential peripherals
- reduced graphics settings
- did flights to different destinations and from different airports
- updated all drivers
- turned XMP off
- turned the windows graphics setting off (it was already off)
- enabled/disabled rolling cache and rebuilt cache
- IN PROCESS: waiting on a clean reinstall to see how that goes
System:
Ryzen 5 3600
Rtx 3080 FE
16 GB Corsair RAM (3600Mhz)
Windows 10
Crash occurs anywhere between 20-30 mins after loading into the Sim. Doesnāt matter where Iām going to or from. Doesnāt matter which view I am in or how many times I change view/pan around.
Before SU8 and SU9, I was able to complete 3+ hour flights. Now I can barely make it to the descent phase of a flight that is less than an hour.
The updates definitely did something - Iād say the game is broken at the minute, especially when you canāt be on the sim for more than an hour before it CTDās or gives an error.
2 Likes
Hi! Same here, with me it happens sometimes when I click on World Map in menu. Iāve never had it while flying. rtx 3060 laptop ryzen 7 5800H
Whatever theyāve done with SU9 and WU9, they have managed to cock the sim up for quite a substantial number of both PC and Xbox users alike, it seems.
2 Likes
Then, with the new Memory, did it Pass 100% over an extended period, and forced elevated temperature ā ( Summer is coming !!)
If so, then the cost of the new memory was justified ā¦ even if it did not 100% cure your MSFS woesā¦