Hard crashing PC locks up

"

FrankieFusion#7976 wrote:

So - update as to my situation at least into what's been going on.

Well, after one user in here posted Shroud's twitch clip, I tried doing what he said to do between changing zones or instances;

Turning off multithreading in the options and turning it back on every single time.

Ironically, this has worked for me. I went all weekend after my last post without a single crash whatsoever.

I don't know if this helps others moving forward, but at least it's something that I've seen that works well. IE - It's the only option i've attempted thus far out of the 50 different ones that legitimately worked for me.

I have been doing that for a while and it works.
The problem is when I forget to turn it off entering a map and then boom xD

Also I'm disabling cores 0 and 1 for PoE so at least when I forget the multithread thing the PC doesn`t crash and just have to force close PoE...

we can bet how many sites that thread can count

"

Seba2007#3315 wrote:

I said the same thing for the past 30 pages no AMD gpu users. It’s all 30, 40 series gpus. I am here on this thread from the beginning no AMD gpu users.

This post is spreading misinformation. It happens to every kind of PC build: AMD, Nvidia, Intel, Windows 10, Windows 11 does not matter.

From the thread:

"

Juulis#7698 wrote:

Also getting full PC freezes and have to hard reset PC. 4 times now.

Ryzen 5 5600
RX 6700XT

"

RaikoNya#0876 wrote:

Boss fight vs Balbala.
Poison phase and flat black screen and nothing. Hard reboot pc then try again and same result.
Specs:
Intel Core i5-12400F
Gigabyte B760 Gaming X DDR4
MSI AMD Radeon RX 7600 (8176 МБ)
Win 10 22H2

"

Emrad#6679 wrote:

I thought the servers were overloaded, but I'm stuck with the same issues people report here.

After reaching Act 2 and killing the first boss there, teleporting to the Clearfell Encampment crashes the game entirely every single time.

I suspect the issue started since Windows updated to 24H2.

System:

RX 7900 XTX
7800X3D
32 GB RAM

"

dailymilkman#4683 wrote:

Using a gaming laptop, used to run poe 1 just fine with vulkan. poe 2 keeps bricking my laptop to the point it crashes (blackscreens) the entire device, requiring a restart.

G14 zephyrus 2022
AMD Ryzen 7-6800HS
AMD RX 6700S
16 GB RAM
playing on SSD
windows 23H2

Crashes mainly happen in startup (after the gears loading), if it doesnt, the game runs poorly (50-60fps) with all low settings, vulkan, FSR performance. Have tried almost every combination of ingame settings, drivers are up to date, and tried limiting cpu core affinity to no avail. Im not sure if my specs are just too outdated or if the game is unoptimized to my specific setup. Any help is appreciated. Thanks.

"

ShuffleInc#0544 wrote:

Same issue, X3D CPU, but using Win10 22H2.

My system spec:
* Windows 10 22H2 (build 19045.5131)
* AMD Ryzen 7 5800X3D
* 32GB DDR4 RAM
* AMD RX 7900XTX
* AMD Adrenalin drivers 24.12.1 (latest version; released 05.12.2024.)
* Steam version of the game.

Usually the game starts to hang. If i quickly pres Ctrl+Alt+Del it then blue screens and restarts.
It usually freezes every 20-30 mins.

We just should up this post but stop homemade solutions.

We need GGG / Windows, updates solution’s

Keeping this post up and first may make GGG reacting or something I guess.

I still have hope.

"

Imperius_Fate#0368 wrote:

This issue is a CPU-sided issue where it locks your PC mainly because POE2 messes up with your CPU utilisation. Many of the games I play can stress my CPU well enough to 100% most of the times, but POE2 is a special case when it comes to loading screens freezing my entire PC.

Well, most people think the programs have direct access to the hardware and the entire system is something simple and straight forward. Short answer - no, you're wrong. They problem is WAY more serious than you think.

"

Timothy_GGG wrote:

Hi everyone, whilst we have already been investigating this issue already, it would be massively helpful if you could provide your dxdiag output by doing the following on windows:

run > dxdiag > save all information

and sending me that file or it's contents in a private message.

Thanks!

Don't forget that GGG has already someone looking into it!

"

Cainrith#2807 wrote:

This is a strong assertion that is not necessarily substantiated by the evidence provided. If the freeze were caused by user-mode threads, this would indeed indicate a flaw in the OS's privilege isolation and resource management. This should not be possible unless there is a vulnerability that permits such abuse (e.g., a privilege escalation exploit).

Instead, a more likely scenario is that the OS is not letting abuse happen. If so, an excessive or invalid request from user mode may cause the kernel to malfunction as it tries to enforce control.

It's just my assumption, sure.

OS shoudn't let abuse kernel API anyway even if it's not made on purpose but because of mistake / design flaw. We have good example - CrowdStrike driver caused BSOD because one of the function received inadequate parameters (the data structure changed its format) WITHOUT THE CHECKS. So from the user perspective it doesn't matter is it vulnerability at the kernel level or design flaw or anything else - user applications MUST NOT crash the entire system or lead to sort of spinlocks / halt (cli + hlt combo passed through stack overflow).

Even if poe crashes at shader compilation, the OS should start exception handling routine (utilizing user defined handler, specific runtime handler or default OS handler) and close the application, clearing and freeing all allocated resources, collecting all garbage, closing handles, etc.

"

cursorTarget#1174 wrote:

"

Cainrith#2807 wrote:

This is a strong assertion that is not necessarily substantiated by the evidence provided. If the freeze were caused by user-mode threads, this would indeed indicate a flaw in the OS's privilege isolation and resource management. This should not be possible unless there is a vulnerability that permits such abuse (e.g., a privilege escalation exploit).

Instead, a more likely scenario is that the OS is not letting abuse happen. If so, an excessive or invalid request from user mode may cause the kernel to malfunction as it tries to enforce control.

It's just my assumption, sure.

OS shoudn't let abuse kernel API anyway even if it's not made on purpose but because of mistake / design flaw. We have good example - CrowdStrike driver caused BSOD because one of the function received inadequate parameters (the data structure changed its format) WITHOUT THE CHECKS. So from the user perspective it doesn't matter is it vulnerability at the kernel level or design flaw or anything else - user applications MUST NOT crash the entire system or lead to sort of spinlocks / halt (cli + hlt combo passed through stack overflow).

I agree. If it were up to me I would add a functionality to Windows that blacklisted any application that tries to overplay its hand. Blacklisted and made them public: "This app tried this, and it was built by these people".

In this case I blame PoE2 because they knew what they were working with. When a building collapses due to an earthquake I do not blame the ground, I blame the construction company, because they knew what they were building on where.

I can confirm now that it also happens on dx11. Played for a few hours yesterday somewhat fine (it gets very jittery after a few area loads, but you can restart the game). Struggles to get 60fps smoothly (dx12 it would be 144fps without dlss).

Today after a few hours at the very start of act3 (first area after encampment) and it hard froze the pc.

OS: Windows 11 Home + the infamous 24H2
CPU: Ryzen 7600x
GPU: 4060 ti 8gb
RAM: 16GB (system page file 32gb, yes insanity) 5600mhz/6000mhz
MOBO: PRO B650M-A WIFI (MS-7D77)
Drive: Nvme (not using expansion card)

I used to think the ram was bad and didn't support the overclock set by the ram profile itself, moved it down to 5600. No difference, poe2 is the only game i've played on this system that hardlocks like this.

Original problem is this game hard locks on dx12 and vulkan for me. Even using BES cpu limiter, that just allows me to play longer before it locks up. I believe the lockup always happens when its loading an area.

"

RosivDamotil#0039 wrote:

"

Timothy_GGG wrote:

Hi everyone, whilst we have already been investigating this issue already, it would be massively helpful if you could provide your dxdiag output by doing the following on windows:

run > dxdiag > save all information

and sending me that file or it's contents in a private message.

Thanks!

Don't forget that GGG has already someone looking into it!

They did not check those DxDiags. People reported that they did not access the files they've put on the net.

If you did not reach level 25/Act 1 etc. you cannot DM. For example I cannot DM. I can only send a support mail. They asked for DMs to exclude people who were new to this game in order to bias their selection.

I honestly suspect that they already knew about this issue but hoped that it would blow off and did not expect this much attention on it.