Fsx Crashes After 30 Minutes

[Sebastian Thorndike]

I am currently staying on version 522 and everything is stable. Updated to the latest version and there were crashes after 10 minutes. I had to roll back to 522. I hope this will be fixed in the future

As I remember, I could play the game for around one whole hour yesterday before it became freezing, and after I took the advice of updating to the latest NVIDIA version, it decreasd to 15-30 mins. Holy shti.

After the last update whenever I try to play or spectate a ranked multiplayer game, the game crashes after almost twenty minutes of playing or spectating, without giving any error messages.
I have Windows 11 with the latest updates and the latest graphics drivers installed.
I have a Core i5 12600KF with 16GB of RAM and a Nvidia GeForce GTX 1060 3GB.

What has always been an issue with this game since its release is the virtual memory or pagefile size, go to settings and increase it, random crashes and invisible farms were all related including invisible units in early builds.

well, the update is producing another issue. When I open any skp file it tells me the file is already open by another user. It is not. I am the only user. I must say no and open it again. Then it opens. This occurs with any file I open even if I had it open, closed it, and try to reopen.

I disabled all the extensions that I added from the beginning till after the crashing occurred.
No help. I have now disabled every extension shown. No conclusion yet.
The issue with already open is still present - I never got that error with the original install.

UPDATE: It appears that the lock issue is mostly - maybe only - occurring after a crash now.
Hard to keep my mind on it, it is so aggravating. The crash seems to be occurring mostly when I am moving things around.

Locking can also be a permission issue with an overly protective OS. People opening a file from an email or thumb drive can get the same read-only message. In those cases, the OS sees the file as foreign and possibly dangerous so you only get a read-only. Doing a Save As in SU with another name and to a location on your HD makes the OS happy.

Disabling hardware acceleration is a troubleshooting step - not a cure. OpenGL is composed of a set of function calls. Driver developers may leave out a few critical function calls required by SU. Each version of SU uses the driver differently, so you may have a different working experience with different versions of SU on the same machine.

Look at your NVIDIA control panel. You should be able to access it by r-clicking on your desktop. Go to 3D Settings > Manage 3D settings. What is anisotropic filtering and Antialising mode set to? Are you relying on the settings to be globally set or do you set special settings for individual programs?

I still have the crashes in 2.685 - what it does is to go into a save mode USUALLY during a move operation. MOST of the time it will crash but not always. If it does not crash it takes a very long time - 30 to 60 sec to come back ready. It creates the temp #.SKP files, sometimes a number of them, and the autosave file, then crashes.
I open the autosave file and continue. The biggest issue is that I loose all the history so I cannot undo things.

At the start of this thread Marc, who had had a glance at your Bugsplat reports, said that to him it looked like the crash was related to plugins. You had a few of them installed. Are they all new, 2015-specific versions? Have you tried disabling all plugins, and, if crashing stops, bringing them back one at a time to see id it resumes?

I hop into the F/A 18c in the free flight mission in Caucuses, start heading inland at below 2000 feet and I will get black flickers on my screen. These flickers will intensify and then my normal desktop will show, with DCS on the taskbar and the crash report thing pops up.

Do you have the Corsair iCUE software installed? Recent testimonies showed it could lead DCS to this kind of crash. If you have it, close it before playing and see if your crashes keep happening.

One thing to note, I am seeing 15-20 less fps with the exact same graphics settings as before, no problem tho as I only have a GTX1060, and can only expect such performance. (mostly high settings and 40-50fps.) I'll fiddle around and see what I can figure out.

Now on to the crashes, after a new Saved Games\DCS folder, if I leave the graphics setting at their default (mostly low) I can fly for 30 minutes maybe a bit longer then some black flashes will start, not many and they will not intensify. DCS will not crash, but once every 20 seconds or so I will get a black flash. This only happens when flying low, under 2000 feet, when cruising around at 25'000 feet no flashes whatsoever.

With a new Saved Games\DCS folder, setting my graphics to where I like them (mostly high) game will crash after 15-20 minutes of low flying. When the flashes start and I get up to 25'000 feet, they stop and game will not crash.

I set my graphics setting to my preferred settings, fly around fairly low and take note of my fps. When the flashes start I exit DCS, go to NVidia control panel, and set my max fps to approx 5 less than what I had in DCS. In my case I set it to max 45fps, this so far, has not caused a crash or any black flashes. I did however go and enable the G-Sync compatible setting for my screen, just to make the 45fps look/feel better.

After letting DCS make a new Saved Games\DCS folder, game will not crash until 20-30 minutes of low level flying. (Low level is more demanding on gpu) After the 1st crash, game will crash with only 1-2 minutes of low level flying. This I can reproduce consistently.

It doesn't matter which graphics setting is where, if my gpu will be running over 95%, I will get the black flashes followed by a crash. Currently I am limiting my gpu usage by setting a max frame rate, and that works, however with draw backs. If I fly up high its nice to have the 80+fps, but if I cap fps for low level, I cannot enjoy the higher fps at higher altitude.

I immediately ran the heaven benchmark and it almost made it through the benchmark test. At scene 24 of 26 mostly green flashes appeared and benchmark closed down with no error message. Haven't had this issue with benchmark before.

Looks like it could be a hardware issue here, I wonder if its the PSU not giving enough power or the GPU starting to die. Both are approx 4 years old, and have run without any problems whatsoever. Why it started to happen after the update to 2.7.2 I don't know.

Another thing that I noticed right away, there is virtually no stuttering now, I would get the occasional stutter here and there, only time it really bothered me was during air-to-air re-fueling or the 5 seconds prior to touching down on the carrier. I get 50 fps flying low, and 80+ up high, with the settings I set in MSI Afterburner I would say I am getting 2-3 fps less, but I don't notice it, in fact without the stutters it feels smoother.

I think I'll leave voltages and frequencies alone for now. I just don't understand enough of it. DCS is remarkably smoother than its ever been for me, to get these frames in DCS with an entry level graphics card I've always thought is pretty amazing. Now with virtually no stutter, AAR and carrier landing got much easier, I got nothing to complain about.

DCS has such a great community. I have played lots of Battlefield, and way too much Counter Strike (CSGO). CSGO I had to completely quit because of its community, almost seems like it brings out the worst in people. Battlefield I played for the planes & jets, but after DCS it feels pointless for me.

The only thing that actually comes to mind is that I have 2 Dark Core Pro SE Mouse's and the ones is running through my Virtuoso SE Dongle on Multipoint and the other is using the original Dongle but plugged into a a USB expansion card below my GPU and that the only thing I can think that has changed other then the update.

While I can't offer any concrete help, I can say that my computer, updated to the same version, also crashes within minutes of this error. I also have a Dark Core RGB Pro mouse that is paired to the computer using the dongle of the Virtuoso SE. I also noticed that sometimes ICUE doesn't start synching after booting like it normally does.

That error actually shows that iCUE itself is not the cause of the crash but rather something else you have installed. This specific error happens when you have extremely outdated third-party software installed and running causing a conflict leading to a crash. You will also most likely notice other Application Error events also showing system level DLLs as the faulting module for crashing applications.

NTDLL.DLL exports the Windows Native API. The Native API is the interface used by user-mode components of the operating system that must run without support from Win32 or other API subsystems. Most of this API is implemented in NTDLL.DLL and at the upper edge of ntoskrnl.exe (and its variants), and the majority of exported symbols within these libraries are prefixed Nt, for example NtDisplayString. Native APIs are also used to implement many of the "kernel APIs" or "base APIs" exported by KERNEL32.DLL.[3][4][5] The large majority of Windows applications do not call NTDLL.DLL directly.[6]

So what the error actually suggests is that iCUE is making use of ntdll - either directly or indirectly - to perform its functions. It also suggests that iCUE is doing so in a manner that creates the fault (e.g. a memory leak).

I'm not a coding expert, but I write and compile my own executables and dlls - all making calls to Windows DLLs to have a rudimentary understanding of the issue. I suggest Corsair stop blaming other software and examine their own code making calls that eventually reach ntdll (note that iCUE doesn't need to make a call to ntdll directly - other DLLs used may take a call from iCUE and pass that call to ntdll).

I have a Quest 2. When connecting it to the PC via Link cable it works perfectly fine for about 10 minutes and then it crashes. When it crashes there are some artifacts on the Quest, kind of like a line that glitches over the screen and the rest of the images are still. The software (game and rift software) on PC runs perfectly fine without it crashing, indicating that its not an issue on the game itself.

c80f0f1006