Hard crashing PC locks up

"

EiG#3709 wrote:

I found a way to play the game without my PC freezing. I tried all possible solutions, but none worked. The only way it worked was by setting affinity in the task manager on the PathOfExile process, disabling CPU 0 and CPU 1. However, I experienced FPS problems during gameplay using this method.

Then I tried a new way, and it worked—my FPS problem is gone, and the freezing too. Instead of disabling CPU 0 and CPU 1, I disabled CPU 2 and CPU 3. Now my game is running very well, and loading times are pretty quick. I tested this for 5 days and the issues are all gone. I would like to share this with you guys, maybe it can help someone else.

Thanks

"

KissFC#2626 wrote:

After getting tired of my personnal computer getting freeze with a 100% CPU usage, i got the great idea of putting and trying to see what happens on my ES debug station, which have an out of band CPU thread and memroy analyzer (namelly a debug and software profiling station).

The way they're handling multi threading is threatened by modern standard, upgraded UEFI and well secured OSes as a core threat, thus stopping the suspicious threads marked as threat. Similar to how speculative/transient execution CPU vulnerabilities works.
But as the main program isn't flagged as a threat and is considered secure, the OS do not stop it from generating new threads, and the whole process works like a fork bomb.

At this point, i strongly suggest GGG to make a full review of their networking code and to enable fork bombing detection on their compiler because it is something that should never happens.

"

After getting tired of my personnal computer getting freeze with a 100% CPU usage, i got the great idea of putting and trying to see what happens on my ES debug station, which have an out of band CPU thread and memroy analyzer (namelly a debug and software profiling station).

The way they're handling multi threading is threatened by modern standard, upgraded UEFI and well secured OSes as a core threat, thus stopping the suspicious threads marked as threat. Similar to how speculative/transient execution CPU vulnerabilities works.
But as the main program isn't flagged as a threat and is considered secure, the OS do not stop it from generating new threads, and the whole process works like a fork bomb.

At this point, i strongly suggest GGG to make a full review of their networking code and to enable fork bombing detection on their compiler because it is something that should never happens.