Constant Crash to Desktop

Here's my thought

Somewhere DX and Multithreading are failing.

Seems to be a thing for i13k and other newer multicores

___

Vulkan is more GPU dependent than DX

If I load in any DX with multithreading enabled, I crash.

I can successfully load and run in vulkan with multithreading turned off.
Juice get rubberbandy but its playable

Updated my Nvidia GPU drivers (1060 6GB) and running without crashing for now. Give it a try ppl.

"

Updated my Nvidia GPU drivers (1060 6GB) and running without crashing for now. Give it a try ppl.

Nope. Still crashing to desktop. Happens most frequently in the forest...not sure why.

Last update i hope. - so I turned off some cosmetic that said it did an effect when I use an orb of transmutation or something. So far I've done 6 maps full packed and have not errored. I'm still getting a ton of jarring/lag but not crashing.

This just started the other day with failed to decrypt PID, buffer overflow and this Failed to create effect graph node "EvolvingNoise21" in graph "Metadata/Effects/Graphs/GpuParticles/Update/Noises/CurlNoise_Wind.fxgraph"

I did a verify files through steam, not sure what else to do. I crash when running just about anything.


Ive attempted a complete uninstall/reinstall and still getting the same issues, cannot play at all because of the issue.


Update:

Removed game from steam, full installed from website, noticed it was still pretty choppy/bad. Changed network mode to Predictive and I can at least play so far without getting the errors or force close to desktop.

2nd update:

Was able to play for 1 hour then started getting errors again.

3rd update:

Still unable to go into any maps
2024/02/13 21:48:46 3834000 88a90509 [DEBUG Client 5960] Got Instance Details from login server
2024/02/13 21:48:46 3834062 b7403414 [INFO Client 5960] [DOWNLOAD] Pre-downloading "Content/Data/WorldAreas/MapWorldsStagnation"
2024/02/13 21:48:46 3834062 b7403414 [INFO Client 5960] [DOWNLOAD] Pre-downloading "Streaming/Content/Data/WorldAreas/MapWorldsStagnation"
2024/02/13 21:48:46 3834062 327596b2 [INFO Client 5960] [SHADER] Delay: OFF
2024/02/13 21:48:46 3834062 ca3a69d2 [INFO Client 5960] Connecting to instance server at 203.15.120.27:6112
2024/02/13 21:48:46 3834109 ca3a5095 [DEBUG Client 5960] Connect time to instance server was 31ms
2024/02/13 21:48:46 3834140 1186a081 [DEBUG Client 5960] Generating level 83 area "MapWorldsStagnation" with seed 1964104716
2024/02/13 21:48:49 3837531 f22b6987 [INFO Client 5960] Tile hash: 311214969
2024/02/13 21:48:49 3837531 f22b6986 [INFO Client 5960] Doodad hash: 264912068

Absurd that there isn't any support communication here.

DX12 has given me the most stability, only giving me a crash when either in abyss/deli/big juice.

I tried to switch to DX11 & Vulkan for testing, but now it is constant crashing no matter which settings I try out.

Even going back to DX12 I'm still getting constant crashes. The same exact settings which I've had the least crashes with previously is now giving me CONSTANT crashes, just because I switched the renderer from DX12 to DX11 back to DX12.

edit: just reinstalled the game and deleted the shader caches. same exact problem occurs. never had this problem until this league. it was a fun league while it lasted, i cannot play the game like this

Been playing for the last week or so with no issue.
Got this error a few times yesterday, along with the crash to desktop.

"

2024/03/03 02:34:30 1540949062 bb7a4b87 [WARN Client 22056] Failed to create effect graph node (ID: 3488310295). Node type does not exist
2024/03/03 02:34:30 1540949062 bb7a4b65 [WARN Client 22056] Failed to create effect graph node "EvolvingNoise21". Node type does not exist
2024/03/03 02:34:30 1540949062 f5c7da64 [WARN Client 22056] Failed to create effect graph node "EvolvingNoise21" in graph "Metadata/Effects/Graphs/GpuParticles/Update/Noises/CurlNoise_Wind.fxgraph"

Went to do a quick map before bed and can't even log in now. 5-6 times i got to town, then crashed going to hideout, now I cant even load in to town.

Haven't changed anything.
Not exactly a good experience after been away from PoE a few months...

anyone with newer intel processors might want to take a look here:

https://www.reddit.com/r/intel/comments/1awpon0/is_your_intel_core_i913900k_crashing_in_games/



the smaller link in that post to tom's hardware explaining what could be going on:

https://www.tomshardware.com/pc-components/cpus/is-your-intel-core-i9-13900k-crashing-in-games-your-motherboard-bios-settings-may-be-to-blame-other-high-end-intel-cpus-also-affected

"

ps7ekken wrote:

anyone with newer intel processors might want to take a look here:

https://www.reddit.com/r/intel/comments/1awpon0/is_your_intel_core_i913900k_crashing_in_games/



the smaller link in that post to tom's hardware explaining what could be going on:

https://www.tomshardware.com/pc-components/cpus/is-your-intel-core-i9-13900k-crashing-in-games-your-motherboard-bios-settings-may-be-to-blame-other-high-end-intel-cpus-also-affected

I appreciate the sentiment, however, looking over the previous posts/threads since league launch, its clearly not something we can 'fix'. There is about 50 different 'part/sometimes/less crashy solutions' posted, with varying components to 'blame', clarifying that it is in-fact nothing to do with any of it.

We've had this happen plenty of times over the years, and it usually resolves it 'self one random day, by magic, apparently. Whilst GGG remain silent.

It's not the newer intel chips, as plenty of players without them have the problem, its not Nvidia drivers, as plenty don't use Nvidia, etc... The only common trend is Path of Exile.

It's fairly evident there is some error in the league/patch build, that they can't/wont find, that's it.

"

Chalace2 wrote:

"

ps7ekken wrote:

anyone with newer intel processors might want to take a look here:

https://www.reddit.com/r/intel/comments/1awpon0/is_your_intel_core_i913900k_crashing_in_games/



the smaller link in that post to tom's hardware explaining what could be going on:

https://www.tomshardware.com/pc-components/cpus/is-your-intel-core-i9-13900k-crashing-in-games-your-motherboard-bios-settings-may-be-to-blame-other-high-end-intel-cpus-also-affected

I appreciate the sentiment, however, looking over the previous posts/threads since league launch, its clearly not something we can 'fix'. There is about 50 different 'part/sometimes/less crashy solutions' posted, with varying components to 'blame', clarifying that it is in-fact nothing to do with any of it.

We've had this happen plenty of times over the years, and it usually resolves it 'self one random day, by magic, apparently. Whilst GGG remain silent.

It's not the newer intel chips, as plenty of players without them have the problem, its not Nvidia drivers, as plenty don't use Nvidia, etc... The only common trend is Path of Exile.

It's fairly evident there is some error in the league/patch build, that they can't/wont find, that's it.

I appreciate your "sentiment" as well, but I seem to have missed the part in this thread where you posted your PC's specs and said you were running a 12th, 13th, or 14th gen Intel processor and were "crashing to desktop" (thread topic) along with others posting here.


In fact, Intel themselves was quoted admitting there is in fact a problem with newer chips/board combos and power limits in not just those I linked but in many other posts within the last 2 weeks that could easily be found by a Google search.


If you took the time to read any of them you'd realize it's related to motherboards allowing the power limits to essentially self or auto overclock under certain conditions and power spiking the chip.


So, if anyone is running a 12th, 13th, or 14th gen chip the Intel information I linked above could actually pertain to their issues.


Now, I'm not telling or suggesting everyone to jump into their bios settings or download over-clocking software and start tinkering around. There are quite a few free software options out there that will show in real time the power draws of the CPU and other components to give them some insight as to what may be happening.


Maybe the information will help some people here since I've seen quite a lot of newer Intel specs posted recently.

"

If you took the time to read any of them you'd realize it's related to motherboards allowing the power limits to essentially self or auto overclock under certain conditions and power spiking the chip.

You missed the point entirely. (People providing 50 different solutions that don't/can't actually fix the issue)

I have no need to read any of that, so why would I waste my time on it? Intel might be having issues, but that is not the cause, nor the solution to this specific issue that's been going on for 3+ months.

Evident by the fact there are people running 10 year old systems, brand new systems, Intel, AMD, NVIDIA, and everything in between, all getting the same errors.

Again, logic would suggest its a build issue, as that is the only common factor.