Hard crashing PC locks up

"

Stormscourge#2254 wrote:

I see two problems with the game, so far as my own system errors were concerned:

1. Bad DirectX 11/12 usage by the game. (Constant DXD3D texture load errors when using DirectX 11 or Direct X 12) - I solved that by changing the API renderer to Vulkan in the game settings. But that's only 1 problem solved.


2. The other problem is the game is not optimized for mainstream systems and is basically brute-forcing your CPU to run with no apparent load self-limiting happening. Regardless of which API you use, the game is acting like a CPU stress test when it loads shaders during zone transitions. During most load scenarios, the game is using 100% clock boost on all my CPU cores. In fact, in some cases, it's using MORE than 100% - or trying to anyway. This will cause instant system instability in ALL but the most highly optimized and cooled PC setups. Your PC will crash if a game like POE2 tries to push your CPU to max workload and there's not enough voltage to do that AND keep Windows running. If TJmaxx (thermal max) doesn't trigger right away, your Power Limits will hit cap instead, causing a log-jam with CPU operations during loads, and if a game like POE2 ignores that and keeps pushes the CPU and RAM anyway, your motherboard UEFI will detect a voltage shortage and shut down your system to prevent damage. Hence the whole system crashes with POE2.

If you launch your windows event viewer and look up the Admin Log at the time your PC crashed, you'll probably see some kind of Kernel Panic error at the time of the crash. That's your system hard-shutting down your PC to protect it from damage.

The only workaround I have for this problem, for MY system on which I have a strong PBO undervolt set, is to run the game on only 7 primary cores and leave the other 9 cores free for Windows systems. This prevents both overheating and instability caused by POE2 hogging all my CPU cycles. I'm reverse-brute-forcing POE2 to only have access to half my CPU. It forces the system to WAIT for loads to finish.

But not all PC setups are made the same. As I said above, I undervolt for the sake of my system health and safety. None of my other games or even benchmarking test are affected by this undervolt. Some people just run on stock settings. Some stock settings are OC'd by mobo's default settings or some sort of "extreme mode" nonsense. Some CPUs can handle this game only shutting off 2 cores because they are running on the factory settings that have higher caps for voltage to let your CPUs hit max boosts without causing instability, and have good enough cooling to prevent hitting thermal thresholds. I need to shut off more cores on my system to get THIS game running stable. Depends on your CPUs "silicon lottery" limits. That why not all the suggestions here will work for everyone's systems.

I've made it to 36 hours game time now without a crash using Vulkan and blocking half my CPU to POE2. - But that's my own personal PC limit testing. This game seems to run fine on only 7 CPU cores for me. If I let it have all 16 cores, or even 14 out of 16 cores, it'll crash before I even get to the login screen.

*Shader caching SHOULD be preventing this CPU overload, especially after you first run the game to compile and store the shaders, but that might be where the causes of these crashes are originating with POE2. That's probably what GGG needs to fix on their end.

"

Fugazor#1825 wrote:

GGG is on vacation do not expect any fix for next 2 weeks.

Workaround is to park 2 cores during loading, this will prevent some crashes and convert 99% of them from hard freeze to crash to desktop.

"

You can use:
1) https://github.com/Kapps/PoEUncrasher easiest option, just run (can also not as admin) and done
2) process lasso (uncheck affinity core 0/1 always)
3) manualy in task manager -> details -> poe exe -> uncheck cpu 0/1 (need to do it every start of game)

Used some forum sparkles here to get attention, sadly OP does not care to update first topic, nor GGG care to sticky workaround.

"

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.

"

Stormscourge#2254 wrote:

I see two problems with the game, so far as my own system errors were concerned:

1. Bad DirectX 11/12 usage by the game. (Constant DXD3D texture load errors when using DirectX 11 or Direct X 12) - I solved that by changing the API renderer to Vulkan in the game settings. But that's only 1 problem solved.


2. The other problem is the game is not optimized for mainstream systems and is basically brute-forcing your CPU to run with no apparent load self-limiting happening. Regardless of which API you use, the game is acting like a CPU stress test when it loads shaders during zone transitions. During most load scenarios, the game is using 100% clock boost on all my CPU cores. In fact, in some cases, it's using MORE than 100% - or trying to anyway. This will cause instant system instability in ALL but the most highly optimized and cooled PC setups. Your PC will crash if a game like POE2 tries to push your CPU to max workload and there's not enough voltage to do that AND keep Windows running. If TJmaxx (thermal max) doesn't trigger right away, your Power Limits will hit cap instead, causing a log-jam with CPU operations during loads, and if a game like POE2 ignores that and keeps pushes the CPU and RAM anyway, your motherboard UEFI will detect a voltage shortage and shut down your system to prevent damage. Hence the whole system crashes with POE2.

If you launch your windows event viewer and look up the Admin Log at the time your PC crashed, you'll probably see some kind of Kernel Panic error at the time of the crash. That's your system hard-shutting down your PC to protect it from damage.

The only workaround I have for this problem, for MY system on which I have a strong PBO undervolt set, is to run the game on only 7 primary cores and leave the other 9 cores free for Windows systems. This prevents both overheating and instability caused by POE2 hogging all my CPU cycles. I'm reverse-brute-forcing POE2 to only have access to half my CPU. It forces the system to WAIT for loads to finish.

But not all PC setups are made the same. As I said above, I undervolt for the sake of my system health and safety. None of my other games or even benchmarking test are affected by this undervolt. Some people just run on stock settings. Some stock settings are OC'd by mobo's default settings or some sort of "extreme mode" nonsense. Some CPUs can handle this game only shutting off 2 cores because they are running on the factory settings that have higher caps for voltage to let your CPUs hit max boosts without causing instability, and have good enough cooling to prevent hitting thermal thresholds. I need to shut off more cores on my system to get THIS game running stable. Depends on your CPUs "silicon lottery" limits. That why not all the suggestions here will work for everyone's systems.

I've made it to 36 hours game time now without a crash using Vulkan and blocking half my CPU to POE2. - But that's my own personal PC limit testing. This game seems to run fine on only 7 CPU cores for me. If I let it have all 16 cores, or even 14 out of 16 cores, it'll crash before I even get to the login screen.

*Shader caching SHOULD be preventing this CPU overload, especially after you first run the game to compile and store the shaders, but that might be where the causes of these crashes are originating with POE2. That's probably what GGG needs to fix on their end.