Hard crashing PC locks up

"
Ashaya2#7109 wrote:
Because it's clearly a new issue. a few isolated crashes 10 years ago, are not the same as the scale of this one. look at the reply count, on both major threads. we're pushing 10k replies. And that's in just 2 mega threads.

Its not, it is the exact same crash that you get in POE1, that has been happening since at least 2017.
its not. my pc never crashed playing poe 1.
"
its not. my pc never crashed playing poe 1.

You know theres a lot of people saying "works on my machine." It sounds just as dumb when you do it.
"
notcory#2048 wrote:
"
Ashaya2#7109 wrote:
Because it's clearly a new issue. a few isolated crashes 10 years ago, are not the same as the scale of this one. look at the reply count, on both major threads. we're pushing 10k replies. And that's in just 2 mega threads.

Its not, it is the exact same crash that you get in POE1, that has been happening since at least 2017.


I have thousands upon thousands of hours in poe1. Just this last league, i played for nearly 800 hours. I didn't start crashing until i installed 24h2 in november.

Now, this doesn't necessarily mean that 24h2 is causing the crash. But it does mean that it's making the crash worse. Somebody earlier said that it was placebo, because people were updating their systems for poe2. 24h2 isn't a public build. You have to go out of your way to get it, by opting into the insider program. 90% of windows users don't do that. Especially not gamer's, who know how bad new updates can be.

I'm in a guild discord, with a few hundred member's, most of us playing poe2. Even if we are generous, and say 150 people, only 2 of us are crashing. And we're the only 2 people on 24h2.

And even then, Windows themselves acknowledged the bug. It caused crashes in Ubisoft games. So Windows themselves have said it's on their end. I don't know what you want. Keep tinfoiling I guess.
"
The only true solution is disabling multi-threading.[/u]

It's WORKAROUND and NOT solution. Solutuion is when you fix your code in the problematic modules and roll the updates out.
Bit the bullet and clean installed Windows 23H2 today. Can confirm, no more freezes or crashes.
"
Ashaya2#7109 wrote:
Keep tinfoiling I guess.

I would argue all that I snipped is more akin to tinfoil than saying a bug thats existed for years was ported over into the sequel of a game using the same engine, and as such wont be fixed. But I'm also not coping.
This is not just a minor bug that the developers can take lightly – we are dealing with an issue that can potentially cause serious hardware problems.

I have noticed that the CPU temperature spikes way too high when running Path of Exile 2 (PoE2).

For context, I am using a 360mm AIO liquid cooler along with 5 additional case fans. I can run Cinebench and Prime95 stress tests for over an hour without encountering issues or reaching temperatures as high as those seen with PoE2.

From this, it seems clear that PoE2 is putting an extreme and sudden load on the CPU, which is likely causing the temperature to rise rapidly and probably causing the crash.

Fix Suggestion for the Devs
A fast fix for the Devs would and could very likely be:
at changing Levels/Areas just remove Hyperthreading ONLY for loading / loading Screens! BOOM Problem Solved

Interestingly, the crashes stop when I disable Hyper-Threading specifically for the game.

System Specifications:
OS: Windows 11 24H2
CPU: AMD Ryzen 7 9800X3D
RAM: 64 GB DDR5 (6000 MHz)
Motherboard: MSI MAG X870 Tomahawk WiFi (BIOS version: 1.A1F)
GPU: RTX 4080

The crashes occur regardless of the renderer used – DX11, DX12, and Vulkan – so this doesn’t seem to be tied to a specific rendering backend.
"
notcory#2048 wrote:
"
Ashaya2#7109 wrote:
Keep tinfoiling I guess.

I would argue all that I snipped is more akin to tinfoil than saying a bug thats existed for years was ported over into the sequel of a game using the same engine, and as such wont be fixed. But I'm also not coping.


Quick search of the bug reports section, I've found 6 threads going back to 2013 discussing an issue even remotely similar to this, 4 of those with 0 replies. And i'm the one coping.

Seriously, Windows acknowledged that this bug is on their end. What more proof could you possibly need? It's not the same crash.
Bump for fix!

Report Forum Post

Report Account:

Report Type

Additional Info