Hello everybody,
I have crashes to desktop near big cities. I was hoping that somebody with experience with these matters can help me solve this, for as much as possible. To do this, I describe the problem and then will give you my own ideas what could be the problem. But before I go and try to solve this, it is better that some of you with more IT knowledge then me give me advice about this.
Here is the problem:
-
Today I had 2 CTD’s, one above Brussels and one above Antwerp. For one of these cities I also download a big scenery package of 1,7 GB or so.
-
My system specs are: I9-9900K 3.6Ghz, but o’clocked to 5.0 Ghz, a MSI GTX 1080 with 8 GB (not TI) and 32 GB RAM, and I am running MSFS of a sata SSD of 2T.
-
Before the crash, I was having an FPS of around 23 or so, with some ups and downs. At one of the CTD’s I was using Navigraph as external app, so I thought that was the problem. But at the other CTD, I was just flying and it crashed.
-
I use FSLT, Sky Dolly and some addon scenery also.
So what can be causes of this problems?
- I think, that perhaps my system can not handle my current display settings. But, I do not understand, how you can know, what a good, save display setting is. Because with 23 FPS or so, I still think it is flyable. And of course I like maximum beauty. So I want to set the display settings lower, but my questions then is, how do I know what is low enough, to make sure that no more CTD’s occur? What FPS should I on average have above big cities or big airports so that I know that my settings are low enough, so that I avoid CTD’s?
2 Perhaps my O’clock is causing this CTD. But then, it is a pretty stable O’clock, because I having been playing Farming Simulator 22 for hundreds of hours, with no CTD’s. So can this be the problem then?
-
Perhaps, my virtual memory runs out. But I do not even know what that means, but I read that on the internet that that is a problem that can occur. But how can I avoid that? How do I know that? I attach a screenshot of the Event viewer. You see that the exception code of the CTD was 0x80000003 and the fault offset was 0x0000000001f422e2 Perhaps this indicates something?
-
I am running MSFS of an SSD sata harddisk, perhaps that is the problem?
Anyone any solutions?
So you see, I want to set my display settings lower, but I do not know how much. I want to try to not o’clock my computer, but I do not know if this is the problem even. I want to solve the possible virtual memory issue, but I do not know what I am doing even. I want perhaps in the future by another SSD NVMe or so, but I do not know if this is the problem.
So perhaps somebody, with this problem description, and these possible causes, can give my some kind of steps to take to resolve my CTD issue, or some information that is useful in my situation.
Also perhaps it would be wise if there is somewhere another log that shows what causes the CTD. I attached the screenshot of the Event Viewer, but perhaps there is another clue somewhere else?
Because I am enjoying the beauty of MSFS, so I would rather not set the display settings very low. But the problem is really, that I do not know how low I should go.
Hopefully somebody can help me avoid CTD’s in the future. They really make me sad when you are in a nice flight, because it feels you have wasted your time. So it would be nice if I cannot have any CTD’s anymore.
Happy New Year and greetings,
Boudewijn Nijssen
