Sudden CTD after Years No Problems

[ReggieC]

Hello,
I'm suddenly getting a CDT with P3Dv5 HF3 after about 15 seconds of starting the program. I have had years of trouble free operation until this point. I tried uninstalling the client (deactivating), and reinstalling, which worked fine with reactivation. However, I'm still getting the CDT.
The only change I have made is that I installed CCleaner and ran it's Registry Repair. That's when the CDT started. I ran the event viewer and found an error at the same time I tried to run the program. Below is the result.

Computer:
intel(R) Core(TM) i7-9700F CPU @ 3.00GHz
Windows 11
Nvidia GForce RTX 2060 Super 8Gb
32Gb RAM

I hope you can help,
Reggie

Log Name: System
Source: Microsoft-Windows-DistributedCOM
Date: 7/13/2022 5:43:24 AM
Event ID: 10016
Task Category: None
Level: Warning
Keywords: Classic
User: THUMPER025\reggi
Computer: Thumper025
Description:
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}
and APPID
{15C20B67-12E7-4BB6-92BB-7AFF07997402}
to the user THUMPER025\reggi SID (S-1-5-21-2624397461-2057897641-2188295766-1002) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" />
<EventID Qualifiers="0">10016</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2022-07-13T10:43:24.9876114Z" />
<EventRecordID>29816</EventRecordID>
<Correlation ActivityID="{c899d3c5-8257-4655-886a-a7c93fff0ee0}" />
<Execution ProcessID="1092" ThreadID="1468" />
<Channel>System</Channel>
<Computer>Thumper025</Computer>
<Security UserID="S-1-5-21-2624397461-2057897641-2188295766-1002" />
</System>
<EventData>
<Data Name="param1">application-specific</Data>
<Data Name="param2">Local</Data>
<Data Name="param3">Activation</Data>
<Data Name="param4">{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}</Data>
<Data Name="param5">{15C20B67-12E7-4BB6-92BB-7AFF07997402}</Data>
<Data Name="param6">THUMPER025</Data>
<Data Name="param7">reggi</Data>
<Data Name="param8">S-1-5-21-2624397461-2057897641-2188295766-1002</Data>
<Data Name="param9">LocalHost (Using LRPC)</Data>
<Data Name="param10">Unavailable</Data>
<Data Name="param11">Unavailable</Data>
</EventData>
</Event>

[JorgenSA]

Reggie,

The log from Event Viewer does not provide any clues.

But try this:

You need the time of the crash, if necessary provoke a new one and note down the time.

Then go to Event Viewer, then Windows Logs, and under that Application. Now look for an entry that says "Error" around the crash time you noted. Paste the info from there in a new post here.

Jorgen

[ReggieC]

All I see is a "Warning" with this information:

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" />
<EventID Qualifiers="0">10016</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2022-07-13T11:59:19.9860234Z" />
<EventRecordID>30254</EventRecordID>
<Correlation ActivityID="{746d9492-89e6-4df9-9c82-54f102742d52}" />
<Execution ProcessID="1104" ThreadID="9828" />
<Channel>System</Channel>
<Computer>Thumper025</Computer>
<Security UserID="S-1-5-21-2624397461-2057897641-2188295766-1002" />
</System>
- <EventData>
<Data Name="param1">application-specific</Data>
<Data Name="param2">Local</Data>
<Data Name="param3">Activation</Data>
<Data Name="param4">{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}</Data>
<Data Name="param5">{15C20B67-12E7-4BB6-92BB-7AFF07997402}</Data>
<Data Name="param6">THUMPER025</Data>
<Data Name="param7">reggi</Data>
<Data Name="param8">S-1-5-21-2624397461-2057897641-2188295766-1002</Data>
<Data Name="param9">LocalHost (Using LRPC)</Data>
<Data Name="param10">MicrosoftWindows.Client.WebExperience_421.20070.545.0_x64__cw5n1h2txyewy</Data>
<Data Name="param11">Unavailable</Data>
</EventData>
</Event>

[JorgenSA]

It looks to me like this is not a P3D error, but a Windows error.....

I say this because, as you see, there is no mention at all about P3D in the log.

What I would do first here is to run Windows Update, and under update, before you start the update, go under Advanced options and make sure the switch :Receive updates for other Microsoft products" is set to On. Leave that switch on On for the future.

I realize this is a bit like grasping for a straw, but what is there to go on....

Jorgen

[ReggieC]

It was already set as "on". I am doing a clean reinstall.

Thank you.

[JorgenSA]

OK, good luck. Let us know how it goes?

Jorgen

[hermes82]

try searching windows for "reliability " it'll come up with your faulting module and time, try 3 restarts first and after running with ctd go back and check all 3 faulting modules in the event's section by right clicking and selecting view technical details for each of the three crashes marked Prepar3D.exe and see if they match, my last crash was facilities.dll

[JorgenSA]

Hermes82,

I searched my Windows for "reliability" just now, and nothing like you said came up. And why provoke 3 crashes, when one is enough?

Jorgen

[hermes82]

I said three because it's handy to compare all three to see if the faulting module is the same every time, sometimes you can have different faulting modules

[JorgenSA]

Provoke ONE crash, then fix root cause of that.

The clue as to why such a crash occurs will be in Windows Event Viewer, if it is a P3D crash. Windows errors behave differently.

Then see if a crash recurs. If it does, then fix root cause of that. And so on.

The idea is to proceed logically, so you know what you are doing, not to pile 3 possible causes on top of each other.

And the search for "reliability" got forgotten?

Jorgen

[Martyson]

I said three because it's handy to compare all three to see if the faulting module is the same every time, sometimes you can have different faulting modules

Hello hermes82 ,

Yes, good to know all the errors or the same errors appearing on your setup.

I also have the Reliability (as you previously mentioned) monitor on my setup.


You mentioned:
"my last crash was facilities.dll"

What have you done so far to check it out?


In addition to Reliability you could:

To try to isolate what is causing the problem or e.g., a CTD
Look in the Windows Event Viewer and get the
Faulting Module Name
example:

[ReggieC]

Well, I just did a complete clean reinstall and everything is working again.

[JorgenSA]

Good show!

Happy flying -

Jorgen

[hermes82]

my facilities crash was caused by EZCA, I googled it and found that a hotfix was available for P3D v5.3 but EZCA hadn't notified me of it, I downloaded it and all is well now

[Martyson]

my facilities crash was caused by EZCA, I googled it and found that a hotfix was available for P3D v5.3 but EZCA hadn't notified me of it, I downloaded it and all is well now

Hello hermes82 ,

Thanks for the follow up with the resolution information.

Somehow EZDok escaped showing up in both:
Event Viewer
Reliability Monitor


Note:
I have EZDok but I am currently using Chaseplane without problems.