Recently we have seen a lot of codes used to unlock our products being offered for discounted prices. Almost all of them are bought using stolen credit cards. These codes will all be blocked by our systems and you will have to try to get your money back from the seller, we are unable to assist in these matters. Do be very careful when you see a deal that is almost too good to be true, it probably is too good to be true.

Jump to content

Archived

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

Budlake

PFPX repeatedly crashes at random times

Recommended Posts

As has been reported by others in earlier posts (as long ago as 2013) my copy of PFPX is crashing at random times without any indication of cause.

Will somebody please help me resolve this issue?

Thank you

Mike

Share this post


Link to post

Take a look into the Windows Event Log (Application Log) (eventvwr.exe) and copy the error message from there.

A possible next step would be to have the Process Explorer running simultaneously, and the moment your PFPX crashes and before hitting any ok button in the Windows message box informing you about the crash, use it to 

  • right click on the PFPX item in the list of processes
  • select "Create Dump..."
  • select "Create Minidump..."

This file would then need to be provided to FligtSimSoft for detailed analysis. I would suggest to open a ticket directly with them to get this thing sorted out as quickly as possible.

Share this post


Link to post
2 hours ago, mopperle said:

What do you expect with lack of any detail?

2 hours ago, mopperle said:

 

This is not the type of comment that I would expect when this forum is billed by the Aerosoft website as being the quickest and possibly most efficient way of getting product support.

It is also surprising that such comment should come from a moderator.

If you want more information then ask for it - politely but do not just ignore the request!

Mike

50 minutes ago, Tom A320 said:

Take a look into the Windows Event Log (Application Log) (eventvwr.exe) and copy the error message from there.

A possible next step would be to have the Process Explorer running simultaneously, and the moment your PFPX crashes and before hitting any ok button in the Windows message box informing you about the crash, use it to

  • right click on the PFPX item in the list of processes
  • select "Create Dump..."
  • select "Create Minidump..."

This file would then need to be provided to FligtSimSoft for detailed analysis. I would suggest to open a ticket directly with them to get this thing sorted out as quickly as possible.

Thank you Tom, I will endeavour to do as you suggest and get back to you.

Regards

Mike

Share this post


Link to post

Hello Tom,

It has crashed again, follows is the error log from Events Viewer:

Log Name:      Application
Source:        Application Error
Date:          17/11/2015 11:46:02
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Aonang
Description:
Faulting application name: PFPX.exe, version: 1.2.3.0, time stamp: 0x55fbc06d
Faulting module name: PFPX.exe, version: 1.2.3.0, time stamp: 0x55fbc06d
Exception code: 0xc0000005
Fault offset: 0x001c87b3
Faulting process id: 0x2ed8
Faulting application start time: 0x01d1211ac1efe7f0
Faulting application path: C:\aerosoft\Professional Flight Planner X\PFPX.exe
Faulting module path: C:\aerosoft\Professional Flight Planner X\PFPX.exe
Report Id: c64e0199-8d20-11e5-a209-60a44c5f0e08
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="2015-11-17T11:46:02.000000000Z" />
    <EventRecordID>68170</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Aonang</Computer>
    <Security />
  </System>
  <EventData>
    <Data>PFPX.exe</Data>
    <Data>1.2.3.0</Data>
    <Data>55fbc06d</Data>
    <Data>PFPX.exe</Data>
    <Data>1.2.3.0</Data>
    <Data>55fbc06d</Data>
    <Data>c0000005</Data>
    <Data>001c87b3</Data>
    <Data>2ed8</Data>
    <Data>01d1211ac1efe7f0</Data>
    <Data>C:\aerosoft\Professional Flight Planner X\PFPX.exe</Data>
    <Data>C:\aerosoft\Professional Flight Planner X\PFPX.exe</Data>
    <Data>c64e0199-8d20-11e5-a209-60a44c5f0e08</Data>
  </EventData>
</Event>

 

Regards

Mike

Share this post


Link to post

Hi Mike,

the crash log doesn't point to any external source (external from PFPX), so please head over to FlightSimSoft and open a ticket with them.

http://www.flightsimsoft.com/support/

If you are able to provide a mini dump as described above I am sure the problem with quickly be found and fixed.

Share this post


Link to post

Hi Tom,

I have already opened a support ticket with FlightSimSoft. I have asked them how I can send the dumpfile, which is 23Mb, but they have not responded to that.

They say that the problem has been known for some time (I know that from this forum) and are working on it which does not bode well for a quick solution.

Mike

Share this post


Link to post

Standard! PFPX crashes random times with me too. I've got use to it. You won't get a solution on this forum or even by opening a ticket.

Learn to live with it

Share this post


Link to post

Believe it or not, I have never had it crash. I only use PFPX to find a route and the fuel required. Once that is done, I export the route, and print the OFP, delete the flight and close PFPX until the next flight. I send no information either way between PFPX and TOPCAT. The two programs are on different desktops that are not networked.

Share this post


Link to post
On 27 November 2015, Driver170 said:

Learn to live with it

Thanks Mike for the word of encouragement, I wonder whether you would have the same to say if it were FSX.

Mike

Share this post


Link to post

Thanks for posting in the Developers forum and reporting back Mike - much appreciated. I have experienced the same on occasion and would be thankful if the developers discovered the issue and resolved it. If they are aware of the issue and not asking for additional input, then I'll just hang tight for any updates, (although I will add my 2 cents on their forum as well to let them know that it is impacting at least one more customer).  It's good that the application is still under active development and updates are issued occasionally. 

Don't let the unhelpful comments get to you!

- Jim

 

Share this post


Link to post

Thank you very much Jim, I have never come across so much difficulty in getting support from a munufacturer or its recommendeed agent.

Judging by posts in this forum this has been a known issue for two years at least but no solution has been documented.

Unfortunately the manufacturer is just as lethargic in its support. I have issued a ticket and offered them a mini-dump file but at 21Mb it is too large to send by email. I have asked them (twice) how I can send it to them but as yet they have not responded to that request. I have received no progress reports for from them for just short of two weeks now. It is very frustrating, and annoying! :-(

Share this post


Link to post
On 29 November 2015 at 01:45:07, Budlake said:

Thanks Mike for the word of encouragement, I wonder whether you would have the same to say if it were FSX.

Mike

But this is an issue we can't fix

Share this post


Link to post
1 minute ago, Driver170 said:

But this is an issue we can't fix

Hello Driver170,

Who can't fix it? Aerosoft or FlightSimSoft?

It might be helpful if you were to expand on that statement. However, as it is my obvious question is... why not?

It seems to me that there is little to no interest in fixing this problem-from either party. The problem has been reported in this forum for more than two years without any comments or statements, other than those in response to my post, in all that time.

FlightSimSoft has not bothered to ask me for details of the problem; I have only been asked what I was doing in the lead-up to the crashes but, as I reported the crashes are random, so therefore there is no identifiable cause. Microsoft's Events Viewer was of no use whatsoever.

I have offered to provide FlightSimSoft with a dump file taken from MS Process Explorer but the company has ignored my request for advise on how I can deliver it to them as, at 21Mb, it is far too big to send by email.

If FlightSimSoft do not try to determin the symptoms it is unlikely that it will be able to fix it so to say that it cannot be fixed without at least attempting to find out the cause is unacceptable and strongly suggests that FlightSimSoft (or even Aerosoft) have no intention of fixing it at all which is very sad and very worrying.

Good money has been forked out for this programme but at times it is just not fit for purpose!

Mike

Share this post


Link to post

I don't know and i don't care who does it. Maybe if you expand your search and see this is a common problem with PFPX.

Only reply and response you get is either NONE or send a support ticket.

Good luck.

Share this post


Link to post
5 hours ago, Budlake said:

Hello Driver170,

Who can't fix it? Aerosoft or FlightSimSoft?

It might be helpful if you were to expand on that statement. However, as it is my obvious question is... why not?

It seems to me that there is little to no interest in fixing this problem-from either party. The problem has been reported in this forum for more than two years without any comments or statements, other than those in response to my post, in all that time.

FlightSimSoft has not bothered to ask me for details of the problem; I have only been asked what I was doing in the lead-up to the crashes but, as I reported the crashes are random, so therefore there is no identifiable cause. Microsoft's Events Viewer was of no use whatsoever.

I have offered to provide FlightSimSoft with a dump file taken from MS Process Explorer but the company has ignored my request for advise on how I can deliver it to them as, at 21Mb, it is far too big to send by email.

If FlightSimSoft do not try to determin the symptoms it is unlikely that it will be able to fix it so to say that it cannot be fixed without at least attempting to find out the cause is unacceptable and strongly suggests that FlightSimSoft (or even Aerosoft) have no intention of fixing it at all which is very sad and very worrying.

Good money has been forked out for this programme but at times it is just not fit for purpose!

Mike

I am not sure who Driver170 is but he does not speak for us. If he speaks for FlightSimSoft I will ask him to make that more obvious.

We are unable to fix this problem for the simple reason that we did not create this product and are only the resellers. For second line support we fully depend on FlightSimSoft. Now clearly this is a abnormal issue as we are simply unable to recreate it and we got thousands of customers who do not have this issue. That always makes it damned hard to solve it and any fix will have to be one to the files on your system and not in the product. To solve it we basically have to find out an issue on your machine. At the same time we know with 100% certainty that the issue will be fixed when you format your disk and do a clean windows install. It's not a problem of the software we sold but something on your disk. 

Now I fully understand that this is very unwelcome news. But sometimes it is the only advise we can give. Let me give you an example, on Saturday I was helping a customer on whose system a lot of software had problems. Airbus etc etc. As he was a very nice gent and I was curious I was wiling to check into it. It took me 2 and a half hour to find out that he had installed a early beta of a Windows runtime installed. Deleting that one and installing a clean one and the issue was solved. All our software ran fine. 

See what I mean? I took 2,5 hours to fix an issue unrelated to our software. Pretty stupid as I could have spend that time a lot better and I should have said to the customer that we were sorry but that we could not assist as the fault clearly was in the OS and not in our software. Customers generally do not accept that ('but all other software runs fine') but if is is issue that happens to one or a handful of customer and not all the others the logical reason simply HAS to be a local on that particular system. I know that for some weird reason I can't get the PMDG NGX to run on my machine, it keeps crashing. But I also know that the reason is something on my system and that if I would invest a lot of time I might find the reason. But I also know I am too lazy for that and it will have to wait till January when I plan to install the OS again. I'm 100% confident it will run then.

If you contact us on support@aerosoft.com with all the details I will see if FlightSimSoft did indeed drop the ball here and left the ticket open, if so we'll talk to them and refund your order. In your mail to support please refer to this post. 

 

 

 

Share this post


Link to post

I am very wary about talking too soon but I may have fixed the problem, if not fully then partially, as I have not had a crash for quite a long time now.

I uninstalled PFPX along with the Aibus318/321 software and cleaned the registry. I then re-installed them all and have only had one or perhaps two crashes in the past week or so.

I also increased my DDR3 RAM from 8GB to 16GB but I have no evidence that that has had any effect.

I continue to monitor it with fingers crossed and bated breath.

Mike

Share this post


Link to post

I still get occassional crashes but nowhere near as frequent.

I have put the PFPX folder into the exceptions list of Windows Security Essentials; whether that has a significant effect is probably too early to determine.

Mike

Share this post


Link to post

I, too, get random crashes with this software. Usually 10 minutes  after I exported my flightplans the programme crashes with no indication of what is happening. 

Share this post


Link to post

I have the same problem as PFPX is always crashing about 2 or 3 hours into the flight. Exception code is always 0xc000001d and fault module PFPX.exe as described below.

 

Ill generate the crash dump the next time it crashes.

 

Version=1
EventType=APPCRASH
EventTime=130962089736993268
ReportType=2
Consent=1
UploadTime=130962089737898914
ReportIdentifier=e372f884-b146-11e5-8956-74d43509ee4d
IntegratorReportIdentifier=64d62881-dd90-4c07-825f-f5780733a23a
WOW64=1
NsAppName=PFPX.exe
Response.BucketId=cad88a5c430ba160869ca492b2996d67
Response.BucketTable=1
Response.LegacyBucketId=107602619843
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=PFPX.exe
Sig[1].Name=Application Version
Sig[1].Value=1.2.3.0
Sig[2].Name=Application Timestamp
Sig[2].Value=55fbc06d
Sig[3].Name=Fault Module Name
Sig[3].Value=PFPX.exe
Sig[4].Name=Fault Module Version
Sig[4].Value=1.2.3.0
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=55fbc06d
Sig[6].Name=Exception Code
Sig[6].Value=c000001d
Sig[7].Name=Exception Offset
Sig[7].Value=001c87b4
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=10.0.10240.2.0.0.768.101
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=bdcb
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=bdcb33e65a9843796b7ec31cc25bda3b
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=689d
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=689d12abf00dd47c453b5e1a156c0fa3
UI[2]=D:\PFPX\PFPX.exe
UI[3]=Professional Flight Planner X has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[0]=D:\PFPX\PFPX.exe
LoadedModule[1]=C:\WINDOWS\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\WINDOWS\SYSTEM32\KERNEL32.DLL
LoadedModule[3]=C:\WINDOWS\SYSTEM32\KERNELBASE.dll
LoadedModule[4]=C:\WINDOWS\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.10240.16384_none_3bccb1ff6bcd1849\comctl32.dll
LoadedModule[5]=C:\WINDOWS\SYSTEM32\msvcrt.dll
LoadedModule[6]=C:\WINDOWS\SYSTEM32\GDI32.dll
LoadedModule[7]=C:\WINDOWS\SYSTEM32\USER32.dll
LoadedModule[8]=C:\WINDOWS\SYSTEM32\IMM32.DLL
LoadedModule[9]=C:\WINDOWS\SYSTEM32\MSCTF.dll
LoadedModule[10]=C:\WINDOWS\SYSTEM32\ADVAPI32.dll
LoadedModule[11]=C:\WINDOWS\SYSTEM32\sechost.dll
LoadedModule[12]=C:\WINDOWS\SYSTEM32\RPCRT4.dll
LoadedModule[13]=C:\WINDOWS\SYSTEM32\SspiCli.dll
LoadedModule[14]=C:\WINDOWS\SYSTEM32\CRYPTBASE.dll
LoadedModule[15]=C:\WINDOWS\SYSTEM32\bcryptPrimitives.dll
LoadedModule[16]=C:\WINDOWS\SYSTEM32\winmm.dll
LoadedModule[17]=C:\WINDOWS\SYSTEM32\WINMMBASE.dll
LoadedModule[18]=C:\WINDOWS\SYSTEM32\cfgmgr32.dll
LoadedModule[19]=C:\WINDOWS\SYSTEM32\DEVOBJ.dll
LoadedModule[20]=C:\WINDOWS\SYSTEM32\OPENGL32.dll
LoadedModule[21]=C:\WINDOWS\SYSTEM32\GLU32.dll
LoadedModule[22]=C:\WINDOWS\SYSTEM32\DDRAW.dll
LoadedModule[23]=C:\WINDOWS\SYSTEM32\DCIMAN32.dll
LoadedModule[24]=C:\WINDOWS\SYSTEM32\PSAPI.DLL
LoadedModule[25]=D:\PFPX\zlib1.dll
LoadedModule[26]=C:\WINDOWS\SYSTEM32\mfc140.dll
LoadedModule[27]=C:\WINDOWS\SYSTEM32\ole32.dll
LoadedModule[28]=C:\WINDOWS\SYSTEM32\VCRUNTIME140.dll
LoadedModule[29]=C:\WINDOWS\SYSTEM32\combase.dll
LoadedModule[30]=C:\WINDOWS\SYSTEM32\OLEAUT32.dll
LoadedModule[31]=C:\WINDOWS\SYSTEM32\ucrtbase.dll
LoadedModule[32]=C:\WINDOWS\SYSTEM32\SHLWAPI.dll
LoadedModule[33]=C:\WINDOWS\SYSTEM32\UxTheme.dll
LoadedModule[34]=C:\WINDOWS\SYSTEM32\MSIMG32.dll
LoadedModule[35]=C:\WINDOWS\SYSTEM32\WINSPOOL.DRV
LoadedModule[36]=C:\WINDOWS\SYSTEM32\bcrypt.dll
LoadedModule[37]=C:\WINDOWS\SYSTEM32\SHELL32.dll
LoadedModule[38]=C:\WINDOWS\SYSTEM32\windows.storage.dll
LoadedModule[39]=C:\WINDOWS\SYSTEM32\kernel.appcore.dll
LoadedModule[40]=C:\WINDOWS\SYSTEM32\shcore.dll
LoadedModule[41]=C:\WINDOWS\SYSTEM32\powrprof.dll
LoadedModule[42]=C:\WINDOWS\SYSTEM32\profapi.dll
LoadedModule[43]=C:\WINDOWS\SYSTEM32\urlmon.dll
LoadedModule[44]=C:\WINDOWS\SYSTEM32\iertutil.dll
LoadedModule[45]=C:\WINDOWS\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.10240.16603_none_d15a3826af6dca5f\gdiplus.dll
LoadedModule[46]=C:\WINDOWS\SYSTEM32\WS2_32.dll
LoadedModule[47]=C:\WINDOWS\SYSTEM32\NSI.dll
LoadedModule[48]=C:\WINDOWS\SYSTEM32\MSVCP140.dll
LoadedModule[49]=C:\WINDOWS\SYSTEM32\WININET.dll
LoadedModule[50]=C:\WINDOWS\SYSTEM32\VERSION.dll
LoadedModule[51]=C:\WINDOWS\SYSTEM32\dwmapi.dll
LoadedModule[52]=C:\WINDOWS\SYSTEM32\ntmarta.dll
LoadedModule[53]=C:\WINDOWS\SYSTEM32\RICHED20.DLL
LoadedModule[54]=C:\WINDOWS\SYSTEM32\USP10.dll
LoadedModule[55]=C:\WINDOWS\SYSTEM32\msls31.dll
LoadedModule[56]=C:\WINDOWS\SYSTEM32\cryptsp.dll
LoadedModule[57]=C:\WINDOWS\system32\rsaenh.dll
LoadedModule[58]=C:\WINDOWS\SYSTEM32\clbcatq.dll
LoadedModule[59]=C:\WINDOWS\system32\dataexchange.dll
LoadedModule[60]=C:\WINDOWS\system32\d3d11.dll
LoadedModule[61]=C:\WINDOWS\system32\d2d1.dll
LoadedModule[62]=C:\WINDOWS\system32\dcomp.dll
LoadedModule[63]=C:\WINDOWS\system32\dxgi.dll
LoadedModule[64]=C:\WINDOWS\system32\twinapi.appcore.dll
LoadedModule[65]=C:\WINDOWS\system32\USERENV.dll
LoadedModule[66]=C:\WINDOWS\SYSTEM32\coml2.dll
LoadedModule[67]=C:\WINDOWS\system32\asycfilt.dll
LoadedModule[68]=C:\WINDOWS\SYSTEM32\WindowsCodecs.dll
LoadedModule[69]=C:\WINDOWS\SYSTEM32\nvoglv32.DLL
LoadedModule[70]=C:\WINDOWS\SYSTEM32\SETUPAPI.dll
LoadedModule[71]=C:\WINDOWS\SYSTEM32\WTSAPI32.dll
LoadedModule[72]=C:\WINDOWS\SYSTEM32\WINTRUST.dll
LoadedModule[73]=C:\WINDOWS\SYSTEM32\MSASN1.dll
LoadedModule[74]=C:\WINDOWS\SYSTEM32\CRYPT32.dll
LoadedModule[75]=C:\WINDOWS\SYSTEM32\WINSTA.dll
LoadedModule[76]=C:\Windows\SYSTEM32\ieframe.dll
LoadedModule[77]=C:\WINDOWS\SYSTEM32\sxs.dll
LoadedModule[78]=C:\WINDOWS\SYSTEM32\ondemandconnroutehelper.dll
LoadedModule[79]=C:\WINDOWS\SYSTEM32\IPHLPAPI.DLL
LoadedModule[80]=C:\WINDOWS\SYSTEM32\WINNSI.DLL
LoadedModule[81]=C:\WINDOWS\SYSTEM32\winhttp.dll
LoadedModule[82]=C:\WINDOWS\system32\mswsock.dll
LoadedModule[83]=C:\WINDOWS\SYSTEM32\DNSAPI.dll
LoadedModule[84]=C:\Windows\System32\rasadhlp.dll
LoadedModule[85]=C:\WINDOWS\System32\fwpuclnt.dll
LoadedModule[86]=C:\WINDOWS\SYSTEM32\edputil.dll
LoadedModule[87]=C:\WINDOWS\SYSTEM32\wintypes.dll
LoadedModule[88]=C:\WINDOWS\SYSTEM32\policymanager.dll
LoadedModule[89]=C:\WINDOWS\SYSTEM32\msvcp110_win.dll
LoadedModule[90]=C:\WINDOWS\SYSTEM32\XmlLite.dll
LoadedModule[91]=C:\Program Files (x86)\EZCA\ezcacontrol.dll
LoadedModule[92]=C:\WINDOWS\SYSTEM32\DInput8.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Professional Flight Planner X
AppPath=D:\PFPX\PFPX.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=309C0B0594EFCF1EA69A4E0DF2548BEB
 

Share this post


Link to post

Yet another crash. I have generated the DUMP file. What should I do with it? Is there a support email that I can send it to? 

 

Thanks

Share this post


Link to post
On 02 January 2016 at 2:36 PM, tgcbraun said:

Yet another crash. I have generated the DUMP file. What should I do with it? Is there a support email that I can send it to?

 

Thanks

I asked that very question in November and I have still not received a reply! :-(

Share this post


Link to post
Just now, Tom A320 said:

Please take a look here:

 

Thanks Tom.

Share this post


Link to post
Guest
This topic is now closed to further replies.

×
×
  • Create New...