Hard crashing PC locks up

Same issue here. Every time I go through a loading screen its 50/50 whether the PC is going to completely lock up or not. Happened like 10 times today. It's nearly unplayable for me right now.

Running a 3080 with a 7800X3D. Latest GPU and chipset drivers, latest Windows 11 build.

Vulkan vs DX12 makes no difference.
The core affinity "fix" does nothing.

Whoever is it fault, Microsoft or GGG, I sure hope it gets fixed quickly because this is ass.

"

rmwrip123#1564 wrote:

Ca. You describe the affinity workaround please?

When you launch game have the task manager open. Go to Details tab and find the poe2.exe. Right click on it and click set affinity. Untick the first two (cpu 0 and cpu 1). Game can still crash but now you can ctrl alt delte out of it and close it in task manager instead game causing your entire computer to freeze and you having to hard rest it with power button.
At least this worked for me when game crashed.

"

smeppe#2506 wrote:

I think we would appreciate it if this was put back up on the known issues post as well. I know not every issue is listed there but this is literally game breaking, in some cases PC breaking.

It's been in there the entire time,

"

Investigating cases where some players experience crashes and have to restart their PCs.

"

Engsodegard#7782 wrote:

Same issue here. Every time I go through a loading screen its 50/50 whether the PC is going to completely lock up or not. Happened like 10 times today. It's nearly unplayable for me right now.

Running a 3080 with a 7800X3D. Latest GPU and chipset drivers, latest Windows 11 build.

Vulkan vs DX12 makes no difference.
The core affinity "fix" does nothing.

Whoever is it fault, Microsoft or GGG, I sure hope it gets fixed quickly because this is ass.

core affinity doesn't let you tab out of the frozen game?

"

smeppe#2506 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!

I think we would appreciate it if this was put back up on the known issues post as well. I know not every issue is listed there but this is literally game breaking, in some cases PC breaking.

It is. It never left. I don't understand why people keep claiming this.

"- Investigating cases where some players experience crashes and have to restart their PCs."

"

aelius28#3912 wrote:

"

smeppe#2506 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!

I think we would appreciate it if this was put back up on the known issues post as well. I know not every issue is listed there but this is literally game breaking, in some cases PC breaking.

It is. It never left. I don't understand why people keep claiming this.

"- Investigating cases where some players experience crashes and have to restart their PCs."

They're probably looking at the PoE bug report forum and not the PoE2 Early Access forums.

"

upintheclouds#1429 wrote:

"

Engsodegard#7782 wrote:

Same issue here. Every time I go through a loading screen its 50/50 whether the PC is going to completely lock up or not. Happened like 10 times today. It's nearly unplayable for me right now.

Running a 3080 with a 7800X3D. Latest GPU and chipset drivers, latest Windows 11 build.

Vulkan vs DX12 makes no difference.
The core affinity "fix" does nothing.

Whoever is it fault, Microsoft or GGG, I sure hope it gets fixed quickly because this is ass.

core affinity doesn't let you tab out of the frozen game?

Nope, still locks up everything.

"

Engsodegard#7782 wrote:

"

upintheclouds#1429 wrote:

"

Engsodegard#7782 wrote:

Same issue here. Every time I go through a loading screen its 50/50 whether the PC is going to completely lock up or not. Happened like 10 times today. It's nearly unplayable for me right now.

Running a 3080 with a 7800X3D. Latest GPU and chipset drivers, latest Windows 11 build.

Vulkan vs DX12 makes no difference.
The core affinity "fix" does nothing.

Whoever is it fault, Microsoft or GGG, I sure hope it gets fixed quickly because this is ass.

core affinity doesn't let you tab out of the frozen game?

Nope, still locks up everything.

Wierd it lets me do it. Tho it only happened once in the last 13 hours of play.

So, I found a sure way to avoid the problem, but it's very convoluted. It's a combination of methods. This is when using Windows 11, should work for Windows 10 but not Linux.

1) Use https://github.com/valleyofdoom/ReservedCpuSets to create a CPUSet. I created one with 12 of my 16 cores on a Ryzen processor.

2) Reboot (unfortunately the cpu set changes only take after a reboot)

3) Now, if you check your core usage, you should have only the non-cpu-set cores being used. In my case, I had no usage on the first 12 cores and all usage was on the last 4 ones.

4) Use Process Lasso or the `cmd` batch file posted on this thread somewhere to set the PathOfExile executable file (.exe) CPU affinity to the same cores as the cpuset. This is important, setting affinities across cpu sets makes everything worse.

Now you hve your game running on the 12 cores, and the OS/rest of the things running on the last 4 cores. There are still some stuff that can jump around the CPUset but I played six hours yesterday without a single lockup or crash.

Unfortunately, when you want to do anything else on the computer you will have to undo the Reserved CPU Sets config again (basically deselect all cores on the ReservedCPUSets program) and reboot.

For reference, I found the CPUSet stuff while looking at this https://www.reddit.com/r/pcmasterrace/comments/17pq1qp/setting_cpu_cores_exclusive_for_games_and_windows/

Edit: added that the information is for Windows. Funnily enough I started looking for CPUSets because I use Linux a lot and that's a function on linux kernels. Turns out windows also implemented a less practical version of it :D
Also, Process Lasso seems to have support for CPU Sets but I haven't tried to see if it works the same or not.

Info for nerds:

"

This (CPU Sets) is an extension of the WindowsIoT CSP Soft Real-Time Performance configuration and assumes you have read the documentation. SetRTCores essentially prevents interrupts and tasks from being scheduled on reserved cores so that you can isolate real-time applications from user and kernel-level disturbances by configuring affinity policies.

"

smeppe#2506 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!

I think we would appreciate it if this was put back up on the known issues post as well. I know not every issue is listed there but this is literally game breaking, in some cases PC breaking.

It's there?