I kinda noticed this while doing rigour testing with both dx9 and dx10. Dx9 is 100% stable as of now. Dx10 however, looks like I'm getting CTD every now and then.

 

Here's the appcrash details I get each time:

 

Problem signature:

  Problem Event Name: APPCRASH

  Application Name: fsx.exe

  Application Version: 10.0.61472.0

  Application Timestamp: 475e17d3

  Fault Module Name: d3d11.dll

  Fault Module Version: 6.2.9200.16492

  Fault Module Timestamp: 50f31443

  Exception Code: c0000005

  Exception Offset: 000a8004

  OS Version: 6.1.7601.2.1.0.256.1

  Locale ID: 1037

 

Additional information about the problem:

  LCID: 1037

 

Read our privacy statement online:

  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

 

If the online privacy statement is not available, please read our privacy statement offline:

  C:\Windows\system32\en-US\erofflps.txt

 

Any clues on this? I've been digging fsx info like a mad the past few days and I think I pretty much applied every good fix that's out there. Aside from the CTD, I'm getting awesome performance, great fps, anisotropic filtering works a treat. Everything is great besides the occasion scenery that's not 100% compatible with dx10.

Had this one myself a couple of times, and (if I remember correctly) traced it down to some chunk of FSX addon needing one of the Visual C Redistr versions, 

 

2010 64-bit here ; 32-bit here:  2012 64-bit here: 32-bit here. I don't think it was a DirectX problem, but you can check which versions you have from these tools here:-

 

Cleanup Tool, Verifier Tool, and VersionChecking Tool.

 

Sometimes you can get a problem with DX, but almost every program you install, particularly games, will also install a fresh copy of whatever version of DirectX the developers used. 

 

Good Luck!

 

All the Best,

Google Exception Code: c0000005 . This is not an error in the app, but one in the hardware, that the app trips. It could be caused by an over zealous Over clock, or a problem in the CPU.

I slightly doubt it's a cpu problem. It's not even overclocked and I never experienced such errors in other games/apps. I ran diag.exe, but since I'm running win 7 (x64), it's obviously @ dx 11. Those Visual C Redist, does 2012 override 2010 or is it considered a separate install?

 

Edit: I checked my programs and features and found this:

 

Looks like I don't have the 2012 version, so guess I should install it? Also it looks like different versions are installed as stand-alones. Maybe I can remove old versions of the same redist?

 

No - each one is installed by any app which needs it, with some versions provided by the OS. Only delete one if you know you can reinstall it right away. The versions are not backwards-compatible, and here are what I have currently.  I've been searching for my fix for this, but can't find it, with the exception that this file is one Googled a month or so ago, and this site gave me lots of things to try. I believe the actual error was caused because I had begun using Visual Basic 2010 and 2012 Express (in an attempt to convince myself that I can program things) and this dll is used by the graphics engine. It was probably not a good idea to run both at the same time, and may have corrupted the file. What it has to do with FSX or any addon, is anybody's guess, but I think removing VB 2010 & 2012 and then re-installing just 2012 fixed the issue, as it did not re-occur after that.

 

http://pcsupport.about.com/od/findbyerrormessage/a/d3d11-dll-not-found-missing-error.htm

 

Hope this helps.

 

 

Tom is correct with the error: a "5" generally means more vCore is needed, but I think that was an inability of the OS to correctly pin the error, as I believe DirectX - all versions - talk to the hardware - at least the GPU, but maybe the proc thread as well..

I'll try installing the 2012 redist and we'll see what happens. Although, I have moved from dx10 to dx9 for now. Just because some sceneries seem to be in-compatible. Maybe I should make myself 2 batch files for installing a dx10 cfg and a dx9 cfg so I can toggle between the two.

I've found over the years that  c0000005 can also be caused by FSX simply not finding an asset in the cache while in flight that it was looking for; it considers the hard-drive cache as part of memory, and so if something is missing "in memory" it is looking for, it can generate this exception as well.

 

That can happen intermittently if the terrain (or clouds) data is not streaming off the HD fast enough, simple as that.

 

If it's a repeatable problem in a specific situation every time, that can be different.

This is an automatic message.

 

This topic has been moved from "DX-10 Discussions, Hints and Help" to "Crash To Desktop (CTD) Forum". This move has been done for a number of possible reasons.

• The most likely reason is that the post was off topic.
• The topic could also have contained images or a video that were not appropriate to the original forum it was posted in.
• The images might not have been "illustrative" or "explanatory" in nature.
• The topic could have been moved because we deemed it to be more appropriately placed elsewhere.

Please ensure that your posts are "on topic" and contain illustrative images or videos as appropriate. Do not post videos or images just for entertainment purposes anywhere but in the screen shot or video forums.

 

Members who continue to post off topic posts can be denied entry to specific forums in order to reduce and remove the practice. Your cooperation is appreciated.

I have gotten that fatal error several times now.  Always the same d3d11.dll module.  It is dx10 related for sure as I went back to dx9, and it disappeared.

Exactly! I do enjoy dx9 too.

 

 

I'll try installing the 2012 redist and we'll see what happens.

 

FSX does not use MSV 2012.  Only versions 2005, 2008, and 2010.  Addon developers and Microsoft use only a certain version for their application so you must have all three installed.  They are not backward compatible.  Do you have the d3d11.dll in your main FSX directory?  If so, please remove it as it is not compatible with FSX.

 

Best regards,

Jim

Nope, d3d11.dll is not present in my fsx folder.