I’m saying that it’s important to keep the computer cool, and well within the thermal, voltage, and power limits that stress high quality hardware.
Also, that the debloated Windows install may be a fundamental reason mine is running as stable as it is. Look at the components (checkmarked) that Windows was installed without:
As for 24H2…I only know what I’ve read, which tell me that it’s problematic.
Ok, I’ll take a look at this but I know my hardware is nowhere near overheating or remotely getting hot because I get the crash the moment I turn my pc on and load the sim up, always seems to happen as soon as I taxi to the runway. But hasn’t done it for the last 250 hours of gameplay. Hardware is as follows
I7 12th gen 12700k
64gb ram
Nvidia 3070ti 12gb VRAM
Running windows 11 on the new 24H2 windows 11 update.
The first rule of troubleshooting something that has been working for 250 hours, and suddenly stopped working is: What changed?
If nothing has changed, then you have to start looking into possible hardware component failure. That can be difficult.
What model power supply do you have?
This is what I started doing and recently updated my RAM from 32 to 64 but still having the same repeat issue… all other games are fine though including x-plane 12 and dcs and other large title games it’s just 2024 that is being weird.
Nothing else has changed, I’m running vanilla game nothing in community folder.
PSU is a Corsair 1200w
I believe there are multiple causes of this behaviour. The things they have in common - screens go black, all input stops, only resetting the PC gets you back, and if you leave it long enough it will BSOD and restart - seem to be a result of a driver crash that takes down Windows. But which driver, and why it crashes, I think is variable. And why it’s seemingly MSFS 2024 that triggers the driver crash, I suspect is at the root of the problem and is what Asobo needs to reproduce, diagnose and solve.
In my original case it was related to my Intel network card, and updating the drivers for that seemed to fix the problem. I always had 64GB.
Since I’ve switched from an Intel to an AMD system, I’ve had no issues of this kind. Not that I’m suggesting going AMD is a fix, but I think it’s specific drivers for specific hardware that is the root cause of the crashes, they’re just being triggered by MSFS 2024 in some (weird) way.
It’s so tough to troubleshoot driver interaction problems, just like it’s hard to know why my system runs basically trouble-free.
Event Viewer can sometimes help, but when all you see is ‘Faulting Module xxxxxxxx, flightsimulator2024.exe’ it tells you basically nothing. I’m guessing there’s more information available, but I don’t know how to get to it.
Updated system BIOS and chipset drivers are important, of course.
If it goes all the way to a system crash, and you let it do so rather than resetting the machine, you’ll get a minidump file generated as part of the BSOD process.
There are several tools available for free that will help you analyse the minidump file. This will, among other things, tell you which driver it was that faulted. That’s how I found out it was tcpip.sys in my case, which led me to my NIC drivers.
(Note that the faulting driver is not the same as the faulting module which you might see in Event Viewer.)
I had something similar happen to me.
Periodically - but especially at installation - I would hear a buzzing sound through the audio for about 20(±) seconds, then it would hard crash to either a reboot or a hard-halt state that required a full power-off at the PSU back panel switch with a minute or so wait.
There seemed to be no rhyme or reason, so I tried a few bios tweaks - no change.
So! I decided to pull the system apart, check the heat-sink compound on the processor, (yes, it can dry out over time), and decided to change it. I also cleaned the contacts on everything I plugged into the MoBo - RAM, video card, M.2 SDD cards, (two of them), a couple of PICe x1 interface cards, etc.
Then. . . .
Good old Mister Murphy decided to drop in for a cuppa’ tea and cookies - and - I slammed my motherboard with a tool trying to put the processor heat-sink back in place! Busted a bunch of traces and I couldn’t repair them so - $120 USD later I had a new, (slightly upgraded) motherboard.
Note that this is a Gigabyte 550 Gaming X Pro AM-4 socket MoBo with a Ryzen 5800 (?) X3D processor, so it’s not exactly bleeding edge.
I upgraded the BIOS on the new MoBo to the latest rev, made sure I downloaded the correct drivers for the new MoBo, and put things together.
I set the following settings in my bios:
I did NOT set:
In the Windows Power Management settings I set:
Within the “Change settings for this plaln” settings, I set:
Within the “Change advanced power settings” I set:
Click “OK” to save, close all windows, and reboot to make sure it sticks.
In-game settings:
I set the in-game video graphics settings to the defaults chosen for me at installation time except that I turned off all references to ray-[something], I enabled VSync at “100% display frame rate”, and I set TAA (Temporal Ant-Aliasing).
Set everything else as you see fit.
This is what worked for me. Maybe my MoBo was on the hairy-edge of dying anyway and maybe the slightly better MoBo solved a lot of problems - I don’t know. However, this is what I have set and things are working much better for me now - no CTDs (knock wood!) and no more crashes to the bios or hard halts.
I hope this helps.
Set any other choices you wish.
Another thing:
If you had your system hard-crash to the bios, you should do two more very important things:
An off-line chkdsk on your system drive as well as any other active drives in your system. Run the following within an administrative command prompt and after running this, immediately reboot. If it finds errors, repeat until no errors are found.
chkdsk [drive:] /F /V /X /sdcleanupAfter the final reboot after running chkdsk on all disk drives, run the following from an administrative command prompt:[1] (While connected to the Internet!)
DISM.exe /Online /Cleanup-image /Restorehealthsfc /scannowNote that both DISM and SFC can take an extended period of time to complete - possibly even hours and hours - depending on the condition of your machine when you run them.
Also note that you should re-run DISM if it finds any problems and repeat running it until it completes without any issues. SFC follows the same rules: If it finds issues, reboot and re-run it (along with DISM), until it finds no problems. Once you get both to run without difficulties, reboot your system and run it one more time just to make sure. You are not finished until you get two successful runs in a row with an intervening reboot.
I would recommending saving those two commands as a script, (or save the script I published here: FPS performance - VRAM bug? - #1519 by Jimrh1993), and periodically run it on your system (again from an administrative command prompt).
I keep this on my desktop and run it about once a week or so as soon as the system has booted to the desktop, (and settled down), I reboot again and I’m golden. So far, after I replaced the MoBo, I’ve not had any issues with this aside from the first check after installing the new MoBo. (knock wood!)
Try this and let me know what’s happening.
==============================
Additional note:
If you run this periodically and find that it’s finding and repairing problems again and again without any known reason, there is something seriously wrong with your system.
I’d check:
==================== Footnotes ====================
Was able to start and complete some career missions and also several freeflights. Then after an update to allow more 2020 aircraft to be used in the game started getting major crashes. This popped up:
Any help would be appreciated. Did perform the DISM with no positive results.
Did you mean “with no negative (fault) results”?
Did you run SFC? How about chkdsk?
If both DISM and SFC ran without reporting errors and a chkdsk is clean, then you have hit one of the many bugs in MSFS-2024 - and I would start a separate thread for it.
Still, keep an eye on the DISM/SFC to make sure that there are no intermittent problems messing you up.
Sorry, no positive results as in being able to start a flight. This happens after an aircraft, weather, airport selections are made. The plane take a brief bit to spawn on the runway, then start the flight and almost immediate system/program crash before take off.
The actual game boots just fine, even received the update what, a day ago?
Exactly what aircraft and exactly where?
Pilatus PC 12, Daher TBM 930, Cessna 172. The TBM 930 also randomly changes livery without any input.
All USA… KSAN, KSEE, KPSP, KTPA, KPIE, KIND
Thought it might have been airports so tried a variety.
Was able to complete a short (stay in pattern) flight this morning in the PC12.
Did not begin “cold and dark”.
What changed…
Yesterday attempted the same short flight only to CTD just before landing. Everything was operating just fine until that point.
The flight controls connected were:
Honeycomb Alpha Yoke
Honeycomb Bravo Throttle Quadrant WITH the new update to get lights working.
Velocity One Rudder Pedals
Also had an Elgato Stream Deck MK.2 connected and “on” but apparently this does not work in 2024 without buying that Axis and Ohs software.
Todays successful flight:
Velocity One Flightsick
Velocity One Rudder Pedals
Unplugged the Stream Deck and quit the Elgato program
Now have to try with the Honeycomb Hardware without the Elgato software running and stream deck unplugged and see what happens.
