CTD After 8 Hours

How do we fix this. It happens after about 8 hours of flying. I have doe the NDU thing and my drivers are all up to date.

Very frustrating Asobo

Faulting application name: FlightSimulator.exe, version: 1.26.5.0, time stamp: 0x00000000
Faulting module name: KERNELBASE.dll, version: 10.0.22000.778, time stamp: 0x5f5438c2
Exception code: 0x80000003
Fault offset: 0x00000000000f90e2
Faulting process id: 0x24f8
Faulting application start time: 0x01d88e7712595e24
Faulting application path: D:\Steam Library\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 9d97c7b4-c6e2-4d1b-b6ba-fe84be9d6f53
Faulting package full name:
Faulting package-relative application ID:

How do we fix this?

If your running an intel processor you might want to try whats on this page:

BTW when you ask for help, it helps people to help you if you let us know what processor grahics card, memory, operating system etc you have.

Intel I7 9700K
EVGA 2070 Super GPU
32GB DDR 3200 RAM
Windows 11
I currently have Intelligent Standby List Cleaner installed. Also I am hearing this ois a memory leak error. This issue has plagued me since SU9 update.

you not need that, it can also cause issues like you get if you clean-up the memory while a application is running ( can , not must, as always ).

But dont forget: possible for kernelbase.dll can also be a system issue, like overheating ( in special after 8h ).

Otherwise lots of reasons are possible. You can use the forum search function with keywords like “KERNELBASE.dll 0x80000003” , may be you find a possible hint within the existing topics.

Yeah Id check out the post above, install the program, set it up, and run it. You also may want to click of speedstor and see if that makes a difference…at the moment turning off speedstor helped a bit for now it seems, but again its MSFS what works this time might not work the next.

I’m gonna say 6% loss is not the answer.

1 Like

I really hate installing programs that supposedly fix a problem that Asobo and Microsoft need to fix.

They seem to cause more issues.

Here is the next line above the error.
Fault bucket 1293028787197923626, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: FlightSimulator.exe
P2: 1.26.5.0
P3: 00000000
P4: KERNELBASE.dll
P5: 10.0.22000.778
P6: 5f5438c2
P7: 80000003
P8: 00000000000f90e2
P9:
P10:

It wasnt here, but then I have an old processor i7-6 but it still lets you set other stuff that may or may not help, you can turn off speed step without going into the bios, there are tweaks for nvidia and ati cards, so its not useless.

And its not the actual loss, its that when the program needs to use one of those registers, its busy more then likely forcing MSFS to re broadcast the process.

I used to have CTDs after long flights, which I fixed by disabling the rolling cache.

Mines has been disabled for a long time.

I also use an MSI Afterburner profile to cap my GPU’s power to 50% of max during the cruise phase of longer flights, so that my PC is effectively “cruising” during that time. This drops my GPU and CPU temps to around 50C each and saves around 175W consumption too. I return it to 100% when commencing descent.

That is an interesting approach … if you have time please fill in your profile with a brief system spec (it will force you to select a platform once you do enter to alter it FYI)

1 Like

Profile updated.

As an aside, the 50% power profile gives me 25+ FPS, even in VR, so I can still interact with the aircraft and use external views and it still looks good. If I am going away from my computer for a while, I also have a 40% profile which drops power and temps slightly further and drops FPS to 15, around the minimum for keeping everything ticking over.

1 Like

This happened to me last night. I was flying a VATSIM event and everything about the Sim ran absolutely fine for 8 hours 20mins. On approach to WSSS at around 1500 feet, the Sim started to stutter for a few seconds, recovered and continued normally until 200feet before touchdown. Then froze for about 10 seconds and CTD. Default scenery, No rolling cache active, Headwind A330 with stock livery, LittleNavMap, Navigraph and Vatsim open. Used Pushback Toolbar at the beginning of the flight. No other external programs in use.

Specs:
AMD Ryzen 7 3800X
32GB RAM
RTX2060 Super

Any number of things can cause that sort of error. Typical things that would cause it include:

  • random external factors, the neighbour firing up his MIG welder and putting spikes on the neighbourhood power grid for example
  • memory leak that gradually uses more ram until you eventually run out
  • other resource leak (file handles etc) that eventually becomes critical
  • faulty ram in the upper registers that does not show as an issue until you use most of your ram
  • heat issues
  • driver issues

Follow the following steps…