Simhas been CTD for me for the last few months since the last Sim Update

User Support Hub Crashes (CTDs)
,
1

Are you using Developer Mode or made changes in it?

No

Have you disabled/removed all your mods and addons? If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the Community Support section.

Yes

Brief description of the issue:

My sim constantly crashes to desktop, sometimes in the menu, sometimes in game. I thought it was a problem with my VR, but it does it without my VR headset installed in flatscreen mode as well. I have tried emptying my community folder, and have even reformated Windows 11. I’ve been using the sim since December 2020, and only started experiencing issues around June I think, whenever the last sim update was.

Provide Screenshot(s)/video(s) of the issue encountered:
No screenshots, but here is the error report. It’s always the same error code.
Faulting application name: FlightSimulator.exe, version: 1.33.8.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.33.8.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000025c4dc9
Faulting process ID: 0x0x4B54
Faulting application start time: 0x0x1D9D236750B7BCE
Faulting application path: D:\Program Files (x86)\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: D:\Program Files (x86)\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Report ID: dc1fcc15-848c-47da-8dda-5cb6d9633626
Faulting package full name:
Faulting package-relative application ID:

Detailed steps to reproduce the issue encountered:

It just happens around 60 percent of the time I run the sim.

Many issues may be due to an outdated graphics card. Please state your Graphics Card Driver Manufacturer (NVIDIA, Intel, AMD) and Version (Learn how to find your current graphics card driver version):

My GPU, motherboard drivers are all up to date.

PC specs and peripheral set up:

I have a high end 13900K, 4090 PC, running on two NVME drives, a Samsung 990 Pro for Windows and the Sabrent Rocket for MSFS. It can crash whether my flight peripherals are plugged in or not.

If on PC, Fault Bucket ID - Instructions here - Please type in just the Fault Bucket ID # rather than a screenshot for privacy reasons:

Fault bucket 1236062886058525194, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: FlightSimulator.exe

Build Version # when you first started experiencing this issue:

Since it updated to SU12 I believe. At least the beginning of June, possible since May. I hardly use the sim any more as its got to the point where it is beyond frustrating. When I works, I fly four or five times a week, so I’d love to get it fixed.

:loudspeaker: For anyone who wants to contribute on this issue, Click on the button below to use this template:

Do you have the same issue if you follow the OP’s steps to reproduce it?

Provide extra information to complete the original description of the issue:

If relevant, provide additional screenshots/video:

If on PC, Fault Bucket ID - Instructions here - Please type in just the Fault Bucket ID # rather than a screenshot for privacy reasons:

2

Moved to Tech Talk which is more appropriate whilst others help you troubleshoot :+1:

How much RAM do you have?

1 Like
3

Thankyou. I have 32 GB of 5600 Mhz DDR 5, and 24GB ram on my card. The sim has been working fine since Decemeber 2020 when I purchased, it’s just started to play up since the end of May, beginning of June, directly following an update. I think it was a Sim update but maybe a world update, I can’t remember now.

1 Like
4

Have you run a stress test for the memory?
This is the one I use.

Run a 1 hour test for ram and see if you get any errors.

1 Like
5

Thanks, I just completed the stability test. It ran for 30 minutes and stopped, 70 cycles, but there were no errors. I don’t think it’s my hardware as no other game or application has any issues and my computer never crashes outside of MSFS.

6

This is usually as it can’t find memory it expected / needed or read from the disk (into memory).

Just because your system doesn’t crash in any other tasks isn’t a sure sign that it’s still not a hardware problem because MSFS pushes a system like nothing else really.

When you say the test stopped after 30 mins, you mean it just stopped or you didn’t set a 1 hour run?

What settings did you use to do the test? I’ll have to rid out the settings I was advised to use that really pushed the ram hard.

7

I mean I just ran a default test and it was set up for 30 minutes, so it completed it without any issues. I’m sure its not my hardware. The PC was brand new in December last year and hasn’t had a single issue in any other game or application. How would I determine if it’s a hardware issue, just leave a test going overnight?

8

So I just asked ChatGPT again, man this little AI fella is super useful. Has given me some real pointers.

Hey buddy

ChatGPT

Hello! How can I assist you today?

User

Can you explain the following exception code for me please, Exception code: 0xc0000005

ChatGPT

Certainly! The exception code “0xc0000005” refers to a common Windows operating system error known as an “Access Violation” or “Access Denied” error. This error occurs when a program attempts to access a memory location that it’s not allowed to access, or when it attempts to perform an operation that requires higher privileges than it has been granted.

Here’s a breakdown of the exception code:

  • “0x” indicates that the following characters are in hexadecimal notation.
  • “c0000005” is the specific hexadecimal code that corresponds to the error. This code is also known as the “exception code.”

In more technical terms, this exception code is part of the Windows Structured Exception Handling (SEH) mechanism, which is used to handle exceptions and errors in software. When a program encounters an access violation, it usually means that it has attempted to read from or write to a memory address that it doesn’t have permission to access, or that the memory address doesn’t exist.

Common causes of this error include:

  1. Null Pointer Dereference: Trying to access or modify data through a pointer that’s pointing to an invalid (null) memory location.
  2. Buffer Overflows: When a program writes data beyond the boundaries of a buffer, leading to memory corruption and access violations.
  3. Memory Corruption: When some part of the program unintentionally modifies memory used by another part, leading to unexpected behavior.
  4. Data Execution Prevention (DEP): DEP is a security feature that prevents the execution of code in certain memory regions. If a program tries to execute code in a non-executable region, an access violation can occur.
  5. Stack Overflow: When the program’s call stack becomes too large, it can overwrite critical data structures, causing access violations.
  6. Invalid Memory Addresses: Attempting to access memory addresses that don’t exist or are outside the program’s allocated memory.

To diagnose and fix this error, you’ll typically need to analyze the program’s code, identify where the access violation is occurring, and address the underlying issue. This might involve checking for null pointers, verifying buffer sizes, and ensuring correct memory allocation and deallocation practices.

Keep in mind that troubleshooting and resolving these errors can sometimes be complex, depending on the specific context and programming environment. If you’re encountering this error in a specific program, you might need to refer to the program’s documentation or seek assistance from its support channels.

User

is Exception code: 0xc0000005 likely to be caused by faulty hardware, for example, bad ram, or is it more of a software issue generally?

ChatGPT

Exception code “0xc0000005” (Access Violation) is more commonly associated with software issues rather than hardware problems. It typically arises due to programming errors, memory-related issues within the software, or security mechanisms preventing unauthorized memory access. However, it’s important to note that while this exception code itself is often related to software, faulty hardware can indirectly contribute to such errors.

Here’s how hardware issues, particularly bad RAM, can impact the occurrence of access violation errors:

  1. Memory Corruption: Faulty RAM can lead to data corruption in memory. If a program’s data or code is stored in a memory location that gets corrupted due to bad RAM, attempts to access that memory can result in an access violation error.
  2. Random Errors: Bad RAM can cause random and unpredictable behavior in software. This might lead to unexpected memory access patterns that trigger access violation errors.
  3. Inconsistent Behavior: Software bugs and memory-related issues caused by bad RAM might not be consistent. The errors might appear sporadically, making them difficult to diagnose.
  4. Stack Corruption: If the call stack (used to manage function calls and local variables) gets corrupted due to faulty RAM, it can result in access violations when the program tries to access variables or return addresses that have been altered.
  5. Data Integrity: If the program’s data structures get corrupted in memory due to bad RAM, attempting to access or modify these structures can lead to access violations.

While hardware problems can potentially contribute to these errors, they are not the only source. Software bugs, incorrect memory handling, programming mistakes, and other software-related issues are more common triggers of access violation errors. To diagnose whether bad RAM or hardware issues are involved, you might consider running hardware diagnostics, memory tests, and stress tests on your system.

If you’re consistently encountering access violation errors, it’s a good idea to investigate both software and hardware aspects to identify the root cause. Fixing the software-related issues should be the first priority, but if you suspect hardware problems, addressing them could help eliminate potential sources of instability in your system.

1 Like
9

Blow me… so what you are saying is humans aren’t really needed any more. :smiley:

But… it still could be ram :stuck_out_tongue:

Lemme call on @MrTonySM to tell you the best settings for OCCT 1 hour test.

1 Like
10

Hello!!! Ok you want to DL occt OCBASE/OCCT : Free, all-in-one stability, stress test, benchmark and monitoring tool for your PC

Screenshot 2023-08-19 211931
Screenshot 2023-08-19 2119311908Ă—1114 96.3 KB

These are your settings, and hit start

If you pass this test. run Windows powershell. You can type powershell in the windows search bar, right click. Run as administrator

First, you can copy this… SFC /scannow

Next… DISM /Online /Cleanup-Image /ScanHealth

if it finds an error… DISM /Online /Cleanup-Image /RestoreHealth

2 Likes
11

That error looks like a broken store component. DISM hopefully sorts you out. ChatGPT 0, MrTonySM 1. If I’m right, plz remember to mark as solution. Thank you and best of luck

2 Likes
12

Thanks!, I will do all the above as instructed after the UFC has finished. It will be amazing if I can fix the issues.

What does broken store component mean? Do you mean from the MSFS store, bad data? Or a store space on my drive?

1 Like
13

yo, do the stress test while the fight is on. @Baracus250 has a great suggestion. then you are not waiting

1 Like
14

It means your windows has a corruption. It might be from bad memory. we will find out

15

Ok, it’s running now!

16

wickeeeeeed, who’s fighting btw… what am i missing. We need UFC on pc. ■■■■ ps5 version is so sick

17

Also personally My driver verision from May 30th 2023 is perfect with no issues

1 Like
18

to add, man. cant believe its been this long since I’ve suggested this. Run in powershell, chkdsk and hit Enter. then, chkdsk /r and chkdsk /f if you get errors. just to make sure DISM has got your corruption under control. As this could also be an ssd error. Just want to make sure.

EDIT: can only be one of three culprits on this, bad memory, bad ssd, bad luck

EDIT2: what memory do you have? post like this F4-3600C18D-32GTZR as example. and all your specs

19

It’s 32GB Corsair Dominator DDR5 5600, the part number is CM32GX5M2TB5600C36
Rest of system is 13900K, 4090, Asus Z690 Hero Maximus, 1TB Samsung 990 Pro Windows drive, the sim is a on a 2TB Sabrent Rocket.

Test is 50 minutes in, no errors detected yet, which is good I guess.

1 Like
20

it is, it just might be a random corruption. DISM will get it it. just about 99.9% positive. That memory should run great on that system. No where near taxing mem controller. its actually the bottleneck on your system. way underpowered for you specs, but that is another convo