d3d11.dll Error

[Aharon]

Shalom and greetings all my pals,

After few months of smooth flying, FSX has now refuses to open by saying the error message as seen below:

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.16570
Fault Module Timestamp: 5153774d
Exception Code: c0000005
Exception Offset: 00010860
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033

So I researched on the internet for solution to the d3dll.dll error problem. The common answer is to remove Windows Update KB2670838 but I do not have that in laptop and looking at past update history in windows 7 shows no evidence of installation of Windows Update KB2670838.

I used FSX's automatic repair method to repair FSX but that did not produce any positive results.

Anybody got an idea?

Thanks,

Aharon

[Airspeed]

Hi Aharon,
This type of problem is WAY over my head, but when I looked it up, I found this:
People also ask
What is d3d11 dll file?
For for many popular game programs , D3d11.dll is a file that has the important relation with their smooth running on the computer. It is a DLL module belonging to DirectX and often triggers some error problems with DirectX 10 and DirectX 11, let's see what happen on your computer when you get its error message.
From this, it may be connected with DirectX (I no longer believe everything I read)
So, have you changed anything to do with DX? New game needed later version or something?

[DaveG]

Are you using any shader mods like reShade or ENB?

[Aharon]

Hi Airspeed

I do not even have DX11 in my laptop which is STRANGE considering the fact that my FSX has been using DX9 and what makes it MORE stranger is that my FSX has always been set to deactivate DX10 preview since 4 years ago yet FSX refuses to open with the d3d11.dll error message!!

DaveG, I am not using reShade or ENB. I do not even have SweetFX. I do not even have the infamous KB number upgrade that everybody calls EVIL.

I think my heavily used 4 year old laptop is dying. I am afraid I would need to buy new laptop but I do NOT NOT want Windows 10 because everybody say FSX never never works with Windows 10!!

Regards,

Aharon

[DaveB]

Hmm..

I've seen this pop up from time to time and for what seems like no reason at all. This said.. there's always a reason. Have you recently added a new model or scenery?
ATB
DaveB

[Aharon]

Have you recently added a new model

Only Jahn's new version 3.12 C-47 but I am 100 percent that this new model is definitely not cause of the problem as I had been using it for 2 weeks without problems.

I already tried dxdiag and it refused to run due to its announced error message Fault Module Name: d3d11.dll.

Maybe time to buy new laptop!

Regards,

Aharon

[DaveB]

No.. I don't think it's the C-47 either. No one else has reported this problem so I doubt the model is to blame. Is there any way you can get hold of a copy of d3d11.dll? I've just had a look in Win7 System32 and I seem to have a hell of a lot of d3d**.dlls.. many more than I was expecting!! However, I have only one d3d11.dll and its dated 6/12/2014 10:58.

ATB
DaveB

[Aharon]

LOL

I have four D3DLL.dll located in
C:\Windows\winsxs\x86_microsoft-windows-directx-direct3d11_31bf3856ad364e35_7.1.7601.22313_none_e3b8b50ecff381db. One of them is dated 11/20/2010. The other three have same date 3/14/2015. I tried deleting them or renaming them but laptop refused to let me do so.

I also have d3dx11_42.dll and d3dx11_43.dll located in C:\Windows\System32. I tried deleting them or renaming them but laptop refused to let me do so.

DXdiag refused to run due to the d3d11.dll error message. I even reinstalled new DX. No luck too

Regards,

Aharon

[DaveB]

Hmm.. I don't know what to suggest for the best. Getting rid of your laptop seems a bit drastic though

ATB
DaveB

[Aharon]

Getting rid of your laptop seems a bit drastic though

Agreed even though it is almost 5 year old, it is still doing well and blazing fast. I think some files are corrupted OR some sector of drive is corrupted. Ran scandisk which revealed no problem.

Regards,

Aharon