July 17, 20178 yr Hi guys, Since installing P3Dv4 on release I have had a total of 3 crashes, two of which I have determined the cause of. Just had my third one, flying the 737-900 KLM out of EHAM. Was at cruise, not doing anything but looking around the beautiful flight deck enjoying the night lighting. There were a couple of stutters as the sun was setting and the general lighting in the sim me was diminishing, and then the dreaded p3d crash occurred. Here is my report from Windows, anyone have an idea of what it might have been? I know these reports are normally quite general in their descriptions, but since the 737 is new to V4 I thought it might make sense to post this anyway, there might be a deeper issue at play here that the guys at PMDG would like to have a look at. (side note: I did just install the new version of ASCA, and a friend of mine flying the same route, also in the 737, but the 800 variant, crashed at approx the same location, also with the new ASCA, so it's most probably that) Source Prepar3D exe Summary Stopped working Date 17-Jul-17 21:48 Status Report sent Description Faulting Application Path: D:\p3dV4\Prepar3D.exe Problem signature Problem Event Name: APPCRASH Application Name: Prepar3D.exe Application Version: 4.0.28.21686 Application Timestamp: 594a7255 Fault Module Name: StackHash_1388 Fault Module Version: 10.0.15063.447 Fault Module Timestamp: a329d3a8 Exception Code: c0000374 Exception Offset: PCH_34_FROM_ntdll+0x00000000000A5EF4 OS Version: 10.0.15063.2.0.0.256.48 Locale ID: 1033 Additional Information 1: 1388 Additional Information 2: 13880aeb2643ecf562d7da12a4104ce1 Additional Information 3: 3fca Additional Information 4: 3fca017e79ca8cae24cc552c0fae1e3c Extra information about the problem Bucket ID: b19c63061a082594c48902aa6edc525e (120798616358) Sander Rutte
July 18, 20178 yr 5 hours ago, harvester21 said: Hi guys, Since installing P3Dv4 on release I have had a total of 3 crashes, two of which I have determined the cause of. Just had my third one, flying the 737-900 KLM out of EHAM. Was at cruise, not doing anything but looking around the beautiful flight deck enjoying the night lighting. There were a couple of stutters as the sun was setting and the general lighting in the sim me was diminishing, and then the dreaded p3d crash occurred. Here is my report from Windows, anyone have an idea of what it might have been? I know these reports are normally quite general in their descriptions, but since the 737 is new to V4 I thought it might make sense to post this anyway, there might be a deeper issue at play here that the guys at PMDG would like to have a look at. (side note: I did just install the new version of ASCA, and a friend of mine flying the same route, also in the 737, but the 800 variant, crashed at approx the same location, also with the new ASCA, so it's most probably that) Source Prepar3D exe Summary Stopped working Date 17-Jul-17 21:48 Status Report sent Description Faulting Application Path: D:\p3dV4\Prepar3D.exe Problem signature Problem Event Name: APPCRASH Application Name: Prepar3D.exe Application Version: 4.0.28.21686 Application Timestamp: 594a7255 Fault Module Name: StackHash_1388 Fault Module Version: 10.0.15063.447 Fault Module Timestamp: a329d3a8 Exception Code: c0000374 Exception Offset: PCH_34_FROM_ntdll+0x00000000000A5EF4 OS Version: 10.0.15063.2.0.0.256.48 Locale ID: 1033 Additional Information 1: 1388 Additional Information 2: 13880aeb2643ecf562d7da12a4104ce1 Additional Information 3: 3fca Additional Information 4: 3fca017e79ca8cae24cc552c0fae1e3c Extra information about the problem Bucket ID: b19c63061a082594c48902aa6edc525e (120798616358) That's a weird one because there's no faulting module. Could you run the flight again without ASCA and see if you get the crash? Cheers, Chris Brand
July 18, 20178 yr Author Hi Chris, Thanks for your reply! Looked further into the issue, it seems neither my friend or myself had installed the latest AIRAC update into the new version of ASP4 that we installed a few days ago. It still had 1601 installed, wich by now is very outdated. We both had a 1707 flight plan loaded into ASP4. Since we both crashed pretty much at the same way point, we now believe that this might have been the cause. I have updated the AIRAC cycle for ASP4 and will try try the flight again today. Will report back this evening. Looks more and more like ASP4 and dose of user negligence were the culprit in this case. In any case, just to be thorough, here is the report from event viewer showing the faulting module. Faulting application name: Prepar3D.exe, version: 4.0.28.21686, time stamp: 0x594a7255 Faulting module name: ntdll.dll, version: 10.0.15063.447, time stamp: 0xa329d3a8 Exception code: 0xc0000374 Fault offset: 0x00000000000f775f Faulting process id: 0x22b8 Faulting application start time: 0x01d2ff2844f6febd Faulting application path: D:\p3dV4\Prepar3D.exe Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll Report Id: ef7ee908-866a-454d-94ec-bc353de4abf5 Faulting package full name: Faulting package-relative application ID: Sander Rutte
July 18, 20178 yr 3 minutes ago, harvester21 said: Hi Chris, Thanks for your reply! Looked further into the issue, it seems neither my friend or myself had installed the latest AIRAC update into the new version of ASP4 that we installed a few days ago. It still had 1601 installed, wich by now is very outdated. We both had a 1707 flight plan loaded into ASP4. Since we both crashed pretty much at the same way point, we now believe that this might have been the cause. I have updated the AIRAC cycle for ASP4 and will try try the flight again today. Will report back this evening. Looks more and more like ASP4 and dose of user negligence were the culprit in this case. In any case, just to be thorough, here is the report from event viewer showing the faulting module. Faulting application name: Prepar3D.exe, version: 4.0.28.21686, time stamp: 0x594a7255 Faulting module name: ntdll.dll, version: 10.0.15063.447, time stamp: 0xa329d3a8 Exception code: 0xc0000374 Fault offset: 0x00000000000f775f Faulting process id: 0x22b8 Faulting application start time: 0x01d2ff2844f6febd Faulting application path: D:\p3dV4\Prepar3D.exe Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll Report Id: ef7ee908-866a-454d-94ec-bc353de4abf5 Faulting package full name: Faulting package-relative application ID: Ah yes that could be a culprit, unfortunately that's a really generic crashing module which doesn't really point to anything. Hopefully you're right with the AIRAC cycle and that fixes your issues Cheers, Chris Brand
July 18, 20178 yr Author Yeah, as I mentioned in my OP, these reports usually don't give many clues.. I will, as mentioned, recreate the conditions of yesterday's flight this evening and see if it works as expected now. Will let you all know if this solved the problem. Sander Rutte
July 19, 20178 yr Author Good morning, Just wanted to report that the flight went without a hitch yesterday. I guess the updated AIRAC potentially solved this issue. Have a good day! Sander Rutte
Archived
This topic is now archived and is closed to further replies.