Hard crashing PC locks up

On the server selection screen, just after turning on the game.
Opened the settings and changed dx12 to vulcan.
At that moment the game froze as sometimes happens when loading. Had to restart the PC.
Another drop in the ocean of my rage.

Hello i would like to inform on a few things that helped me out greatly.
I've got the followings specs:

4060
Ryzen 7 9700X
SSD 7000/7000
32gb ram 5600 mhz
W11 24h2

I was having frequent hard crashes on loading screens like the rest of you, and tried a lot of different things to no avail.

However changing from DX12 to Vulkan has made my crashes go away, i've been zoning a lot to test this. I've also played 14HRs since i changed to Vulkan, and haven't experienced any crashes.

Im still running process lasso in case it were to happen again. I recommend this to anyone who is afraid for their setups.

For process lasso, you can right click poe.exe and set a permanent affinity, like task manager but it remembers as long as you are running the program.
(for those who dont know just uncheck core 0 and 1, will let you terminate the process when it hard crashes, instead of a full operative system crash)

Another solution for process lasso that i recently changed to, was to remove the permanent affinity, and instead right click poe.exe go to cpu limiter and make a rule that says if poe uses 95% of cpu for 0 seconds then uncheck 2 cores for 15 seconds.

Hope this helps someone, i know this won't work for everyone.

"

Hyperboia#7698 wrote:

Switching to core type of hypervisor scheduler solved my problem with PC crashes.
To select a scheduler type:
1. Open a command prompt with administrator privileges
2. Enter bcdedit /set hypervisorschedulertype core
3. Reboot PC

More info there.

It works. Thank you!

"

Hyperboia#7698 wrote:

Switching to core type of hypervisor scheduler solved my problem with PC crashes.
To select a scheduler type:
1. Open a command prompt with administrator privileges
2. Enter bcdedit /set hypervisorschedulertype core
3. Reboot PC

More info there.

What type of system are you on? Do you have SMT enabled and are you on 24h2? It would be wild if this fixed the issue since it would point to memory isolation and Microsoft's use of virtual machines for security as being at least partially responsible for the crash.

I should add that I think GGG is doing something really funky while loading zones since I can run prime95 with large FFTs all day long without a crash and I've yet to experience a similar crash in any other game. Still, MS is obviously playing a part in this issue as well based on the crash being far less prevalent < 24h2 builds and there are even reports that narrow it down to a specific patch in 24h2.

I will also again reiterate the importance of this getting resolved. I have a strong suspicion that this bug could push hardware to the breaking point; this is especially true with how a lot of the AMD overclocks work by setting the PBO scalar to 10x Hopefully someone can test this with voltage probes assuming the headers exist on some boards.

"

norj#5385 wrote:

What type of system are you on? Do you have SMT enabled and are you on 24h2? It would be wild if this fixed the issue since it would point to memory isolation and Microsoft's use of virtual machines for security as being at least partially responsible for the crash.

I should add that I think GGG is doing something really funky while loading zones since I can run prime95 with large FFTs all day long without a crash and I've yet to experience a similar crash in any other game. Still, MS is obviously playing a part in this issue as well based on the crash being far less prevalent < 24h2 builds and there are even reports that narrow it down to a specific patch in 24h2.

I will also again reiterate the importance of this getting resolved. I have a strong suspicion that this bug could push hardware to the breaking point; this is especially true with how a lot of the AMD overclocks work by setting the PBO scalar to 10x Hopefully someone can test this with voltage probes assuming the headers exist on some boards.

r7 3700x, SMT On, PBO Off, W11 24H2. For me crashes started after update to 24H2, so something wrong with root scheduler in this update.

Hello,

Hard crash and freeze for me too at loading map , my config is 11600K , RTX 4070 , 32 giga corsair and poe install in NVME

"

norj#5385 wrote:

"

Hyperboia#7698 wrote:

Switching to core type of hypervisor scheduler solved my problem with PC crashes.
To select a scheduler type:
1. Open a command prompt with administrator privileges
2. Enter bcdedit /set hypervisorschedulertype core
3. Reboot PC

More info there.

What type of system are you on? Do you have SMT enabled and are you on 24h2? It would be wild if this fixed the issue since it would point to memory isolation and Microsoft's use of virtual machines for security as being at least partially responsible for the crash.

I should add that I think GGG is doing something really funky while loading zones since I can run prime95 with large FFTs all day long without a crash and I've yet to experience a similar crash in any other game. Still, MS is obviously playing a part in this issue as well based on the crash being far less prevalent < 24h2 builds and there are even reports that narrow it down to a specific patch in 24h2.

I will also again reiterate the importance of this getting resolved. I have a strong suspicion that this bug could push hardware to the breaking point; this is especially true with how a lot of the AMD overclocks work by setting the PBO scalar to 10x Hopefully someone can test this with voltage probes assuming the headers exist on some boards.

We will never know the exact reason unless GGG comes out and explains it but the main reason this crash happens is that PoE2 is trying to do something Windows does not allow it to do, and during this process PoE2 throws a fit, and this results in the system being choked out of resources it needs to sustain running itself.

The PoEUncrasher actually works by gently and extremely swiftly guiding the "untangling" process when it detects the initial "tantrum" from PoE2. I am not sure if continue playing the game by using PoEUncrasher is 100% safe, it seems like it is, but we can never know fully until we see the long term effects. What I fear, although not really substantiated, is that allowing PoE2 to run in this manner might be shortening CPU's component lifespan.

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

I've tried just about every suggestion on here with mixed results. The PoEUnCrasher worked the best but the game became very laggy/sluggish after it *adjusted* the CPUs a few times due to unresponsiveness.

In the end, I just reverted to Windows 11 23H2 and everything works fine again. No more hard crashes. When I see a real fix from GG, then I'll upgrade Windows back to 24H2.

"

sunocoz#2181 wrote:

I've tried just about every suggestion on here with mixed results. The PoEUnCrasher worked the best but the game became very laggy/sluggish after it *adjusted* the CPUs a few times due to unresponsiveness.

In the end, I just reverted to Windows 11 23H2 and everything works fine again. No more hard crashes. When I see a real fix from GG, then I'll upgrade Windows back to 24H2.

Where are you guys getting 23H2? Windows just installs 24H2 directly for me.

"

Shirofune#6303 wrote:

"

sunocoz#2181 wrote:

I've tried just about every suggestion on here with mixed results. The PoEUnCrasher worked the best but the game became very laggy/sluggish after it *adjusted* the CPUs a few times due to unresponsiveness.

In the end, I just reverted to Windows 11 23H2 and everything works fine again. No more hard crashes. When I see a real fix from GG, then I'll upgrade Windows back to 24H2.

Where are you guys getting 23H2? Windows just installs 24H2 directly for me.

For me, I went to Windows Update and selected "Go Back to previous version".