chewwy94 5 Posted August 2, 2017 Share Posted August 2, 2017 Well after livestreaming my initial impressions of the aircraft for 8 hours, with 2 flights completed, I was really happy with the aircraft and enjoying flying it. Unfortunately my luck seems to have ran out as I have now had 4 CTD's within the space of about an hour of "in sim time". There is no set time in the flight this happens, just randomly when it feels like crashing. I received 2 event viewer faulting module paths claiming the CTD to be caused by the F:\Prepar3d v4|acontain.dll Since then I have had another 2 CTD's, this time caused by F:\Prepar3d v4\SimObjects\Airplanes\Aerosoft CRJ Base\panel\ASCRJ.dll It's also a real shame that the aircraft does not seem to be compatible with FSUIPC autosave. I have tried twice to load in the aircraft after these CTD's, and the aircraft doesn't want to load in the panel state of the autosave correctly. Any help would be greatly appreciated as until this is fixed I won't feel comfortable flying the aircraft, let alone trying to entertain a Twitch audience with it! Matt P.S. It is also worth noting that before today I have only ever had 1 CTD in P3D v4, which was caused by the TFDi 717. I have already amounted up hundreds of hours with PMDG products in v4, and have not had a single CTD. Link to comment Share on other sites More sharing options...
Hans Hartmann [OLD] 1419 Posted August 2, 2017 Share Posted August 2, 2017 I'm sorry, but I can't help you here. Just a number of CTDs without any description of circumstances doesn't tell me anything. We haven't had any CTD reports in the beta group for months, so I'm pretty sure that they are not that common, let alone random. Link to comment Share on other sites More sharing options...
chewwy94 5 Posted August 2, 2017 Author Share Posted August 2, 2017 No CTD reports in the beta group for months? I had more reports of CTD's than I could count from viewers in my Twitch chat earlier on so I hope they report them here like I'm trying to do to get them looked into! I have provided a link to the VOD of the stream, showing the exact moment I encounter the first CTD. The others were caught off stream, once whilst parked at the gate setting up the FMS, the other whilst on descent into KSLC after switching into HDG select. You can also see in the VOD me trying to load up the sim with an FSUIPC autosave and the aircraft not correctly retaining the panel state. It would be very coincidental to have 4 CTD's in the space of one hour, with 2 specific faulting modules just randomly. https://www.twitch.tv/videos/163838179 7:45:39 is the timestamp Link to comment Share on other sites More sharing options...
Loïc Lourdel 37 Posted August 2, 2017 Share Posted August 2, 2017 Good evening me too its crash ... Nom de l’application défaillante Prepar3D.exe, version : 4.0.28.21686, horodatage : 0x594a7255 Nom du module défaillant : ASCRJ.dll, version : 1.0.0.1, horodatage : 0x5980443e Code d’exception : 0xc0000409 Décalage d’erreur : 0x000000000016f084 ID du processus défaillant : 0x334c Heure de début de l’application défaillante : 0x01d30bcb7015bcaf Chemin d’accès de l’application défaillante : C:\Prepar3D V4 \Prepar3D.exe Chemin d’accès du module défaillant: C:\Prepar3D V4 \SimObjects\Airplanes\Aerosoft CRJ Base\panel\ASCRJ.dll ID de rapport : 9922cde4-2c77-48ef-9b99-da8efb90fc5d Nom complet du package défaillant : ID de l’application relative au package défaillant : Link to comment Share on other sites More sharing options...
samwheeler 2 Posted August 2, 2017 Share Posted August 2, 2017 I myself did have a CTD as well. Mine was just after departure out of DCA, in the 700, it happened as I moved the range knob. Link to comment Share on other sites More sharing options...
chewwy94 5 Posted August 2, 2017 Author Share Posted August 2, 2017 13 minutes ago, lolocool16 said: Chemin d’accès du module défaillant: C:\Prepar3D V4 \SimObjects\Airplanes\Aerosoft CRJ Base\panel\ASCRJ.dll Well that is already one more person reporting the exact same faulting module within 15 minutes or so of this post being created. Link to comment Share on other sites More sharing options...
Hans Hartmann [OLD] 1419 Posted August 2, 2017 Share Posted August 2, 2017 16 minutes ago, chewwy94 said: https://www.twitch.tv/videos/163838179 7:45:39 is the timestamp Do I see that right that there was a crash out of nowhere, no waypoint change, no input, no nothing? 16 minutes ago, chewwy94 said: No CTD reports in the beta group for months? Yes, exactly that. Do you really think we would have released a product that crashes and we know it? Link to comment Share on other sites More sharing options...
reverseidle 0 Posted August 2, 2017 Share Posted August 2, 2017 chewwyCTD Link to comment Share on other sites More sharing options...
chewwy94 5 Posted August 2, 2017 Author Share Posted August 2, 2017 Just now, Hans Hartmann said: Yes, exactly that. Do you really think we would have released a product that crashes and we know it? I don't remember insinuating that you knew about this? Hence why I am posting it on here to report it back to you and ask for help..... It just seemed a little weird that you haven't had a single report of a CTD in the aircraft for months, but within the space of only a few hours I've been told about numerous ones. As I said, I hope they all report them to help. Link to comment Share on other sites More sharing options...
Hans Hartmann [OLD] 1419 Posted August 2, 2017 Share Posted August 2, 2017 I don't deny that there apparently is some issue that escaped the beta test. I'm doing my best to find out what it is and what causes it. The more detailed information I can get, the higher is the chance that I find it quickly and can fix it without much delay. Link to comment Share on other sites More sharing options...
chewwy94 5 Posted August 2, 2017 Author Share Posted August 2, 2017 Along with the video shown up above, I am now pasting the entire fault logs from each of the individual CTD's Crash 1 at 18:34:06 BST (This was the crash shown in the VOD. No buttons clicked outside or inside the sim. Mouse was hovering over the MFD) Faulting application name: Prepar3D.exe, version: 4.0.28.21686, time stamp: 0x594a7255 Faulting module name: acontain.dll, version: 4.0.28.21686, time stamp: 0x594a71d5 Exception code: 0xc000041d Fault offset: 0x0000000000003123 Faulting process id: 0x5374 Faulting application start time: 0x01d30b9536f7fdad Faulting application path: F:\Prepar3d v4\Prepar3D.exe Faulting module path: F:\Prepar3d v4\acontain.dll Report Id: a82a512e-9f0a-4d3e-99b4-594d4f4063d0 Faulting package full name: Faulting package-relative application ID: Crash 2 at 18:43:22 BST with the same faulting module: Faulting application name: Prepar3D.exe, version: 4.0.28.21686, time stamp: 0x594a7255 Faulting module name: acontain.dll, version: 4.0.28.21686, time stamp: 0x594a71d5 Exception code: 0xc000041d Fault offset: 0x0000000000003123 Faulting process id: 0x14ec Faulting application start time: 0x01d30bb5b7b7d3fe Faulting application path: F:\Prepar3d v4\Prepar3D.exe Faulting module path: F:\Prepar3d v4\acontain.dll Report Id: da16d705-7557-4577-b647-c83cc7239289 Faulting package full name: Faulting package-relative application ID: Crash 3 at 20:22:42 BST. When CTD happened I was checking the iPad for my zero fuel weight to enter into the FMC: Faulting application name: Prepar3D.exe, version: 4.0.28.21686, time stamp: 0x594a7255 Faulting module name: ASCRJ.dll, version: 1.0.0.1, time stamp: 0x5980443e Exception code: 0xc0000409 Fault offset: 0x000000000016f084 Faulting process id: 0x2848 Faulting application start time: 0x01d30bc3f845aa51 Faulting application path: F:\Prepar3d v4\Prepar3D.exe Faulting module path: F:\Prepar3d v4\SimObjects\Airplanes\Aerosoft CRJ Base\panel\ASCRJ.dll Report Id: 4c51a9f2-8adf-4c6a-b430-1a9a0b2c99ed Faulting package full name: Faulting package-relative application ID: Crash 4 at 21:12:22 BST. This CTD occurred when I had reached the final waypoint of the STAR in my flight plan and switched to HDG select on the MCP to vector myself onto the downwind leg. Altitude was 10000ft and speed around 240 knots: Faulting application name: Prepar3D.exe, version: 4.0.28.21686, time stamp: 0x594a7255 Faulting module name: ASCRJ.dll, version: 1.0.0.1, time stamp: 0x5980443e Exception code: 0xc0000409 Fault offset: 0x000000000016f084 Faulting process id: 0x48a8 Faulting application start time: 0x01d30bc4ddb54a7e Faulting application path: F:\Prepar3d v4\Prepar3D.exe Faulting module path: F:\Prepar3d v4\SimObjects\Airplanes\Aerosoft CRJ Base\panel\ASCRJ.dll Report Id: 4b058d43-4f46-448b-af36-27785e82b44d Faulting package full name: Faulting package-relative application ID: Link to comment Share on other sites More sharing options...
Hans Hartmann [OLD] 1419 Posted August 2, 2017 Share Posted August 2, 2017 OK, thanks. I'll try to reproduce those. One more question: what other add-ons (utility type, not scenery) were running at the time? I want to make sure that my testing environment is as similar to your system as possible. Link to comment Share on other sites More sharing options...
chewwy94 5 Posted August 2, 2017 Author Share Posted August 2, 2017 1 minute ago, Hans Hartmann said: what other add-ons (utility type, not scenery) were running at the time? I usually run a multitude of addons, which again haven't caused me issues with any other aircraft, however the only ones being used during these crashes were Active Sky 16, Active Sky Cloud Art, and Chaseplane. I have reported these modules to Kevin from Chaseplane to see if there is any possibility it has any relation to Chaseplane, however I doubt it would be so. Link to comment Share on other sites More sharing options...
Hans Hartmann [OLD] 1419 Posted August 2, 2017 Share Posted August 2, 2017 No, we haven't had problems with any of these modules. I have AS16 running and many of the testers used Chaseplane since the very first alpha. I looked up the exception code 0xc0000409 and I start to have an idea what might happen. I need to do some more testing though. Link to comment Share on other sites More sharing options...
dkinder5063 6 Posted August 2, 2017 Share Posted August 2, 2017 I've had 2 CTDs with my CRJ as well. One while on approach into ORD when trying to adjust my arrival runway in the FMC and the second one while setting up my FMC in ORD for a flight to MCI. Very frustrating. Link to comment Share on other sites More sharing options...
dkinder5063 6 Posted August 2, 2017 Share Posted August 2, 2017 Here are my log dumps: First CTD: Faulting application name: fsx.exe, version: 10.0.62615.0, time stamp: 0x559f9a9a Faulting module name: ASCRJ.dll, version: 1.0.0.1, time stamp: 0x59804424 Exception code: 0xc0000409 Fault offset: 0x001ecad4 Faulting process id: 0x2b78 Faulting application start time: 0x01d30ba1b1d9b2ff Faulting application path: D:\Program Files (x86)\Steam\steamapps\common\FSX\fsx.exe Faulting module path: D:\Program Files (x86)\Steam\steamapps\common\FSX\SimObjects\Airplanes\Aerosoft CRJ Base\panel\ASCRJ.dll Report Id: 86d03c27-9422-410d-aeac-c68761f2a3d4 Faulting package full name: Faulting package-relative application ID: Second CTD: The program fsx.exe version 10.0.62615.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel. Process ID: 1f8c Start Time: 01d30bd1e089707e Termination Time: 101 Application Path: D:\Program Files (x86)\Steam\steamapps\common\FSX\fsx.exe Report Id: 5b842daf-08a9-41fc-bd9d-e72bda8a8fd1 Faulting package full name: Faulting package-relative application ID: Looks like its the same exception code Chewy got. 0xc0000409 Link to comment Share on other sites More sharing options...
chewwy94 5 Posted August 2, 2017 Author Share Posted August 2, 2017 It should be noted that I flew a 2 hour route from KIDA - KMSP and then 2 hours back to KMSP - KIDA without a single hitch as the entire Twitch VOD shows. The same addons were being used as listed above. I restarted the sim when landing at KMSP to fix the nav light bug with the SPAI traffic addon, and then turned around the aircraft without restarting the sim once landing back at KIDA to head to KSLC. Link to comment Share on other sites More sharing options...
Hans Hartmann [OLD] 1419 Posted August 2, 2017 Share Posted August 2, 2017 Do you remember what FMS page you had open during those last two CTDs? Link to comment Share on other sites More sharing options...
chewwy94 5 Posted August 2, 2017 Author Share Posted August 2, 2017 Off the top of my head I believe the right FMS was on the legs page and the left FMS was either on the PROG page, the PERF INIT page where you enter gross weight etc., or the VNAV 3/3 page. These may not be totally accurate as it's just roughly off the top of my head and each CTD were captured at different times of flight so I most likely had different FMS pages up in each scenario. Link to comment Share on other sites More sharing options...
Hans Hartmann [OLD] 1419 Posted August 2, 2017 Share Posted August 2, 2017 OK. One of the FMSes was definitely on a page that displays a fuel amount. It seems to be the same problem as in this thread: Unfortunately I couldn't reproduce that yet, even with his step-by-step guide. But I keep trying. Link to comment Share on other sites More sharing options...
chewwy94 5 Posted August 2, 2017 Author Share Posted August 2, 2017 I'll see if I can replicate it at any other point tomorrow if I get a chance to take a look myself and report back. Please let me know if there is any other information you need. Link to comment Share on other sites More sharing options...
PineappleWizard 44 Posted August 3, 2017 Share Posted August 3, 2017 I too have had an ASCRJ.dll CTD. Flying into KSEA on the MARNR6, flying in HDG mode, VS mode, used the LEGS page to put in SONDR as the next waypoint like one does for direct to in Boeing aircraft, and that is when the sim crashed. P3D v4 with AS16, Chaseplane, navigraph data. Also attached is a screenshot of when it happened. I had the MFD popup open, left FMS on LEGS and right FMS on PROG. Really hope you guys can get this ironed out. Great aircraft, but unflyable with CTDs. Faulting application name: Prepar3D.exe, version: 4.0.28.21686, time stamp: 0x594a7255 Faulting module name: ASCRJ.dll, version: 1.0.0.1, time stamp: 0x5980443e Exception code: 0xc0000409 Fault offset: 0x000000000016f084 Faulting process id: 0x2b38 Faulting application start time: 0x01d30be5b78218f0 Faulting application path: C:\P3D\Prepar3D.exe Faulting module path: C:\P3D\SimObjects\Airplanes\Aerosoft CRJ Base\panel\ASCRJ.dll Report Id: b1a5d484-50d4-4aa1-9d21-6c66c0e3379f Faulting package full name: Faulting package-relative application ID: Please login to display this image. Link to comment Share on other sites More sharing options...
mseiwald 79 Posted August 3, 2017 Share Posted August 3, 2017 Had the same issue now 2 times in a row at T2G EDDM Gate 345 with the LH CRJ900. All i did was start the flight -> Select Ready for Engine Start Phase, Go to Ground Services and Connect Wheelchocks, GPU and Ground Air. On the overhead turned on Ground Power and then in DAVE opened the Pax and Cargo Doors, switching to PFPX to create a flight plan. While inserting the data in PFPX the flightsim crashed. 2 Times the same procedure, 2 times CTD after a few seconds with this error: Name der fehlerhaften Anwendung: Prepar3D.exe, Version: 4.0.28.21686, Zeitstempel: 0x594a7255 Name des fehlerhaften Moduls: ASCRJ.dll, Version: 1.0.0.1, Zeitstempel: 0x5980443e Ausnahmecode: 0xc0000409 Fehleroffset: 0x000000000016f084 ID des fehlerhaften Prozesses: 0x9258 Startzeit der fehlerhaften Anwendung: 0x01d30bfb8a8d8494 Pfad der fehlerhaften Anwendung: C:\Flusi\Lockheed Martin\Prepar3D v4\Prepar3D.exe Pfad des fehlerhaften Moduls: C:\Flusi\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\Aerosoft CRJ Base\panel\ASCRJ.dll Berichtskennung: a45cf670-13a3-4dfd-9171-1eca69974757 Vollständiger Name des fehlerhaften Pakets: Anwendungs-ID, die relativ zum fehlerhaften Paket ist: Link to comment Share on other sites More sharing options...
atco 63 Posted August 3, 2017 Share Posted August 3, 2017 6 hours ago, chewwy94 said: It should be noted that I flew a 2 hour route from KIDA - KMSP and then 2 hours back to KMSP - KIDA without a single hitch as the entire Twitch VOD shows. The same addons were being used as listed above. I restarted the sim when landing at KMSP to fix the nav light bug with the SPAI traffic addon, and then turned around the aircraft without restarting the sim once landing back at KIDA to head to KSLC. Your CTD's might have something to do with that pirate-ware AI package you are running there. The SPAI pack is a widely known rip off of models, textures and flightplans from the AI community. Much of my work is included in it without my consent. A great shame you are using and publicising a pirated addon to your viewers. https://www.avsim.com/forums/topic/513098-spai-ai-traffic-pack-gone/ The acontain.dll is related to AI aircraft, would not surprise me at all if that rip off AI package had all kinds of nasty surprises lurking in it. Link to comment Share on other sites More sharing options...
Bigryan62 0 Posted August 3, 2017 Share Posted August 3, 2017 Dont believe its SPAI causing it. many of my friends are using different AI packages and getting CTD with the same DLL "acontain.dll " Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.