Hard crashing PC locks up

Nulled.

Welp, after 2 weeks of trying every possible fix with nothing working I found my 'solution'.

Turned out I had 3 corrupted files in my Steam install. After verifying and re-installing the files, my game worked again. Before that I had a crash on loading Hunting Grounds/Act 1 on every try.

Weird stuff.

Started to hard crash even with POeUncrasher

Given how long this issue has existed and how little acknowledgement the matter has received from the devs its pretty clear to me that this inst a priority to GGG. Their lack of communication regarding this makes it explicitly clear that they have plenty of players for whom the game is working fine and they don't care to invest any time/resources for a subset of players they don't need. I think this issue will not be fixed anytime soon, if ever, and this entire thread is being outright ignored. Big shame bc the game seems amazing but I'd rather not play at all than mess up my pc with the constant crashing.

"

damaGecs#1789 wrote:

Started to hard crash even with POeUncrasher

Ditto over the past 2 days. PoEUncrasher was working GREAT. Probably time for a break anyway

Really wished they took the player base serious when they paid and cant play because of constant crashing. They are just looking the other way completely. Watched that whole patch reveal for a quick answer of its not their problem, its nvidias fault, maybe we can download a monitoring system so they can watch us crash? They claim it takes an hour to replicate a crash, not from what alot of us are experiencing.

"

KissFC#2626 wrote:

After getting tired of my personnal computer getting freeze with a 100% CPU usage, i got the great idea of putting and trying to see what happens on my ES debug station, which have an out of band CPU thread and memroy analyzer (namelly a debug and software profiling station).

The way they're handling multi threading is threatened by modern standard, upgraded UEFI and well secured OSes as a core threat, thus stopping the suspicious threads marked as threat. Similar to how speculative/transient execution CPU vulnerabilities works.
But as the main program isn't flagged as a threat and is considered secure, the OS do not stop it from generating new threads, and the whole process works like a fork bomb.

At this point, i strongly suggest GGG to make a full review of their networking code and to enable fork bombing detection on their compiler because it is something that should never happens.

This post deserves it's own thread that needs to be bumped daily until it's acknowledged

I don't understand why this problem is still not resolved.. I stopped playing because of that.

"

KissFC#2626 wrote:

After getting tired of my personnal computer getting freeze with a 100% CPU usage, i got the great idea of putting and trying to see what happens on my ES debug station, which have an out of band CPU thread and memroy analyzer (namelly a debug and software profiling station).

The way they're handling multi threading is threatened by modern standard, upgraded UEFI and well secured OSes as a core threat, thus stopping the suspicious threads marked as threat. Similar to how speculative/transient execution CPU vulnerabilities works.
But as the main program isn't flagged as a threat and is considered secure, the OS do not stop it from generating new threads, and the whole process works like a fork bomb.

At this point, i strongly suggest GGG to make a full review of their networking code and to enable fork bombing detection on their compiler because it is something that should never happens.

Check this, we cannot normally play

I was able to resolve this issue by doing the following:

1. Uninstalled all Armory Crate/ASUS software (specific to my MB)

2. Updated BIOS to latest ver

3. Joined "beta (stable)" tier of Windows Insider Program and ran all available updates (including optional updates).

4. Set custom settings for POE2 in Nvidia Control Panel:
a.) Image Scaling: On
b.) Anisotropic filtering: App-controlled
c.) Antialiasing - FXAA: On
d.) Antialiasing - Gamma correction: On
e.) Antialiasing - Mode: App-controlled
f.) Antialiasing - Transparency: 8x (supersample)
g.) Background Application Max Frame Rate: Off
h.) CUDA - GPUs: Use these GPUs: GeForce GTX 2080 Ti (All)
i.) CUDA - Sysmem Fallback Policy: Prefer to Sysmem Fallback
j.) Low Latency Mode: Ultra
k.) Max Frame Rate: 144 FPS (to match my monitor refresh rate)
l.) Monitor Technology: G-SYNC
m.) Multi-Frame Sampled AA (MFAA): On
n.) OpenGL GDI compatibility: Auto
o.) OpenGL rendering GPU: NVIDIA GeForce RTX 2080 Ti
p.) Power management mode: Prefer maximum performance
q.) Preferred refresh rate (Dell S2716DG): Highest available
r.) Texture filtering - Anisotropic sample optimization: Off
s.) Texture filtering - Negative LOD bias: Allow
t.) Texture filtering - Quality: Quality
u.) Texture filtering - Trilinear optimization: On
v.) Threaded optimization: On
w.) Triple buffering: On
x.) Vertical sync: Off

5. In-game settings:
a.) Renderer: DirectX12
b.) Display: NVIDIA GeForce RTX 2080 Ti
c.) Mode: Windowed Fullscreen
d.) VSync: Off
e.) Dynamic Resolution: On
f.) Window Resolution: 2560 x 1440 (Native)
g.) Upscale Mode: NVIDIA DLSS
h.) Max Image Quality: Quality
i.) Sharpness: 15%
j.) HDR: Off (not supported)
k.) Texture Quality: High (Default)
l.) Texture Filtering: 8x Anisotropic Filtering
m.) Lighting: Shadows + Global Illumination
n.) Shadow + GI Quality: Low (Default)
o.) Sun Shadow Quality: High (Default)
p.) Number of Lights: High (Default)
q.) Water Detail Level: High (Default)
r.) NVIDIA Reflex: On + Boost
s.) Foreground FPS Cap: 144 (matches monitor refresh rate)
t.) Background FPS Cap: 30
u.) Triple-Buffering: On
v.) Target Framerate: 60
w.) Engine Multithreading: On

This obviously strictly applies to NVIDIA cards, but some of this may still be useful regardless. Hope this helps!