POE 2 Complete PC Freeze while loading screen

"

AwwYiss1#2063 wrote:

So here's the problem.

Every single one of your solutions that everyone posts are Anecdotal, none of them solve any of the issues and they're at best, shoddy workarounds. (my personal favorite are people suggesting things detrimental to the health of their PC saying it worked for them, or "lowered the amount of crashes i'm getting!")

While i love that everyone wants to play this game so bad, None of the fixes is a blanket fix, and there's still no true root cause to what is making this happen.

We're over 250 pages on one thread, and another 218 on this thread with zero responses out side of a cursory message in the known issues thread that there's a problem with misleading information about the windows 11 24h2 update.

There's nothing proving that any of the things here have fixed a wide swath of people, outside of intentionally degrading performance of the client by core parking, turning off multithreading, reinstalling windows and hoping, and even then it's not fixing the problem, it's putting a shitty bandaid on it.

This isn't just limited to AMD systems, it's Intel as well, and it's multi-generational hardware, not the newest AM5 chipset, not just a 4000 series Nvidia card, nothing that is linking all of these cases together aside from the PoE2 client having a serious issue programmatically taking 100% of the available CPU and choking everything out, typically what SEEMS to be due to how shaders are loaded or generated.

My issue here is the lack of communication or results of almost a week of testing, dxdiag logs from users who have PM'd them to GGG.

The people replying here are the ones that are frustrated enough to post, which means by volume this is probably a significantly larger issue happening to more people.

I don't care that it's Early Access. Early access here should be to fix these glaring issues in your code first, via QA and bug fixing and then balance changes afterward. GGG has a large subset of people who have spent hundreds of dollars on the game, or bought a supporter pack because they believe in this company and the game, and we're getting very little return on investment.

I've been able to play in spats here and there, but loading into some zones i just hard crash, in others, (looking at you, Trials) i just crash to desktop. I accept the crash to desktop, that is gonna happen, i expect it to happen in early access.

However, I do not expect a crash that is repeatable by potentially thousands of users that is HARD LOCKING a machine to the point of a hard reboot to take weeks to rectify or communicate about, and it's getting frustrating seeing these threads grow in size with no communication about the problem, but a lot of fixes for balance, when you have a ton of users who CANNOT PLAY YOUR GAME.

"

Prypiat54#5023 wrote:

Seriously , how it's possible ?

I encouraged 3 other friends to play it, and I should have kept quiet. Out of 4 people, only 1 can actually launch the game, while the others are all experiencing crashes, including me, with a crash right at launch. We all have different PC configurations.

4070S - r5 5600x - win11

"

AwwYiss1#2063 wrote:

So here's the problem.

Every single one of your solutions that everyone posts are Anecdotal, none of them solve any of the issues and they're at best, shoddy workarounds. (my personal favorite are people suggesting things detrimental to the health of their PC saying it worked for them, or "lowered the amount of crashes i'm getting!")

While i love that everyone wants to play this game so bad, None of the fixes is a blanket fix, and there's still no true root cause to what is making this happen.

We're over 250 pages on one thread, and another 218 on this thread with zero responses out side of a cursory message in the known issues thread that there's a problem with misleading information about the windows 11 24h2 update.

There's nothing proving that any of the things here have fixed a wide swath of people, outside of intentionally degrading performance of the client by core parking, turning off multithreading, reinstalling windows and hoping, and even then it's not fixing the problem, it's putting a shitty bandaid on it.

This isn't just limited to AMD systems, it's Intel as well, and it's multi-generational hardware, not the newest AM5 chipset, not just a 4000 series Nvidia card, nothing that is linking all of these cases together aside from the PoE2 client having a serious issue programmatically taking 100% of the available CPU and choking everything out, typically what SEEMS to be due to how shaders are loaded or generated.

My issue here is the lack of communication or results of almost a week of testing, dxdiag logs from users who have PM'd them to GGG.

The people replying here are the ones that are frustrated enough to post, which means by volume this is probably a significantly larger issue happening to more people.

I don't care that it's Early Access. Early access here should be to fix these glaring issues in your code first, via QA and bug fixing and then balance changes afterward. GGG has a large subset of people who have spent hundreds of dollars on the game, or bought a supporter pack because they believe in this company and the game, and we're getting very little return on investment.

I've been able to play in spats here and there, but loading into some zones i just hard crash, in others, (looking at you, Trials) i just crash to desktop. I accept the crash to desktop, that is gonna happen, i expect it to happen in early access.

However, I do not expect a crash that is repeatable by potentially thousands of users that is HARD LOCKING a machine to the point of a hard reboot to take weeks to rectify or communicate about, and it's getting frustrating seeing these threads grow in size with no communication about the problem, but a lot of fixes for balance, when you have a ton of users who CANNOT PLAY YOUR GAME.

"

AndreWtheTOI#2909 wrote:

Solved it!
PoE2 shows in NVidia app as PoE1.
Make it properly show PoE2 there and the issues are solved.

Here's some suggested ways to make it show correctly in the NVidia app:
1. Try reinstalling the NVidia app
2. Start the game from the NVidia app

Or

1. Uninstall POE2 and if you have it POE1 as well.
2. Important... delete both POE1 and 2 folders from your Documents/ My Games folder.
3. Do a search on your drive(s) for anything "Path of Exile", highlight all results and delete the files and folders then do the same search for "Grinding Gears" just in case there's any remnants that may be there. Then, empty your recycle bin!
4. Clean your shader cache... empty that sucker.
5. Rerun a scan in Nvidia App and make certain Path of exile is gone from your installed games.
6. Restart windows.
7. Do a fresh install of POE2 only (don't install POE1)

"

ErosEngineer#6213 wrote:

"

AwwYiss1#2063 wrote:

So here's the problem.

Every single one of your solutions that everyone posts are Anecdotal, none of them solve any of the issues and they're at best, shoddy workarounds. (my personal favorite are people suggesting things detrimental to the health of their PC saying it worked for them, or "lowered the amount of crashes i'm getting!")

While i love that everyone wants to play this game so bad, None of the fixes is a blanket fix, and there's still no true root cause to what is making this happen.

We're over 250 pages on one thread, and another 218 on this thread with zero responses out side of a cursory message in the known issues thread that there's a problem with misleading information about the windows 11 24h2 update.

There's nothing proving that any of the things here have fixed a wide swath of people, outside of intentionally degrading performance of the client by core parking, turning off multithreading, reinstalling windows and hoping, and even then it's not fixing the problem, it's putting a shitty bandaid on it.

This isn't just limited to AMD systems, it's Intel as well, and it's multi-generational hardware, not the newest AM5 chipset, not just a 4000 series Nvidia card, nothing that is linking all of these cases together aside from the PoE2 client having a serious issue programmatically taking 100% of the available CPU and choking everything out, typically what SEEMS to be due to how shaders are loaded or generated.

My issue here is the lack of communication or results of almost a week of testing, dxdiag logs from users who have PM'd them to GGG.

The people replying here are the ones that are frustrated enough to post, which means by volume this is probably a significantly larger issue happening to more people.

I don't care that it's Early Access. Early access here should be to fix these glaring issues in your code first, via QA and bug fixing and then balance changes afterward. GGG has a large subset of people who have spent hundreds of dollars on the game, or bought a supporter pack because they believe in this company and the game, and we're getting very little return on investment.

I've been able to play in spats here and there, but loading into some zones i just hard crash, in others, (looking at you, Trials) i just crash to desktop. I accept the crash to desktop, that is gonna happen, i expect it to happen in early access.

However, I do not expect a crash that is repeatable by potentially thousands of users that is HARD LOCKING a machine to the point of a hard reboot to take weeks to rectify or communicate about, and it's getting frustrating seeing these threads grow in size with no communication about the problem, but a lot of fixes for balance, when you have a ton of users who CANNOT PLAY YOUR GAME.

GGG is starting their month long holiday today so there will be no fix until mid January at least I reckon.

"

m33ts4k0z#0771 wrote:

"

AwwYiss1#2063 wrote:

...
long nonesense ranting
...

Sorry bro but deactivating multithreading does indeed completely solve the crashes.