Hard crashing PC locks up

Playing in Fullscreen instead of Fullscreen Windowed seems to be fixing the crashes for me.

I'm running:
Windows 11 24H2
Ryzen 7 2700x
GTX 1080TI
DX12
Latest everything: drivers, updates, even optional windows updates

"

d3xt3r08#2744 wrote:

Playing in Fullscreen instead of Fullscreen Windowed seems to be fixing the crashes for me.

I'm running:
Windows 11 24H2
Ryzen 7 2700x
GTX 1080TI
DX12
Latest everything: drivers, updates, even optional windows updates

Aaand nvm. It crashed right after I wrote this

"

Kapps#5390 wrote:

For those who are having the issue where your PC hard freezes during loading screens, either this tool or the manual workaround (setting the process affinity of PoE) might help: https://github.com/Kapps/PoEUncrasher/

The windows flag it as a trojan as soon as I donwload it.

Can you please check what is the cause of that?

Ever since the patch, I can only get through about 2 maps before my entire pc blue screens and restarts. Has happened about 15 times.

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 000000000000000c, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffff9f0182ac0180, The PRCB address of the hung processor.
Arg4: 000000000000000a, The index of the hung processor.

Debugging Details:
------------------


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 1109

Key : Analysis.Elapsed.mSec
Value: 1566

Key : Analysis.IO.Other.Mb
Value: 0

Key : Analysis.IO.Read.Mb
Value: 1

Key : Analysis.IO.Write.Mb
Value: 0

Key : Analysis.Init.CPU.mSec
Value: 312

Key : Analysis.Init.Elapsed.mSec
Value: 3702

Key : Analysis.Memory.CommitPeak.Mb
Value: 97

Key : Analysis.Version.DbgEng
Value: 10.0.27725.1000

Key : Analysis.Version.Description
Value: 10.2408.27.01 amd64fre

Key : Analysis.Version.Ext
Value: 1.2408.27.1

Key : Bugcheck.Code.LegacyAPI
Value: 0x101

Key : Bugcheck.Code.TargetModel
Value: 0x101

Key : Failure.Bucket
Value: CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumulateTicks

Key : Failure.Hash
Value: {95498f51-33a9-903b-59e5-d236937d8ecf}

Key : Stack.Pointer
Value: ISR

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Version
Value: 10.0.19041.1


BUGCHECK_CODE: 101

BUGCHECK_P1: c

BUGCHECK_P2: 0

BUGCHECK_P3: ffff9f0182ac0180

BUGCHECK_P4: a

FILE_IN_CAB: 121824-6343-01.dmp

FAULTING_THREAD: ffffaf08f67a6080

FAULTING_PROCESSOR: a

PROCESS_NAME: PathOfExileSteam.exe

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

STACK_TEXT:
ffff9f01`82bf6c88 fffff800`0b241aee : 00000000`00000101 00000000`0000000c 00000000`00000000 ffff9f01`82ac0180 : nt!KeBugCheckEx
ffff9f01`82bf6c90 fffff800`0b06d9cd : 00000000`00000000 ffff9f01`82c40180 00000000`00000246 00000000`0003456a : nt!KeAccumulateTicks+0x1d733e
ffff9f01`82bf6cf0 fffff800`0b065f01 : 00000000`00034569 00000000`0001f323 ffff9f01`82c40180 00000000`00000001 : nt!KiUpdateRunTime+0x5d
ffff9f01`82bf6d40 fffff800`0b067dc3 : ffff9f01`82c40180 00000000`00000000 fffff800`0ba31760 00000000`00000001 : nt!KiUpdateTime+0x4a1
ffff9f01`82bf6e80 fffff800`0b064fd2 : ffff860c`e0d4f3c0 ffff860c`e0d4f440 ffff860c`e0d4f400 00000000`00000000 : nt!KeClockInterruptNotify+0x2e3
ffff9f01`82bf6f30 fffff800`0b0d7e65 : 00000007`cca3fb52 ffffaf08`c9b2bdc0 ffffaf08`c9b2be70 00000000`00000000 : nt!HalpTimerClockInterrupt+0xe2
ffff9f01`82bf6f60 fffff800`0b20092a : ffff860c`e0d4f440 ffffaf08`c9b2bdc0 0000000f`e6bfe770 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffff9f01`82bf6fb0 fffff800`0b201157 : 00000165`710e9e50 ffffaf08`f2396080 ffff860c`e0d4f440 ffffaf09`00e7c8e0 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffff860c`e0d4f3c0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37


SYMBOL_NAME: nt!KeAccumulateTicks+1d733e

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.5247

STACK_COMMAND: .process /r /p 0xffffaf08f379e080; .thread 0xffffaf08f67a6080 ; kb

BUCKET_ID_FUNC_OFFSET: 1d733e

FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumulateTicks

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {95498f51-33a9-903b-59e5-d236937d8ecf}

7800x3d + 3090 + WIN11 24H2

Ever since the patch still Freezing, crashing my pc on loading screen when changing map

"

Ali_S#0148 wrote:

"

Kapps#5390 wrote:

For those who are having the issue where your PC hard freezes during loading screens, either this tool or the manual workaround (setting the process affinity of PoE) might help: https://github.com/Kapps/PoEUncrasher/

The windows flag it as a trojan as soon as I donwload it.

Can you please check what is the cause of that?

The source code is public and is safe. You don't need to worry. 100% False Alert.

Probably it's SmartScreen saying that the program isn't signed. It doesn't mean it's flagging it as a trojan, it means it's a program Windows doesn't know about (which makes sense since it's made by some random guy).

Ever since the patch loading into certain zones (Hunting Grounds atm) freezes my entire PC and forces me to hard reset.

I tried running the "PackCheck.exe" which didn't help. Here are the results,


Playing on a 7800x3d, 4070TI, Windows 11.

This game is GGG...

That was me trying to say Good but my computer froze and crashed.

"

Erionn#6306 wrote:

"

lunshea#1054 wrote:

...and the radio silence on this matter, can you smell the arrogance? I assume GGG has stepped into the role of a true AAA game company now, along with Ubisoft, EA and so on...didn't take long. :)

Comments like this are baffling, honestly grow up. It's listed as a high priority issue in the stickied known issues thread, and if they don't have a fix yet what do you want them to do? You want Them wasting their time here saying they're still working on it, when it is still listed as a known issue?

The stickied post has not been updated since Dec7. That's more than TEN days ago. I work in the dev field and I handle several servers for clients, this level of silence is not acceptable for any tech business. It may be just a game, but it's still a business and people are spending money on it not just for EA but also on MTX. You are the one that needs to grow up and grow out of the "this is just a game" mindset. This is a business entity, period.