CTDs with V5.1HF1

[kaha]

Unfortunately I get CTDs. I did not have a single CTD with V5.1, now with V5.1HF1 CTDs occur at least once every flight, maybe once per hour in average. It also depends on what I'm doing. For example if I switch from fullscreen to windowed mode more often, there are more CTDs.

It's always the same log entry, it's a warning only with event ID 1001 and it mentions Prepar3d.

I did many tests with different aircraft, different scenery, rebuilt .cfg, but there definitely is no rule. With a complex plane in ORBX TE it doesn't happen more often than with a default plane in China.

I can play MSFS (and do context switches from fullscreen to window), Assassins Creed Valhalla and other games for hours and everything works well. I made stress test with my PC, but nothing happens.

I removed overclocking from the 2080TI and from the CPU, but CTDs persist. Only in P3D. Something must be wrong with the installation.


I now have to find out what's the cause for it. I will uninstall it and install it again, starting with the Client. If necessary I will uninstall everything and start with a clean V5.1HF1 installation.

I flew 2 legs with HF1. One was ok, the other suffered from 2 CTDs.

Here are 2 screenshots. One of the log entry and one in game shot with MSI afterburner and GPU-Z visible to show GPU temperature at 99% load. The in game shot is 4K, so you can zoom in.

https://www.dropbox.com/s/aembg7ju4uwfpbx/P3D_V5.1HF1.jpg?dl=0

https://www.dropbox.com/s/7d8runc70spjb5s/P3D_V5.1HF1_1001.jpg?dl=0


Karl

[kaha]

Reinstalled the client, no joy. Probably will install from scratch.

Karl

[nbrich1]

Oh boy, sorry to hear Karl.. will definitely wait for a bit before playing with 5.1x.

[kaha]

Norm, I think I might just be unlucky. 5.1HF1 is behaving nicely. Mostly.  And a clean install every now and then could be an advantage overall.

Thank you,
Karl

[jeff3163]

Have you activated the debug checkboxes for scenery/content errors?   

[kaha]

Good idea, Jeff. I switched it on and had more than 400 errors in the log file.

Most of them of type duplicate section names or key names or key values outside sections in aircraft.cfg or duplicate key names in effects files.

Then there was one error in an add-ons.xml of freeware CYYT.

I managed to eliminate most of it (alone 300 are from FlyTampas Las Vegas scenery), so only some are left, nothing special, that always was in.

I will do a clean installation now.

Thank you,
Karl

[kaha]

It took me 1 1/2 hours to uninstall all addons. I made a list with all the addons I uninstalled, 125 I counted. 22 of them could not be uninstalled because of various reasons, mostly they were not found at their original location.

I will now clean up the registry, remove all traces of all Prepare3D versions on my PC and then start from scratch.

Karl

[kaha]

I'm up and running again. On V5.1HF1 vanilla. Just flying a leg for MFC with the Maule and all standard settings, also standard scenery.

I excpect it working now.

After that I will start to implement scenery and airplanes.

Karl

[kaha]

It looks good so far. I have Tongass in and ORBX. There is one thing that doesn't seem right. Synching in ORBX Center puts airports between base scenery of P3D. For example S45. I made a vide. But it looks ok, doesn't it?

https://vimeo.com/482340897

Karl

[kaha]

After I installed all my ORBX addons the crash was back again. I think tracked it down to the ORBX HD buildings. That's my best guess at the moment, because I can reproduce it:

- HD Buildings insatalled -> crash
- HD Buildings not installed -> no crash

I made a ticket at ORBX support, let's wait what they say.

But, it makes sense because at some point of time after installing HF1 I reinstalled all ORBX Global parts and the building and tree parts.


So, with no HD Buildings installed I can fly without crashes at the moment.

Karl

[stiletto2]

Hi Karl,

Your initial pic post indicates that the video card is crashing.  If it is a Device Hung Error, how much VRAM is available right before you get the error?

Rod

[kaha]

Hi Rod,

I have to check. I will do a video, so the last frame before the screen goes black can be checked.

Karl

[kaha]

But I think it was not more than 5 from 10 GB

Karl

[nbrich1]

The orbx add-on xml stuff is creating a weird in your scenery.cfg. Might need to make a phantom scenery folders to use to set up the top insertion point.. (IE: Third party Libs-top). And use the tongass lower as the bottom insertion point.. hopefully when sync, that might put all the entries in the correct order.. (If not, then you'll have to edit some of those ORBX add-on.xml to change some of those orbx region/airport layers# to force them to go to their correct intended location which is above Tongass.   
Orbx central can make a mess of the layering.. but then, so can Lorby!

[nbrich1]

For anyone getting a Device Hung Error (P3Dv4.3 and above usually) on a Windows 10 64 bit OS:
with Nvidia drivers:

The problem: a thing called TDR checker monitors the computer’s hardware, particularly the GPU. When the GPU stops responding with the computer for 2 seconds TDR checker restarts the driver. The TDR checker was good on paper but did not work in the real world as a GPU can stop responding when it is working hard.

Here is the solution that worked for me, it requires an extra sub key entry into the Windows registry, so please only implement if you feel OK with editing your registry!

- Exit all Windows based programs,
- Click on the Windows Start button, type regedit in the Search box,double-click regedit.exe from the results above.
If you are prompted for an administrator password or confirmation, type the password or provide confirmation,
- Browse to and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers
- On the Edit menu, click New, and select the QWORD (64-bit) value from the drop-down menu,
- Type ‘TdrLevel’ as the Name and click Enter,
- Double-click TdrLevel and set the value as 0 (it is set to that by default, but double check) and click OK,
- Close the registry editor and restart your computer for the changes to take effect!

I saw this fix mentioned earlier in this thread, but make sure you create a Qword (64bit) key for Windows 64 bit OS and NOT a Bword (32 bit) key because that will not give the right result.


If you encounter a DXGI hung/removed error again please make sure that this key still exists in your registry!
It happened to me once that the key vanished after a Windows Update, resulting in the dreadful DXGI hung error once again.


Further notes: 
https://www.pugetsystems.com/labs/hpc/Working-around-TDR-in-Windows-for-a-better-GPU-computing-experience-777/