5.4: App Hangs

[miraclemax]

I have never had so many APP Hangs in P34dv5.4, or any version, for that matter, since last October. I've done a "cursory" add-on check but I have so many that I've just concentrated on the likely ones: Pilots 2024 Mesh, all ORBX (no vector), full AIG, MAIW, Active Sky and I've been running all these, except with Pilot's 2020 mesh, since 5.3 came out. And yes, I have MANY sceneries but they have worked flawlessly for over a year. PMDG, AS Airbus, QW 787 CS 757. No OC, no overheat but huge P3D cpu usage in conjunction with hang. Happens anywhere in world at cruise alt. with any A/C. I run P3d with stock Affinity Mask, pretty high cfg settings and unlimited FR; but again, this never was a problem. Here is the error info from this afternoon.

Log Name: Application
Source: Application Hang
Date: 1/12/2024 12:27:57 PM
Event ID: 1002
Task Category: Hanging Events
Level: Error
Keywords:
User: SYSTEM
Computer: ALPHAPRIME
Description:
The program Prepar3D.exe version 5.4.9.28482 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.

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Hang" Guid="{c631c3dc-c676-59e4-2db3-5c0af00f9675}" />
<EventID>1002</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>101</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2024-01-12T18:27:57.4751299Z" />
<EventRecordID>44971</EventRecordID>
<Correlation />
<Execution ProcessID="1416" ThreadID="13304" />
<Channel>Application</Channel>
<Computer>ALPHAPRIME</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="AppName">Prepar3D.exe</Data>
<Data Name="AppVersion">5.4.9.28482</Data>
<Data Name="ProcessId">0x2e80</Data>
<Data Name="StartTime">0x1da457e596be408</Data>
<Data Name="TerminationTime">209</Data>
<Data Name="ExeFileName">D:\P53\Prepar3D.exe</Data>
<Data Name="ReportId">c1ec61f0-a655-44eb-af73-7d5f4dac144f</Data>
<Data Name="PackageFullName">
</Data>
<Data Name="PackageRelativeAppId">
</Data>
<Data Name="HangType">Unknown</Data>
</EventData>
</Event>

//////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

Source
Prepar3D exe

Summary
Stopped responding and was closed

Date
‎1/‎12/‎2024 12:27

Status
Not reported

Description
A problem caused this program to stop interacting with Windows.
Faulting Application Path: D:\P53\Prepar3D.exe

Problem signature
Problem Event Name: AppHangB1
Application Name: Prepar3D.exe
Application Version: 5.4.9.28482
Application Timestamp: 6463925f
Hang Signature: e218
Hang Type: 134217728
OS Version: 10.0.22631.2.0.0.256.48
Locale ID: 1033
Additional Hang Signature 1: e2187fb02a7182c4169cd9acdd7c8a45
Additional Hang Signature 2: c060
Additional Hang Signature 3: c0608ff4740efaa84189304bc3147902
Additional Hang Signature 4: e218
Additional Hang Signature 5: e2187fb02a7182c4169cd9acdd7c8a45
Additional Hang Signature 6: c060
Additional Hang Signature 7: c0608ff4740efaa84189304bc3147902

I know it says P3D stopped interacting but I have a feeling that since this seems to have started at one point, that the trouble is in windows... a specific update.

p.s. Doing a key word search now.

I have a i9-12900; 3080ti; 32G RAM 4800mhz with 3 SSDs: SYS/P3D/Addons. WIN11 pro.
max

[JorgenSA]

I noticed that there is a time-stamp (Date: 1/12/2024 12:27:57 PM) in the error messages.

Is there any "Error" entries in Windows Event Viewer at that time?

If so, post the entry here, or in a pinch, just the exception code.

You also mention "full AIG" - what exactly do you mean by that?

If I assume that you mean flight plans compiled with the AIG Manager, then I believe that Ray Proudfoot has experienced something similar.

The MAIW flight plans you have would not be an issue, since you would have compiled those with AIFP.

Jorgen

[mpni]

Hi
Another similar issue here:
https://www.prepar3d.com/forum/viewtopi ... 3&start=30
You can search with "AppHangB1 prepar3d".
Regards
Michel

[JorgenSA]

At one time I had a sort of "hangs" in v. 5.4.9, but I would rather clall it mini-stutters, lasting a few and up until maybe 15 seconds.

I solved that by moving my AI aircraft - I have a real lot of those, many thousands - from a SSD drive to a folder on a NVMe drive.

Jorgen

[miraclemax]

The only relevant error timestamp in any of the logs is in the APP Logs, as shown in OP; nothing in System.

All I could find on the key word (0x8000000000000000) search is possible corrupted C++; but I'm not knowledgeable enough to know if that is even relevant. Would something like that show up in the System log?

By full AIG I mean 100% commercial run at 100% in AITC and all my AI is on a separate NVME SSD also.

I also use OnCourse Software's PF3 atc app; but that runs on separate pc.

For all you AIG users out there, do not use ATCAPI (ATCAPI.dll) in P3Dv5.4; it may give you an 'Application Crashing Event' error.

Checked SODE and it is up to date; no SODE errors.

Jorgen, when you say "Windows Event viewer", what do you mean? I looked in <Event Viewer\App and services logs\Microsoft\Windows> and from there I wouldn't know which folder to look in.

Later yesterday I had an uneventful flight from RJAA to ZGSZ... so go figure.
Regards,
max

[Ray Proudfoot]

@miraclemax, Jorgen is right. I’ve had multiple freezes of P3D v5.4 and they’re definitely associated with AIG BGL files. But with over 1300 of them it’s an impossible job to identify those causing the problems. Especially when they happen in Australia, Finland, Sardinia, USA and England.

This only happened after updating to 5.4. I never had the problem with v5.3HF2. I reverted to that over two weeks ago and haven’t had a single freeze since.

Just to clarify. The freezes would often take up to a few minutes but then the sim recovered and was fine thereafter. I’ve had then as soon as the wheels left the runway and also when landing with just 8ft left. They never happened on the ground.

[JorgenSA]

I don't use the AIG bgl file format myself, because they are proprietary and I am not aware of any tool that is able to de-compile them. In addition, the AIG Manager is useless on my system, given the amount of scenery, AI flightplans and AI aircraft that makes its initial run for data collection take way over 24 hours.

I believe - and this is something I must stress is a theory - that such hangs occur when you run into an area where a lot of flight plans become active at the same time. Flight plans become active, or live, in the sim when you get into about 100 NM "from them", for lack of a better word. Then the system has to look through the flight plan and come up with the required aircraft etc etc, which takes time and disk accesses. Again and again, this is a theory based on whatever I have been able to pick up over the years, and I may of course not have it right.

Jorgen

[JorgenSA]

And then on to the Event Viewer.

What you do is note down the time of a crash - Miraclemax, you have that timestamp from a previous post.

Then right-click on your Windows Start button and select Event Viewer from the menu. In Event Viewer, click on the little arrow next to "Windows Logs", then click on "Application". Now, in the top center pane you'll see a lot of events, with time-stamps on them. Scroll down the events to the time-stamp you noted earlier, and there you should see one or two events titled "Error". When you now click on those, the error information will appear in the bottom center pane. This is the error information needed to troubleshoot a CTD, copy and paste that information in a message here. If you cannot do that, then the really essential part of the error information is the exception code, which we then need here.

Jorgen

[miraclemax]

This is the only error (in red) that shows up under <Application> at the time of the crash.

Log Name: Application
Source: Application Hang
Date: 1/12/2024 12:27:57 PM
Event ID: 1002
Task Category: Hanging Events
Level: Error
Keywords:
User: SYSTEM
Computer: ALPHAPRIME
Description:
The program Prepar3D.exe version 5.4.9.28482 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.

No exception code.

Your comment about AIG/AIGTC may have merit. I'm going to check that out.

Also, I mentioned that I use PF3 for ATC on a separate PC (via Wide Client). Out of curiosity I checked Event Viewer on that PC for errors at that same time. I found an error 36 seconds EARLIER than the one on my P3D PC; it has an exception code.

*************************************BELOW IS FROM 2ND PC:************************************

Log Name: Application
Source: Application Error
Date: 1/12/2024 12:27:21 PM ///////////////////36 seconds earlier/////////////////////
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: Alpha
Description:
Faulting application name: WideClient.exe, version: 7.1.5.9, time stamp: 0x5ef4b189
Faulting module name: ntdll.dll, version: 10.0.19041.3693, time stamp: 0x3ab9e7d5
Exception code: 0xc0000005
Fault offset: 0x0005f787
Faulting process id: 0x1cd0
Faulting application start time: 0x01da4576d63e3b6a
Faulting application path: C:\WideClient\WideClient.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: a3706f18-77ee-4f25-a5f7-2ab5fda36533
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>100</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2024-01-12T18:27:21.5019703Z" />
<EventRecordID>118837</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>Alpha</Computer>
<Security />
</System>
<EventData>
<Data>WideClient.exe</Data>
<Data>7.1.5.9</Data>
<Data>5ef4b189</Data>
<Data>ntdll.dll</Data>
<Data>10.0.19041.3693</Data>
<Data>3ab9e7d5</Data>
<Data>c0000005</Data>
<Data>0005f787</Data>
<Data>1cd0</Data>
<Data>01da4576d63e3b6a</Data>
<Data>C:\WideClient\WideClient.exe</Data>
<Data>C:\WINDOWS\SYSTEM32\ntdll.dll</Data>
<Data>a3706f18-77ee-4f25-a5f7-2ab5fda36533</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>

Does the time difference make this possible, is this cause & effect? If I go way back in the logs on 2nd PC the WC error does not show up.

At any rate... no exception code.
Ich danke ihnen sehr, Jorgen!!
Am besten,
max

[miraclemax]

That is, no exception code for P3D error. Sorry.
max

[JorgenSA]

Wanna bet?

What is this then, copied from your post:

Exception code: 0xc0000005

Our good old friend, indicating that Windows detected that "something" attempted to write to an area of RAM where it had no access rights.

Unfortunately, there is nothing to indicate what this "something" is, but in all the cases of this that I have seen, including on my own system, it has proven to be a badly programmed or incompatible add-on.

Jorgen

[Martyson]

Faulting application name: WideClient.exe

FSUIPC on your 2 PC setup.

[JorgenSA]

Faulting application name: WideClient.exe

FSUIPC on your 2 PC setup.

Maybe - root cause just may be "something else".

Jorgen

[Ray Proudfoot]

I’ve used WideClient for years. I’ve never had reason to believe it can cause problems. The code is extremely robust and still in use by lots of people.

[JorgenSA]

My "feeling" (which may be totally wrong) is that "something" - the bad guy we're trying to find - is passing something like a bad parameter to WideClient, which then barfs on it and Windows in turn throws the exception code.

And I totally agree, Ray - all the Dowson software I have ever used has been rock-solid. I have had one problem with FSUIPC over the years, and the root cause was sitting at my keyboard.

Jorgen