I am wondering if anyone else has been having this issue. MSFS is up to date, my Community folder has seven entries in it which are up to date and shown as compatible with SU7. Prior to the beta update (patch) I had not experienced any BSOD. The only other recent change/addition was purchasing the SWS Kodiak 100. The BSOD’s began sometime after December 2021. I’ve had about ten or so occur, during flights that last between 40 minutes to an hour and a half. Today, I was in the Kodiak (engine not running) just going through the G1000 nxi to become more familiar with the unit, about 20 minutes into that another BSOD. Most have occurred in the Kodiak, but also on two occasions the Cessna 172 (glass cockpit) and Cessna 208 Caravan. Some have occurred while using the iPhone head tracking App (Smooth Track) and some without using head tracking.

I run MSFS with moderate settings, high and medium no ultra. The sliders (LOD) are set at 80.  Vsync is on frames set at 60. The OS is Windows 10 (all up to date). System  is an i7 9700k overclocked to 4.9 GHz, 32 Gb RAM and a 2070 Super GPU. Running at 4K settings on a Samsung 55” gaming TV.

I just think it is odd that this began happening after the SU7 beta update/patch. I’ve searched many of the forums, but haven’t found anything like the issue I’m having. Even checked forum subjects all relating to the SWS Kodiak just in case others who have purchased it also we’re having the issue I am. Found nothing.

If anyone else is having this problem and have a fix in mind, please reply. Anyone that may have a clue, please also chime in. 
 

Thanks and Happy Flying!

 

 

My MSFS will dissapear as soon as I am satisfied everything will be OK this time this run....alas I wish....

Nearly every flight, usually at the beginning, CTD

And yes, I think it is the BETA and I dont know how to get out of it

Funny, hahaha

It is not a flight simulator it is a Bing maps viewer with a pretty cockpit thrown in, forget anout  ILS, weather, AI,

it is just nice topgraphy...

1 hour ago, Wblackret said:

I am wondering if anyone else has been having this issue. MSFS is up to date, my Community folder has seven entries in it which are up to date and shown as compatible with SU7. Prior to the beta update (patch) I had not experienced any BSOD. The only other recent change/addition was purchasing the SWS Kodiak 100. The BSOD’s began sometime after December 2021. I’ve had about ten or so occur, during flights that last between 40 minutes to an hour and a half. Today, I was in the Kodiak (engine not running) just going through the G1000 nxi to become more familiar with the unit, about 20 minutes into that another BSOD. Most have occurred in the Kodiak, but also on two occasions the Cessna 172 (glass cockpit) and Cessna 208 Caravan. Some have occurred while using the iPhone head tracking App (Smooth Track) and some without using head tracking.

I run MSFS with moderate settings, high and medium no ultra. The sliders (LOD) are set at 80.  Vsync is on frames set at 60. The OS is Windows 10 (all up to date). System  is an i7 9700k overclocked to 4.9 GHz, 32 Gb RAM and a 2070 Super GPU. Running at 4K settings on a Samsung 55” gaming TV.

I just think it is odd that this began happening after the SU7 beta update/patch. I’ve searched many of the forums, but haven’t found anything like the issue I’m having. Even checked forum subjects all relating to the SWS Kodiak just in case others who have purchased it also we’re having the issue I am. Found nothing.

If anyone else is having this problem and have a fix in mind, please reply. Anyone that may have a clue, please also chime in. 
 

Thanks and Happy Flying!

 

 

Are you experiencing BSOD (Blue Screen of Death)  or just CTD (Crash to Desktop).? A BSOD usually indicates a problem with your computer. A hardware issue like bad ram, overheat situation, bad power supply, wrong BIOS settings, etc, or a bad overclock.   Since it seems to happen to you 20 to 40 minute in, it might be a heat issue. You might need to do some stress tests on your PC.  Software like MSFS by itself, usually cannot crash your whole computer, causing a memory dump and shutting down your PC. 

 

I had no issues with the latest Beta, but since it came out of Beta, I have been getting several CTD.  Usually, with 3 to 20 min in. Not sure what causing it yet. Frustrating for sure. 

 

 

 

I was experience relatively common crashes to desktop (CTDs) in the sim - some of which would actually cause a full PC reboot.  Is that what you are experiencing?  After much investigation (disabling countless mods to see if one of them was causing the issue) I determined it was related to the rolling cache (which I thought was disabled, but had apparently been re-enabled by the sim at some point).  I disabled the rolling cache and deleted the cache files, which seems to have 100% cured my CTD issues.

12 hours ago, Wblackret said:

System is an i7 9700k overclocked to 4.9 GHz

What is your core voltage set at?  If you haven't already take it up a tiny notch and re-try.  Over time as you may know your CPU can degrade ever so slightly such that it requires more core voltage.

My computer is only a year and a half old, built by a reputable company. I will try disabling the rolling cache and see if that cures the issue. If not investigate further. Thanks for all the responses.

14 minutes ago, Wblackret said:

My computer is only a year and a half old, built by a reputable company. I will try disabling the rolling cache and see if that cures the issue. If not investigate further. Thanks for all the responses.

Have you tried with the community folder empty?

 

11 hours ago, rickjake said:

A BSOD usually indicates a problem with your computer. A hardware issue like bad ram, overheat situation, bad power supply, wrong BIOS settings, etc, or a bad overclock.

Agreed. A BSOD or spontaneous reboot is likely hardware or an unstable OC.

Edited January 20, 20224 yr by DylanM

14 minutes ago, Wblackret said:

I will try disabling the rolling cache

I think that'll do nothing. If you're experiencing BSOD issues, is something related to your computer, not necessarily caused by MSFS itself. What it's for sure is that running MSFS puts stress in your computers, as it uses CPU and GPU, but you need to investigate on your overclocking (if any) or heat stress, as pointed out already, caused by bad ventilation of your CPU.

40 minutes ago, Wblackret said:

My computer is only a year and a half old, built by a reputable company. I will try disabling the rolling cache and see if that cures the issue. If not investigate further. Thanks for all the responses.

Yes and at 4.9Ghz it's been overvolted and that is what the reputable company did to deliver to you a 9700K at 4.9Ghz.  And if this was the case from the start it's been overvolted for 1.5y which is sufficient to start showing a need for more core voltage.  You seem bent on chasing shadows yet most everyone responding understands this is a hardware issue.  Do yourself a favor and look to see what your core voltage is at using CPU ID or look in the BIOS.  It would be helpful to know where the reputable company set it as chips vary substantially and if your chip was not on the good end of the spectrum it may well have been fed higher core voltage so the reputable company won't hear from you for awhile--it happens.  My CPU is largely the same chip.  I assembled my machine 1.5y ago and the initial core voltage to sustain 4.9Ghz was 1.18v.  It now requires 1.195v to retain stable operation.  Still, this is very low for this CPU and so we have a better than average 9900K.  You can easily apply 1.3v to this CPU and get away with it--for awhile.

Edited January 20, 20224 yr by Noel

Since I was bent on “chasing shadows” (re NOEL’s reply) went one on one with builder and connected to them via computer. As it turns out, CPU voltage is fine, overclock is stable after testing. The core voltage is 1.356 V and does not need adjusted from where it was set when originally built/overclocked. Actually found some corrupt files (windows) that were more than likely the culprit. Since then, several hours of flight and so far no further problems.

I do appreciate everyone’s responses and I want it to be clear that I was not ignoring the fact that BSOD’S are related more with hardware, but sometimes there can be other issues and in my case it apparently worked out that way. At least things appear to be sorted out.

Thanks again!

3 hours ago, Wblackret said:

do appreciate everyone’s responses and I want it to be clear that I was not ignoring the fact that BSOD’S are related more with hardware

Thank you for the clarification because to me it appeared you were looking for anything but hardware.  What kinds of peak temps are you seeing w/ your [email protected]?.  Just curious because the core voltage is as high as it is. One wonders where the corrupted windows files came from--perhaps during their initial setup as they were adjusting voltages and frequencies.  Good you are back up and flying w/o troubles may it continue for you.