If you're running multiple sticks of ram, you could try 16gb worth at a time and see how it goes. If you're running a pair of 16GB and have 4 slots, may be worth confirming that they are in the desired slots when running a pair.

 

 

At the risk of jinxing my luck, it seems that I have a partial cure to my CTD problem. 

The most helpful turned out to be limiting the power usage of 4090 to 70% using MSI Afterburner. I probably lost 1 or 2 fps, not really sth discernable in flight. 

After that, it appears that I need to make sure the 2D screen at full screen after entering VR, otherwise MSFS will CTD rather consistently with that famous "DXGI_ERROR_DEVICE_HUNG". 

Sticking to these two measures, I have one flight completed after 4 hours without CTD, one CTDed just short of 2 hours, and one running more more than two hours now. 

It's possible that my video card is having some stability issues when pushed hard to 100% for long period. In MSFS VR the 4090 constantly burns ~430W all the time with core at 2790MHz, although temperatures are fine. Limited to 70%, it runs at 310W and core around 2500MHz. My card could be just a not so good sample, or I should try to reseat/replug it and double check my powersupply (1000W) but I don't have time for this right now. 

Of course, this is still not the cure, but 2 hours are more than enough for my VR flight. 

 

   

Sounds like you're on to something! What 4090 do you have? (Just curious) 

It's a PNY 4090 I bought from eBay during the peak of 4090 shortage, with $500 premium. I know I should have waited but... 

I just finished a 4 hour flight at 60% power limit no problem too. The fps maybe a further 1-2 frames lower, but still I got around 35 fps taking off from KLGA overflying Manhattan, TLOD=300. It's almost puzzling why power limiting has such a small impact on 4090's performance. 

Nonetheless, I noticed that each time after I exit the finished flight, windows instantly crashed to a blue screen leading to system reboot. I'd guess the root cause of CTD is still the MSFS. Some hopes on the coming SU13 update.   

By the way, I use C172 with G1000 on AP to test. Each time I only spend a few minutes to start the flight, turn-on AP asap after take-off, shift to VR and just let the flight run by its self. Not too bad. I have ForeFlight for my flying in real world and it can connect and monitor MSFS flight too, very convenient. 

Edited September 25, 20232 yr by FlyIce

i wonder if theres a more recent firmware available for it?

is there an update for your motherboard?

I checked and there is no new bios to my motherboard. Good point I should check for 4090 firmware update. But I strongly believe the culprit is in the MSFS, powerlimiting the card only helps to make it stable longer.

If SU13 still doesn't solve the CTD issue, I'll reinstalled the MSFS. I realized this is not my bloody old days of FSX which a clean reinstallation is like pulling half of my teeth off - one tooth a time... With MSFS all settings are in the clouds and all extras are in the community folder. All it takes just couple hours of letting my PC slug through downloading/installing.  

Just in case, since you also suggested checking the memory, I ordered a pair of 32GB DDR5 to upgrade the system to 64GB. I wanted more memory anyway. 

Edited September 26, 20232 yr by FlyIce

pny might have fixed a gpu power management issue in a firmware update.  

for over a year we had a room full of pre-built desktops that would intermittently bsod under certain conditions, as a result of a single stick of ram being plugged into the wrong socket. The built in ram / system test reported everything was fine. They seemed to work perfectly 95% of the time.

Edited September 27, 20232 yr by dogmanbird

Hi, I just read your topic and I think I have the exact same problem and found a possible solution today.

To make a long story short, my CTDs are the same as yours and yes it feels like there is a limit to what it can take. 

Ive been looking for solutions for months, tried sooo much but nothing solid...until maybe now..maybe..hopefully

I still have a list of possible solutions and I try one per flight/CTD

Today I disabled and unistalled my NVIDIA high definition audio, since i dont need it. My audio via the G2 reverb is realtek. (I did this because i read somewhere that nvidia and realtek dont get along...)

And also for the first time Ive put a framerate limit on my fps via nvidia control panel. Ive put mine on 35

Now what happened today was 3  flights (EHAM-GCTS-LPFA-EHAM in the A310) without a ctd...........

Ive noticed everytime before when ctd my gpu 3d spiked together with video decode so..together with your findings it might make sense that the fps limit could have solved it...

Im not entirely sure yet im gonna do some more testing upcoming days but it look promising.

Really hope this helps for you as we are all in the same boat! 😞

 

4 hours ago, Guest Zonnie90 said:

Today I disabled and unistalled my NVIDIA high definition audio, since i dont need it. My audio via the G2 reverb is realtek. (I did this because i read somewhere that nvidia and realtek dont get along...)

And also for the first time Ive put a framerate limit on my fps via nvidia control panel. Ive put mine on 35

Now what happened today was 3  flights (EHAM-GCTS-LPFA-EHAM in the A310) without a ctd..........

Thank you for the info. This is exactly one of the reasons that I keep documenting my trouble shooting here - to find someone in the same boat and help each other. I remember someone at official forum also said sth about conflict between Nvidia and Realtake audios maybe causing CTD. Glad this is working for you and I'll definitely try your suggestion as to uninstall Nvidia audio.

For the framerate limit, I wonder it might have similar effects as power limiting, just making the card run less stressed and that apparently alleviates the CTD problem. 

SU13 just came out, it'll be hands full for me to test SU13, driver uninstall, frame limit, power limit, etc tonight. 

Unfortunately I just had another CTD... 😕  su13 looked so promising..i even had higher fps in VR but then after about 30 mins at FL380 KBOS - KPHL in the A310..CTD

So the framerate limit is not the right solution for my computer. Up to the next on my list..

Well, my first flight of SU13 KLGA-KARL also ended CTD in 15 minutes. I removed Nvidia audio driver, and set frame limit to 45 and purposefully didn't open MSI Afterburner to do powerlimiting.

My first impression of SU13 that VR is noticeably smoother and gained probably 5fps on average. MSFS went frozen after 15 min with "DXGI_ERROR_DEVICE_HUNG" error and crash/closed after few minutes. Didn't drag down my PC though like it often did before, so a little bit better. I'll try powerlimiting by MSI AB again tonight. 

Well after su13 im getting crashes after entering vr...

I did few more test flights and unfortunately CTD is not cured. However SU13 does feel a bit more stable, as its CTD is much more benign and consistent in nature. So far all CTDs ended up with DXGI..HUNG error. The sim would appear frozen but did not crash the whole PC as before, so I can simply close it. Definitely a bit progress made here.

Similar to pre-SU13, there appears a strong correlation between power-limit of 4090 and how soon MSFS freezes. 75% limit seems to be rather consistent in giving me flights over at least one hour and I just had one overnight flight lasted for 6 hours before sim freeze. At 90% or 85% I got two flights frozen up before 20 min. Of course this is just a strong hint not statistics... 

Again, power-limiting 4090 does not cure the CTD, but definitely helps a lot to alleviate the problem. Worth trying as it's super simple and easy using MSI Afterburner, plus the performance loss is really negligible. 

Edited September 30, 20232 yr by FlyIce

do any of these updates (right down bottom of page in the 4090 section) match your video card? might be worth trying it if it does

https://www.pny.com/company/support/nvidia-geforce

 

 

Edited October 1, 20232 yr by dogmanbird

Yeah I already updated the PNY 4090 bios. I also tested by overclocking its core by +200MHz to 2950MHz, and MSI Kombustor GPU stress test ran at 100% power no glitch for hours, burning a constant 415-420W. So I would guess the card itself is unlikely the problem.

By setting 4090 at 80% power, AND, underclocking its core by -400MHz to 2350MHz, I just completed an 11 hour VR flight of KBOS-KLGA-KPIT-KMCI-KAUS flying RV14A (all on AP except for taking off and landing, of course). At these settings the performance loss is about 9%, and I'll probably stick with these settings for a while. 

Edited October 1, 20232 yr by FlyIce