LarrySinNJ

I probably get a CTD on >50% of the flights I start with the same faulting module - ucrtbase.dll.  This never happened prior to retail release.  I will get the crash usually during flight, and not when I am interacting with the sim.  Sometimes I get the crash when transitioning from the flight setup to the sim itself.  I have tried virtually all of the suggested fixes, driver updates, run as admin, reinstalling VC++ libs, virtual memory changes, etc.

I even did a clean boot, started the sim, created a flight and got the plane on the runway.   And then went to sleep.  No one interacting on the PC.  The sim crashed at 1:00AM.  No one touched the PC for 2+ hours. 

So odd...

[Edit] - and two three more CTDs this morning...

 

Well if it helps, I got back into simming recently with FS2020, and I am getting consistent CTDs in FS2020 with ucrtbase.dll errors.  Tried pretty much everything except a full windows reinstall which I won't do.  

1 hour ago, CarlosF said:

Are you OC your video card?

I don't know if this will help, but I too had CTD consistently while flying, sometimes during approach/landing, other times while changing settings, found out that the OC settings (MSI Afterburner)  were a bit too high for MSFS, same settings worked fine for XP, I guess MSFS is more demanding, anyway once I set settings back to default, no more CTD.

 

 

Nope Carlos, no overclocking.  CPU or GPU...

Didn't help me.  Still get CTD consistenly, usually when flying, occasionally when going from setup to flight.  Pretty much always due to ucrtbase.dll

Here's the error I get:

Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x5f467af2
Faulting module name: ucrtbase.dll, version: 10.0.19041.488, time stamp: 0x0d8057d8
Exception code: 0xc0000409
Fault offset: 0x0000000000071218
Faulting process id: 0x584c
Faulting application start time: 0x01d688525f40f8a4
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.7.14.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report Id: 36eb593f-ee95-4733-9fdf-f43f3a878d2b
Faulting package full name: Microsoft.FlightSimulator_1.7.14.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

I get CTD usually in random flights, occasionally from setup menu going to flight.  Event viewer generally shows the faulting module as ucrtbase.dll.  I have been through most of the suggested solutions including uninstalling and reinstalling the C++ libraries, updated drivers, and suggested in-game settings.   Nothing has worked.  Since I get this error consistently, I'm guessing there is an issue with a C++ function, as opposed to driver, overclocking or peripherals.  I've been through the flightsimulator.com forums, with no luck. 

Any ideas/suggestions appreciated...

Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x5f467af2
Faulting module name: ucrtbase.dll, version: 10.0.19041.488, time stamp: 0x0d8057d8
Exception code: 0xc0000409
Fault offset: 0x0000000000071218
Faulting process id: 0x828
Faulting application start time: 0x01d6884309c3a479
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.7.14.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report Id: 9ac4e918-a0e7-43fd-9ec7-7e3c07d6fbe2
Faulting package full name: Microsoft.FlightSimulator_1.7.14.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: Ap

An overclock would help, all you would have to do is get a decent cooler for the CPU. You should be able to get that thing to 3.0 fairly easy. The Q6600 have been known to go to 3.6, but that takes some effort.

I have the stock Intel cooler now. I'd love to find the right cooler that won't require a bracket on the underside of the motherboard, as I really don't want to disassemble the entire rig.

Have a 2

Running Vista 32, w/ DX10 and Aero interface. Whenever I start FSX,(now with Acceleration), I get a message that Windows is changing to Window Vista Basic Color Scheme, and the Aero features don't function. In FSX, the DX10 Preview is checked.Is this correct??

Finished building a new PC, with virtually no issues. Running Vista Business, FSX SP1. Set up my first Delta flight from KBOS-KEWR, and when on final about 2NM out, I get an FSX Error saying that I have run out of available memory. 2GB RAM + 4GB Swap shouldn't kill the program, should it?