Exception - Can not create thread
Game crashes when changing zones. This happens fairly frequently... Message pops up "Can not create thread." This is the most common message. I've also seen the message "Art/Textures/armour/helmet/uniques/BestiaryHelmet/BestiaryHelmet_gloss.dds":Failed to uncompress texture file" and "Resolving Art/Textures/Interface/Loadingimages/Hideout.dds failed"
https://imgur.com/a/mSFOZ Последняя редакция: xhunt3r#1736. Время: 15 мар. 2018 г., 16:24:57 Last bumped15 мар. 2018 г., 17:56:11
Эта тема была автоматически архивирована. Ответы невозможны.
|
![]() |
Thanks for posting this. I am getting that error message almost every second region change right now.
|
![]() |
That seems likely to be a similar root cause as other reporting, which have DirectX telling PoE E_OUT_OF_MEMORY, or that it couldn't allocate the requested amount of memory. This is not necessarily a PoE problem, simply that PoE is reporting it.
On the basis that your random crash might be similar, a set of things to try: 1. Delete the shader cache directory content in the PoE install directory. [1] 2. In the nvidia control panel, if available, set "debug mode" to disable factory overclocking. 3. If otherwise (any vendor) overclocked, step down at least ten percent, and see if the problem continues. 4. Ditto CPU. 5. Check fans are functioning correctly and clean, and ventilation working as expected in case. 6. Check this isn't a power supply to the hardware issue. 7. Disable and/or remove anything that gets in the rendering path: common candidates are the twitch client, reshade, gemfx, fps displays, "game DVR" style features of windows or vendors. 8. If you use Discord, ensure it is not in a voice or chat session while running the game. If none of that helps you, you can help further debug this by grabbing listdlls, loading PoE, entering a regular zone or map, then running that tool against it. Post the list to pastebin or equivalent, and link it from here. That'll help narrow down what common elements are in the crashes. [1] Be aware, deleting the content of the shader cache has (apparently) resolved similar issues for others, but it should not be necessary, and it will reduce performance as the system needs to recompile each shader the first time it was encountered. Try it once, and once only. Do not do this on a regular basis. |
![]() |
Here is the ListDLLs results.
https://pastebin.com/sW9V753R |
![]() |