VivJan Posted November 28, 2013 Share Posted November 28, 2013 Due to computer crashing whilst loading FSX, which in hindsight was a good thing, we started again from scratch. Installed FSX & it was fine, decided to put ORBX England on next, that was fine, graphics steady & all looked excellent. Installed the latest libs. Ran FSX no problem. Made no changes to any cfg's no other programs changed or installed. Installed NA PNW, all ok ran FSX flew around Darrington & Concrete just in basic state, no addon airports installed. FSX exited the program back to the desktop just as expected. Installed the same libs update as used after England install, flew around the same areas, turned off FSX lo & behold crashed on exit. We did notice as PNW was loading that at no time did it ask for permission to use the files, which it had when installing England. As we haven't put too much on, am I right in thinking I need to start again or have I missed installing something important. Thanks Viv & Jan Link to comment Share on other sites More sharing options...
Holger Sandmann Posted November 28, 2013 Share Posted November 28, 2013 Hi Viv and Jan, FSX crashes can happen for all sorts of reasons and are thus difficult to diagnose. It would help to get more information about the CTD and particularly the module that cause it. If the crash-on-exit itself doesn't give you any error message you could share with us you can probably track it down in the Windows Event Viewer log; please see http://www.orbxsystems.com/forum/topic/50165-permanent-crash-of-fsx-at-lands-inn-after-kwys-install/?p=442599 Cheers, Holger Link to comment Share on other sites More sharing options...
bumprock Posted November 28, 2013 Share Posted November 28, 2013 Hi Holger, I have recently moved up to a Windows 8 OS with FSX and PNW as well as FTX Global installed. When traveling SE from Smithers, BC towards Houston, with the scenery active, the system suddenly announce that FSX has stopped working and click to close. It is totally repeatable with the FTX area active, or with FTX Global in hybrid. It does not exit with just the FTX Global. Here is the event log entry: Log Name: Application Source: Application Error Date: 11/28/2013 2:12:24 PM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: STWDesktop Description: Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14 Faulting module name: g2d.dll, version: 10.0.61637.0, time stamp: 0x46fadb58 Exception code: 0xc0000005 Fault offset: 0x000843ac Faulting process id: 0x1bb0 Faulting application start time: 0x01ceec6cff65d96a Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe Faulting module path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\g2d.dll Report Id: 02dd8fbb-5861-11e3-beb5-a41f7274f99b Faulting package full name: Faulting package-relative application ID: Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2013-11-28T19:12:24.000000000Z" /> <EventRecordID>14043</EventRecordID> <Channel>Application</Channel> <Computer>STWDesktop</Computer> <Security /> </System> <EventData> <Data>fsx.exe</Data> <Data>10.0.61637.0</Data> <Data>46fadb14</Data> <Data>g2d.dll</Data> <Data>10.0.61637.0</Data> <Data>46fadb58</Data> <Data>c0000005</Data> <Data>000843ac</Data> <Data>1bb0</Data> <Data>01ceec6cff65d96a</Data> <Data>C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe</Data> <Data>C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\g2d.dll</Data> <Data>02dd8fbb-5861-11e3-beb5-a41f7274f99b</Data> <Data> </Data> <Data> </Data> </EventData> </Event> Link to comment Share on other sites More sharing options...
VivJan Posted November 29, 2013 Author Share Posted November 29, 2013 Hi Holger, thanks to your detailed instructions, we have a screenshot of the crash on exit out of FSX, we have also left on the screenshot the message we get on screen when we exit the game. Thanks for your help Viv & Jan Link to comment Share on other sites More sharing options...
Holger Sandmann Posted November 29, 2013 Share Posted November 29, 2013 Hi guys, Viv & Jan, it's possible that the aiplayer.dll crash stems from an incorrect file included with PNW SP5; please see http://www.orbxsystems.com/forum/topic/37852-error-ai-player-at-skagit/#entry384444 bumprock, unfortunately, g2d errors are quite generic and thus hard to diagnose and fix; see http://forum.aerosoft.com/index.php?/topic/69824-ctd-mid-flight-fault-module-name-g2ddll/ . I'd suggest doing Google searches with suitable keywords and hopefully some of the discussions show similarities to your own setup. Cheers, Holger Link to comment Share on other sites More sharing options...
VivJan Posted December 4, 2013 Author Share Posted December 4, 2013 Hi Holger, we haven't been ignoring you, we have reinstalled the computer from windows up, FSX is now ok, PNW is on without problems, plus some more ORBX scenery including patches & libraries. Thank you for your suggestions which worked, we are very grateful for all your help. Best wishes Viv & Jan Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.