Hard crashing PC locks up

still hard crashed today, needed to full manual reboot.

"

SirBlogzaLot#1061 wrote:

In case it's helpful: I tried switching from DirectX12 to Vulkan and I was actually able to play for quite a while without a problem. I played probably five hours over 3-4 sessions with plenty of trips to town and back and encountered no problems like I had before.

But then I did hard crash, once again just after loading into a town. Maybe switching was just another placebo, but I do wonder if there's something to the delay it took to get there.

I was hopeful I'd averted the problem, but given I haven't, I'm probably going to wait to play again until there's a serious update addressing these crashes. :(

After 269 pages on this topic, I think switching between DX12 or Vulkan has been tested in the first 2 pages.

Have been hard crashing every other hour today. No issue when playing other games like FFXIV, last epoch, d4.

yep still crashing here XD. Was playing fine on a previous character, decided to make a new character, crashed loading into the first area, ended process, reloaded and loaded in with new character and crashed immediately again. Glad I set my core affinities.

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.

Amazingly GGG has no fix for a game that runs terribly and forces freezes of pc. However, the community is finding our own fixes. What works for me now is the Windows Defender exclusion and Poe2uncatcher. Both decribed here in detail. Sad to see GGG sidelined and passive in regard to fixing very serious game issues..

bump -- GGG pls update on your progress

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.

I've uninstalled for now and changed my review to negative, can't be bothered with the incessant crashing anymore. It's just putting me in a bad mood, and I don't want that for xmass. I'll give it another go sometime next year.

GGG is probably off for Christmas, and resolving this may take a while...

So, is there a C/C++ programmer, who is currently experiencing the bug, who would like to waste a day to produce a DLL that gets around the bug?

Given that we know the bug doesn't occur when multithreading is disabled within PoE, then serializing all Vulkan calls will also solve the problem. But this is also way overkill.

The idea would be to create a proxy DLL that catches specific Vulkan calls and only allows one call at a time to go through (though a mutex, or a CRITICAL_SECTION in winapi speak). The bug occurs during loading, so the calls related to uploading/copying/mapping buffers are prime targets.

So vkCreateWin32SurfaceKHR() would get caught, where you grab the function pointers (GetModuleHandleA()/GetProcAddress()) for many Vulkan functions, including vkCreateWin32SurfaceKHR() itself, where the call is then forwarded.

It would be an iterative process to converge on the minimum set of Vulkan functions that must be caught and serialized, to prevent the issue from occurring while providing best performance.

Tedious, it would take about a day, and help a bunch of people. I can help with guidance and/or code but I can't reproduce the problem on any machine here, so I couldn't do much.