GGG is arbitrarily locking threads about HARD CRASHES THAT BRICK PCS!

The thread "PoE 2 is actively damaging PCs and GGG is on Holiday without fixing it - Loading Screen PC Freeze"
has been locked for no real reason on Dec 29, 2024, 11:34:16 PM by an official account brazenly stating "This thread has been closed, as it is generating many posts that breach the Code of Conduct. If you have any concerns about this, please feel free to contact us at support@grindinggear.com"

The same support which has previously stated that they are not currently working. When you send an email to the support people have reported that they got an email back after two weeks stating they are not providing support at the moment.

The support also tries to remove or discourage any reference to the best working solution that is PoEUncrasher. Any direct mention of its creator gets removed by support.

Furthermore, I ask anyone who sees this message to please give a negative review for Path of Exile 2 on Steam.

If you're able to run software to "uncrash" things, then the PC ain't bricked.

"

codedependent#1277 wrote:

If you're able to run software to "uncrash" things, then the PC ain't bricked.

That software stops the crash itself from happening in an ingenious way. Basically you run it before starting the game, when it detects the crash it arranges your core affinities and PoE2's priority.

Without it the game hard crashes. There are 2 main threads that are still up with almost 6000 replies, some of which report bricking.

As it is a third party program I do not condone its use. Everyone should decide by themselves whether it is okay to use it or not.

Furthermore, I ask anyone who sees this message to please give a negative review for Path of Exile 2 on Steam.

OMG THIS HAPPENED TO MY PC 3 TIMES IN 15 MINS. I HAD TO MANUALLY PRESS MY POWER BUTTON TO RESTART MY COMPUTER BECAUSE THE WHOLE FKN THING FROZE!!!!!!!!!!

I'M TOO SCARED TO GO ONTO POE2 NOW FOR THE SAKE OF MY COMPUTER. ALSO MY COMPUTER IS BRAND NEW AND CAN RUN ANYTHING.

"

Cainrith#2807 wrote:

That software stops the crash itself from happening in an ingenious way. Basically you run it before starting the game, when it detects the crash it arranges your core affinities and PoE2's priority.

It doesn't detect anything. It just parses Client.txt for specific substrings matching RegEx pattern:

"

Regex startGameMatcher = new(@"^\d{4}/\d{2}/\d{2} \d{2}:\d{2}:\d{2} \d+ [a-fA-F0-9]+ \[INFO Client \d+\] \[ENGINE\] Init$", RegexOptions.Compiled);
Regex startLoadMatcher = new(@"^\d{4}/\d{2}/\d{2} \d{2}:\d{2}:\d{2} \d+ [a-fA-F0-9]+ \[INFO Client \d+\] \[SHADER\] Delay: OFF$", RegexOptions.Compiled);
Regex endLoadMatcher = new(@"^\d{4}/\d{2}/\d{2} \d{2}:\d{2}:\d{2} \d+ [a-fA-F0-9]+ \[INFO Client \d+\] \[SHADER\] Delay: ON", RegexOptions.Compiled);

"

[SHADER] Delay: OFF
[SHADER] Delay: ON

If the game decides to process shaders in the other time it will crash.

Eveyrone can do the same by setting affinity manualy in their Task Manager / Process Explorer / System Informer without relying on 3rd party software from "Joe Schmoe"(c)

BUMP

"

cursorTarget#1174 wrote:

"

Cainrith#2807 wrote:

That software stops the crash itself from happening in an ingenious way. Basically you run it before starting the game, when it detects the crash it arranges your core affinities and PoE2's priority.

It doesn't detect anything. It just parses Client.txt for specific substrings matching RegEx pattern:

"

Regex startGameMatcher = new(@"^\d{4}/\d{2}/\d{2} \d{2}:\d{2}:\d{2} \d+ [a-fA-F0-9]+ \[INFO Client \d+\] \[ENGINE\] Init$", RegexOptions.Compiled);
Regex startLoadMatcher = new(@"^\d{4}/\d{2}/\d{2} \d{2}:\d{2}:\d{2} \d+ [a-fA-F0-9]+ \[INFO Client \d+\] \[SHADER\] Delay: OFF$", RegexOptions.Compiled);
Regex endLoadMatcher = new(@"^\d{4}/\d{2}/\d{2} \d{2}:\d{2}:\d{2} \d+ [a-fA-F0-9]+ \[INFO Client \d+\] \[SHADER\] Delay: ON", RegexOptions.Compiled);

"

[SHADER] Delay: OFF
[SHADER] Delay: ON

If the game decides to process shaders in the other time it will crash.

Eveyrone can do the same by setting affinity manualy in their Task Manager / Process Explorer / System Informer without relying on 3rd party software from "Joe Schmoe"(c)

So it detects it this way. Detection does not have to be some sort of complex behaviour, as long as it gets the job done anything is fine.

I think no human is fast enough to open task manager and set PoE2 to real-time while the crash is happening.

I agree on "3rd party software from "Joe Schmoe"(c)", for this time the creator seems actually a good guy but we can never know. Being exposed to this is not how a paying customer should be treated. For example I do not use it.

Furthermore, I ask anyone who sees this message to please give a negative review for Path of Exile 2 on Steam.

"

Cainrith#2807 wrote:

So it detects it this way. Detection does not have to be some sort of complex behaviour, as long as it gets the job done anything is fine.

It only detects the loading screen. Nothing more. We have many users who experience crashes not only due to loading screens. Or the users who crashed despite changed affinity/priority.

It doesn't change IAT or vtable entries, it doesn't overrides the exception handler(s), it doesn't set breakpoints, it doesn't analyze the possible shared objects (like mutex / semaphore). It only parses Client.txt with some delay (20 ms) preemptivly changing affinity / priority in a HOPE that it will help which makes that method very unreliable. It's not even close to the definition of "detecting crash". Not every single loading screen crashes the system.

"

cursorTarget#1174 wrote:

"

Cainrith#2807 wrote:

So it detects it this way. Detection does not have to be some sort of complex behaviour, as long as it gets the job done anything is fine.

It only detects the loading screen. Nothing more. We have many users who experience crashes not only due to loading screens. Or the users who crashed despite changed affinity/priority.

It doesn't change IAT entries, it doesn't overrides the exception handler(s), it doesn't set breakpoints, it doesn't analyze the possible shared objects (like mutex / semaphore). It only parses client.txt with some delay (20 ms) which makes that method very unreliable.

So it detects the portion which most crashes happen and avoids it.

I don't believe that with your supposed expertise that you are missing the reason why the users who crashed despite changed affinity/priority crashed: The cores that they have freed this way was not enough for their system to run. When they did increase the number of cores beyond PoE2's reach they stopped crashing.

Please stop derailing threads.

Furthermore, I ask anyone who sees this message to please give a negative review for Path of Exile 2 on Steam.