Hello,

For the last two weeks I have been following all the advice in CTD AVSIM manual with no luck.  I'm afraid I have reached the limit of my knowledge to fix my P3DV4 experience.

What I see:  P3DV4 screen appears for 13 seconds and then disappears.  The Task Manager still shows the CPU is running at 13.5% or so. Used the Task MGR to shut P3D down.

I have no addon scenery and the REALAIR planes were all accepted and activated by P3D.

Here is the info from the DXdiag:

[DXDiag notes removed as not needed per the AVSIM CTD Guide.  Guide just tells you to look at it for "problems".  Information provided (and removed) provides little or not information to solve this task and means nothing].  Edit by Jim Young

DxDiag Notes
------------
      Display Tab 1: No problems found.
        Sound Tab 1: No problems found.
        Sound Tab 2: No problems found.
        Sound Tab 3: No problems found.
        Sound Tab 4: No problems found.
          Input Tab: No problems found.

Display Devices

---------------
           Card name: NVIDIA GeForce GTX 1080
        Manufacturer: NVIDIA
          
---------------

Windows Error Reporting:
+++ WER0 +++:
Fault bucket 2045577423227372570, type 5
Event Name: AppHangB1
Response: Not available
Cab Id: 0

Problem signature:
P1: explorer.exe
P2: 10.0.17763.348
P3: 03d46193
P4: b1d6
P5: 134217728
P6:
P7:
P8:
P9:
P10:

+++ WER1 +++:
Fault bucket , type 0
Event Name: AppHangB1
Response: Not available
Cab Id: 0

Problem signature:
P1: explorer.exe
P2: 10.0.17763.348
P3: 03d46193
P4: b1d6
P5: 134217728
P6:
P7:
P8:
P9:
P10:

+++ WER2 +++:
Fault bucket 2045577423227372570, type 5
Event Name: AppHangB1
Response: Not available
Cab Id: 0

Problem signature:
P1: explorer.exe
P2: 10.0.17763.348
P3: 03d46193
P4: b1d6
P5: 134217728
P6:
P7:
P8:
P9:
P10:

+++ WER3 +++:
Fault bucket , type 0
Event Name: AppHangB1
Response: Not available
Cab Id: 0

Problem signature:
P1: explorer.exe
P2: 10.0.17763.348
P3: 03d46193
P4: b1d6
P5: 134217728
P6:
P7:
P8:
P9:
P10:

+++ WER4 +++:
Fault bucket 126041383541, type 5
Event Name: VSSetup
Response: Not available
Cab Id: 0

Problem signature:
P1: unknown
P2: unknown
P3: 14.0.1528.0
P4: unknown
P5: unknown
P6: FixDotNet;unknown
P7: unknown
P8: unknown
P9: unknown
P10:

+++ WER5 +++:
Fault bucket , type 0
Event Name: VSSetup
Response: Not available
Cab Id: 0

Problem signature:
P1: unknown
P2: unknown
P3: 14.0.1528.0
P4: unknown
P5: unknown
P6: FixDotNet;unknown
P7: unknown
P8: unknown
P9: unknown
P10:

+++ WER6 +++:
Fault bucket 126041383541, type 5
Event Name: VSSetup
Response: Not available
Cab Id: 0

Problem signature:
P1: unknown
P2: unknown
P3: 14.0.1528.0
P4: unknown
P5: unknown
P6: FixDotNet;unknown
P7: unknown
P8: unknown
P9: unknown
P10:

+++ WER7 +++:
Fault bucket , type 0
Event Name: VSSetup
Response: Not available
Cab Id: 0

Problem signature:
P1: unknown
P2: unknown
P3: 14.0.1528.0
P4: unknown
P5: unknown
P6: FixDotNet;unknown
P7: unknown
P8: unknown
P9: unknown
P10:

+++ WER8 +++:
Fault bucket 1720582076479650544, type 5
Event Name: RADAR_PRE_LEAK_64
Response: Not available
Cab Id: 0

Problem signature:
P1: Prepar3D.exe
P2: 4.5.11.29713
P3: 10.0.17763.2.0.0
P4:
P5:
P6:
P7:
P8:
P9:
P10:

+++ WER9 +++:
Fault bucket 1311734131973656302, type 5
Event Name: RADAR_PRE_LEAK_64
Response: Not available
Cab Id: 0

Problem signature:
P1: SupportAssistAgent.exe
P2: 3.2.0.90
P3: 10.0.17763.2.0.0
P4:
P5:
P6:
P7:
P8:
P9:
P10:

Many thanks for your help, I'll be happy to work with you to get me back in the air!

Ted

 

7 hours ago, ted757 said:

Hello,

For the last two weeks I have been following all the advice in CTD AVSIM manual with no luck.  I'm afraid I have reached the limit of my knowledge to fix my P3DV4 experience.

What I see:  P3DV4 screen appears for 13 seconds and then disappears.  The Task Manager still shows the CPU is running at 13.5% or so. Used the Task MGR to shut P3D down.

I have no addon scenery and the REALAIR planes were all accepted and activated by P3D.

Here is the info from the DXdiag:

[DXDiag notes removed as not needed per the AVSIM CTD Guide.  Guide just tells you to look at it for "problems".  Information provided (and removed) provides little or not information to solve this task and means nothing].  Edit by Jim Young

DxDiag Notes
------------
      Display Tab 1: No problems found.
        Sound Tab 1: No problems found.
        Sound Tab 2: No problems found.
        Sound Tab 3: No problems found.
        Sound Tab 4: No problems found.
          Input Tab: No problems found.

Display Devices

---------------
           Card name: NVIDIA GeForce GTX 1080
        Manufacturer: NVIDIA
          
---------------

Windows Error Reporting:
+++ WER0 +++:
Fault bucket 2045577423227372570, type 5
Event Name: AppHangB1
Response: Not available
Cab Id: 0

Problem signature:
P1: explorer.exe
P2: 10.0.17763.348
P3: 03d46193
P4: b1d6
P5: 134217728
P6:
P7:
P8:
P9:
P10:

+++ WER1 +++:
Fault bucket , type 0
Event Name: AppHangB1
Response: Not available
Cab Id: 0

Problem signature:
P1: explorer.exe
P2: 10.0.17763.348
P3: 03d46193
P4: b1d6
P5: 134217728
P6:
P7:
P8:
P9:
P10:

+++ WER2 +++:
Fault bucket 2045577423227372570, type 5
Event Name: AppHangB1
Response: Not available
Cab Id: 0

Problem signature:
P1: explorer.exe
P2: 10.0.17763.348
P3: 03d46193
P4: b1d6
P5: 134217728
P6:
P7:
P8:
P9:
P10:

+++ WER3 +++:
Fault bucket , type 0
Event Name: AppHangB1
Response: Not available
Cab Id: 0

Problem signature:
P1: explorer.exe
P2: 10.0.17763.348
P3: 03d46193
P4: b1d6
P5: 134217728
P6:
P7:
P8:
P9:
P10:

+++ WER4 +++:
Fault bucket 126041383541, type 5
Event Name: VSSetup
Response: Not available
Cab Id: 0

Problem signature:
P1: unknown
P2: unknown
P3: 14.0.1528.0
P4: unknown
P5: unknown
P6: FixDotNet;unknown
P7: unknown
P8: unknown
P9: unknown
P10:

+++ WER5 +++:
Fault bucket , type 0
Event Name: VSSetup
Response: Not available
Cab Id: 0

Problem signature:
P1: unknown
P2: unknown
P3: 14.0.1528.0
P4: unknown
P5: unknown
P6: FixDotNet;unknown
P7: unknown
P8: unknown
P9: unknown
P10:

+++ WER6 +++:
Fault bucket 126041383541, type 5
Event Name: VSSetup
Response: Not available
Cab Id: 0

Problem signature:
P1: unknown
P2: unknown
P3: 14.0.1528.0
P4: unknown
P5: unknown
P6: FixDotNet;unknown
P7: unknown
P8: unknown
P9: unknown
P10:

+++ WER7 +++:
Fault bucket , type 0
Event Name: VSSetup
Response: Not available
Cab Id: 0

Problem signature:
P1: unknown
P2: unknown
P3: 14.0.1528.0
P4: unknown
P5: unknown
P6: FixDotNet;unknown
P7: unknown
P8: unknown
P9: unknown
P10:

+++ WER8 +++:
Fault bucket 1720582076479650544, type 5
Event Name: RADAR_PRE_LEAK_64
Response: Not available
Cab Id: 0

Problem signature:
P1: Prepar3D.exe
P2: 4.5.11.29713
P3: 10.0.17763.2.0.0
P4:
P5:
P6:
P7:
P8:
P9:
P10:

+++ WER9 +++:
Fault bucket 1311734131973656302, type 5
Event Name: RADAR_PRE_LEAK_64
Response: Not available
Cab Id: 0

Problem signature:
P1: SupportAssistAgent.exe
P2: 3.2.0.90
P3: 10.0.17763.2.0.0
P4:
P5:
P6:
P7:
P8:
P9:
P10:

Many thanks for your help, I'll be happy to work with you to get me back in the air!

Ted

 

You have had several AppHangsB1 but there are no solutions.  AppHangs were caused by Windows Explorer, not P3D.  There was one or two that showed an event name "Radar_Pre_Lead_64" but that did not cause a crash or freeze as it occurs when you are running a resource intensive application.  P3D is pretty resource intensive but not going to crash P3D.

The guide indicated you should download and installed AppCrashView and run that application.  See if there were any crashes and see if there are any faulting modules.  You did not do this; instead, you copied and pasted DXDiag report which contains no valuable information unless it says "Problems Found" and it did not.  The AppCrashView report will show you every crash that occurred on your computer from the time you first installed Windows.  The Event Viewer might have some valuable information but definitely not DXDiag.

Did you know that some RealAir products are not compatible with P3DV4?  You should not have them installed.  Uninstall.  Some are compatible but P3D is at v4.5 so I question whether they meet the full compatibility.  Some of your error messages above indicate dotnet version unknown and dotnet's are used by Microsoft to make sure a product runs properly.  It does not indicate the version of dotnet unknown but the AVSIM CTD Guide, page 27, has more information on investigating this.  It could be the dotnet required by RealAir.  I would move the RealAir entries from your installation and place them in a temporary directory and try a flight again.  If no crash (related to P3D), then it could be the dotnet missing or not installed properly.

The VSSetup error is another Microsoft error and related to Microsoft Visuals C++ Redistributables - not with P3D - https://github.com/Microsoft/vssetup.powershell

You have the latest update to Windows 10 installed.

On page 10, AVSIM CTD Guide, it shows you how to fix most freezes and crashes with P3DV4.  Those procedures fix 99% of all crashes.

8 hours ago, ted757 said:

The Task Manager still shows the CPU is running at 13.5% or so. Used the Task MGR to shut P3D down.

The sim has not shut down fully so why you are still seeing 13.5% which is really nothing.  There are a lot of modules loaded during the running of P3D (not owned by P3D but addons), that do not shutdown properly.  This is why we recommend you disable any dll.xml that might be running (there are two - one in the same folder as your p3d.cfg and the default is located in the same folder as your scenery.cfg.  If you have no addons as you indicated, the dll.xml will be empty.  See page 12 of the AVSIM Guide.

I've had this type of CTD start occurring several times after P3D crashed, usually while hot-swapping acft during scenery configuration runs.  In every case, I was able to get back to normal ops by restoring all my config files from the last good save using Lorby-SI's freeware P3D Addon Manager utility.  This leads me to believe I had a config file corrupted as a result of the abnormal termination/crash.

If you have no add-on scenery and just the RA planes, i'd recommend uninstalling P3D completely, and then making sure the generated files are all removed.  LM has instructions on how to remove the generated files on their forums.  Uninstalling P3D leaves those generated config files in place, so a borked config file present before the uninstall/reinstall will still be there to cause trouble if it isn't explicitly removed between the uninstall and reinstallation.

Assuming you get it working OK, I can't recommend that P3D Addon Manager enough...with one click you can quickly take a snapshot of all the important config files and then, if needed, restore them just as quickly, which saves hours of butt pain trying to find a problem in a config file or having to rebuild a configuration after it's lost.  In addition to saving my bacon by recovering my config back to a working state a bunch of times, it's also an awesome tool for managing complex scenery configs.

Regards

Your problem is due to your computer running out of resources. 

 

RADAR_PRE_LEAK_64: RADAR is the slightly inexact acronym for Microsoft's Windows Resource Exhaustion Detection and Resolution feature. One component of this feature is the Resource Exhaustion Resolver, which "notifies you of the three top resource consumers so that you can take action by shutting one or more of these applications down to increase resource availability". 

Footnote:https://arstechnica.com/civis/viewtopic.php?f=8&t=1322989

Edited April 23, 20197 yr by dgraham1284

The last comment on that Ars thread is pretty funny, and spot on.

The RADAR_PRE_LEAK_64 just means it's using a lot of resources, which is exactly what p3d does.

Cheers!

 

First of all, Thanks for the very detailed replys, they are deeply appreciated! 

Here is the latest WER from a few minutes ago when I tried to start P3D.

The WER for some reason does not show todays date so I'm sending the one that shows for 4/22/19 below.

I did move the REALAIR aircraft to the desktop prior to this start.

Version=1
EventType=VSSetup
EventTime=132004371308731921
ReportType=1
Consent=1
UploadTime=132004371310138633
ReportStatus=268435456
ReportIdentifier=4770ef73-de00-4ce6-b054-28c805bceab4
Wow64Host=34404
Wow64Guest=332
OriginalFilename=FixDotNet.exe
AppSessionGuid=00000a60-0001-000e-aa3f-e55f46f9d401
TargetAppId=W:00063204bf464470ff9f8f92b8d99941fdfa00000904!000053ce299c8cbcdededca062e6bc2a514bf9a5987c!FixDotNet.exe
TargetAppVer=2016//02//27:06:00:37!79eed!FixDotNet.exe
BootId=4294967295
TargetAsId=536
IsFatal=4294967295
EtwNonCollectReason=4
Response.BucketId=73294b0498c9edf02d1be19114c0ab3d
Response.BucketTable=5
Response.LegacyBucketId=126041383541
Response.type=4
Sig[0].Name=Problem Signature 01
Sig[0].Value=unknown
Sig[1].Name=Problem Signature 02
Sig[1].Value=unknown
Sig[2].Name=Problem Signature 03
Sig[2].Value=14.0.1528.0
Sig[3].Name=Problem Signature 04
Sig[3].Value=unknown
Sig[4].Name=Problem Signature 05
Sig[4].Value=unknown
Sig[5].Name=Problem Signature 06
Sig[5].Value=FixDotNet;unknown
Sig[6].Name=Problem Signature 07
Sig[6].Value=unknown
Sig[7].Name=Problem Signature 08
Sig[7].Value=unknown
Sig[8].Name=Problem Signature 09
Sig[8].Value=unknown
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=10.0.17763.2.0.0.768.101
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
UI[3]=.NET Framework Repair Tool
State[0].Key=Transport.DoneStage1
State[0].Value=1
OsInfo[0].Key=vermaj
OsInfo[0].Value=10
OsInfo[1].Key=vermin
OsInfo[1].Value=0
OsInfo[2].Key=verbld
OsInfo[2].Value=17763
OsInfo[3].Key=ubr
OsInfo[3].Value=437
OsInfo[4].Key=versp
OsInfo[4].Value=0
OsInfo[5].Key=arch
OsInfo[5].Value=9
OsInfo[6].Key=lcid
OsInfo[6].Value=1033
OsInfo[7].Key=geoid
OsInfo[7].Value=244
OsInfo[8].Key=sku
OsInfo[8].Value=101
OsInfo[9].Key=domain
OsInfo[9].Value=0
OsInfo[10].Key=prodsuite
OsInfo[10].Value=768
OsInfo[11].Key=ntprodtype
OsInfo[11].Value=1
OsInfo[12].Key=platid
OsInfo[12].Value=10
OsInfo[13].Key=sr
OsInfo[13].Value=0
OsInfo[14].Key=tmsi
OsInfo[14].Value=5694
OsInfo[15].Key=osinsty
OsInfo[15].Value=3
OsInfo[16].Key=iever
OsInfo[16].Value=11.437.17763.0-11.0.120
OsInfo[17].Key=portos
OsInfo[17].Value=0
OsInfo[18].Key=ram
OsInfo[18].Value=12278
OsInfo[19].Key=svolsz
OsInfo[19].Value=1676
OsInfo[20].Key=wimbt
OsInfo[20].Value=0
OsInfo[21].Key=blddt
OsInfo[21].Value=180914
OsInfo[22].Key=bldtm
OsInfo[22].Value=1434
OsInfo[23].Key=bldbrch
OsInfo[23].Value=rs5_release
OsInfo[24].Key=bldchk
OsInfo[24].Value=0
OsInfo[25].Key=wpvermaj
OsInfo[25].Value=0
OsInfo[26].Key=wpvermin
OsInfo[26].Value=0
OsInfo[27].Key=wpbuildmaj
OsInfo[27].Value=0
OsInfo[28].Key=wpbuildmin
OsInfo[28].Value=0
OsInfo[29].Key=osver
OsInfo[29].Value=10.0.17763.437.amd64fre.rs5_release.180914-1434
OsInfo[30].Key=buildflightid
OsInfo[31].Key=edition
OsInfo[31].Value=Core
OsInfo[32].Key=ring
OsInfo[33].Key=expid
OsInfo[34].Key=containerid
OsInfo[35].Key=containertype
OsInfo[36].Key=edu
OsInfo[36].Value=0
FriendlyEventName=VSSetup
ConsentKey=VSSetup
AppName=Microsoft .NET Framework Repair Tool
AppPath=C:\7a697c8e18b5599be62aa8\FixDotNet.exe
ApplicationIdentity=00000000000000000000000000000000
MetadataHash=340475938

HERE IS THE CUSTOM VIEW FROM THE EVENT VIEWER:

<?xml version="1.0"?>

<ViewerConfig><QueryConfig><QueryParams><Simple><Channel>Application,Security,System,HardwareEvents,Internet Explorer,Key Management Service,Microsoft-Windows-All-User-Install-Agent/Admin,Microsoft-Windows-AppHost/Admin,Microsoft-Windows-Application Server-Applications/Admin,Microsoft-Windows-AppModel-Runtime/Admin,Microsoft-Windows-AppReadiness/Admin,Microsoft-Windows-Storage-ATAPort/Admin,Microsoft-Client-Licensing-Platform/Admin,Microsoft-Windows-DataIntegrityScan/Admin,Microsoft-Windows-DataIntegrityScan/CrashRecovery,Microsoft-Windows-DSC/Admin,Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin,Microsoft-Windows-DeviceSetupManager/Admin,Microsoft-Windows-Dhcp-Client/Admin,Microsoft-Windows-Dhcpv6-Client/Admin,Microsoft-Windows-Diagnosis-Scripted/Admin,Microsoft-Windows-Storage-Disk/Admin,Microsoft-Windows-EDP-Application-Learning/Admin,Microsoft-Windows-EDP-Audit-Regular/Admin,Microsoft-Windows-EDP-Audit-TCB/Admin,Microsoft-Windows-GenericRoaming/Admin,Microsoft-Windows-Hyper-V-Guest-Drivers/Admin,Microsoft-Windows-Hyper-V-Hypervisor-Admin,Microsoft-Windows-Hyper-V-VID-Admin,Microsoft-Windows-Kernel-EventTracing/Admin,Microsoft-Windows-Mobile-Broadband-Experience-SmsRouter/Admin,Microsoft-Windows-MUI/Admin,Microsoft-Windows-PowerShell/Admin,Microsoft-Windows-PrintService/Admin,Microsoft-Windows-Provisioning-Diagnostics-Provider/Admin,Microsoft-Windows-Provisioning-Diagnostics-Provider/AutoPilot,Microsoft-Windows-Provisioning-Diagnostics-Provider/ManagementService,Microsoft-Windows-PushNotification-Platform/Admin,Microsoft-Windows-RemoteApp and Desktop Connections/Admin,Microsoft-Windows-RemoteAssistance/Admin,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS/Admin,Microsoft-Windows-RemoteDesktopServices-RemoteFX-Synth3dvsc/Admin,Microsoft-Windows-RetailDemo/Admin,Microsoft-Windows-SecurityMitigationsBroker/Admin,Microsoft-Windows-SmartCard-TPM-VCard-Module/Admin,Microsoft-Windows-SMBWitnessClient/Admin,Microsoft-Windows-Storage-Tiering/Admin,Microsoft-Windows-Storage-ClassPnP/Admin,Microsoft-Windows-Storage-Storport/Admin,Microsoft-Windows-TerminalServices-ClientUSBDevices/Admin,Microsoft-Windows-TerminalServices-LocalSessionManager/Admin,Microsoft-Windows-TerminalServices-PnPDevices/Admin,Microsoft-Windows-TerminalServices-Printers/Admin,Microsoft-Windows-TerminalServices-RemoteConnectionManager/Admin,Microsoft-Windows-User Device Registration/Admin,Microsoft-Windows-VerifyHardwareSecurity/Admin,Microsoft-Windows-WindowsBackup/ActionCenter,Microsoft-Windows-Workplace Join/Admin,OpenSSH/Admin,Windows PowerShell</Channel><Level>1,2,3</Level></Simple></QueryParams><QueryNode><Name>Administrative Events</Name><Description>Critical, Error and Warning events from all administrative logs</Description><QueryList><Query Path="Application" Id="0"><Select Path="Application">*[System[Level=1 or Level=2 or Level=3]]</Select><Select Path="Security">*[System[Level=1 or Level=2 or Level=3]]</Select><Select Path="System">*[System[Level=1 or Level=2 or Level=3]]</Select><Select Path="HardwareEvents">*[System[Level=1 or Level=2 or Level=3]]</Select><Select Path="Internet Explorer">*[System[Level=1 or Level=2 or Level=3]]</Select><Select Path="Key Management Service">*[System[Level=1 or Level=2 or Level=3]]</Select><Select Path="Microsoft-Windows-All-User-Install-Agent/Admin">*[System[Level=1 or Level=2 or Level=3]]</Select><Select Path="Microsoft-Windows-AppHost/Admin">*[System[Level=1 or Level=2 or Level=3]]</Select><Select Path="Microsoft-Windows-Application Server-Applications/Admin">*[System[Level=1 or Level=2 or Level=3]]</Select><Select Path="Microsoft-Windows-AppModel-Runtime/Admin">*[System[Level=1 or Level=2 or Level=3]]</Select><Select Path="Microsoft-Windows-AppReadiness/Admin">*[System[Level=1 or Level=2 or Level=3]]</Select><Select Path="Microsoft-Windows-Storage-ATAPort/Admin">*[System[Level=1 or Level=2 or Level=3]]</Select><Select Path="Microsoft-Client-Licensing-Platform/Admin">*[System[Level=1 or Level=2 or Level=3]]</Select><Select Path="Microsoft-Windows-DataIntegrityScan/Admin">*[System[Level=1 or Level=2 or Level=3]]</Select><Select Path="Microsoft-Windows-DataIntegrityScan/CrashRecovery">*[System[Level=1 or Level=2 or Level=3]]</Select><Select Path="Microsoft-Windows-DSC/Admin">*[System[Level=1 or Level=2 or Level=3]]</Select><Select Path="Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin">*[System[Level=1 or Level=2 or Level=3]]</Select><Select Path="Microsoft-Windows-DeviceSetupManager/Admin">*[System[Level=1 or Level=2 or Level=3]]</Select><Select Path="Microsoft-Windows-Dhcp-Client/Admin">*[System[Level=1 or Level=2 or Level=3]]</Select><Select Path="Microsoft-Windows-Dhcpv6-Client/Admin">*[System[Level=1 or Level=2 or Level=3]]</Select><Select Path="Microsoft-Windows-Diagnosis-Scripted/Admin">*[System[Level=1 or Level=2 or Level=3]]</Select><Select Path="Microsoft-Windows-Storage-Disk/Admin">*[System[Level=1 or Level=2 or Level=3]]</Select><Select Path="Microsoft-Windows-EDP-Application-Learning/Admin">*[System[Level=1 or Level=2 or Level=3]]</Select><Select Path="Microsoft-Windows-EDP-Audit-Regular/Admin">*[System[Level=1 or Level=2 or Level=3]]</Select><Select Path="Microsoft-Windows-EDP-Audit-TCB/Admin">*[System[Level=1 or Level=2 or Level=3]]</Select><Select Path="Microsoft-Windows-GenericRoaming/Admin">*[System[Level=1 or Level=2 or Level=3]]</Select><Select Path="Microsoft-Windows-Hyper-V-Guest-Drivers/Admin">*[System[Level=1 or Level=2 or Level=3]]</Select><Select Path="Microsoft-Windows-Hyper-V-Hypervisor-Admin">*[System[Level=1 or Level=2 or Level=3]]</Select><Select Path="Microsoft-Windows-Hyper-V-VID-Admin">*[System[Level=1 or Level=2 or Level=3]]</Select><Select Path="Microsoft-Windows-Kernel-EventTracing/Admin">*[System[Level=1 or Level=2 or Level=3]]</Select><Select Path="Microsoft-Windows-Mobile-Broadband-Experience-SmsRouter/Admin">*[System[Level=1 or Level=2 or Level=3]]</Select><Select Path="Microsoft-Windows-MUI/Admin">*[System[Level=1 or Level=2 or Level=3]]</Select><Select Path="Microsoft-Windows-PowerShell/Admin">*[System[Level=1 or Level=2 or Level=3]]</Select><Select Path="Microsoft-Windows-PrintService/Admin">*[System[Level=1 or Level=2 or Level=3]]</Select><Select Path="Microsoft-Windows-Provisioning-Diagnostics-Provider/Admin">*[System[Level=1 or Level=2 or Level=3]]</Select><Select Path="Microsoft-Windows-Provisioning-Diagnostics-Provider/AutoPilot">*[System[Level=1 or Level=2 or Level=3]]</Select><Select Path="Microsoft-Windows-Provisioning-Diagnostics-Provider/ManagementService">*[System[Level=1 or Level=2 or Level=3]]</Select><Select Path="Microsoft-Windows-PushNotification-Platform/Admin">*[System[Level=1 or Level=2 or Level=3]]</Select><Select Path="Microsoft-Windows-RemoteApp and Desktop Connections/Admin">*[System[Level=1 or Level=2 or Level=3]]</Select><Select Path="Microsoft-Windows-RemoteAssistance/Admin">*[System[Level=1 or Level=2 or Level=3]]</Select><Select Path="Microsoft-Windows-RemoteDesktopServices-RdpCoreTS/Admin">*[System[Level=1 or Level=2 or Level=3]]</Select><Select Path="Microsoft-Windows-RemoteDesktopServices-RemoteFX-Synth3dvsc/Admin">*[System[Level=1 or Level=2 or Level=3]]</Select><Select Path="Microsoft-Windows-RetailDemo/Admin">*[System[Level=1 or Level=2 or Level=3]]</Select><Select Path="Microsoft-Windows-SecurityMitigationsBroker/Admin">*[System[Level=1 or Level=2 or Level=3]]</Select><Select Path="Microsoft-Windows-SmartCard-TPM-VCard-Module/Admin">*[System[Level=1 or Level=2 or Level=3]]</Select><Select Path="Microsoft-Windows-SMBWitnessClient/Admin">*[System[Level=1 or Level=2 or Level=3]]</Select><Select Path="Microsoft-Windows-Storage-Tiering/Admin">*[System[Level=1 or Level=2 or Level=3]]</Select><Select Path="Microsoft-Windows-Storage-ClassPnP/Admin">*[System[Level=1 or Level=2 or Level=3]]</Select><Select Path="Microsoft-Windows-Storage-Storport/Admin">*[System[Level=1 or Level=2 or Level=3]]</Select><Select Path="Microsoft-Windows-TerminalServices-ClientUSBDevices/Admin">*[System[Level=1 or Level=2 or Level=3]]</Select><Select Path="Microsoft-Windows-TerminalServices-LocalSessionManager/Admin">*[System[Level=1 or Level=2 or Level=3]]</Select><Select Path="Microsoft-Windows-TerminalServices-PnPDevices/Admin">*[System[Level=1 or Level=2 or Level=3]]</Select><Select Path="Microsoft-Windows-TerminalServices-Printers/Admin">*[System[Level=1 or Level=2 or Level=3]]</Select><Select Path="Microsoft-Windows-TerminalServices-RemoteConnectionManager/Admin">*[System[Level=1 or Level=2 or Level=3]]</Select><Select Path="Microsoft-Windows-User Device Registration/Admin">*[System[Level=1 or Level=2 or Level=3]]</Select><Select Path="Microsoft-Windows-VerifyHardwareSecurity/Admin">*[System[Level=1 or Level=2 or Level=3]]</Select><Select Path="Microsoft-Windows-WindowsBackup/ActionCenter">*[System[Level=1 or Level=2 or Level=3]]</Select><Select Path="Microsoft-Windows-Workplace Join/Admin">*[System[Level=1 or Level=2 or Level=3]]</Select><Select Path="OpenSSH/Admin">*[System[Level=1 or Level=2 or Level=3]]</Select><Select Path="Windows PowerShell">*[System[Level=1 or Level=2 or Level=3]]</Select></Query></QueryList></QueryNode></QueryConfig><ResultsConfig><Columns><Column Path="Event/System/Level" Visible="" Type="System.String" Name="Level">280</Column><Column Path="Event/System/Keywords" Type="System.String" Name="Keywords">70</Column><Column Path="Event/System/TimeCreated/@SystemTime" Visible="" Type="System.DateTime" Name="Date and Time">330</Column><Column Path="Event/System/Provider/@Name" Visible="" Type="System.String" Name="Source">240</Column><Column Path="Event/System/EventID" Visible="" Type="System.UInt32" Name="Event ID">240</Column><Column Path="Event/System/Task" Visible="" Type="System.String" Name="Task Category">241</Column><Column Path="Event/System/Security/@UserID" Type="System.String" Name="User">50</Column><Column Path="Event/System/Opcode" Type="System.String" Name="Operational Code">110</Column><Column Path="Event/System/Channel" Type="System.String" Name="Log">80</Column><Column Path="Event/System/Computer" Type="System.String" Name="Computer">170</Column><Column Path="Event/System/Execution/@ProcessID" Type="System.UInt32" Name="Process ID">70</Column><Column Path="Event/System/Execution/@ThreadID" Type="System.UInt32" Name="Thread ID">70</Column><Column Path="Event/System/Execution/@ProcessorID" Type="System.UInt32" Name="Processor ID">90</Column><Column Path="Event/System/Execution/@SessionID" Type="System.UInt32" Name="Session ID">70</Column><Column Path="Event/System/Execution/@KernelTime" Type="System.UInt32" Name="Kernel Time">80</Column><Column Path="Event/System/Execution/@UserTime" Type="System.UInt32" Name="User Time">70</Column><Column Path="Event/System/Execution/@ProcessorTime" Type="System.UInt32" Name="Processor Time">100</Column><Column Path="Event/System/Correlation/@ActivityID" Type="System.Guid" Name="Correlation Id">85</Column><Column Path="Event/System/Correlation/@RelatedActivityID" Type="System.Guid" Name="Relative Correlation Id">140</Column><Column Path="Event/System/Provider/@EventSourceName" Type="System.String" Name="Event Source Name">140</Column></Columns></ResultsConfig></ViewerConfig>

I do have and use the Lorby app for the scenery.  I have run the Delete generated files and no joy with that.  Basically I have uninstalled P3D at least three times following the guide and no joy either.  So I'll follow you guy's steps here and hope for success.

Here are my computer specs for resource information:

OS Name    Microsoft Windows 10 Home
Version    10.0.17763 Build 17763
Other OS Description     Not Available
OS Manufacturer    Microsoft Corporation
System Name    AURORA
System Manufacturer    Alienware
System Model    Aurora
System Type    x64-based PC
System SKU    0
Processor    Intel(R) Core(TM) i7 CPU         960  @ 3.20GHz, 3201 Mhz, 4 Core(s), 8 Logical Processor(s)
BIOS Version/Date    Alienware A11, 10/28/2009
SMBIOS Version    2.5
Embedded Controller Version    255.255
BIOS Mode    Legacy
BaseBoard Manufacturer    Alienware
BaseBoard Product    04VWF2
BaseBoard Version    A00
Platform Role    Desktop
Secure Boot State    Unsupported
PCR7 Configuration    Binding Not Possible
Windows Directory    C:\WINDOWS
System Directory    C:\WINDOWS\system32
Boot Device    \Device\HarddiskVolume1
Locale    United States
Hardware Abstraction Layer    Version = "10.0.17763.404"
User Name    Aurora\Ted
Time Zone    Pacific Daylight Time
Installed Physical Memory (RAM)    12.0 GB
Total Physical Memory    12.0 GB
Available Physical Memory    7.49 GB
Total Virtual Memory    14.4 GB
Available Virtual Memory    7.57 GB
Page File Space    2.38 GB
Page File    C:\pagefile.sys
Kernel DMA Protection    Off
Virtualization-based security    Not enabled
Device Encryption Support    Reasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and device is not InstantGo, Un-allowed DMA capable bus/device(s) detected, TPM is not usable
Hyper-V - VM Monitor Mode Extensions    Yes
Hyper-V - Second Level Address Translation Extensions    Yes
Hyper-V - Virtualization Enabled in Firmware    Yes
Hyper-V - Data Execution Protection    Yes

 

 

Ted

Edited April 23, 20197 yr by ted757
add comment

Sure looks like you have something seriously boogered up in your .Net framework.  IMHO, you can spend weeks trying to sort that out, or go ugly early and do a clean reinstall of Windows 10.  Also, that 2009 BIOS in your i7-960 is very old...I'd check to see if there's a newer version and, if so, update it before reinstalling Windows.

In case you were unaware, MS has a web-based installation media creator that will create a bootable USB stick on-the-fly with the latest version of Win 10, so very few updates should be needed initially:

https://support.microsoft.com/en-us/help/15088/windows-10-create-installation-media

Regards

Thanks for the reinstall suggestion.  I have already tried the "windows Refresh" and "Windows "Reset" from the Windows settings page.  That was last week and obviously no joy.

I started this "hobby" back Microsoft Flight sim 98, then to FS, FS Steam and then made the jump to P3D.  P3D has worked flawlessly until one morning when all this started.  I have seen others struggle through this and I'm really afraid to do a REAL install of windows 10.

Should uninstall P3DV4 again, follow the guide's instruction?  Feeling a little paralyzed right now!

Ted

 

IMHO, a Windows 10 reinstall should be your last resort.  You should be able to reinstall the dotnets based on the information in the AVSIM CTD Guide.  The reset feature does not work well with P3D and P3D addons.  You might as well reformat your HDD and reinstall Windows clean.  It's about the same thing.  I have had several ugly experiences.  A reset will easily wipe out your registry entries for P3D and all add ons even though the preview shows it will not.  You want more frustrations?  Reset.

4 hours ago, ted757 said:

I do have and use the Lorby app for the scenery.  I have run the Delete generated files and no joy with that.

You can temporarily remove all of your add-on Scenery as discussed above by going to Documents/Prepar3DV4 Add-ons.  Move all of the contents (not the folder) to a temporary directory like C:/Temp.  This will eliminate all scenery add-ons from loading.  If you still get the crash, then you can assume it is not an add-on scenery causing your issues. 

Please read and follow the information provided by others regarding you running out of resources. 

4 hours ago, ted757 said:

Here is the latest WER from a few minutes ago when I tried to start P3D.

How do you get this WER was from P3D?  Where does it state you tried to start P3D?  It only shows you tried to start the DotNet Repair Tool at some time.  Follow the directions I made earlier - The VSSetup error is another Microsoft error and related to Microsoft Visuals C++ Redistributables - not with P3D - https://github.com/Microsoft/vssetup.powershell.  You have to wonder if you didn't bork an installation of a scenery, an aircraft, or a utility that is loaded when you first startup P3D and is loaded by the dll.xml.  To me, this indicates something was not installed properly and P3D is balking, not because of the VSSetup error as that is a separate function not even closely related to the installation of P3D.  When P3D is calling, say, some addon scenery to load or a utility to load, Microsoft Windows will run a VSSetup error to tell you there is something seriously wrong when that scenery or aircraft was called.

When you get your freezes (not crashes - have not seen a crash yet), when does it happen?  Were you just starting P3D to the setup up screen?  Did you set up a flight scenario and load it?  Was it after takeoff?  Was it near landing?  As stated in the AVSIM CTD Guide, these are important questions as each scenario means something different.  For instance, some scenery and the dll.xml modules load at startup.  The scenario load gets you to your departure airport in the aircraft you selection and also loads terrain, weather, and scenery files and continues to do that even while sitting at your departure airport.  An issue and there will be a freeze.  See near the end of the AVSIM CTD Guide where it tells you what others have done to fix their problem when first starting up P3D, loading the flight, while at the airport, after takeoff, and during landing.

 

 

 

Jim,

This crash occurs right when the L/M screen appears at startup, it shows loading scenery files, blue bars twice and then 7 seconds later it all disappears.  Never even got to the flight set up screen.

Ted,

 

8 minutes ago, ted757 said:

Jim,

This crash occurs right when the L/M screen appears at startup, it shows loading scenery files, blue bars twice and then 7 seconds later it all disappears.  Never even got to the flight set up screen.

Ted,

 

Then it is one of the modules in the dll.xml that is causing the freeze.  Did you update fsuipc and ASP4 after updating to 4.5?  This is usually the cause as developers who had compatibility with 4.4, now need to update their add-ons to 4.5.

Will advise on this suggestion...

T

Jim,

Updated FSUPIC to latest, but I use Sky Force 3d and not Active Sky.  It is not installed right now.

I did find a file called DLL in the AppData under Roaming here is what it said:

<?xml version="1.0" encoding="WINDOWS-1252"?>

<SimBase.Document version="1,0" Type="Launch"> <Descr>Launch</Descr> <Filename>dll.xml</Filename> <Disabled>False</Disabled> <Launch.ManualLoad>False</Launch.ManualLoad> <Launch.Addon> <Name>FSUIPC 5</Name> <Disabled>False</Disabled> <Path>C:\Program Files\Lockheed Martin\Prepar3D v4\Modules\FSUIPC5.dll</Path> </Launch.Addon> </SimBase.Document>

 

The Modules folder in the L/M P3D only contains 4 FSUPIC items.  One FSUPIC Document folder, one FSUPIC5 Install text document, one FSUPIC.DLL, and one FSUPIC5.key.

After all this I ran the P3DV4 EXE and the same thing happened, no joy this morning.

I have NO add on aircraft installed and NO add on scenery installed at all, only a fresh install if P3DV5 from yesterday, No shaders,.  Only the Lorby scenery organizer installed.  I caused no problems before this episode began.

Here is the Event Viewer from this latest attempt:

Log Name:      System
Source:        Microsoft-Windows-DistributedCOM
Date:          4/24/2019 8:29:14 AM
Event ID:      10016
Task Category: None
Level:         Error
Keywords:      Classic
User:          AURORA\Ted
Computer:      Aurora
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 Aurora\Ted SID (S-1-5-21-4168704676-1823929620-91171720-1001) 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>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8080000000000000</Keywords>
    <TimeCreated SystemTime="2019-04-24T15:29:14.163830300Z" />
    <EventRecordID>378</EventRecordID>
    <Correlation />
    <Execution ProcessID="344" ThreadID="6412" />
    <Channel>System</Channel>
    <Computer>Aurora</Computer>
    <Security UserID="S-1-5-21-4168704676-1823929620-91171720-1001" />
  </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">Aurora</Data>
    <Data Name="param7">Ted</Data>
    <Data Name="param8">S-1-5-21-4168704676-1823929620-91171720-1001</Data>
    <Data Name="param9">LocalHost (Using LRPC)</Data>
    <Data Name="param10">Unavailable</Data>
    <Data Name="param11">Unavailable</Data>
  </EventData>
</Event>

Thoughts??

Ted

 

 

 

Edited April 24, 20197 yr by ted757

Those errors are not P3D or P3D related.  The Events are very common and Googling " The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID", will find a fix for this error but so far I cannot get it fixed.  I understand they the event will not harm your computer and to just let the event go unfixed.

2 hours ago, ted757 said:

he Modules folder in the L/M P3D only contains 4 FSUPIC items.  One FSUPIC Document folder, one FSUPIC5 Install text document, one FSUPIC.DLL, and one FSUPIC5.key.

After all this I ran the P3DV4 EXE and the same thing happened, no joy this morning.

I have NO add on aircraft installed and NO add on scenery installed at all, only a fresh install if P3DV5 from yesterday, No shaders,.  Only the Lorby scenery organizer installed.  I caused no problems before this episode began.

The FSUIPC5 utility is for P3DV4 and appears to be installed properly.  We are not nearing the point of a complete reset of your computer.  So far I see no errors for that would cause P3DV4 down.

Is there a dll.xml in the same folder as the scenery.cfg?  This is the default one.  If you have any Carenado default aircraft, this xml would load the Carenado modules and I have seen issues with these every so often.