How do you do a clean install of the driver?
i have the same issue but i have installed FSLTL for the trafic (50 for IFR aircraft and 4 for static aircraft), i have a GTX 1080 but in the next few day i change for a RTX 3080 I donāt know if this will solve the problem but I will feedback.
1 Like
My issues started when I started using FSLTL, not sure if that is the cause as I havenāt had a chance to fly without it and test.
1 Like
When you are installing the driver, thereās a button called customize, inside it you can select the clean install, they remove old version drivers from your system and install a new one.
1 Like
I have the same problem since I installed FSLTL yesterday, on two flights two CTDs while everything worked fine with update 10
I can confirm this.
I did 4 Flights today with FSLTL and 4 crashed today. I did futher 2 today without FSLTL and none crashed.
All 6 flights the same route, runways sids and stars (EDDF - LFKB) and same plane, procedures, etc.
FSLTL Injector was updated very early this morning, not sure if this update causes the issue.
I will do 2 further flights without FSLTL and see what happens. But I am pretty sure itĀ“s FSLTL.
2 Likes
From their discord about todays update 1.1 (meanwhile updated to 1.1.1):
Bug Fixes:
- Renamed Toolbar components to prevent conflicts with other addons hopefully reducing the number of CTDās caused by FSLTL (ā¦)
Shortened, because this thread is not about FSLTL but memory errors.
1 Like
Strange thing is that I just changed the settings related to OC for CPU and MEMORY in CMOS setup to default. I think all the CTD disappeared. I am not sure which one (over clock for CPU or memory) caused the problems. I think I need some more test flight.
CMOS for Gigabyte board
- CPU Upgrade: set to default
- Extreme Memory Profile (X.M.P.): set to Disabled
This is what helped me when I had these CTDs - reduce all types of overclocks - GPU, CPU, RAM, VRAM. They would still occur, but much less frequently so I could actually use the sim (was even able to complete a GA world tour, lol).
Which probably indicates that overclocking is not the only thing contributing to the likelihood of getting this CTD, along with all of the other potential solutions that have yielded some, albeit temporary, success.
I should be getting bored of saying this, but the problem really needs to be diagnosed and solved by MS/Asobo.
3 Likes
Indeed. But as I really like this sim, I tried āeverythingā to make it as stable as possible while waiting for an official solution. This thread is a great example of user support. However with trying all sorts of ātweaksā, thereās also the possibility of introducing more problems to the OS/sim. So itās a bit of a risky process.
2 Likes
for me too
1 Like
I confirm, as soon as I use FSLTL, I have crashes especially on approach, I tried without FSLTL with the default traffic and everything works fine, I have updated version 1 1 1 of injector and even when lowering the ultra. I specify that I have rather a good config to run the sim.
1 Like
I just completed a 2hr flight using FSLTL the entire way, with no CTDs at all. I canāt say the update to the FSLTL injector fixed the issue for me without flying a few more times, but Iām glad at least this flight was successful!
or it could be that another addon, any addon, loaded into memory when MSFS starts, changes the chances of this memory-related issue occurring?
Well I had never had this error before using FSLTL. I installed FSLTL and then I get the memory error 3 times in 3 flights. Seems more than a coincidence to me.
If you read the whole thread, you will find that other addons have been implicated, yet removing them does not totally remove the problem, even though it might initially appear to have done so.
Also, again before FSLTL was released, people have also changed their hardware setup, removing XMP/overclocks etc, yet again a period of no errors doesnāt last very long.
I suppose it is possible that another type of āmemory could not be readā error, looking like the one that started this thread, has arrived with FSLTL, but it does look to be exactly the same issue.
Yes, you are right. Itās the matter of frequency. less CTD but not the solution. Now I cannot even finish a short flight.
Hi,
I havenāt had this RAM Error message since SU10 Beta.
Now just now I had this RAM error again for the first time in SU10.
Iāve been using FSLTL since the first day and until today there was no problem.
I am not sure if it is due to FSLTL.
But I was really happy that I didnāt have this RAM error anymore since SU10 Betaā¦ Again very disappointing that the error is still there
Iām really afraid that it will be here until MS/Asobo fix it and they donāt appear to be in too much of a rush to do so.
It does look like its chances of happening can be affected by anything that changes the memory imprint of MSFS and/or changes in demand on the MS servers, but either way, I think that it is highly unlikely to be caused by a bug in any of the addons that have been previously implicated. It might be affected by the fact that different addons are loaded however.
A real PITA issue that needs to be sorted, once and for all.