I read about ReShade issues which cause same, but I assumed / hope that we doing test-cases here with all that tools disabled 
1 Like
IM sorry I meant under the traffic tab aircraft traffic type is to set it to off.
Well. Yes and no. Iâve tried extended periods in vanilla. Still CTDs.
I use it the same way. Currently in a vanilla flight as I want to test something else as well 
Until I got the CTD again⌠
Yeah, was afraid of that. Would be easier if you also had same issues. Why do I get âmemory could not be readâ with shaders and you donât? Why do you get it without shaders I donât?
the exe.xml is generated when you install additional programs for example when you install FSUICP and not from MSFS2020 when you start it
I have currently removed everything I donât really need so you can also start the programs manually and maybe you will find the cause for the CTD if it is an external program that is causing this.
I do. Normally I run the sim with addons and ReShade. And I get CTDs. Vanilla sim = still CTDs. But I havenât used the sim only in vanilla for the last month or so, since I started getting the CTDs. Because I want to use the sim for other purposes than testing 
I checked what you said and replaced drivers, but still getting this error from time to time. So this audio thing is not the fix for all memory could not be read errors.
Another thing comes to mind @MichaMMA. How long do we have to run the sim in vanilla mode to be sure we are not getting the CTDs. This is tricky as this type of CTD is very elusive and intermittent. I could set up the 787 for a 12 hour flight, go to bed and wake up to the aircraft still in the air. Then go do a quick spin in the 152 and get the CTD after 3 minutes. Of course Iâm exaggerating here to prove a point.
It is the solution to the problem âMemory Canât Be Read at 0x000000â. It is NOT the fix if there is some address other than a bunch of zeroes.
Iâve walked over a dozen people through the fix. Can you send a picture of your Windows - System - Sound screen?
Ok, there I might be wrong then! For me it wasnt just a bunch of zeros
Oh, well. Canât be much help then..sorry.
Mine ends with the number 8?
May I risk a suggestion for those having this âmemory cannot be readâ error, to run a memtest86 in your BIOS to check the integrity of your RAM. This error is - generally - linked to faulty RAM and may not necessarily caused by MSFS. Also check your error report in Windows under âHARDWAREâ (it is in bold and not sent to Microsoft because it is obviously not something they can solve at their end), if you find your error(s) reported here, chances are that it may be your RAM.
Maybe run a search for âmemtestâ on this thread and you might see that it is not the first time it has been suggested, tried and reported back on.
From memories of a fair few months of reading this thread, some people have actually had errors reported, a lot have run it to find no errors at all, yet both groups still suffer this CTD.
It is an odd one for sure.
1 Like
I guess the error is the same in Steam and MS-Store, right?, I am in MS-Store.
I downloaded âReshade for UWPâ and made my own .bat-file with FinalLight-reshade (also added Lumasharpen from all the Reshades you get when downloading the program ). Looks better than ever now! No more âmemory could not be readâ.
Sorry for getting away from the subject, but this seemed to be the cause of my memory-error.
Su9, Dx11, Nvidia 512.95
2 Likes
Thatâs very interesting. Yet again Iâve been running the sim as vanilla, and it seems stable. I usually just take off with full tanks and leave the sim running in the background.
Not sure if I understand you correctly though. Are you saying that you had the memory CTDs with ReShade, but then found a fix to be able to use it? In that case Iâm extremely interested
Could you elaborate a bit more on the .bat you made and how you got this working? Or perhaps if youâre on Avsim we could continue the discussion there in the recent ReShade thread.
@TjejKalas @CptPiett8113 If no response are you both in MS-Store version?, I did a search and I did not found nothing of version in this thread, I guess that was already answered and I do not remember that, though I didn´t found it with google.