July 12, 20178 yr Hopefully someone has some advice for me, I recently upgraded my NGX to the latest version using Roberts' advice of a clean install. My issue is now when I close FSX I get an APPCRASH message with the fault module name PMDG_737NGX_2.dll. This did not happen prior to upgrade. Any ideas? Thanks Andrew Dixon Andrew Dixon"If common sense was compulsory everyone would have it but I am afraid this is not the case"
July 12, 20178 yr Author Just an update, PMDG_777X_2.dll gives the same error as the PMDG_737NGX_2.dll when exiting FSX. These appear to be Flexnet security activation modules that give an error. The previous versions did not give an error. Regards Andrew Dixon Andrew Dixon"If common sense was compulsory everyone would have it but I am afraid this is not the case"
July 13, 20178 yr Author Bump.....anyone? Andrew Dixon"If common sense was compulsory everyone would have it but I am afraid this is not the case"
July 13, 20178 yr Commercial Member Andrew, We have a few reports from some users about this. We are evaluating, but it is a very low priority right now because it isn't affecting anyone while simming. We have a few higher priority items that are affecting people WHILE simming- so we want to knock those down first. Once we find what is causing this, we will kill it too... Robert S. Randazzo PLEASE NOTE THAT PMDG HAS DEPARTED AVSIM You can find us at: http://forum.pmdg.com
July 13, 20178 yr Author Thanks Robert for the reply. I have rolled back for the present and will update once a solution is sourced. Andrew Dixon"If common sense was compulsory everyone would have it but I am afraid this is not the case"
July 13, 20178 yr Commercial Member 4 hours ago, Dicko said: Thanks Robert for the reply. I have rolled back for the present and will update once a solution is sourced. Just out of curiosity, why would one go back to a previous version when this crash is only occurring when you are intentionally closing the sim? Granted, a crash issue should be addressed, but why sacrifice using the latest version when the only negative effect is that the sim crashes instead of closing normally when you're going to intentionally close it. Crashing mid-flight? Sure...but when going to close the sim anyway? Kyle Rodgers
July 13, 20178 yr Author Hi Kyle, FSX was running very well on my system prior to the upgrade why introduce an issue? Its just me. When a fix is offered I will then upgrade. Ultimately I will upgrade my PC and move to P3D4 and I reckon that wont be too far down the track. Andrew Dixon"If common sense was compulsory everyone would have it but I am afraid this is not the case"
July 13, 20178 yr Commercial Member 8 minutes ago, Dicko said: FSX was running very well on my system prior to the upgrade why introduce an issue? Its just me. When a fix is offered I will then upgrade. Fair enough, and that makes sense to a certain degree. Was still curious, so I asked. Kyle Rodgers
December 26, 20178 yr Author bump Andrew Dixon"If common sense was compulsory everyone would have it but I am afraid this is not the case"
February 2, 20206 yr With me on my FSX the same thing is happening now in 2020 I already did a report to PMDG and nothing resolved I find it strange that from 2017 to today 2020 nothing is really revolted😡😡 João Peralta
April 21, 20224 yr Hello, Has anyone found a solution or an explanation for this problem? I have the same problem with P3Dv4.5 and PMDG 737 NGXu v2.91.0830 Thank you. ------------------------------------------------------------------ Signature du problème : Nom d’événement de problème: BEX64 Nom de l’application: Prepar3D.exe Version de l’application: 4.5.14.34698 Horodatage de l’application: 5e94b5c2 Nom du module par défaut: PMDG_737NGXu.dll_unloaded Version du module par défaut: 0.0.0.0 Horodateur du module par défaut: 5fdbddbe Décalage de l’exception: 00000001b371ce30 Code de l’exception: c0000005 Données d’exception: 0000000000000008 Version du système: 6.1.7601.2.1.0.256.48 Identificateur de paramètres régionaux: 1036 Information supplémentaire n° 1: d407 Information supplémentaire n° 2: d40771d80355fad1dd5e50ce7ddbf91f Information supplémentaire n° 3: 8c98 Information supplémentaire n° 4: 8c9858a873e1f41174c7562ffd3c1eee ------------------------------------------------------------------ Edited April 21, 20224 yr by StephaneS
Archived
This topic is now archived and is closed to further replies.