v5.4 Occasional hang with all cores to 100%

[mpni]

Hi bhorv67
Have a look at your CPU temperature during a flight.
In the windows parameters / games, is the game mode activated?
Regards
Michel

[bhorv67]

Bhorv67, a quote: "Some without any Windows Event log entry".

In those that produce an Event Viewer entry, what are the exception codes there?

Jorgen

Here's the full output:

Faulting application name: Couatl64_P3D.exe, version: 4.8.0.5301, time stamp: 0x6536a6da
Faulting module name: ucrtbase.dll, version: 10.0.22621.2506, time stamp: 0x097c794c
Exception code: 0xc0000409
Fault offset: 0x000000000007f61e
Faulting process id: 0x0x224
Faulting application start time: 0x0x1DA106760E6736D
Faulting application path: C:\Program Files (x86)\Addon Manager\couatl64\Couatl64_P3D.exe
Faulting module path: C:\Windows\System32\ucrtbase.dll
Report Id: 3e018187-308b-4029-a9a6-813831bc0ea9
Faulting package full name:
Faulting package-relative application ID:

[bhorv67]

Hi bhorv67
Have a look at your CPU temperature during a flight.
In the windows parameters / games, is the game mode activated?
Regards
Michel

Under normal operations, temps are well within spec. One of the main reasons I skip the HT cores is to keep temps in line. However, when all cores suddenly go to 100%, temps are 90-95c.
Game mode is active.

[JorgenSA]

The exception code here:

Exception code: 0xc0000409

can be a difficult one to get rid of. Searching the web for it brings up this:

https://www.google.com/search?q=Excepti ... e&ie=UTF-8

But I remember that I got somewhat frustrated by this. So, since I had enough space on my C: drive, I installed Microsoft Visual Studio, both the 2019 and the 2022 versions, and the error went away.

Jorgen

[bhorv67]

Update on this issue. Appears to be solved.

Offending issue was related to a 3rd party app modifying shaders.
Restoring to default shaders corrected the problem.

Will continue to monitor and report back any updates.
Appreciate all the help.

[bhorv67]

Resurrecting this thread - the issue persists.

The behavior is now the sim runs (all the time) with all cores maxed - this has never happened in the past. I haven't changed a thing in my environment. Previously, I would get moments of freezes when all cores are maxed, and now all cores are maxed all the time - but now I'm getting the freezes little by little through the flight, until a complete freeze, then CTD.

If there ever is a windows log created, the offending module relates to FSDT's couatl process, but I feel what's happening is windows is just getting a report of that process crashing while whatever this issue is going on is causing this max usage of cpu cores.

I really don't know what else to try to solve at this point.

As stated earlier, I'm about to try a repair of the p3d base files and see what happens.

[robpol471]

Hi bhorv67,

I can tell you that in my case the P3D freezes or CTD without specific error reports appeared when, to reduce the high temperatures of the I9 13900k which with P3D reached peaks between 90/95° C, I started to reduce the CPU Vcore in the Bios.

On my Asus Rog Strix Z790 A the Bios in Auto overclocked the I9 13900k to 5.5 Ghz (with two cores reaching 5.8 Ghz) and the Vcore to 1.450.

I made several attempts reducing the Vcore but at 1.360 I started with P3D freezes and several CTDs without specific reports and also blue error screens on the Desktop.

My best solution to no longer have blocks or CTDs with P3D and a max peak core temperature below 80°C with P3D was to set the frequency of all the processor cores at 5.4 Ghz with a Vcore at 1.370.

Obviously I don't know if this post of mine can be useful to you but, if you haven't already done so, you can try to reduce the Ghz in the Bios
of 2/300 Mhz of the CPU leaving the same Vcore and check whether or not the freezes or CTD appear on P3D.

[bhorv67]

Hi bhorv67,

I can tell you that in my case the P3D freezes or CTD without specific error reports appeared when, to reduce the high temperatures of the I9 13900k which with P3D reached peaks between 90/95° C, I started to reduce the CPU Vcore in the Bios.

On my Asus Rog Strix Z790 A the Bios in Auto overclocked the I9 13900k to 5.5 Ghz (with two cores reaching 5.8 Ghz) and the Vcore to 1.450.

I made several attempts reducing the Vcore but at 1.360 I started with P3D freezes and several CTDs without specific reports and also blue error screens on the Desktop.

My best solution to no longer have blocks or CTDs with P3D and a max peak core temperature below 80°C with P3D was to set the frequency of all the processor cores at 5.4 Ghz with a Vcore at 1.370.

Obviously I don't know if this post of mine can be useful to you but, if you haven't already done so, you can try to reduce the Ghz in the Bios
of 2/300 Mhz of the CPU leaving the same Vcore and check whether or not the freezes or CTD appear on P3D.

Appreciate the suggestion, but I believe my issue is from some addon that's corrupted or a recent Win11 update conflicting with something.

The strange thing is no matter which cores I set the mask to, those cores will be at 100% utilization once the plane is in flight. While this is happening, scenery isn't loading properly.
It doesn't matter which plane I use (default or 3rd party), the behavior is the same.

I've even systematically disabled addons one at a time and tested, with no joy.
I think I'm at the point where I have to completely uninstall everything and start over.
The repair (and uninstall/reinstall) of just P3d did not help

[pestridge77]

Hi bhorv67
Let we know the result.
Regards
Michel

HI reporting back - Apologies for the delay.
After removing the cfg and having p3d creating a new, the issue persists.
Recently though the freezes are now resulting in a CTD. Some without any Windows Event log entry.

Today during a flight, the cpu began to suddenly put all cores to 100% (I'm using a 13900k and have the affinity set to use only the primary cores, skipping the ht cores. I've also skipped core 0,1 for system and addons). Instead of p3d freezing, the flight continued as normal, but with all cores at 100%. This went on for maybe 15 minutes until a sudden CTD. This time there was a Windows Event log entry, but the faulting module is the typical 'ucrtbase.dll'. Interesting that the faulting application is couatl64_P3d.exe, which is FSDT's scripting engine. That could just be a coincidence as I haven't had issues with any of the FSDT scenery.

I think I may try a repair of the p3d core files and see if that helps.
I know the proper steps is to always disable all the 3rd party addons, but i have so many, it would be impossible to figure out which is causing the issue.

Maybe some of this will make sense. I'm thinking a windows 11 update likely changed some system file that is causing the issue.
I did notice today that Corsair iCue crashed while I was having the P3d issue, perhaps there's a driver corruption?

I think it might be the GPU driver or Windows Updates. Everything youve said shows to me that it isnt P3D causing these issues. Changes in the environment tho can.

When was the last time you updated your GPU driver or Windows?

[Sabre57]

On V6 I've been noticing that over the course of a flight that my CPU and GPU temps slowly rise up to 80 C with occasional jumps higher. CPU utilization doesn't go over about 70% and in some cases is cruising along at 50% or less with know reduction of temps. Reducing P3D settings has little to no effect. Other applications work just fine.

I don't have a solution just adding my observations.

I may try downgrading my GPU drivers, since I'm on the most recent, and see if that has any effect.

[bhorv67]

Hi bhorv67
Let we know the result.
Regards
Michel

HI reporting back - Apologies for the delay.
After removing the cfg and having p3d creating a new, the issue persists.
Recently though the freezes are now resulting in a CTD. Some without any Windows Event log entry.

Today during a flight, the cpu began to suddenly put all cores to 100% (I'm using a 13900k and have the affinity set to use only the primary cores, skipping the ht cores. I've also skipped core 0,1 for system and addons). Instead of p3d freezing, the flight continued as normal, but with all cores at 100%. This went on for maybe 15 minutes until a sudden CTD. This time there was a Windows Event log entry, but the faulting module is the typical 'ucrtbase.dll'. Interesting that the faulting application is couatl64_P3d.exe, which is FSDT's scripting engine. That could just be a coincidence as I haven't had issues with any of the FSDT scenery.

I think I may try a repair of the p3d core files and see if that helps.
I know the proper steps is to always disable all the 3rd party addons, but i have so many, it would be impossible to figure out which is causing the issue.

Maybe some of this will make sense. I'm thinking a windows 11 update likely changed some system file that is causing the issue.
I did notice today that Corsair iCue crashed while I was having the P3d issue, perhaps there's a driver corruption?

I think it might be the GPU driver or Windows Updates. Everything youve said shows to me that it isnt P3D causing these issues. Changes in the environment tho can.

When was the last time you updated your GPU driver or Windows?

Doubt its the gpu driver - I always update when an update is released.
Win11 auto updates as needed. I do however think there is some corruption with possibly a recent Win11 update with some system files in P3d. I've never had any issues like this in the past.

To update what's happening lately, is all available cores are at 100% soon as the plane is in flight. Scenery is not loading due to the sim being overloaded.
I've also tried eliminating addons, and adding back one at a time, with no joy.
I've then tried a complete uninstall/reinstall of the P3d base files - still no luck.

When I finally get enough time over the holidays, I may just start over with a fresh install of everything.
I'm sure there are old addon files that may still have regisrty entries causing problems (maybe leftover black marble files) and whoknows what else.
Just really not looking forward to 4 days of restoring my rig.