Hello guys,

I also get the message "memory could not be written" and a crash to desktop.

What does it mean, is there any new solution?

I checked my RAM, I do a /sfc scan, I lower my RAM Mhz, lower the settings etc. nothing helped. This message appears roundabout 35 min after T/O during flight.

I'm on Version 1.27.18.0

2 hours ago, mobiel said:

Hello guys,

I also get the message "memory could not be written" and a crash to desktop.

What does it mean, is there any new solution?

I checked my RAM, I do a /sfc scan, I lower my RAM Mhz, lower the settings etc. nothing helped. This message appears roundabout 35 min after T/O during flight.

I'm on Version 1.27.18.0

I had two similar events the other day (su10 beta). This has never happened to me before, nor has it happened since. 

-B

2 hours ago, mobiel said:

What does it mean

It means “Buckle your seatbelt Dorothy, 'cause Kansas is going bye-bye!”. 

Someone has fixed it with a driver rollback:

https://devsupport.flightsimulator.com/questions/7149/ctds-the-instruction-at-referenced-memory-at-0x00.html

You didn’t change anything on your system? They just started to appear?

Then again there has been stability issues with latest beta updates, although most common seems to have been “GPU related” CTD messages.

 

4 minutes ago, Cpt_Piett said:

It means “Buckle your seatbelt Dorothy, 'cause Kansas is going bye-bye!”. 

Someone has fixed it with a driver rollback:

https://devsupport.flightsimulator.com/questions/7149/ctds-the-instruction-at-referenced-memory-at-0x00.html

You didn’t change anything on your system? They just started to appear?

Then again there has been stability issues with latest beta updates, although most common seems to have been “GPU related” CTD messages.

 

Yes I did not change anything on my system.

Sometimes I got "Memory could not be written" sometimes "Memory could not be read"

1 hour ago, Cpt_Piett said:

You didn’t change anything on your system? They just started to appear?

Yes. No new drivers. Only two instances of the error and then no more (so far😄)

-B

I have also received this message and CTD a couple of times in the past week, and not on the beta. Hopefully the next drivers will resolve it.

20 minutes ago, btacon said:

Only two instances of the error and then no more (so far😄)

Fingers crossed then!

I had a CTD in the last week, it it was the first CTD I've had in a couple of months.  It could be related if there was a streaming data problem that hit us all at the same time.

I run SU9 still.  I'm not in the SU10 beta.

The specific error I saw (using Win10's Event Viewer) was a "stack overflow", but I don't recall seeing "Memory could not be written".

For beta testers it's probably not a bad idea to have a look here: 

https://forums.flightsimulator.com/c/sim-update-10-beta/ctds-bug-report-su9-beta/335

Thanks.

I'm not sure whether it is a device issue. I think it is a problem with the code in MSFS

5 minutes ago, mobiel said:

I think it is a problem with the code in MSFS

I think this is not unlikely. Like with the "your GPU has overheated or your overclock has failed" type of CTD message in the recent beta that suddenly a lot of users had. 

Yes I also get this massage sometimes after loading the main menu.

In this case I don't think that SU10 will solved the "read" and "written" memory issues. 

Edited September 12, 20223 yr by mobiel

I'm sorry to say I've pretty much given up on MSFS for now. Since SU9 I've had very little consistent flight time, juct a constant set of niggles. All the problems with the low frame rates at ground level, lots of stutters, CTDs and these memory problems. I had't used the sim for a couple of weeks and tried a couple of short flights yesterday. Clean system, no addons whatsoever, ten minutes into a flight in your basic X-Cub and boom, "memory could not be written" and CTD.

I don't get any such problems reported in any other software, but thought, OK, I'll run a memory check. Ran the basic Windows built-in memory check. Ran for maybe three hours but on completion couldn't even find the event to check the results. Tried again overnight doing the extended tests, but after twelve hours this morning it hadn't progressed more than about 22%, which is about where it was when I packed it in last night. So now running the Passmark test. Seven hours in, halfway through (I do have 64Bg to get through) and no errors reported, as I expected.

If SU10 doesn't sort out at least some of these issues I am going to be one p****d off bunny, with all the time and expense I've put in to this sim. It really has been a case of two steps forward and one back with pretty much each update for me.

When it's playing nice it is simply magnificent. Head, shoulders, heck, even ankles, above everything else. But when it gets into a sulk it's a real brat.

18 minutes ago, andy1252 said:

I'm sorry to say I've pretty much given up on MSFS for now. Since SU9 I've had very little consistent flight time, juct a constant set of niggles. All the problems with the low frame rates at ground level, lots of stutters, CTDs and these memory problems. I had't used the sim for a couple of weeks and tried a couple of short flights yesterday. Clean system, no addons whatsoever, ten minutes into a flight in your basic X-Cub and boom, "memory could not be written" and CTD.

I don't get any such problems reported in any other software, but thought, OK, I'll run a memory check. Ran the basic Windows built-in memory check. Ran for maybe three hours but on completion couldn't even find the event to check the results. Tried again overnight doing the extended tests, but after twelve hours this morning it hadn't progressed more than about 22%, which is about where it was when I packed it in last night. So now running the Passmark test. Seven hours in, halfway through (I do have 64Bg to get through) and no errors reported, as I expected.

If SU10 doesn't sort out at least some of these issues I am going to be one p****d off bunny, with all the time and expense I've put in to this sim. It really has been a case of two steps forward and one back with pretty much each update for me.

When it's playing nice it is simply magnificent. Head, shoulders, heck, even ankles, above everything else. But when it gets into a sulk it's a real brat.

If it were me I would download and run MemTest86.

11 minutes ago, Mace said:

If it were me I would download and run MemTest86.

That is the Passmark test. I'm only running it to prove to myself that there's nothing wrong with my ram and I don't expect to find any errors.