POE 2 Complete PC Freeze while loading screen

"
Cainrith#2807 написал:

good-faith software used by a good-faith user having a problem where it uses a System API in a way it should not be used.

Oh really? Is that your concept? There is NO "good-faith software" and "good-faith user" in terms of security and stability. This is the reason why the user mode applications limited in their rights despite being "good" (or "trustful") and the using root or Administrator accounts are very bad practice and not recommended. Every single application is a potential bugfest which may lead to system crash and / or data corruption. We already passed these times with MS DOS, Windows 1/2/3/95/97/98(SE)/ME.

"
Cainrith#2807 написал:

That topic was about detecting hardware damage. You said to people who were concerned about hardware damage to use chkdsk /f.

I corrected you:
1)chkdsk /f does not check for hardware damage.
2)chkdsk /r does check for some of the hardware damage.
3)If one has a SSD and not a HDD (most people in year 2024) then using that SSD's SMART software is better for checking hardware damage.

As I already told - you can't read. I'm not even talking about understanding, but you literally can't use your eyes. I suggested to use chkdsk /f ... read letter by letter... NOT TO FIX PHYSICAL DAMAGE, BUT TO FIX LOGICAL FS ERRORS like your Windows ALREADY does if dirty bit set on. It happens each time the system didn't finish CACHED WRITES and the data was lost, for example in sudden power loss or BSOD. You can fix dirty bit manually using fsutils. Nothing less, nothing more. It has nothing to hardware damage. If you UNSURE that the dirty bit was set properly or your Task Scheduler didn't complete boot-up tasks you can initiate the check manually by using chkdsk /f or autochk by setting the dirty bit on. In 99.99% cases your OS does it AUTOMATICALLY without your interaction, because it is STANDARD PROTOCOL from the Microsoft. If you have actual hardware damage, using chkdsk is bad idea in general, neither /f, nor /r

"
Cainrith#2807 написал:

1)NVIDIA drivers cannot fix the bug on PCs with AMD GPU.
2)The bug NVIDIA refers to is not this problem. The problem they are fixing is another crash. The game is a crash-fest.

1) I know. This is the reason why I DID ask the AMD users to make some research and find information on the ATI / AMD forums. Oh wait, you can't read.
2) NVIDIA Representative (pidge2k) created new thread inherited from the user's one (xploid) with the question about PoE 2 crash, not Ubisoft's issues (m_w_h). I suppose you never used Reddit before.

"
Cainrith#2807 написал:

Why are you so obsessed with Blizzard and not Square Enix?
When Ubisoft encountered a crashing problem like this they kept on communicating despite the fact that the problem was on Windows' side.

I don't give a crap about Blizzard and the other ones, but assumption that GGG paid me or other users (like IT guys above) to "deflect" this shit is complete and utter nonsense and delusional. The only thing that I can agree with you is that GGG should interact with their playerbase and help to fix the issue by interracting with the industry (Microsoft, driver / firmware writers, etc.). I already told why it is happened and I have some information that I cannot post here becuse it will break GGG rules 100%, but I can provide it privately. As nobody PMed me, so people don't care. Sure, babycrying on forums is the "our" way, indeed.

"
mishkan426#4504 написал:
"
cursorTarget#1174 написал:

ou deny the fact that NVIDIA acknowledged the problem and promised to address it in upcomming driver package.

One point, does NVIDIA write drivers for AMD? or I don't understand something

You're understanding correctly. And it is good question. So we have to expect some fix for AMD users from... AMD. Everyone who have access to the ring 0 level are potentially responsible for this issue.
Последняя редакция: cursorTarget#1174. Время: 31 дек. 2024 г., 21:49:39
BUMP
Dear journal,
2032, still full system crash on loading screen.
So, PoEUncrasher (v1.3) active, Win Game Mode off, System/Graphics to Performance in Windows for pathofexilesteam.exe/pathofexile_x64steam.exe and limiting FPS to 100 ingame seems to help.
System/Graphics to Performance setting also fixed NVIDIA APP recognising PoE2 properly. No more PoE2 crashing.
"
Lapinator#3736 написал:
Dear journal,
2032, still full system crash on loading screen.

Ahahaha, still saying its fault of windows 20 hvk version XD...
How long we will have to suffer this + plus forcing to shut down all the time PC i dont think that it is healthy for PC hardware, its almost 3 weeks and nothing, hello there POE2 Team are you doing something 3 weeks ....... nothing
I struggled with that issue too, always had to do a complete shutdown and start pc again. But strangely after i installed a Nvidia hotfix drivers(566.45) it fixed the game for me, meaning no crashes/lockups anymore.
just get it fixed already. ppl quiting just bcs of this stupid problem, how can u have experience over a decade and still make this kind of problem, u cost us time and bad experience because of this stupid freeze
"
cursorTarget#1174 написал:
"
Cainrith#2807 написал:

good-faith software used by a good-faith user having a problem where it uses a System API in a way it should not be used.

Oh really? Is that your concept? There is NO "good-faith software" and "good-faith user" in terms of security and stability. This is the reason why the user mode applications limited in their rights despite being "good" (or "trustful") and the using root or Administrator accounts are very bad practice and not recommended. Every single application is a potential bugfest which may lead to system crash and / or data corruption. We already passed these times with MS DOS, Windows 1/2/3/95/97/98(SE)/ME.

"
Cainrith#2807 написал:

That topic was about detecting hardware damage. You said to people who were concerned about hardware damage to use chkdsk /f.

I corrected you:
1)chkdsk /f does not check for hardware damage.
2)chkdsk /r does check for some of the hardware damage.
3)If one has a SSD and not a HDD (most people in year 2024) then using that SSD's SMART software is better for checking hardware damage.

As I already told - you can't read. I'm not even talking about understanding, but you literally can't use your eyes. I suggested to use chkdsk /f ... read letter by letter... NOT TO FIX PHYSICAL DAMAGE, BUT TO FIX LOGICAL FS ERRORS like your Windows ALREADY does if dirty bit set on. It happens each time the system didn't finish CACHED WRITES and the data was lost, for example in sudden power loss or BSOD. You can fix dirty bit manually using fsutils. Nothing less, nothing more. It has nothing to hardware damage. If you UNSURE that the dirty bit was set properly or your Task Scheduler didn't complete boot-up tasks you can initiate the check manually by using chkdsk /f or autochk by setting the dirty bit on. In 99.99% cases your OS does it AUTOMATICALLY without your interaction, because it is STANDARD PROTOCOL from the Microsoft. If you have actual hardware damage, using chkdsk is bad idea in general, neither /f, nor /r

"
Cainrith#2807 написал:

1)NVIDIA drivers cannot fix the bug on PCs with AMD GPU.
2)The bug NVIDIA refers to is not this problem. The problem they are fixing is another crash. The game is a crash-fest.

1) I know. This is the reason why I DID ask the AMD users to make some research and find information on the ATI / AMD forums. Oh wait, you can't read.
2) NVIDIA Representative (pidge2k) created new thread inherited from the user's one (xploid) with the question about PoE 2 crash, not Ubisoft's issues (m_w_h). I suppose you never used Reddit before.

"
Cainrith#2807 написал:

Why are you so obsessed with Blizzard and not Square Enix?
When Ubisoft encountered a crashing problem like this they kept on communicating despite the fact that the problem was on Windows' side.

I don't give a crap about Blizzard and the other ones, but assumption that GGG paid me or other users (like IT guys above) to "deflect" this shit is complete and utter nonsense and delusional. The only thing that I can agree with you is that GGG should interact with their playerbase and help to fix the issue by interracting with the industry (Microsoft, driver / firmware writers, etc.). I already told why it is happened and I have some information that I cannot post here becuse it will break GGG rules 100%, but I can provide it privately. As nobody PMed me, so people don't care. Sure, babycrying on forums is the "our" way, indeed.

"
mishkan426#4504 написал:
"
cursorTarget#1174 написал:

ou deny the fact that NVIDIA acknowledged the problem and promised to address it in upcomming driver package.

One point, does NVIDIA write drivers for AMD? or I don't understand something

You're understanding correctly. And it is good question. So we have to expect some fix for AMD users from... AMD. Everyone who have access to the ring 0 level are potentially responsible for this issue.


Stop been fanboy GGG have to fix his game plenty users have nvidia and also have the same issues yes they released a new driver and still the issue persist so GGG have to fix his fcking problem and i am a long term player who knows that GGG usually dont give a fck about this issues and never even mention they going to work on this cuz they probably wont but this time isnt a fcking f2p shit they took money as a fcking early acess not as a fkcing alpha or beta a fkcing early access is a playable version of the game and having beteween 10 fps or 140 just because the gods will decide if u will do have it or not today cuz i was playing on max fps stable for days till suddendly ggg decided that my game should run 10 fps on login screen after loading the shaders.
Hello, I apologize in advance for my English ^^

After some research, I’ve managed to fix the issue by 90%. I hope this will help you.

When you launch the game, go to Task Manager → Details → right-click POE2 → Set affinity → and uncheck cores 0 and 1. This will allow you, in case of a crash, to use the Task Manager to close POE2 and avoid restarting your PC.

Next, go to Options → Background FPS and set it to 30, then check the box.

Finally, when you enter, whether it’s through a city portal or launching a map, press the Windows key just before entering the portal so that your processor doesn’t go to 100% capacity, thus preventing a crash.

Пожаловаться на запись форума

Пожаловаться на учетную запись:

Тип жалобы

Дополнительная информация