Delta Virtual Airlines Water Cooler | PC Support |
CTD issue |
DVA6295
Captain, B777-200
OLP
Joined on August 18 2008
50 State Club
Globetrotter
Everett Millennium Club
Moose Club
Kangaroo Club
Flying Colonel
DVA Fifteen-Year Anniversary
Two Million Mile Club
Mukilteo, WA
1,794 legs, 5,572.7 hours
2 legs,
3.6 hours online 1,768 legs,
5,501.9 hours ACARS
|
Posted onPost created on
July 22 2017 22:47 ET by Phillip Hendricks
|
Lets hope someone here can help me with this issue? Whenever I setup a flight, I can go about 3-10 minutes before FSX CTD. Below is what the event viewer is saying is going on.
Description:
Faulting application name: fsx.exe, version: 10.0.62615.0, time stamp: 0x559f9a9a
Faulting module name: nvd3dum.dll, version: 22.21.13.8476, time stamp: 0x5952b7cc
Exception code: 0xc0000005
Fault offset: 0x00702aa1
Faulting process id: 0x19f0
Faulting application start time: 0x01d303468032a546
Faulting application path: C:\Steam\steamapps\common\FSX\fsx.exe
Faulting module path: C:\Windows\system32\nvd3dum.dll
Report Id: 17a86527-6f3b-11e7-8b2c-00224d99fe45
I have done all sorts of research on this particular problem. Here are some of the actions I've performed in an effort to correct this problem.
1. Updated the BIOS driver's
2. Checked my system for any out of date driver's
3. Tried an older version of Direct X
4. Installed the current driver's for my GPU. (Ge Force GTX1050 ti) Also tried 7 older driver versions, each time performing a clean install.
5. Everything was okay for a memtest.
Each time I did a driver change, I made sure that anti virus programs were disabled. Depending on what you read, some say that they had the same issue even though they performed a clean install of FSX.
I was considering wiping FSX till I read the post about still crashing after a clean re-install. If anyone has any suggestions on this problem? I would love to hear them.

|
DVA4614
Captain, CRJ-200
Joined on February 25 2007
Stage 1 Jet Century Club
Century Club
DVA Fifteen-Year Anniversary
Madison Heights, MI USA
150 legs, 302.0 hours
3 legs,
4.2 hours online 135 legs,
276.1 hours ACARS
|
Posted onPost created on
July 28 2017 14:39 ET by Peter Tambornini
|
Is your system overclocked?
Peter TamborniniCaptain, CRJ-200
|
|
DVA6295
Captain, B777-200
OLP
Joined on August 18 2008
50 State Club
Globetrotter
Everett Millennium Club
Moose Club
Kangaroo Club
Flying Colonel
DVA Fifteen-Year Anniversary
Two Million Mile Club
Mukilteo, WA
1,794 legs, 5,572.7 hours
2 legs,
3.6 hours online 1,768 legs,
5,501.9 hours ACARS
|
Posted onPost created on
July 29 2017 13:58 ET by Phillip Hendricks
|
I have not overclocked anything.

|
DVA9655
Senior Captain, B747-400
OLP
Joined on January 01 2011
50 State Club
Everett 500 Club
DVA Ten-Year Anniversary
Golden State Club
Two Million Mile Club
Globetrotter
Online Double Century Club
Nine Century Club
"DAL9655, you are cleared for takeoff" New York, NY
999 legs, 5,366.4 hours
242 legs,
882.9 hours online 799 legs,
4,425.5 hours ACARS 12 legs,
40.6 hours event
|
Posted onPost created on
August 01 2017 12:50 ET by Remy Mermelstein
|
FSX is a lost cause. You will spend your entire life trying to go through a flight with no issues...seems if you dont have issues you dont get em, but if you have issues they never leave you. I have a top notch system, high end components, and FSX never performed. It has issues, as a program, mainly being 32-bit...
I would just take the jump to P3DV4, if you can.
THAT said, if you want to try an get FSX working, try running as admin. If you run other programs with it, turn those off and just run FSX...see if it crashes. If it doesnt, then keep turning on other addons till it crashes. Try using default planes.
Try looking at this post as well on that .dll file that keeps crashing: https://forums.geforce.com/default/topic/657016/faulting-module-name-nvd3dum-dll/?offset=15
Try reverting back to an old driver.
The .dll file that is crashing is from your graphics card. If you recently updated your drivers, IK there were issues with the latest batch - I had to revert back to an old driver as well.
You could also delete the .dll file, reinstall the driver or find the .dll file and replace it.
Also check this post: https://www.avsim.com/forums/topic/395330-ctd-caused-by-nvd3dumdll/
But, again, you are gonna spend days and days getting this to work if it does not fix fast, and it might be worth it to just jump the ship.

|
DVA6295
Captain, B777-200
OLP
Joined on August 18 2008
50 State Club
Globetrotter
Everett Millennium Club
Moose Club
Kangaroo Club
Flying Colonel
DVA Fifteen-Year Anniversary
Two Million Mile Club
Mukilteo, WA
1,794 legs, 5,572.7 hours
2 legs,
3.6 hours online 1,768 legs,
5,501.9 hours ACARS
|
Posted onPost created on
August 07 2017 20:49 ET by Phillip Hendricks
|
It's been an interesting time to say the least. So here's what I've done thus far.
Uninstalled all scenery's
Uninstalled all payware aircraft
Uninstalled all utilities
Uninstalled FSX-SE
Deleted any and all traces of FSX from my computer. Re-installed FSX-SE, and re-installed each scenery. After each scenery was installed, I ran FSX to make sure that it installed correctly. I performed this same routine for my payware aircraft, and my utilities. So far everything was working good.
Then I re-installed EZDOK. I was in the process of setting my views in iFly 737 and it CTD. So then I tried my LDS 767. Part way through the process of setting my views? CTD! Moved on and tried it on PMDG 777. Same thing happened. Totally uninstalled EZDOK, and so far I haven't experienced a CTD. Gonna perform some additional short/long flights and see if I got this figured out?

|
DVA9655
Senior Captain, B747-400
OLP
Joined on January 01 2011
50 State Club
Everett 500 Club
DVA Ten-Year Anniversary
Golden State Club
Two Million Mile Club
Globetrotter
Online Double Century Club
Nine Century Club
"DAL9655, you are cleared for takeoff" New York, NY
999 legs, 5,366.4 hours
242 legs,
882.9 hours online 799 legs,
4,425.5 hours ACARS 12 legs,
40.6 hours event
|
Posted onPost created on
August 08 2017 08:37 ET by Remy Mermelstein
|
Phillip Hendricks wrote:It's been an interesting time to say the least. So here's what I've done thus far.
Uninstalled all scenery's
Uninstalled all payware aircraft
Uninstalled all utilities
Uninstalled FSX-SE
Deleted any and all traces of FSX from my computer. Re-installed FSX-SE, and re-installed each scenery. After each scenery was installed, I ran FSX to make sure that it installed correctly. I performed this same routine for my payware aircraft, and my utilities. So far everything was working good.
Then I re-installed EZDOK. I was in the process of setting my views in iFly 737 and it CTD. So then I tried my LDS 767. Part way through the process of setting my views? CTD! Moved on and tried it on PMDG 777. Same thing happened. Totally uninstalled EZDOK, and so far I haven't experienced a CTD. Gonna perform some additional short/long flights and see if I got this figured out? 
I had issues with EZDock as well when using FSX... interesting thx.

|
DVA6295
Captain, B777-200
OLP
Joined on August 18 2008
50 State Club
Globetrotter
Everett Millennium Club
Moose Club
Kangaroo Club
Flying Colonel
DVA Fifteen-Year Anniversary
Two Million Mile Club
Mukilteo, WA
1,794 legs, 5,572.7 hours
2 legs,
3.6 hours online 1,768 legs,
5,501.9 hours ACARS
|
Posted onPost created on
October 15 2017 17:25 ET by Phillip Hendricks
|
The woes continue. I have discovered that some of my payware aircraft are CTD a short time after starting. After the extensive reading I've done, and all the suggested fixes. I think I'm gonna start with a fresh Windows 7 install on a new HDD that I got.

|
DVA9545
Senior Captain, B777-200
OLP, 737-ATP
Joined on March 03 2011
50 State Club
Globetrotter
Quad-Jet Quartermaster
US Coastal Club
US Mountaineer Club
Million Mile Club
Events Double Century Club
DVA Ten-Year Anniversary
Toulouse 500 Club
Bi-Millennium Club
Online Twenty Century
"YUPIIIII" Goiás Brazil
2,492 legs, 5,039.3 hours
2,321 legs,
4,760.9 hours online 2,484 legs,
5,009.7 hours ACARS 271 legs,
683.8 hours event
|
Posted onPost created on
October 16 2017 00:20 ET by Thiago Braga
|
Phillip Hendricks wrote:The woes continue. I have discovered that some of my payware aircraft are CTD a short time after starting. After the extensive reading I've done, and all the suggested fixes. I think I'm gonna start with a fresh Windows 7 install on a new HDD that I got. 
I just did on my a new fresh install (formatted) on my PC too and now I have an awesome P3D V4 working great.

|
DVA11380
Senior Captain, A330-300
OLP
Joined on March 20 2013
50 State Club
Globetrotter
Million Mile Club
Iron Dispatcher
US Coastal Club
Commuter Conquest
US Mountaineer Club
Everett Millennium Club
Events Century Club
Online Fifteen Century
Bi-Millennium Club
DVA Ten-Year Anniversary
"If cats could text you, they wouldn't." Boston, MA
2,082 legs, 4,889.8 hours
1,722 legs,
3,657.3 hours online 2,060 legs,
4,813.2 hours ACARS 172 legs,
354.7 hours event 422 legs dispatched, 311.4
hours
|
Posted onPost created on
October 16 2017 21:17 ET by Bob Donovan
|
Hi Phil.
It's been a long time since I've used FSX, but I seem to remember my Anti-aliasing setting on my Nvidia card causing everything else to go nuts and CTD.
If you are using Nvidia Inspector external settings, you might want to setup a new profile with defaults for the card, then try the lowest AA setting in FSX.
There was a point where I had good frame rates, so I pushed 8xSSA (or something like that) and it was stable for a while, but then started CTD's. I eventually troubleshot it down to AA settings and lowering them stabilized my FSX setup.
Just one of the 2 million things that made FSX crash.

|