Hard crashing PC locks up

"

Cainrith#2807 wrote:

Let me explain the statistical errors they have been committing:

1)The reason why they observed "most" players who have the issue have Windows 24H2 is because "most" players updated their OS and their drivers while preparing for the long-awaited, once delayed launch of this game.

This is the classic "correlation does not imply causation" error, coupled with selection bias. It also comes with ambiguous language trick, they should have given percentages instead of saying "most" but that one is just egging me.

2)Players under level 25 cannot send DMs. Hence they will not be able to send the DxDiags to the GGG. Players who are not active on forums won't see this request, which was not pinned as a separate post. Instead it was put inside two very active threads, causing many people to miss it. Finally GGG does not check any other source of DxDiag that are not DMs.

Hence if they look at the sample they can say "this is an issue that affects players above level 25." or "this is an issue that affects players that use the PoE forums."

This is the classic "the absence of evidence is not the same as evidence of absence". The error committed is sample selection bias.

"

Any possible estimation on a fix for the PC freezing effecting some of the player base? In loading screens the game with freeze and lock up the entire PC forcing a shutdown with the power button. Game also will use 100% of CPU memory on loading screens, with actual gameplay using less.

"

ieovnkr#4861 wrote:

Dear Poe2 gamers,

We are aware that the game crashes during loading screens requiring a full reset of the computer for some users. This is a high priority issue that are working to resolve ASAP as we understand many people paid for the game but are unable to enjoy it. We have identified the issue and are working to resolve this in a future patch. Please stay tuned for further updates.

With love, your GGG

"

.NET Runtime

- Fixes a problem where in rare cases an infinite loop could occur when a thread switches clR for the first time.

"

Error during the Transition to the CLR

The issue described in KB5048162 occurred when a thread transitioned for the first time from another context (e.g., native code or unmanaged memory) into the Common Language Runtime (CLR). In the case of a game, this could happen:

At the start of the game: When initialising components or subsystems.
While loading specific content or game mechanics: For example, shader data, assets, or other resources being processed.
During the execution of scripts: Particularly if they are based on .NET (e.g., C# scripting or managed plugins).
If this bug occurs, the game could freeze, hang, or, in rare cases, even crash.

"

Error during the Transition to the CLR

The issue described in KB5048162 occurred when a thread transitioned for the first time from another context (e.g., native code or unmanaged memory) into the Common Language Runtime (CLR). In the case of a game, this could happen:

At the start of the game: When initialising components or subsystems.
While loading specific content or game mechanics: For example, shader data, assets, or other resources being processed.
During the execution of scripts: Particularly if they are based on .NET (e.g., C# scripting or managed plugins).
If this bug occurs, the game could freeze, hang, or, in rare cases, even crash.

"

I'm not the ultimate nerd, but that sounds plausible to me.

Without the update, the game freezes within 10 loading screens for me. With the update, I've played through two acts and not once has my PC frozen.

Please can someone seriously test this? This can't be a coincidence in my case.

"

69oVerkill69#4406 wrote:

I can only encourage you to install the optional update ‘KB5048162’!

This fixes the following bug:

"

.NET Runtime

- Fixes a problem where in rare cases an infinite loop could occur when a thread switches clR for the first time.

No idea what this means, but what is Chat GPT for?

"

Error during the Transition to the CLR

The issue described in KB5048162 occurred when a thread transitioned for the first time from another context (e.g., native code or unmanaged memory) into the Common Language Runtime (CLR). In the case of a game, this could happen:

At the start of the game: When initialising components or subsystems.
While loading specific content or game mechanics: For example, shader data, assets, or other resources being processed.
During the execution of scripts: Particularly if they are based on .NET (e.g., C# scripting or managed plugins).
If this bug occurs, the game could freeze, hang, or, in rare cases, even crash.

I'm not the ultimate nerd, but that sounds plausible to me.

Without the update, the game freezes within 10 loading screens for me. With the update, I've played through two acts and not once has my PC frozen.

Please can someone seriously test this? This can't be a coincidence in my case.