BUG Frequent 20-30 Game Freeze + map reset (multiple players affected).
|
still hapening a lot (every map where its suddenly highly packed and lots of things happen)
should not be an issue on my mid decent pc (graphics are low) 9800x3d, 870a chips, 32ddr5, nvme gen5, 3060ti. ddu'd driver, new install. cashe to 100gigz tryed everything till now found. " Last edited by raxcyn#5267 on Oct 4, 2025, 4:51:46 AM
|
|
|
+1
|
|
|
This issue dissapeared at 0.3.1 for me.
|
|
|
5 times in one houer ....
FFS raxcyn#5267 check logs or tell me i'm stupid and need new hardware, i dont care ! just wanna be able to play this game !! |
|
|
In my case, I have stopped finding this issue. I've managed to test it out on the following driver versions:
- 576.88 - 581.29 - 581.42 - ASUS Notebook Drivers (561.00 based) Since 0.3.1 I've not encountered the loading logo of death. I do clean reinstall every time (the last cycle with DDU between versions to boot) and, while I feel the Vulkan performance was a tad bit more consistent than DX12, I've managed to run both API's without major issues. Between each driver reinstall I do the full shader cache clear, and delete the minimap folder just for completeness' sake. I do still believe the DX12 engine render path is absurdly bad in optimization and performance - there is a constant shader hit that's really taxing. Related to downgrading drivers again, this seems to only happen in the PoE engine, Diablo 4 and other games don't: - Suffer any weird engine crash issues - Suffer any performance penalties in DX12/Vulkan I've also started annoying Nvidia directly with this issue, but being a single post in their driver forum, it get's passed over - will share the URL's so more people will complain and they'll acknowledge the issue and move the needle (If only to tell GGG to get their game up in engine coding for DX12): 581.47 driver thread - https://www.nvidia.com/en-us/geforce/forums/game-ready-drivers/13/575700/announcing-geforce-hotfix-driver-58147-released-93/3568058/ 581.42 driver thread - https://www.nvidia.com/en-us/geforce/forums/game-ready-drivers/13/575454/geforce-grd-58142-feedback-thread-released-93025/3568051/ |
|
|
Exactly same thing here. Today I lost more XP than I gained... Unplayable.
GGG, Thanks for all your efforts, but this should be top of the list be now... |
|
|
Nvidia started acknowledging - go in and drop your settings and findings
https://www.nvidia.com/en-us/geforce/forums/game-ready-drivers/13/576272/geforce-grd-58157-feedback-thread-released-101425/3570149/ |
|
|
Guys stop posting your gfx logs, it's the same on consoles..
|
|
|
Same here random dc-s random error messages
|
|
|
Hi -
What you are experiencing is the following: - POE2 is not crashing. The NVidia driver you are using has crashed. (black screen) - POE2 detects the NVidia driver crash. - POE2 builds a new game instance. (spinning gears) - The game returns to you and you keep playing. Loss of map exploration: If you have ever closed/exited POE2 while in a zone/map, then restarted POE2 in the map/zone, you will experience the same loss of map exploration. It's part of getting a new game instance. GGG's Jonathan describes the research, conclusion, and fix in the video linked below. Jonathan says the solution is to use a NVidia driver around 560 - I tried 560.81 and have gone for frequent crashes to zero, none, nada for two weeks straight. Link below. Links: GGG discusses the NVIDIA driver crash here: youtube.com/watch?t=6487&v=LtHF35GOZhw&feature=youtu.be 560.81 drivers https://www.guru3d.com/download/geforce-56081-whql-driver-download/ DDU https://www.wagnardsoft.com/display-driver-uninstaller-ddu DDU *completely* removes the current driver and its parts, which doesn't happen with NVidia's "clean installation" option. I boot in Windows Safe Mode and run DDU. You probably should also delete POE2 shader cache subdirectories as well - but I'm not sure if that's mandatory or not. I did. |
|
