[RESOLVED] P3D 4.4 FREEZE CRASH

[cookedinlh]

I've struggled with numerous conflict and WIN 10 issues, one rabbit hole after another I've solve each one . . conflicts with DirectX9 (I'm now on 12). Screen issues C++ Redistributable 2015 won't coexist with 2017 . . and a dozen more. I'm now down to one.

I can fly for 10min or an hour sometimes and randomly P3D v4.4 simply locks up for 15-20 sec and then goes away.
Event Manager says this . . just 1 sec before the crash
==========EVENT REPORT=============
Fault bucket 2104677336513315965, type 5
Event Name: AppHangXProcB1
Response: Not available
Cab Id: 0

Problem signature:
P1: Prepar3D.exe
P2: 4.4.16.27077
P3: 5bfdbb35
P4: 0000
P5: 134250752
P6: unknown
P7: 0.0.0.0
P8:
P9:
P10:

It also says there is a file called "WER713A.tmp.WERInternalMetadata.xml" located at \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER713A.tmp.WERInternalMetadata.xml . . . but when I go there the temp folder is EMPTY . . and now that think about it some more that may be because I closed the Microsoft "I'm just going to collect some data" popup without allowing it to finish.

The only other entry about 20 min before that is an EVENT 1534 User Profile Service that says "Profile notification of event Load for component {B31118B2-1F49-48E5-B6F5-BC21CAEC56FB} failed, error code is See Tracelogging for error details."

Any ideas or pointers would be greatfully appreciated
cookedinlh

[Martyson]

One thing to give a quick try would be the general debugging steps here:
http://www.prepar3d.com/forum/viewtopic ... 2&t=123246

[corinoco]

I've just had very similar issues.

Firstly the EVENT 1534 is a known but unsolved issue in Windows 10 v1809 for a lot of people. I had the same issue until I did a rebuild from scratch - MS seem to introduce more problems than they solve with their service patches these days.

Secondly I suspect that v4.4 is just that little bit harder on hardware, especially RAM. I solved my CTDs by underclocking my RAM by about 10% 1866Mhz down to 1600Mhz.

I can now fly stable for at least 2 hours without a CTD - previously I could only get about 15 mins out of V4.4.

My machine is 6 years old too - and has had a hard life (FSX / P3D / Civ / CAD work / 3DS Max) so most of my components could probably do with replacing.

[cookedinlh]

Further investigation pulled up this WINDOW ERROR REPORT file ReportP3DCrash20-840am.wer . . . . the contents of which is below. I suspect the OS may have been the instigator not P3D itself so I'm also asking MSFT if they know anything. Prior to these crashes there always seems to be a series of WARNINGS from the "User Profile Service" failing to load some component called {B31118B2-1F49-48E5-B6F5-BC21CAEC56FB} with no way to see further what that is.

===============wer content is this . . . plus a data dump of all loaded .dlls and status ==============
Version=1
EventType=APPCRASH
EventTime=131924652547965331
ReportType=2
Consent=1
UploadTime=131924652554994903
ReportStatus=268566528
ReportIdentifier=611b8031-b8e4-4405-9693-60922121a751
IntegratorReportIdentifier=6fce9950-e335-47cb-a7c1-b991ea369a6f
Wow64Host=34404
NsAppName=Prepar3D.exe
OriginalFilename=Prepar3D.exe
AppSessionGuid=0000112c-0001-0011-7214-20f2c2b0d401
TargetAppId=W:00006b12e3fce19ea04af6bedffc2678c5f400000904!0000f4a6d227777f5de7b2e85c3afb498a6b55cc49a0!Prepar3D.exe
TargetAppVer=2018//11//27:21:46:29!2d2651!Prepar3D.exe
BootId=4294967295
TargetAsId=1284
UserImpactVector=286274320
IsFatal=1
EtwNonCollectReason=1
Response.BucketId=20cc69672e87f2bb86a8b596a5ee5851
Response.BucketTable=4
Response.LegacyBucketId=1632754523555387473
Response.type=4

[cookedinlh]

Thanks Martyson . . for the helpful summary. I have done all of that and more except for the but it was useful to know that I've been going in the right direction . .I had not gotten rid of some Addons so will do that now.
Thanks also corinoco for that additional suggestions and corroberation that I'm not totally crazy when I talk to Microsoft . . it's always the AP . . Ive learned so much about the systems incl WIN10 since starting this.

So I created a new MS User Profile to see if this gremlin is expunged . . 2 hrs on the phone with MS was mostly arguing that it could not be an MS issue and just need to reinstall the app . . but creating a profile is a blank sheet and no history or preferences settings and config files are vanilla . . so I've spent another hr or two so far carefully copying just P3D and other sim files needed for this new profile. I've had about 1 1/2 hrs of uneventful flight so will keep testing along these lines.

All of your feedback is very encouraging . . thanks

[cookedinlh]

This is a followup to the OPEN ticket about my crashing P3D libcef.dll issue. Definitely C++ Redist 2015 issue was involved and clearly a Microsoft BUG . . . but there is another called 1534 UserProfile Warning! . . I have flown successfully now for a few hours with no P3D Crash and no more references to libcef.dll or Dxdiag.exe . . and no Warnings that would cause a P3D Pause of several seconds just before the CRASH. The most recent major update WIN10 1809 (Oct 2018) failed to delete 2 obsolete REG Keys that would pause P3D with warnings until it gave up and crashed. I will keep close watch on my Event Manager but unless I see something new, I think this issue is now closed.

I believe I now have the answer, ( from "sevenmm1985" published here https://social.technet.microsoft.com/Fo ... networking in October 2018 . .which should be noted for anyone who needs it.

He had the same issue and wrote this. I have done this fix and it appears to work . . no more 1534 Warnings in the system . .period. P3D v4.4 running smoothly again.

===============sevenmm1985 wrote=================
Finally found a FIX for 1534 error !

1. Open Regedit and navigate to the following two keys
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileNotification
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows NT\CurrentVersion\ProfileNotification
2. Under ProfileNotification check if you have the TDL key
3. Export the TDL key at each location
4. Delete the TDL key at each location
5. Reboot PC to verify

Note:
You'll need take ownership of the TDL Key to be able to delete it.

Works for me like a charm with no downsides.

After this fix the 1534 baragge has stopped in my OS :)