POE 2 Complete PC Freeze while loading screen

"

drx#8804 wrote:

"

gvieira#7895 wrote:

"

drx#8804 wrote:

best hope is to wait till someone use this freezes/crashes to somehow dupe items.. and make it public info. Only this way for fix to come, same day or next..

That makes no sense. It's a client crash, not a server crash.

I expected one to catch the irony, it was a joke. Just to point the fact that they are just fixing duping/exploits and OP builds rn, not giving any attention to this crash issues at all. That's why i wished there was a exploit linked to this issue, cause maybe they would give more attention then. People are using third paty apps to make the game run, for almost a month by now.. Not even a single word from them since 10/12. I don't wanna be mean i sweear, just want to play the game.

"

interbeing#5112 wrote:

Example console output while transitioning through zones and loading screens.

Hibernation mode on (C:\hiberfil.sys exists).

"

07:13:23 fail: Program[0] Detected loading screen, but could not find any process to park.
07:13:24 info: Program[0] Parked cores: 111111111100
07:13:38 warn: Program[0] PoE Process not Responding: Attempting to recover process by setting it to realtime. Note that you need to be running this program as an Administrator for this to work.
07:13:46 fail: Program[0] PoE quit while we set it realtime; resetting loading and realtime status.
07:14:17 fail: Program[0] Detected loading screen, but could not find any process to park.
07:14:17 info: Program[0] Parked cores: 111111111100
07:14:31 warn: Program[0] PoE Process not Responding: Attempting to recover process by setting it to realtime. Note that you need to be running this program as an Administrator for this to work.
07:14:39 fail: Program[0] PoE quit while we set it realtime; resetting loading and realtime status.
...

Hibernation mode off (C:\hiberfil.sys does not exist).

"

07:52:14 info: Program[0] Parked cores: 111111111100
07:52:34 info: Program[0] Parked cores: 111111111100
07:52:50 info: Program[0] Unparked cores: 111111111111
07:53:01 info: Program[0] Parked cores: 111111111100
07:53:12 info: Program[0] Unparked cores: 111111111111
07:53:19 info: Program[0] Parked cores: 111111111100
07:53:22 info: Program[0] Unparked cores: 111111111111
07:53:31 info: Program[0] Parked cores: 111111111100
07:53:35 info: Program[0] Unparked cores: 111111111111
07:53:41 info: Program[0] Parked cores: 111111111100
07:53:42 info: Program[0] Unparked cores: 111111111111
07:53:50 info: Program[0] Parked cores: 111111111100
07:53:58 info: Program[0] Unparked cores: 111111111111
07:54:12 info: Program[0] Parked cores: 111111111100

"

lauralex#6031 wrote:

Lots of misinformation in this thread.

People experiencing crashes should check the Windows Event Viewer or use AppCrashView to provide details of the crash (e.g., exception code, fault offset, module name, etc.).

Crashes are mainly caused by a segmentation fault (due to bad/non-sanitized pointer dereference) and probably due to a bad implementation of thread synchronization routines.

"

dirtybeatfreak#7612 wrote:

"

lauralex#6031 wrote:

Lots of misinformation in this thread.

People experiencing crashes should check the Windows Event Viewer or use AppCrashView to provide details of the crash (e.g., exception code, fault offset, module name, etc.).

Crashes are mainly caused by a segmentation fault (due to bad/non-sanitized pointer dereference) and probably due to a bad implementation of thread synchronization routines.

somebody hasn't read much of the thread at all...

"

lauralex#6031 wrote:

"

dirtybeatfreak#7612 wrote:

"

lauralex#6031 wrote:

Lots of misinformation in this thread.

People experiencing crashes should check the Windows Event Viewer or use AppCrashView to provide details of the crash (e.g., exception code, fault offset, module name, etc.).

Crashes are mainly caused by a segmentation fault (due to bad/non-sanitized pointer dereference) and probably due to a bad implementation of thread synchronization routines.

somebody hasn't read much of the thread at all...

Did you debug the game? 😐

Because I did and I know where the problem is, so please, refrain from posting bs and stop spreading misinformation.

Also, it doesn't affect 24h2 only. I have 23h2.

"

interbeing#5112 wrote:

Awesome! Please let us know when you have fixed it. I tire of these workarounds.