Search the Community
Showing results for tags 'd3d11.dll'.
Found 2 results
-
A little tip I picked up from my VA Chief that worked like a charm for me. I suddenly started getting CTD and FATAL ERRORS after 2 weeks of flying fine all over the US but suddenly I was FATAL ERRORING while trying to depart Tampa to head back home to Texas. I could not get off the ground. Going through start up checks.. CRASH... Taxing CRASH. Thinking about a steak dinner, CRASH. This is something you should do frequently, say after every 3 or so long flights. This is considered Basic FSX Maintenance to keep your sim happy and relatively crash free on this type of crash problem. 1. Navigate to your %appdata% folder and go into LOCAL (Not ROAMING). Find your Microsoft folder and your shader folder. Go into the shader folder. Delete the Shader10 and Shader folder if you have them. Be sure you don't PERMANENTLY delete them. Just delete them to your recycle bin. If something screws up you want to be able to restore the files. 2. Navigate to your C: drive to the ProgramData folder. Navigate to your Microsoft and then FSX folder inside the ProgramData folder. Delete the Facilities and SceneIndexes folders. Do not touch any files outside these folders or the SceneryCache folder. Once again, do not permanently delete these files. Leave them in your recycle bin encase you need to restore them. 3. Start FSX and let it rebuild your Facilities, Scene Indexes and Shader folders. Fly! PROFIT. This little maintenance tip got rid of my CTDs and I was able to come home to Dallas Love in Texas. Hope it helps anyone out that is experiences this type of sudden crashing after your FSX was working fine for days. This type of CTD commonly shows up as D3D11.DLL or StackHash type crashes in Event Viewer/AppCrashViewer.
-
Earlier today I had discussed my excellent performance with settings in P3DV2.5 during flights from KLAX to KPHX - http://forum.avsim.net/topic/461977-bad-performance-in-p3d-25/page-2#entry3183563. I decided to try my normal testing flight from FSDT KORD to FlightBeam's KIAD. Knowing that it was snowing in Washington, I figured this would be a great challenge to land without an OOM. When taking the same flight in FSX with lower settings, I usually have an OOM on approach to KIAD or at touchdown (and that's without nasty weather!). I landed successfully!!! Visibility was less than 10 feet as I did not see the runway or lights until touchdown. FSUIPC monitor was binging with "Running Out of Memory" messages almost at the beginning of the approach phase. After landing and taking the first taxiway off the runway, I got the infamous siren that APP was disconnected and when I went to shut that off, it crashed with about 150MB's of VAS remaining. Here's the FSUIPC report: What was shocking was the fact that the AppCrashView report stated the faulting module was the DirectX d3d11.dll and nothing OOM related (like API.dll or ntdll.dll). Here's that report: It is amazing there was no AppCrash long before landing so I'm very happy and excited with the results I got. It shows that there is some form of management of VAS in P3DV2.5 and that's good. I know that if the weather had not been nasty, I would have had no problems whatsoever. I used the same P3D.cfg settings as posted in the link above. Hope this assessment helps someone else. EDIT: I'm reposting this topic as it got totally messed up with my previous posting of the topic 14 times due to a 503 Server Connection error. The other one was confusing and this is for continuity. Best regards,
