Jump to content

Recommended Posts

Hello,

 

I've sent also a support ticket, but I know about the slow support of PFPX, so I try it in this forum, too.

 

Since several weeks, PFPX is crashing every time I use it.

It does not happen at start, it happens on various occasions, like during planning, but also when PFPX is open and still unused it crashes after a while.

What is sure, it crashes for 100% every time.

It even crashes if the simulator is not opened.

 

I have (re) installed the vcredist 2012 and 2015

I'm using WIN 10 Pro, have admin rights and I'm running PFPX as admin.

PFPX is updated to 1.23

I have uninstalled an reinstalled.

I have tried compatibility mode with Win 8.

There was a time last year where PFPX have been running without any issues, now it is unusable

 

All Iget in the windows crash event is:

 

Name der fehlerhaften Anwendung: PFPX.exe, Version: 1.2.3.0, Zeitstempel: 0x55fbc06d
Name des fehlerhaften Moduls: PFPX.exe, Version: 1.2.3.0, Zeitstempel: 0x55fbc06d
Ausnahmecode: 0xc0000005
Fehleroffset: 0x001de5b5
ID des fehlerhaften Prozesses: 0x130c
Startzeit der fehlerhaften Anwendung: 0x01d14d0456e8bb08
Pfad der fehlerhaften Anwendung: D:\aerosoft\Professional Flight Planner X\PFPX.exe
Pfad des fehlerhaften Moduls: D:\aerosoft\Professional Flight Planner X\PFPX.exe
Berichtskennung: 7ff7bc07-ad1a-4c48-9a1a-ab23ffbaf8c3
Vollständiger Name des fehlerhaften Pakets: 
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: 

 

 

Fast support would be very nice!

Many thanks,

Günter

Link to comment
Share on other sites

  • Replies 55
  • Created
  • Last Reply

Really slow support <_<

 

I have tried now anything:

several reinstalls (of course as admin)

registry cleans

Vredist packages installed

 

I cought now another error message. Sometimes it is that, sometimes it is the above.

 

Name der fehlerhaften Anwendung: PFPX.exe, Version: 1.2.3.0, Zeitstempel: 0x55fbc06d
Name des fehlerhaften Moduls: mfc140.dll, Version: 14.0.23026.0, Zeitstempel: 0x558ceeb2
Ausnahmecode: 0xc0000005
Fehleroffset: 0x0005e8f9
ID des fehlerhaften Prozesses: 0x938
Startzeit der fehlerhaften Anwendung: 0x01d14dfa02e26f19
Pfad der fehlerhaften Anwendung: D:\aerosoft\Professional Flight Planner X\PFPX.exe
Pfad des fehlerhaften Moduls: C:\WINDOWS\SYSTEM32\mfc140.dll
Berichtskennung: 67cf7989-2eaa-4581-9d63-45471f706c58
Vollständiger Name des fehlerhaften Pakets: 
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: 

 

 

 

Currently, PFPX isn't running as longer as 5 Minutes before crashing. Most times earlier.

:angry:

Link to comment
Share on other sites

  • Deputy Sheriffs

Very strange, I have PFPX running now for over 4 hrs, made/edited/exported/deleted/validated various flightplans, had FSX and P3D running in parallel, no crash at all.

Günther I assume that your MS Visual C++ libraries are upt to date, all versions installed?

Link to comment
Share on other sites

Thanks for answering.

 

Yes, I have PFPX also running for some years now.

But the last weeks/month it is crashing.

I don't know, haven't changed the system ...

 

I think, they are up to date.

I have installed the 2015 ones, but if you like, you could give me a link to the most recent ones, just to be sure.

Link to comment
Share on other sites

  • Deputy Sheriffs

The problem is you should install ALL libraries 2005, 2008, 2010.... Sometimes software/dlls are asking for a specific version. backwards compatibility of 2015 doesn't help in that case.

Start here: https://www.microsoft.com/de-de/download/details.aspx?id=3387

Link to comment
Share on other sites

Boa, ist das frustrierend ...

 

Hab nochmal weiter gekramt in den fehlerberichten von microsoft:

 

Spoiler

Version=1
EventType=APPCRASH
EventTime=130971878861651338
ReportType=2
Consent=1
UploadTime=130971878863264070
ReportIdentifier=18c569b9-ba2e-11e5-9c0b-1c6f65324d66
IntegratorReportIdentifier=f247314c-a8da-4cd2-ad3e-e2ae79bd27e3
WOW64=1
NsAppName=PFPX.exe
Response.BucketId=96489d87f41084b9361aa35767d23eaa
Response.BucketTable=1
Response.LegacyBucketId=107857404997
Response.type=4
Sig[0].Name=Anwendungsname
Sig[0].Value=PFPX.exe
Sig[1].Name=Anwendungsversion
Sig[1].Value=1.2.3.0
Sig[2].Name=Anwendungszeitstempel
Sig[2].Value=55fbc06d
Sig[3].Name=Fehlermodulname
Sig[3].Value=PFPX.exe
Sig[4].Name=Fehlermodulversion
Sig[4].Value=1.2.3.0
Sig[5].Name=Fehlermodulzeitstempel
Sig[5].Value=55fbc06d
Sig[6].Name=Ausnahmecode
Sig[6].Value=c0000005
Sig[7].Name=Ausnahmeoffset
Sig[7].Value=001de5b7
DynamicSig[1].Name=Betriebsystemversion
DynamicSig[1].Value=10.0.10586.2.0.0.256.48
DynamicSig[2].Name=Gebietsschema-ID
DynamicSig[2].Value=1031
DynamicSig[22].Name=Zusatzinformation 1
DynamicSig[22].Value=bdcb
DynamicSig[23].Name=Zusatzinformation 2
DynamicSig[23].Value=bdcb33e65a9843796b7ec31cc25bda3b
DynamicSig[24].Name=Zusatzinformation 3
DynamicSig[24].Value=7ae5
DynamicSig[25].Name=Zusatzinformation 4
DynamicSig[25].Value=7ae5ff970d16e403baf57c3408d06e56
UI[2]=D:\aerosoft\Professional Flight Planner X\PFPX.exe
UI[3]=Professional Flight Planner X funktioniert nicht mehr

 

Was da steht, u.a.:

Sig[6].Name=Ausnahmecode
Sig[6].Value=c0000005

 

Von c0000005 liest man andernorts, dass es eine Access violation ist.

  • Accessing a stale pointer. That is accessing memory that has already been deallocated. Note that such stale pointer accesses do not always result in access violations. Only if the memory manager has returned the memory to the system do you get an access violation.
  • Reading off the end of an array. This is when you have an array of length N and you access elements with index >=N.

 

Aber für eine ordentliche Fehlersuche bräuchte man halt Support vom Entwickler ...:unsure:

Link to comment
Share on other sites

ok, dann hoffe ich sehr, dass es dann damit behoben ist, denn momentan kann ich PFPX nicht mehr benutzen, da es keine 5 Min. dauert. bis er abstürzt.

 

Wenn ich irgendeinen Hotfix testen soll, sagt bescheid.

Link to comment
Share on other sites

Hi all:

 

I also have problems with the PFPX. always CTD, after some time..... I have installed the lastes version 1.23. 

I have read that other people have the same problem... 

Perhaps it will be fixed in the next update.

 

Bye and thanks

 

 

 

Link to comment
Share on other sites

  • Deputy Sheriffs
Quote

Perhaps it will be fixed in the next update.

Unforntunately Judith answered in German, so here the translation

Quote

We are working on it.... should be fixed in the next version

Quote

release depends on how many other tickets need to be solved, but January might be possible

taken from post #9 and #11

Link to comment
Share on other sites

  • 3 weeks later...

I have purchased the program on 10 January 2016.

On my PC the program crashes after a different time.

More details here:
Name der fehlerhaften Anwendung: PFPX.exe, Version: 1.2.3.0, Zeitstempel: 0x55fbc06d
Name des fehlerhaften Moduls: PFPX.exe, Version: 1.2.3.0, Zeitstempel: 0x55fbc06d
Ausnahmecode: 0xc0000005
Fehleroffset: 0x001c87b3
ID des fehlerhaften Prozesses: 0x1ef8
Startzeit der fehlerhaften Anwendung: 0x01d15e95a71e5694
Pfad der fehlerhaften Anwendung: F:\Aerosoft\Professional Flight Planner X\PFPX.exe
Pfad des fehlerhaften Moduls: F:\Aerosoft\Professional Flight Planner X\PFPX.exe
Berichtskennung: a22728a8-9b13-460e-a141-8ade7d545e12
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:

 

 

Link to comment
Share on other sites

Hello,

 

I also have problems with the PFPX.

 

CTD from time to time.

Message: PFPX stop working!

Have installed the lastes version 1.23. in windows 7 64bit.

No problems before the update!

Hoop it will be fixed with the next update?

 

Robert

Link to comment
Share on other sites

  • 2 weeks later...

Not sure if this will help find the problem? if you need anything else let me know what and I'll try and grab it next time it happens.

 

Please login to display this image.

Please login to display this image.

Link to comment
Share on other sites

Unfortunately, I do have the same problem:

 

Name der fehlerhaften Anwendung: PFPX.exe, Version: 1.2.3.0, Zeitstempel: 0x55fbc06d
Name des fehlerhaften Moduls: PFPX.exe, Version: 1.2.3.0, Zeitstempel: 0x55fbc06d
Ausnahmecode: 0xc000001d
Fehleroffset: 0x001c87b4
ID des fehlerhaften Prozesses: 0x1428
Startzeit der fehlerhaften Anwendung: 0x01d16c88b41e2fe4
Pfad der fehlerhaften Anwendung: C:\Program Files (x86)\aerosoft\Professional Flight Planner X\PFPX.exe
Pfad des fehlerhaften Moduls: C:\Program Files (x86)\aerosoft\Professional Flight Planner X\PFPX.exe
Berichtskennung: 1160400b-d87d-11e5-a536-ac9e174e7692

 

 

Version=1
EventType=APPCRASH
EventTime=131005203388870309
ReportType=2
Consent=1
ReportIdentifier=1160400c-d87d-11e5-a536-ac9e174e7692
IntegratorReportIdentifier=1160400b-d87d-11e5-a536-ac9e174e7692
WOW64=1
Response.type=4
Sig[0].Name=Anwendungsname
Sig[0].Value=PFPX.exe
Sig[1].Name=Anwendungsversion
Sig[1].Value=1.2.3.0
Sig[2].Name=Anwendungszeitstempel
Sig[2].Value=55fbc06d
Sig[3].Name=Fehlermodulname
Sig[3].Value=PFPX.exe
Sig[4].Name=Fehlermodulversion
Sig[4].Value=1.2.3.0
Sig[5].Name=Fehlermodulzeitstempel
Sig[5].Value=55fbc06d
Sig[6].Name=Ausnahmecode
Sig[6].Value=c000001d
Sig[7].Name=Ausnahmeoffset
Sig[7].Value=001c87b4
DynamicSig[1].Name=Betriebsystemversion
DynamicSig[1].Value=6.1.7601.2.1.0.768.3
DynamicSig[2].Name=Gebietsschema-ID
DynamicSig[2].Value=3079
DynamicSig[22].Name=Zusatzinformation 1
DynamicSig[22].Value=0a9e
DynamicSig[23].Name=Zusatzinformation 2
DynamicSig[23].Value=0a9e372d3b4ad19135b953a78882e789
DynamicSig[24].Name=Zusatzinformation 3
DynamicSig[24].Value=0a9e
DynamicSig[25].Name=Zusatzinformation 4
DynamicSig[25].Value=0a9e372d3b4ad19135b953a78882e789
UI[2]=C:\Program Files (x86)\aerosoft\Professional Flight Planner X\PFPX.exe
UI[3]=Professional Flight Planner X funktioniert nicht mehr
UI[4]=Windows kann online nach einer Lösung für das Problem suchen.
UI[5]=Online nach einer Lösung suchen und das Programm schließen
UI[6]=Später online nach einer Lösung suchen und das Programm schließen
UI[7]=Programm schließen
LoadedModule[0]=C:\Program Files (x86)\aerosoft\Professional Flight Planner X\PFPX.exe
LoadedModule[1]=C:\Windows\SysWOW64\ntdll.dll
LoadedModule[2]=C:\Windows\syswow64\kernel32.dll
LoadedModule[3]=C:\Windows\syswow64\KERNELBASE.dll
LoadedModule[4]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.18837_none_41e855142bd5705d\comctl32.dll
LoadedModule[5]=C:\Windows\syswow64\msvcrt.dll
LoadedModule[6]=C:\Windows\syswow64\GDI32.dll
LoadedModule[7]=C:\Windows\syswow64\USER32.dll
LoadedModule[8]=C:\Windows\syswow64\ADVAPI32.dll
LoadedModule[9]=C:\Windows\SysWOW64\sechost.dll
LoadedModule[10]=C:\Windows\syswow64\RPCRT4.dll
LoadedModule[11]=C:\Windows\syswow64\SspiCli.dll
LoadedModule[12]=C:\Windows\syswow64\CRYPTBASE.dll
LoadedModule[13]=C:\Windows\syswow64\LPK.dll
LoadedModule[14]=C:\Windows\syswow64\USP10.dll
LoadedModule[15]=C:\Windows\syswow64\SHLWAPI.dll
LoadedModule[16]=C:\Windows\system32\IMM32.DLL
LoadedModule[17]=C:\Windows\syswow64\MSCTF.dll
LoadedModule[18]=C:\Windows\system32\winmm.dll
LoadedModule[19]=C:\Windows\system32\OPENGL32.dll
LoadedModule[20]=C:\Windows\system32\GLU32.dll
LoadedModule[21]=C:\Windows\system32\DDRAW.dll
LoadedModule[22]=C:\Windows\system32\DCIMAN32.dll
LoadedModule[23]=C:\Windows\syswow64\SETUPAPI.dll
LoadedModule[24]=C:\Windows\syswow64\CFGMGR32.dll
LoadedModule[25]=C:\Windows\syswow64\OLEAUT32.dll
LoadedModule[26]=C:\Windows\syswow64\ole32.dll
LoadedModule[27]=C:\Windows\syswow64\DEVOBJ.dll
LoadedModule[28]=C:\Windows\system32\dwmapi.dll
LoadedModule[29]=C:\Windows\syswow64\PSAPI.DLL
LoadedModule[30]=C:\Program Files (x86)\aerosoft\Professional Flight Planner X\zlib1.dll
LoadedModule[31]=C:\Windows\system32\mfc140.dll
LoadedModule[32]=C:\Windows\system32\VCRUNTIME140.dll
LoadedModule[33]=C:\Windows\system32\api-ms-win-crt-runtime-l1-1-0.dll
LoadedModule[34]=C:\Windows\system32\ucrtbase.DLL
LoadedModule[35]=C:\Windows\system32\api-ms-win-core-timezone-l1-1-0.dll
LoadedModule[36]=C:\Windows\system32\api-ms-win-core-file-l2-1-0.dll
LoadedModule[37]=C:\Windows\system32\api-ms-win-core-localization-l1-2-0.dll
LoadedModule[38]=C:\Windows\system32\api-ms-win-core-synch-l1-2-0.dll
LoadedModule[39]=C:\Windows\system32\api-ms-win-core-processthreads-l1-1-1.dll
LoadedModule[40]=C:\Windows\system32\api-ms-win-core-file-l1-2-0.dll
LoadedModule[41]=C:\Windows\system32\api-ms-win-crt-string-l1-1-0.dll
LoadedModule[42]=C:\Windows\system32\api-ms-win-crt-heap-l1-1-0.dll
LoadedModule[43]=C:\Windows\system32\api-ms-win-crt-stdio-l1-1-0.dll
LoadedModule[44]=C:\Windows\system32\api-ms-win-crt-convert-l1-1-0.dll
LoadedModule[45]=C:\Windows\system32\api-ms-win-crt-multibyte-l1-1-0.dll
LoadedModule[46]=C:\Windows\system32\api-ms-win-crt-utility-l1-1-0.dll
LoadedModule[47]=C:\Windows\system32\api-ms-win-crt-math-l1-1-0.dll
LoadedModule[48]=C:\Windows\system32\api-ms-win-crt-time-l1-1-0.dll
LoadedModule[49]=C:\Windows\system32\api-ms-win-crt-filesystem-l1-1-0.dll
LoadedModule[50]=C:\Windows\system32\UxTheme.dll
LoadedModule[51]=C:\Windows\system32\MSIMG32.dll
LoadedModule[52]=C:\Windows\system32\WINSPOOL.DRV
LoadedModule[53]=C:\Windows\syswow64\SHELL32.dll
LoadedModule[54]=C:\Windows\syswow64\urlmon.dll
LoadedModule[55]=C:\Windows\syswow64\api-ms-win-downlevel-ole32-l1-1-0.dll
LoadedModule[56]=C:\Windows\syswow64\api-ms-win-downlevel-shlwapi-l1-1-0.dll
LoadedModule[57]=C:\Windows\syswow64\api-ms-win-downlevel-advapi32-l1-1-0.dll
LoadedModule[58]=C:\Windows\syswow64\api-ms-win-downlevel-user32-l1-1-0.dll
LoadedModule[59]=C:\Windows\syswow64\api-ms-win-downlevel-version-l1-1-0.dll
LoadedModule[60]=C:\Windows\system32\version.DLL
LoadedModule[61]=C:\Windows\syswow64\api-ms-win-downlevel-normaliz-l1-1-0.dll
LoadedModule[62]=C:\Windows\syswow64\normaliz.DLL
LoadedModule[63]=C:\Windows\syswow64\iertutil.dll
LoadedModule[64]=C:\Windows\syswow64\WININET.dll
LoadedModule[65]=C:\Windows\syswow64\USERENV.dll
LoadedModule[66]=C:\Windows\syswow64\profapi.dll
LoadedModule[67]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.19061_none_72d6d48d86649709\gdiplus.dll
LoadedModule[68]=C:\Windows\syswow64\WS2_32.dll
LoadedModule[69]=C:\Windows\syswow64\NSI.dll
LoadedModule[70]=C:\Windows\system32\MSVCP140.dll
LoadedModule[71]=C:\Windows\system32\api-ms-win-crt-locale-l1-1-0.dll
LoadedModule[72]=C:\Windows\system32\api-ms-win-crt-environment-l1-1-0.dll
LoadedModule[73]=C:\Windows\system32\ntmarta.dll
LoadedModule[74]=C:\Windows\syswow64\WLDAP32.dll
LoadedModule[75]=C:\Windows\system32\RICHED20.DLL
LoadedModule[76]=C:\Windows\syswow64\CLBCatQ.DLL
LoadedModule[77]=C:\Windows\system32\CRYPTSP.dll
LoadedModule[78]=C:\Windows\system32\rsaenh.dll
LoadedModule[79]=C:\Windows\system32\RpcRtRemote.dll
LoadedModule[80]=C:\Windows\system32\asycfilt.dll
LoadedModule[81]=C:\Windows\system32\WindowsCodecs.dll
LoadedModule[82]=C:\Windows\system32\nvoglv32.DLL
LoadedModule[83]=C:\Windows\system32\WTSAPI32.dll
LoadedModule[84]=C:\Windows\syswow64\WINTRUST.dll
LoadedModule[85]=C:\Windows\syswow64\CRYPT32.dll
LoadedModule[86]=C:\Windows\syswow64\MSASN1.dll
LoadedModule[87]=C:\Windows\system32\WINSTA.dll
LoadedModule[88]=C:\Windows\SysWOW64\ieframe.dll
LoadedModule[89]=C:\Windows\SysWOW64\api-ms-win-downlevel-shell32-l1-1-0.dll
LoadedModule[90]=C:\Windows\system32\api-ms-win-downlevel-shlwapi-l2-1-0.dll
LoadedModule[91]=C:\Windows\system32\SXS.DLL
LoadedModule[92]=C:\Windows\system32\Secur32.dll
LoadedModule[93]=C:\Windows\system32\api-ms-win-downlevel-advapi32-l2-1-0.dll
LoadedModule[94]=C:\Windows\system32\mswsock.dll
LoadedModule[95]=C:\Windows\System32\wship6.dll
LoadedModule[96]=C:\Windows\system32\IPHLPAPI.DLL
LoadedModule[97]=C:\Windows\system32\WINNSI.DLL
LoadedModule[98]=C:\Windows\system32\DNSAPI.dll
LoadedModule[99]=C:\Windows\System32\netprofm.dll
LoadedModule[100]=C:\Windows\System32\nlaapi.dll
LoadedModule[101]=C:\Windows\system32\dhcpcsvc6.DLL
LoadedModule[102]=C:\Windows\System32\npmproxy.dll
LoadedModule[103]=C:\Windows\System32\wshtcpip.dll
LoadedModule[104]=C:\Windows\system32\rasadhlp.dll
LoadedModule[105]=C:\Windows\system32\dhcpcsvc.DLL
LoadedModule[106]=C:\Windows\System32\fwpuclnt.dll
FriendlyEventName=Nicht mehr funktionsfähig
ConsentKey=APPCRASH
AppName=Professional Flight Planner X
AppPath=C:\Program Files (x86)\aerosoft\Professional Flight Planner X\PFPX.exe

 

BR,

Christian

Link to comment
Share on other sites

  • Aerosoft

Well Microsoft owes you some money for sure. Your simulator that has at least 15 known bugs that we testers reported, some rather nasty. Your OS still has bugs the testers reported (two issues I reported for Win10 are still open). Did you ask your money back there?

 

Do we ship software with known issues? Yes, there is not a single bit of software sold that does not have rough edges the developers and publishers know about. At least in 40 years in the business I have not seen a single one. Software has bugs and where possible, feasible and economically possible they should be fixed.

Link to comment
Share on other sites

No, Because those bugs don't affect me, and I can still use the software, i.e. FSX (maybe 1 CTD in what, 40+ uses?)... You software, crashes, each and every single time it is used!  Huge difference, and hardly a comparison.

 

FXPX has been a TOTAL WAIST of my money... 

 

Link to comment
Share on other sites

Well clearly it doesn't crash every single time it is used. I've not had this problem. Let me correct you. It crashes every single time you use it on YOUR system.

 

This would indicated that the problem isn't down to PFPX itself, but rather a conflict between PFPX and something running on YOUR system. Therefore, it's a bit silly to hold Aerosoft responsible.

Link to comment
Share on other sites

  • Deputy Sheriffs

I fully agree with nealmac. If you encounter this problem EVERY time you use PFPX there surely is something wrong on your system. I use PFPX more or less every day, and yes, it crashes from time to time. But I have it once every 2-3 weeks, not more, and only if it running in the background and is not needed anymore anyway.

 

In my opinion you should rather ask for some assistance in getting this problem solved on your system instead of just ranting around.

 

There has been a suggestion to install/update all available Microsoft VC++ Redistribute-able packages (2005, 2008, 2010, 2012, 2013, 2015 / 32bit and 64bit packages each) earlier in this topic. Have you done that already?

 

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.


×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy & Terms of Use