2 hours ago, Clem116 said:

After a FRESH OS install and VANILLA sim, I got a new different CTD 30mins into flight....

Faulting application name: FlightSimulator.exe, version: 1.12.13.0, time stamp: 0x5fda3fe4
Faulting module name: d3d11.dll, version: 10.0.19041.546, time stamp: 0xef86554b
Exception code: 0xc0000005
Fault offset: 0x000000000012e980
Faulting process id: 0x26a4
Faulting application start time: 0x01d6e1785081af91
Faulting application path: D:\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: C:\Windows\SYSTEM32\d3d11.dll
Report Id: 24d12ef5-21b8-49d6-93a4-3614f141591c
Faulting package full name: 
Faulting package-relative application ID: 

Noticed you are OC'd to 5 Ghz. Have you tried diabling XMP and upping Vcore a bit if you can maintain safe temps? 

3 hours ago, Alpine Scenery said:

Could be anything, but it's probably hardware related. Maybe heat, voltage related (PS), memory, or bad video card... You could also try to install the Gamepass version at least temporarily to see if that helps the issue. It could also be a bad memory dimm, and it only happens in the sim because nothing else hardly ever uses that much memory. HW settings, driver issue, bad memory, overheating, bad video card, or bad voltage from PS.

However, more than half the time, it's probably one of three things: a BIOS setting is incorrectly configured, a faulty memory Dimm, or a heat / video card fan issue. Review your temps carefully and try underclocking video card using MSI Afterburner. Underclock it about 5% and try again. Make sure you didn't change anything in your BIOS too much, try using default BIOS settings. If none of that works, try removing one of the memory DIMM's, consult your motherboard manual depending on how many DIMMS you have installed, and try to isolate the memory. If still nothing works, I'd RMA the video card and the memory at the same time, and maybe even the motherboard (if your not past RMA stage). It's easier to just RMA multiple things at once and try a fresh config.

https://forums.flightsimulator.com/t/how-i-fixed-my-exception-0xc0000005-crash-to-desktop/279205/3

 

Memory problems that take ages to manifest after static damage is a classic. It is surprising how may people claim "static protection is unnecessary these days modern memory modules do not need it" and then 6 months later are complaining about the dodgy memory they were sold.  

1 hour ago, DylanM said:

Noticed you are OC'd to 5 Ghz. Have you tried diabling XMP and upping Vcore a bit if you can maintain safe temps? 

That would be my first thought, he has OC'd incorrectly, but that's so obvious that at this point I figured he would have set it back. He should definitely turn off all OC, that's step # 1 if he hasn't already done so.

 

13 hours ago, mpo910 said:

This is only true for maybe 5% of all causes which can lead to this error code. It can also be:

Hardware related

Windows related

.dll related

App Start related

Registry related

....

You knowledge seem to be very high level and it is not helpful for any user at all.

Are you the same guy who posts this all the time over at LM support forum (yep, another platform but I am just curious)?

Marcus

How do you know the 005 error is only true for maybe 5% of all causes.

In this case the 005 error was the only error to talk about.

So I gave the "link" to the author of the 005 error information.

No, I do not report the 005 error information in the LM forum all the time.

Go search the LM forum for yourself..

12 hours ago, mpo910 said:

I was talking about you. Don´t switch the conversation.  I am sorry to say this, but it is really very shortcoming to point a user in a memory access violation direction where most of the time this is not the cause. Your behavior on LM did also irritated lots of other users and that´s why I posted and reacted with this to point the user in other directions where he should look at.

He should try:

• Checking device manager if any hardware issues occur (yellow triangles?)
• Reinstall all VC redists he can get from microsoft site
• reinstall the MSFS app, if he does not have it done already (only the app, not the whole MSFS directory)
• run sfc /scannow at powershell admin
• run dism /online /cleanup-image /scanhealth at powershell admin
• reinstall nvidia driver
• disable all msfs mods
• reinstall ALL hardware components (joysticks etc.)
• Disable, delete and if necessary reset!! all OC profiles for GPU cards

 

This is the way to approach. 

Marcus

 

"it is really very shortcoming to point a user in a memory access violation direction where most of the time this is not the cause. "

You say Most of the time.?

But it may well be the Op's problem now,

I have no idea of what you mean by my behavior on LM forum irritating lots of users.

Where are you getting that information from?

You are free to point the Op in any direction you want to.

But so are other members of this forum.

 

13 hours ago, Clem116 said:

3 - No component store corruption detected.

How many watts is your power supply rated at, post model of P/S too.

At this point, I would try to install the Xbox gamepass version from Microsoft (probably uninstall the Steam one just to be safe, though I'm sure they can co-exist). Also, try running a different high-intensity PC game and see if any issues, maybe play it for at least 15 minutes, go do something else, leave PC on for several hours, and come back and do another 15 minutes. Again, watch all your temps in your PC (from HD to CPU to Video Card, see if anything seems abnormal).

As others have said, disable all your OC for sure, don't turn any OC back on even if it didn't solve it, just leave all OC disabled, last thing you want in this stuff is a multivariate problem interfering with a diagnosis.

Depending what happens after doing the above troubleshooting, I'd then continue to try to isolate the DIMM's or just order new memory entirely (and just return the new memory if it doesn't solve it). Order a different brand of memory this time, some MB's don't like certain memory or sometimes memory is defective.

After all that isolating/troubleshooting, you're probably looking at RMA'n the video card, but you could try the video card in a different PC and then installing MSFS on a different PC if you have one available (using your same video card).

You have to think in terms of isolating the problem, just doing random stuff like reinstalling drivers or changing settings, that can work sometimes, but more often than not you'll keep going in circles.

Edited January 3, 20215 yr by Alpine Scenery

3 hours ago, vonmar said:

"it is really very shortcoming to point a user in a memory access violation direction where most of the time this is not the cause. "

You say Most of the time.?

But it may well be the Op's problem now,

I have no idea of what you mean by my behavior on LM forum irritating lots of users.

Where are you getting that information from?

You are free to point the Op in any direction you want to.

But so are other members of this forum.

 

https://www.avsim.com/forums/topic/588156-reaction-from-beta-tester-lm-forum-on-ugly-cloud-grid/?do=findComment&comment=4391690

https://www.avsim.com/forums/topic/586483-any-little-news-on-p3dv5-update/?do=findComment&comment=4380767

Look here. That's about you. 

Search and you will unfortunately find more. I hope you see that you did not impress "us" by just repeating yourself and also asking stuff which is obviously not relevant.

Just change the way you approach on things and you will get better feedback.

Sorry....off topic here.....now back to topic again.

Marcus

Edited January 3, 20215 yr by mpo910

12 minutes ago, mpo910 said:

https://www.avsim.com/forums/topic/588156-reaction-from-beta-tester-lm-forum-on-ugly-cloud-grid/?do=findComment&comment=4391690

Look here. That's about you. 

Search and you will unfortunately find more.

Marcus

I spent a fair amount of time troubleshooting P3D last year and searching for specific error conditions and codes. On most of the official LM forum threads I read, I'd find this troll posting things like "have you disabled all addons? Have you started the flight at the stock default airport? Have you turned off all weather? Here's a screenshot of it working perfectly for me, you must be at fault". Noticeably, other users would then chip in and the real fault would be quickly diagnosed and fixed.

Clem - how's your PC's cooling? If an important component like the CPU or graphics card is overheating, you'll get crashes. You've formatted and rebuilt the machine which should rule out software problems and short of spending £££ replacing components, the next easiest step is checking things like all the fans are turning when powered on, there's no buildup of dust in cooling fins, etc.

He's pretty close to ruling out software, but I would still install the MS Gamepass version as a next step since it's the easiest thing to do, as the Steam version has been flakier for some people. He should have already been checking temps if he OC'd. He says it was only happening in MSFS, but I don't know how much he tested other things.

After that one test and of course re-checking temps, I'd then move onto assuming bad component.

 

 

 

2 hours ago, mpo910 said:

https://www.avsim.com/forums/topic/588156-reaction-from-beta-tester-lm-forum-on-ugly-cloud-grid/?do=findComment&comment=4391690

https://www.avsim.com/forums/topic/586483-any-little-news-on-p3dv5-update/?do=findComment&comment=4380767

Look here. That's about you. 

Search and you will unfortunately find more. I hope you see that you did not impress "us" by just repeating yourself and also asking stuff which is obviously not relevant.

Just change the way you approach on things and you will get better feedback.

Sorry....off topic here.....now back to topic again.

Marcus

In the first link you posted:

It was directed at you and I just expressed my opinion. 
You will also notice I sign my first and last name so you won’t get confused about who wrote it (in all forums):

“ @ MPO910,
If i were flying a jetliner flight and looked out of the VC cockpit and seen your screenshot I would not thing anything bad about it.
Just keep scanning the gauges and enjoying the flight.

Not: I do not fly the plane(s) from outside views.
Best Regards,
Vaughan Martell (KDTW) “

And Yoyo (I do not know who he is) had his own opinion to express. 

No big deal.

****
In the second link you posted:

The post was not about me. Did you read it?
The post was complaining about forum members trying to help LM on the forums.

Dan’s post  quoted another member (ttbq1) who had questions saying:
“Posted October 17, 2020
On 10/15/2020 at 10:27 AM, ttbq1 said:

Is he part of the LM team? forum moderator? it is incredible the amount of time he spends every day answering posts on LM behalf.

The reply from Dan said:
He says he´s not. Seems to be unemployed having time to comment on everything. 
I feel irritated too about all these people (Jorgen is not alone) defending LMs behavior. 
Martyson (Vaughan Martell (KDTW)) even beats him with about 3 posts a day to 2.57 by Jorgen. 
I don´t know why these guys always post the obvious or the position of their thought LM position.

Dan “

No big deal.


In my opinion you need to spend more time focused on the current topic and solution.
You need not switch the conversation to other forums or waste time instructing members on how to reply to a post.

If you haven't done already, try this here:

https://forums.tomshardware.com/threads/d3d11-dll-caused-an-access-violation-0xc0000005-in-module-d3d11-dll-at-0033-1303e620.3511419/

10 hours ago, Clem116 said:

After a FRESH OS install and VANILLA sim, I got a new different CTD 30mins into flight....
Faulting module name: d3d11.dll, version: 10.0.19041.546
Exception code: 0xc0000005
Fault offset: 0x000000000012e980
Faulting application path: D:\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: C:\Windows\SYSTEM32\d3d11.dll

Doing an OS reinstall means we can exclude the OS as the source of error. I don`t have experience at dll files, but the name of the dll file, the exception code and the fault offset can help localize the error (but unfortunately only for developers). Furthermore the dll catches the error, that means the dll threw an exception code, because it was fed by Bugsobo in a wrong way. If Bugsobo hat properly implemented an exception procedure in their code, nothing would have crashed.

It might be resolved with better hardware (but that`s not the sense of a computer). Crashes occur when bad memory allocation happens for example. Memory allocation errors can be resolved with a 3090 with 24GB RAM, but PCs are meant to be run on a wide range of hardware. They must be just properly programmed. The dll is properly programmed, this is why it catches the error and closes the game. Otherwise you had to close the software manually with the Task Manager. Many experienced programmes told here that Asobo has done a bad job in programming.

Just to exclude the hardware as error, run a Furmark stress test for 30 minutes, run a CPU stress test for the same time, perhaps also a 3D mark benchmark, if everything works fine, you can be sure that your hardware is OK. That is likely the case. Hardware errors cause more likely Bluescreens than crashes.

Try decreasing the graphics settings, alsoI would not overclock the CPU, even deactivate the manufacturers boost mode in BIOS. Increasing the voltage of the CPU is also not a very good idea. All specifically for FS.

56 minutes ago, BigDee said:

If Bugsobo hat properly implemented an exception procedure in their code, nothing would have crashed.

A major access violation cannot just be resumed generally speaking in C++ (it's not a good practice to even try), instead you have to create a dump, so realistically it would have still crashed. If you try to resume on an access violation, especially in a C++ raw thread, you'll often either bleed the OS threads into a locked OS or you can even cause a BSOD. At best case, you'll probably just have a buggy session the rest of the time. It should have been dumped, but writing error handling everywhere isn't always the best thing either.

Plus the error happened in D3D directly and may have had nothing to do with the code, as it could just be HW related.

Edited January 3, 20215 yr by Alpine Scenery

I personally think an exception caught, is a proper way to find a solution. Of course the exception should not try to read a corrupted memory address, but it can do workarounds. In the worst event, the software can close in a proper manner, with an error code to locate the specific function and the problem can be resolved.

At this time we know 0xC0..5 is a memory fault, but there is no way to find, without debugging the problem.

I like the old Windows MFC very much, in many parts, for even the simpliest function, there is more exception code than actual code. This is the way to do it. This is how the dx11.dll did it, it catched the problem. Its not the first time Asobo introduces errors and bugs and I think the code of this game is smashed up in some way, just as the cfg values for airliners and the autopilot.

Edited January 3, 20215 yr by BigDee

Some access violations cannot be caught. If it happens in a certain way on the stack, as is often caused by hardware, the OS has control of those exceptions at a level below the C++ runtime. You would generally need to see the OS dump.

Also, he can check this directory for exceptions in FS2020:
C:\Users\{username}\AppData\Local\CrashDumps

I wouldn't bother really, because any investigations into the exception itself will be less fruitful than doing the full proof isolation procdures as I outlined above. It's a simple case of isolating the problem. Also, I've never found those mem testers to be that great, I've had about 20% luck with them even when memory was bad, so it wouldn't hurt to run a memcheck, but i wouldn't trust the results even if it says it is fine.

 

 

Edited January 3, 20215 yr by Alpine Scenery