Fault Module Name: nvd3dum.dll
I know your going to say graphics card
I'm not telling you it's graphic card. It's Windows ITSELF that told you it's the graphic card. The above report clearly indicates, the graphic driver has crashed.
but I had it tested at the comp shop and it passed all graphic software tests no problems.
That's not really relevant, it might just tell you the card is not broken. However, it doesn't tell anything about the video driver/card combination ability to perform without errors in FSX.
If FSX, for any reasons, triggers an BUG in the video driver, which can't be disclosed by the standard test, because might be also related to an *FSX* bug or an FSX setting, you will have problems in FSX only, with the card happily passing all tests.
The GTX480 is nvidias flagship model at the moment so I don't know why this is happenign when I load your sceneries
You are really too quick to jump to conclusions. Let's search Google for the "nvd3dum.dll" which IS what's happening to you:
Lots of reports of it ( more than 30 thousands, to be precise...), from all kind of sources, like this one:
http://forums.nvidia.com/index.php?showtopic=91437Interesting comment here:
http://forums.nvidia.com/index.php?showtopic=102842The user started having the nvd3dum.dll crash when he broke the fan. Could be that (not strange, for this seaons) your card is overheating when put under heavy load ?
or this one:
http://www.left4deadforums.com/19784-nvd3dum-dll.htmlThis one, also related to FSX:
http://www.flightsimworld.com/forums/index.php?showtopic=155912Interesting comment here:
"Ok, I have worked something out. If I fly at TNCM with lovely weather during the day It works fine. But if I load up TNCM in rain and night then it crashes almost immediately."
Which is exactly what I've said initially: when the system is stressed by ANY complex scenery, FlyTampa in this case, (which of course is not the only thing running, all the addons contribute to the overall stress), something happens, which might be specific to your setup. Heat *could* be a factor here.
I think this gives plenty of evidence it's NOT a problem of our sceneries. It can happen with every software, and it can happen also with other FSX sceneries.