I’ll start off with all the relevant information.
CPU: AMD Ryzen 3800X @ 4.65GHz (70C Load temps)
RAM: Avexir Core 2 32GB (4X8GB) @ 3600MHz 18-14-20-20-38 1T (Samsung C-Die)
Motherboard: Gigabyte Aorus X570 Pro Wifi
GPU: AMD Vega 64 @ 1770MHz / 1150MHz HBM. (36C core / 42C HBM) ((22.5.1 drivers LATEST)
Storage: MSFS is stored on NVME Drive Mushkin Pilot-E 1TB
PSU: CoolerMaster V1300 Platinum
Display: Dell SE2717H
Cooling: Full Custom water cooling.
OS: Windows 10 21H2
I recently updated to MSFS 1.25.9.0. I fly only from South African airports at the moment. I can select any aircraft and any airport. As I click to start the flight it CTD’s. I have NO add ons installed. The game crashes in safe mode as well.
Like I didn’t think of that. OC isn’t the problem. I dont know how many people have said it in this thread and other threads related to the VCRUNTIME140 error. How can a computer, OC’ed or not OC’ed. Run EVERY SINGLE application fine, including applications far more demanding than MSFS. But not MSFS.
EDIT: Also if it was an OC issue it wouldn’t be happening in exactly the same point of game load in EVERY time.
Did you even bother to read my post? Not to be rude. But seriously.
simple try it… then report back. We not need to discuss about issues for OC 'ed systems, because we can never be sure that it is not your OC.
We have a huge topic about VCRUNTIME140 , where it was caused from mods (e.g. garmin replacements - but should not relevant for you ) or hardware issues caused from OC or driver stuff. I remember rare cases it comes from invalid cloud-config or where users former had google-maps-replacement installed. ( edit: and I forgot completly the issues caused from anti-virus tools )
Well that link to download the VCRedistributable might have provisionally done it. I don’t know how many time I removed and reinstalled and downloaded Visual C++ but to no avail.
I removed them AGAIN. probably 5th or 6th time at this point and reinstalled using that package and I just loaded into a flight. I have not tried flying. But I wasn’t even able to load into a flight. I would always crash on the loading screen as you selected “fly”.
before you continue with your finger pointing.. had you in meanwhile time to check a revert of your OC ? ( sould take 5 minutes ).
Also.. which version of vcrtuntime you have installed now ?
And have you tried the common things, like disable anti-vir etc. ? Remove rolling cache file, etc. ?
And to be sure: you never had installed former google-maps-addon and you also removed the folders which e.g. the “working-title” mods created outside of the community folder ?
PS: and yes.. windows 10 works fine and much more stable as these win11
2 hours into flight. Just about to start descent. Crash to desktop. No 1001 event log. The only thing that shows up in event viewer at the time of the crash is: Event ID: 16384, “Successfully scheduled Software Protection service for re-start at 2122-04-22T04:09:47Z. Reason: RulesEngine.” Don’t know if it has anything to do with the crash, but FS2020 once again proves itself to be a joy-killer.
EDIT: Interestingly, I just restarted FS, there was no notice that there was a problem and no option to start in “Safe Mode”. This is a first.
I’m experiencing CTD since Sim Update 9 Hotfix patch 1.25.9.0 (previously to that patch MSFS 2020 was stable and working fine - after the hotfix it is unplayable: CTD when loading or CTD well into the flight. I’m running Win10 21H2 (keeping it up to date) and flying the Milviz 310r). Very disappointing hotfix …
This is the following Event Viewer details:
Faulting application name: FlightSimulator.exe, version: 1.25.9.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.25.9.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x000000000206a89e
Faulting process id: 0x4450
Faulting application start time: 0x01d86919df3961bb
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.25.9.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.25.9.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: 7842778c-17cf-41be-bd2a-ae3fc88bab2a
Faulting package full name: Microsoft.FlightSimulator_1.25.9.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
Well, I have to say that this is by far the worst hotfix since MSFS 2020 started - let’s hope they fix it soon.
may be… it is , as mention in report, the service “Software Protection” which verify the activation state / license of e.g installed software ( also windows itself, so far I remember ). If that thing not works, you get may be strange issues.. I remember it can also let restart the pc…
Try the usually checks like sfc /scannow ; DISM /Online /Clea…
I’d like to chime in here, Ive got a 6900xt GPU and have been having constant driver timeouts when idle in the 3d globe map. Ive tried down-clocking my ram (No XMP) disabled all CPU turbos, forcing my GPU to work at its base clock and not boost. Reinstalled windows and only had vanilla msfs with 0 addons and 0 Programs except msfs.
I have ran prime 95 & furmark together for 24 hours (100% usage on cpu (5900x), gpu and ram (32gb)) , no crashes. I have ran memtest86 for 12, also no issues.
This is without a doubt a problem on microsofts part with AMD cards in my case.
thank you 
