POE 2 Complete PC Freeze while loading screen
Yep. Me too.
|
|
Just tried to swap from DX12 to Vulkan and guess what, the game froze my whole system again.
I'm legit uninstalling the game until further notice. Not going to brick hardware simply to beta test. |
|
bump
|
|
" First of all, I have the same issue and it's widely reported. Second of all, this doesn't cause a bluescreen. Educate yourself. Gaming PC: Win 11, 7600X3D, RTX 4080, 32GB DDR5-6000 CL30, 7000 MB/s SSD, 850W, 3840x2160p 120Hz
Streaming PC: Win 11, i5-12400, RTX 4060, 32GB DDR5-6000 CL36, 7000 MB/s SSD, 450W, 1920x1080p 60Hz |
|
Imagine being able to play.
|
|
WOW, they're still ignoring this thread.
|
|
I also use AMD x3d and freeze frequently at load screen and need to hard reset my PC. Turning off multithreading solves this issue but my fps stays at 10-20fps so I can't play either way. I hope it gets fixed before the holiday.
|
|
Same here, 9800x3d, 4080, win 11 24H2.
It's kinda random, yesterday i was able to play few hours straight whitout freezing my PC, then suddenly got 2 freezes in like ONE hour. I will not try any "fix". GGG should do that rather than ppl. I understand that ppl want some temp fix but it doesnt solve the problem. I hope it will be fixed soon. |
|
I have 3 pc's and luckily 2 of them work... My GF was able to play the first week, but then her pc (pc3) got a update and failed ever since.... Tried to help her with BES 99, 95, 90, 85% no luck, task manager affinity and priority, creating a script to clear cache before game launch. Absolutely no luck, not interested in downgrading os from 23h2 to 24h2 as it clearly works on pc1...
(pc1)5800x3d + 6950xt + 32gb ram+ 24h2 = runs perfectly fine (pc2)3800x + 6750xt + 32gb ram + 23h2 = runs fine, tried 1 crash (not loading screen) (pc3)i5-12400f + 3070 ti + 32gb ram + 24h2 = Runs fine fps wise, crashes after 1-3 map changes and freezes entire system. |
|
" Right, okay... 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). 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. Last edited by StragusPoE#7529 on Dec 21, 2024, 7:38:15 AM
|
|