Getting CTDs again…

[Tom_L 522]

1 hour ago, Bunchy said:

I'd like to report it on WT discord

It's been reported. Matt Nischann said there's no way their CJ4 could crash the sim. It has to be MSFS bugs. Zendesk (yes, i reported there too, dutifully!) however says it's the responsibility of the third party (read: WT) to fix the issue. Go figure!

[Bunchy 222]

That's frustrating, Tom.

It's a shame because I love the CJ4. 

Hopefully it will eventually stabilise with future updates of the sim, then.

 

Stu

[RobJC 2,069]

Well, the DC-6 just crashed. 

[fogboundturtle 2,708]

7 minutes ago, RobJC said:

Well, the DC-6 just crashed. 

Are you sure your OC is not undervolt and causing your crashes ? It's a common issue to have an improper OC that can handle MSFS.  Specially  if it' an undervolt OC. 

[RobJC 2,069]

12 minutes ago, fogboundturtle said:

Are you sure your OC is not undervolt and causing your crashes ? It's a common issue to have an improper OC that can handle MSFS.  Specially  if it' an undervolt OC. 

I will put it back to stock to see. Can’t hurt to try. Thanks!

[RobJC 2,069]

Okay did a test using Optimized settings in BIOS. This sets my RAM speed to 2000 instead of 3200 and lets the CPU go up to 5.2 GHz. Unfortunately at this setting the voltage sent to the CPU is over 1.35, which is generating way too much heat, and will certainly reduce the life of the chip. These 10850K chips run hot, so my next step was to simply change the multiplier to 47. No other changes other than to sync all cores. We'll see how that works. At least the voltage is under 1.3 and temps dropped considerably. Running AIO water cooling, so my cooling isn't the issue. 

[devgrp 1,233]

11 minutes ago, RobJC said:

Okay did a test using Optimized settings in BIOS. This sets my RAM speed to 2000 instead of 3200 and lets the CPU go up to 5.2 GHz. Unfortunately at this setting the voltage sent to the CPU is over 1.35, which is generating way too much heat, and will certainly reduce the life of the chip. These 10850K chips run hot, so my next step was to simply change the multiplier to 47. No other changes other than to sync all cores. We'll see how that works. At least the voltage is under 1.3 and temps dropped considerably. Running AIO water cooling, so my cooling isn't the issue. 

Thats one of the things I also did. Reset my overclock but kept my mem profile.

[RobJC 2,069]

TBM still crashes. 

[Twenty6 692]

Might help to diagnose the problem or eliminate Win10 system files:

https://www.makeuseof.com/difference-between-chkdsk-sfc-and-dism-in-windows-10/

[Ixoye 1,813]

I've have had several crashes when I shall leave the aircraft to main menu, and it is not related to any specific aircraft.

Edited September 21, 2021 by Ixoye

[Flypops 50]

Add me to the list. I've not been able to complete a flight for three days. Come to think of it, that's been since the last Hotfix (or maybe it was a Hotmess?).

[Hernan1 5]

This is so frustrating. 5 pages and no solution to CTD yet. My FS crashed after the last update. It loads up to the page showing "landing Challenges"

 

 

[Hernan1 5]

Just now, Hernan1 said:

This is so frustrating. 5 pages and no solution to CTD yet. My FS crashed after the last update. It loads up to the page showing "landing Challenges"

 

 

 

[udidwht 133]

7 hours ago, Twenty6 said:

Might help to diagnose the problem or eliminate Win10 system files:

https://www.makeuseof.com/difference-between-chkdsk-sfc-and-dism-in-windows-10/

Clean OS install here (4 days ago) and ran DSIM afterwards (latest 10 build) Was flying the DC Designs F-15 (so was son). MSFS is installed on d: 

Had first CTD was online with son. Straight to desktop with...

 

Source
FlightSimulator.exe

Summary
Stopped working

Date
‎9/‎21/‎2021 8:18 PM

Status
Report sent

Description
Faulting Application Path:    C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.19.9.0_x64__8wekyb3d8bbwe\FlightSimulator.exe

Problem signature
Problem Event Name:    MoAppCrash
Package Full Name:    Microsoft.FlightSimulator_1.19.9.0_x64__8wekyb3d8bbwe
Application Name:    praid:App
Application Version:    0.0.0.0
Application Timestamp:    00000000
Fault Module Name:    FlightSimulator.exe
Fault Module Version:    0.0.0.0
Fault Module Timestamp:    00000000
Exception Code:    c0000005
Exception Offset:    000000000139e46c
OS Version:    10.0.19043.2.0.0.256.48
Locale ID:    1033
Additional Information 1:    0e8e
Additional Information 2:    0e8e0bf1a5ef603976b025864a1e1bb1
Additional Information 3:    0d8c
Additional Information 4:    0d8cde3554a3449e91485d86cb569e8b

Extra information about the problem
Bucket ID:    a87424faa47ab46e1c3aff9b329c63c1 (2034219223745323969)

 

Edited September 22, 2021 by udidwht

[udidwht 133]

Update:

 

Not sure if this may be related. I noticed that my X-56 HOTAS had duplicate axis entries for both throttle and stick. Retesting the sim now after removing them. They weren't set that way by me. I guess the previous update/s set them that way. Anyhow everyone check to make sure your axis aren't duplicated on any devices you have plugged in.