What ASUS tools could cause this? I have GPU Tweak III and Armoury Crate.
we have at least one report where GPU Tweak III caused extrem fps lose. I can also remember about Armoury Crate problems and I assume that is relevant for your case.
Arenāt those applications pertinent to the operation of my system? Whatās the alternative?
Application popup: FlightSimulator.exe - Application Error : The instruction at 0x00007FFDD9E991B3 referenced memory at 0x0000000000000000. The memory could not be read.
Click on OK to terminate the program
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}
and APPID
{15C20B67-12E7-4BB6-92BB-7AFF07997402}
to the user DESKTOP-I27OV58\brend SID (S-1-5-21-2748309279-4200193464-863999175-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
Heres what I found in my event viewer after my last crash. Both were reported at the same time. Coincidence?
Count me in also. Numerous crashes and already deleted all ASUS related software, but to no avail apparantly. This is getting extremely frustrating.
I also have a high end pc with RTX3080Ti and i12900 processor. Iāve had the ctd with both xmp on and off. No differences.
Asus Sonic Studio had a bit of a reputation at one time and i uninstalled it after it stopped one of the early Oculus VR games working.
Iāve never reinstalled it though, as i never really needed it, so i donāt know if it has been fixed.
GPU Tweak and also Armoury Crate is not necessary.. Of course in case you like many ābling-blingā at your pc, these application steer e.g. the ābling-blingā. But at least I look at the monitor only 
But you not need to uninstall these tools. Just completely stop it and do some test-flights. If you no longer get crashs, you found may be the reason.
We just only seen, that these tools crashed and therefore the hint into that direction.
@HawkMoth9135 yes.. Sonic Studio was long time number one of troube maker
these yellow COM stuff you can ignore, itās just windows what we must use 
1 Like
Got this error twice tonight in the 737. Interesting thing is I havenāt changed anything from yesterday other than downloading the updated 737 (3.0.42) and also dialing up my FSLTL settings.
I have never seen this error before, but thatās all Iāve done and now Iām getting it -
Application popup: FlightSimulator.exe - Application Error : The instruction at 0x00007FF72575FD44 referenced memory at 0x0000000000000010. The memory could not be read.
Click on OK to terminate the program
I installed the latest NVidia driver (522.25) two nights ago and it was fine on flights yesterday.
I havenāt changed anything else since having that stable flight yesterday and previously, and have now had two straight FS hangs at the start of approach with this memory could not be read error. Iām going to try dialing back FSLTL, but I donāt think I can roll back the 737 version. Not sure what else the issue could be. 
Is this the correct thread for this error message?
Interestingly the sim is still running behind the error message, so I have just dragged it to my second monitor and will carry on flying haha.
1 Like
After numerous failed attempts I have decided to reset my entire PC. After reinstalling Windows 10 and a clean install of MSFS voilaā¦ It works.
Feel like it shouldnāt have had to get to that point but it is what it is. My bigest take away is that there needs to be some kind of system that is capable of logging data and producin a suitable crash report so we can better identify why these types of crashes occur. I think that would make things easier for everyone.
3 Likes
To confirm. I never clicked on the OK, or closed the error window, just dragged into to my other monitor, and I continued all the way to my destination with zero problems, no low performance, no fps drops or anything, was all hunky-dory.
If anything my GPU behaved even better when I finally arrived at iniBuilds EGKK in heavy fog, those two things combine can often cause it to struggleā¦
This wasnāt my case last night. FS stayed open but was completely hung. Unresponsive. Audio still going though, giving the impression it might still be doing something but not really.
Itās wasnāt quite a CTD, just a complete freeze. I had to kill FS process in task manager to quit.
Have done a windows System File Checker tool last night which found a few issues and will dial my traffic back a bit to see if itās ok this morning.
I was also experiencing the same memory error, but after opening the computer case and removing the memory and graphics card from the motherboard, I cleaned the metal part that goes into the slot with an eraser and reassembled it. Since then, I have no errors for 5 hours. Iāll test it a bit more.
This may not help, but it worked in my case.
The metal part of the memory looked clean, but I cleaned it by rubbing it several times with an eraser.
probably coincidence.
I didnt get the crash when I turned off live traffic.
Still unable to use MSFS. I get this memory error message, then CTD or just CTD EVERY time I click on Ready to Fly. This started immediately after the last major update. Iāve updated drivers, both Windows and Nvidia, deleted my Community folder, and prayed. So frustrated ā mainly because of no way to get this fixed!
1 Like
note that this topic is explicitly for āmemory could not be readā error
For other issues, like CTD while click on ready to fly , exists other topics, which e.g. mention to clean your app-data, cloud-data, and others.
So just had this issue with the Fenix A320. Flying Budapest to Eindhoven. Used pause at TOD, returned later and after a minute or two whilst entering the metar info on the FMS I got the memory error.
On windows 11.
NVIDIA driver is the latest studio one.
32gb Ram
3080 10gb card
I9 11900 cpu.
MODERATOR EDIT:
This post was merged into the topic.
Thank you using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.
Are you using Developer Mode or made changes in it?
No
Have you disabled/removed all your mods and addons?
Yes, with exception of 78XHEAVY Mod.
Brief description of the issue:
Flying from CYOW to ESSG and when aicraft flies in vicinity of CYBC, MSFS crashes. I do not have any addons in this area. I have WU11 installed. I did the same flight 3 times now and simulator crashed exactly at the same spot all the times. I have Little NavMap Connect running in background and Little NavMap running on another computer to visually check the area when MSFS crashesā¦ Just above CYBC.
When the simulator crashes, I get the following error:
The instruction at 0x00007FF7BF0DCF94 referenced memory at 0x000000000206F770.
The memory could not be read.
Click OK to terminate the program.
Provide Screenshot(s)/video(s) of the issue encountered:
Not able as everything is frozen
Detailed steps to reproduce the issue encountered:
As indicated above, flying B787-10 from CYOW to ESSG using the following flight plan:
TAKOL Q941 ESTEL ANCER N845A YBC N801A DORYY 59N050W 61N040W 62N030W 62N020W 62N010W VALDI REKLI REVTA ULMUG L617 REPKU Y43 XENTA Z132 LATKU L996 KELIN KELI3S
PC specs and/or peripheral set up if relevant:
12th Gen Intel Core i9 12900K, Corsair 64GB RAM DOMINATOR RGB @5600MHz, Aorus Z690 Xtreme Motherboard, EVGA RTX3090, Corsair AX1600i, using Honeycomb Alpha+Bravo, Logitech Pro rudders and Stream Deck XL for flight
If on PC, Fault Bucket ID - Instructions here - Please type in just the Fault Bucket ID # rather than a screenshot for privacy reasons:
No events in the EVENT LOGā¦ could not locate any failure at the time of PC crash.
Build Version # when you first started experiencing this issue:
It is the first time I am trying this flight today and crashed at every 3 attemps.
Running 1.27.21.0
can you share the coords of that point ( e.g. from little nav map ) ? Have you already tried to fly to that coords without a fligh-plan, and different airplane ?
It is literally happening now on almost every flight. I have NEVER had this issue prior to WU11. Nothing has changed on my end. Happens randomly and at random places. So frustrating.
No fault bucket, no pattern to when this happens, no pattern to aircraft, locations, or anything like that when it happens. Nothing.
Specs:
Ryzen 7 3700X
32 GB DDR4 Memory
GTX 1070
1 TB NVMe SSD
Running at 1080p on Medium Settings
5 Likes
Good evening MichaMMA,
I flew again another flight to Sweden with a different aircraft and it crashed again in vicinity of CYBC. The grids I have captured at the time of the crash are:
- 49Ā° 7ā 53.47"N 68Ā° 13ā 19.69"W
- 49Ā° 9ā 33.32"N 68Ā° 10ā 53.59"W
- 49Ā° 9ā 38.28"N 68Ā° 10ā 41.49"W
So I did another flight with the original aircraft (B787) but with a different flight planā¦ This time I flew 52nm n-w of CYCB (49Ā° 45ā 10.37N 69Ā° 7ā3.33"W) and no crash occured! I was finally able to fly all the way to Sweden!!! Slo I think there is an issue with WU11. I have never experienced that behavior beforeā¦
Not sure what else to add to try to get the issue resolved, or at least investigated!
2 Likes