Hard crashing PC locks up

"

Horcsch#7198 wrote:

Open Nvidia Control Panel Open 3D Settings
Go to App specific settings, choose POE (64 and the other)
At the bottom of the list change the Vulkan/OpenGL thing to DXGI Swapchain
In game, change DX12 to Vulkan

Crashes are gone. No need to mess with SMT or Process Lasso

Thanks. No crushes since yesterday. That has fixed the issue for me.

Rtx 3060 12gb
Ryzen 5 3600
32gb ram
Nvme ssd

Disabling XMP/DOCP (setting it to Auto) in the BIOS has fixed it for me so far.

"

nikoleagle#5373 wrote:

"

Horcsch#7198 wrote:

Open Nvidia Control Panel Open 3D Settings
Go to App specific settings, choose POE (64 and the other)
At the bottom of the list change the Vulkan/OpenGL thing to DXGI Swapchain
In game, change DX12 to Vulkan

Crashes are gone. No need to mess with SMT or Process Lasso

Thanks. No crushes since yesterday. That has fixed the issue for me.

Rtx 3060 12gb
Ryzen 5 3600
32gb ram
Nvme ssd

I'm testing this now. So far, so good.

Please also send a bug report here:
https://www.pathofexile.com/forum/view-thread/3609262

3070 rtx+5900x ryzen
windows 10

Crashes hard on character screen loading.
Like pc goes and make a sound BRRRRR
then hard reset and reboots on its own.

Yesterday i could play a couple times, at launch i had no problems at all.

Btw i use the steam version of poe2

latest nvidia drivers too.

"

Lieu24#4026 wrote:

3070 rtx+5900x ryzen
windows 10

Crashes hard on character screen loading.
Like pc goes and make a sound BRRRRR
then hard reset and reboots on its own.

Yesterday i could play a couple times, at launch i had no problems at all.

Btw i use the steam version of poe2

latest nvidia drivers too.

Can you please send your dxdiag? Or atleast the portion(s) that starts with "Problem signature:
P1: PathOfExileSteam.exe"

"

Shirofune#6303 wrote:

What are you trying to get at?

That all the people posting in this thread have faulty hardware?

Sorry for the late reply. My point is that the roots of the problem are MUCH deeper than it seems to the average player unfamiliar with the basic system architecture. Unfortunately.

The delay for the actual fix caused not because GGG wants to see suffering players and not letting them to play but the actual complexity of the issue affecting underlying systems like OS kernel, driver architecture, probably UEFI and who knows, it must be something else.

But this is not about "DAT GAYM OVALOADS MY CEEPEEYU". High CPU load is only contributing factor in the chain of events happening under the hoot. There is nothing wrong in 100% CPU load if you have properly working hardware and software.

As Pyroga#2822 told earlier, there is probability that we have more than one vulnerability and / or design flaw in the chain of consequences leading us to what we get.

And it is not only about PoE 2. Did you check the links I posted above? Did you know PoE 1 also had the same issue years ago?

"

Seriously theres something so wrong with poe2 and AMD X3D processors.

It affects other CPUs and shader compilation process. I bet that shit existed in the design for years and never was fixed.

"

PanKamienica#5657 wrote:

"

nikoleagle#5373 wrote:

"

Horcsch#7198 wrote:

Open Nvidia Control Panel Open 3D Settings
Go to App specific settings, choose POE (64 and the other)
At the bottom of the list change the Vulkan/OpenGL thing to DXGI Swapchain
In game, change DX12 to Vulkan

Crashes are gone. No need to mess with SMT or Process Lasso

Thanks. No crushes since yesterday. That has fixed the issue for me.

Rtx 3060 12gb
Ryzen 5 3600
32gb ram
Nvme ssd

I'm testing this now. So far, so good.

nope... doesn't work... :(

The ONLY solution that works for me so far is using BES and limiting path of exile cpu usage by -1%, nothing else worked.

"

THELEGENDOFREAK#0494 wrote:

The ONLY solution that works for me so far is using BES and limiting path of exile cpu usage by -1%, nothing else worked.

How many days have you gone without a freeze? Because using BES was the first thing I tried and it went okay for like 7h, then it freezed on a loading screen. Tried increasing the %, same result... some hours of it working, then freeze.