Trying to Fly from EHAM to EGNX after 5-10Mins on the ground doing preflight FS9 Crashes, I've tried to do this severall times now and the same result.
Aircraft useing
PIC WILCO 737-300 BMIbaby
[ERROR REPORT DETAILS]
Problem Event Name: APPCRASH
Application Name: fs9.exe
Application Version: 9.1.0.40901
Application Timestamp: 4135a208
Fault Module Name: nvd3dum.dll
Fault Module Version: 8.17.12.6658
Fault Module Timestamp: 4d27c323
Exception Code: c0000005
Exception Offset: 003d2314
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 2057
Additional Information 1: f264
Additional Information 2: f264a5c699f1187f89bc2bb3c9486dc9
Additional Information 3: 874a
Additional Information 4: 874a921ccdc589c2c8a3d5e42416540f
Read our privacy statement online:
http://go.microsoft....mp;clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
0
FS9 Problem
Started by
Liam170
, Mar 14 2011 05:45 PM
6 replies to this topic
#1
Posted 14 March 2011 - 05:45 PM
#2
Posted 16 March 2011 - 03:44 PM
As the error report "reports", the problem is with nvd3dum.dll
A quick Google reveals that it's an issue with Nvidia drivers/control panel. You should update your Nvidia drivers. You can do that here: http://www.nvidia.co...aspx?lang=en-us
A quick Google reveals that it's an issue with Nvidia drivers/control panel. You should update your Nvidia drivers. You can do that here: http://www.nvidia.co...aspx?lang=en-us
#3
Posted 17 March 2011 - 08:50 PM
Im sure there Upto Date :S, Could NvidaInspecotr be the issue?
#4
Posted 17 March 2011 - 10:33 PM
Liam170, on Mar 17 2011, 09:50 PM, said:
Im sure there Upto Date :S, Could NvidaInspecotr be the issue?
If you're not willing to do it via Nvidia, then you can get them from Microsoft:
Start > Run > devmgmt.msc > click 'Display Adapters' > select your card > click 'Update Driver'
It's an issue with a .dll file associated with your driver. I suggest updating it before doing any drastic action. After a bit more research, it seems that this error occurs when applications "hook" nvd3dum.dll, programs like Fraps and FS addons.
#5
Posted 18 March 2011 - 08:36 PM
Updated Drivers still same error with same Aircraft
PIC Feelthere Wilco 737
AppName: fs9.exe AppVer: 9.1.0.40901 ModName: g2d.dll
ModVer: 9.1.0.40901 Offset: 00086ef9
PIC Feelthere Wilco 737
AppName: fs9.exe AppVer: 9.1.0.40901 ModName: g2d.dll
ModVer: 9.1.0.40901 Offset: 00086ef9
#6
Posted 19 March 2011 - 12:43 PM
The issue here is with g2d.dll
A quick Google tells me that this is a common problem.
See these:
http://nzff.org/foru...?showtopic=6183
http://www.visualfli...p?TOPIC_ID=4009
http://forum.simflig...c/32525-g2ddll/
http://www.forum.aer...showtopic=16226
Looks like rebuilding the CFG solved the problem. Delete the CFG file and it will be rebuilt the next time you open FS.
A quick Google tells me that this is a common problem.
See these:
http://nzff.org/foru...?showtopic=6183
http://www.visualfli...p?TOPIC_ID=4009
http://forum.simflig...c/32525-g2ddll/
http://www.forum.aer...showtopic=16226
Looks like rebuilding the CFG solved the problem. Delete the CFG file and it will be rebuilt the next time you open FS.
#7
Posted 20 March 2011 - 05:03 PM
Strange all worked again today :s..even allowed me to do a few Checkride Circuits, But it did crash again but no Error report after programming the FMC.