NWA1999 5 Posted December 11, 2017 Share Posted December 11, 2017 Hello, On my last two flights KMIA-KATL-KMEM in the CRJ9 I've had CTD at the same point to right before I turn base. I do have add-on scenery for all of these airports. No idea what is causing these Any ideas? Thanks, Robbie Link to comment Share on other sites More sharing options...
Aerosoft Aerosoft Team [Inactive Account] 51558 Posted December 12, 2017 Aerosoft Share Posted December 12, 2017 Can you try without the scenery because if it is at the same point it could be scenery caused. If not share the flight plan. Link to comment Share on other sites More sharing options...
CXA007 0 Posted December 30, 2017 Share Posted December 30, 2017 Not trying to highjack the topic but I had 3 CTD today with the latest update. Happened twice when I popped the pilot displays out in to their 2D versions, but only when the AP was active, on the ground did it and there wasn't an issue. 3rd time, was when I was setting up for an approach switch the yoke off to access the map zoom dial. click the dial and the map zoomed the wrong way, so I clicked it the other way to zoom back in and CTD no warning no pause just shut down.. Running P3Dv4.1 on an I7-6700 (16gig of ram) with an ATI RX480 8gig card pushing 3 monitors at 5760x1080 eyefinity setup.. Be happy to provide any other information.. Link to comment Share on other sites More sharing options...
Aerosoft Aerosoft Team [Inactive Account] 51558 Posted December 30, 2017 Aerosoft Share Posted December 30, 2017 Does the windows log say anything? Link to comment Share on other sites More sharing options...
CXA007 0 Posted January 1, 2018 Share Posted January 1, 2018 On 2017-12-30 at 5:25 AM, Mathijs Kok said: Does the windows log say anything? Didn't see anything in the event log for the issues last week. Crashed again today just as I was switching the AP on after take off. An error box came up telling me the heading hold control failed (or something like that) gave me an Ok button but nothing happened as I pushed it. P3D stayed running however the screen went black, I was able to shut it down via the X on the upper menu bar.. Here is what the windows event log showed for an error at the time.. Log Name: Application Source: Application Error Date: 2018-01-01 3:05:09 PM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: AURORA Description: Faulting application name: Prepar3D.exe, version: 4.1.7.22841, time stamp: 0x59d67e95 Faulting module name: panels.dll, version: 4.1.7.22841, time stamp: 0x59d67e09 Exception code: 0xc0000409 Fault offset: 0x00000000000b5cb8 Faulting process id: 0x2f18 Faulting application start time: 0x01d38331a2443216 Faulting application path: C:\Program Files\Lockheed Martin\Prepar3D v4\Prepar3D.exe Faulting module path: C:\Program Files\Lockheed Martin\Prepar3D v4\panels.dll Report Id: ccabcb5b-234d-4d25-90de-ae6f88ce3843 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="2018-01-01T20:05:09.728239800Z" /> <EventRecordID>1940</EventRecordID> <Channel>Application</Channel> <Computer>AURORA</Computer> <Security /> </System> <EventData> <Data>Prepar3D.exe</Data> <Data>4.1.7.22841</Data> <Data>59d67e95</Data> <Data>panels.dll</Data> <Data>4.1.7.22841</Data> <Data>59d67e09</Data> <Data>c0000409</Data> <Data>00000000000b5cb8</Data> <Data>2f18</Data> <Data>01d38331a2443216</Data> <Data>C:\Program Files\Lockheed Martin\Prepar3D v4\Prepar3D.exe</Data> <Data>C:\Program Files\Lockheed Martin\Prepar3D v4\panels.dll</Data> <Data>ccabcb5b-234d-4d25-90de-ae6f88ce3843</Data> <Data> </Data> <Data> </Data> </EventData> </Event> Link to comment Share on other sites More sharing options...
Aerosoft Aerosoft Team [Inactive Account] 51558 Posted January 2, 2018 Aerosoft Share Posted January 2, 2018 The "Faulting module name: panels.dll," is unfortunately a well known one, if you Google it you will find it related to every kind of product. And almost always without a solution. A screenshot of that error message you mention would be helpful. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.