PoE 2 Crashes entire PC

Fixed? (Added for resolution tracking)

-> Someone on a different post, showed their frame rate at 45 frames or so.
- I noticed mine was capped at 60 even though ingame settings where set to 120. (Slider bar).
- I checked my monitor settings and noticed my gaming monitor was no longer my main display, I changed this and set the advanced settings back to 144hz (I have multiple monitors and recently moved my setup... so my fail there)

However, During "Retesting" I shifted the monitor back to 60hz and no longer the main display. I was able to play the game for a good 5-10 minutes with no issues (Prior it was stuttering and having craziness happen).

So i'm pretty sure GGG did something behind the scenes to fix this.


This is a specific issue as of patch 0.3.0:

I've had stutters and a couple of game crashes before(I assume unrelated), but currently I can't seem to play the game for longer than 5 minutes, it locks up my entire system.

Setup:

Internet: Starlink (I thought this had a factor to play, as previously, network-based stutters have occurred at about the same time frame, however intel laptop works fine one it).

PC: AMD
MoBO: X570 Aorus Master
CPU: AMD 5900X
Ram: 65536MB (64 GB)
GPU: 6800XT (V. 25.8.1)
OS: Windows 11 home (10.0 Build 26100)
PSU: Superflower 2000w Platnium (Added for power reference, as this shouldn't be an issue)

Additional Notes:
* Using Steam, Currently verifying all the files (All files verified, uninstalled, then redownloaded)
* All drivers and software are up to date IAW their respective programs.
* Windows updated
* I do operate in secure boot for compliance with other games.
* I've done vulkan and Dx12
* I did switch registry for Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\0001\UMD (ShaderCache: 32 00) From (31 00)
- Note* I have switched this back, to avoid issues in other games. No noticeable difference

* Crashes seem to be more common when the Options window is open or settings are changed: I.E: I change an option and save, instantly locks up and crashes.
- I can play for about 5 minutes otherwise. (I made it to clearfell in my longest attempt).

* I have checked the logs, it's a big long to enter here but wanted to highlight a couple of warnings:
- 2025/08/29 18:22:24 204656 d7c737f0 [CRIT Client 14120] Unable to load steam stats. Achievements will not work. Error: 2
- 2025/08/29 18:22:23 203671 8fba8a66 [WARN Client 14120] [EShop CallForAction] Failed to load: C:\Users\ryder\OneDrive\Documents\My Games\Path of Exile 2\EShop/calls_for_action_e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855.json does not exist.
- 2025/08/29 18:22:19 199171 64a60fe5 [WARN Client 14120] Failed to create effect graph node (ID: <Steam ID>). Node type does not exist
- 2025/08/29 18:22:19 199171 35d98e37 [WARN Client 14120] Failed to create effect graph node "VertexFlipBookOffset" in graph "Metadata/Effects/Graphs/General/FlipbookOld.fxgraph"

I've been at this for about 4 hours. please let me know if there are any suggestions. I'm currently downloading on my Intel/Nvidia laptop in hopes to bypass this issue in the short term.
Last edited by ryder1337#5598 on Aug 30, 2025, 5:09:15 AM
Last bumped on Aug 31, 2025, 12:12:19 AM
Update:

Game on second computer works perfectly Fine. (Internet doesn't seem to be an issue at all).

All steam files have been verified. However, doing a full re-install as the logs look to be missing a file
Last edited by ryder1337#5598 on Aug 29, 2025, 11:27:06 PM
Please let us know if the reinstall fixes.


"
* I did switch registry for Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\0001\UMD (ShaderCache: 32 00) From (31 00)


Also, first I've heard of this. What's it supposed to do?

ty
Last edited by xStillborn#0949 on Aug 29, 2025, 11:44:51 PM
check your ram model speed frequency and verify if it s rly supported by your motherboard

in bios do you have XMP or same optimsation for ddr amd...ACTIVATED IF Y TRY TO DISABLE IT

goodluck

check your bios if it s last version too


"
Please let us know if the reinstall fixes.


"
* I did switch registry for Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\0001\UMD (ShaderCache: 32 00) From (31 00)


Also, first I've heard of this. What's it supposed to do?

ty


"ShaderCache" value of "32 00" in the Windows Registry is a setting for AMD graphics drivers that forces the shader cache to be "Always On", overriding the default "AMD Optimized" (31 00) or "Off" (30 00) settings. (Per google)
"
Torx34#0712 wrote:
check your ram model speed frequency and verify if it s rly supported by your motherboard

in bios do you have XMP or same optimsation for ddr amd...ACTIVATED IF Y TRY TO DISABLE IT

goodluck

check your bios if it s last version too





Thanks for the advice, XMP was enabled. Disabling made it run smoother for a few minutes, was able to go fight the devourer boss. But during the fight it crashed.

I then looked into turning on SAM (Enabled "Above 4GB decoding" and Re-size BAR Support: in bios first).

Still no luck.

Bios version is: F36b Latest is F39i. I'll keep this post updated.
Edit: Updated Bios to F39i:
- TPM updated and enabled (No success)
- Re-enabled SAM (Per notes above) (No Success).

- I'm still seeing the same "VertexFlipBookOffset error" on my laptop (Which works) so I don't think that is an issue.

- I've checked the event viewer for application errors and noted the following:

* The program PathOfExileSteam.exe version 0.0.0.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.
- Security and Mx noted that it stopped responding and closed, followed by windows was not properly shut down (I had to do a hard shutdown via the power button)(Report was sent.)

I'm pretty unsure what to do at this point.
Last edited by ryder1337#5598 on Aug 30, 2025, 3:40:14 AM
Fixed?

-> Someone on a different post, showed their frame rate at 45 frames or so.
- I noticed mine was capped at 60 even though ingame settings where set to 120. (Slider bar).
- I checked my monitor settings and noticed my gaming monitor was no longer my main display, I changed this and set the advanced settings back to 144hz (I have multiple monitors and recently moved my setup... so my fail there)

However, During "Retesting" I shifted the monitor back to 60hz and no longer the main display. I was able to play the game for a good 5-10 minutes with no issues (Prior it was stuttering and having craziness happen).

So i'm pretty sure GGG did something behind the scenes to fix this.
"

"ShaderCache" value of "32 00" in the Windows Registry is a setting for AMD graphics drivers that forces the shader cache to be "Always On", overriding the default "AMD Optimized" (31 00) or "Off" (30 00) settings. (Per google)


Thanks.

I kept running into answers such as below and threads about keyboards not working w/ win11. Didn't think to try just "ShaderCache" Value (:facepalm:)

"
The provided context does not contain any information about the registry path "Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class{4d36e968-e325-11ce-bfc1-08002be10318}\0001\UMD" or its relation to Poe 2. The context discusses issues related to the keyboard class registry key {4d36e96b-e325-11ce-bfc1-08002be10318}, specifically concerning the UpperFilters value and driver problems like Code 19, but it does not mention the specific path or the term "Poe 2"
[Regression] DX12 & Vulkan Renderers Show "CRITICAL VRAM" Warning on Low Settings After 0.3.0 Update

Description:
Following the update to version 0.3.0, both the DirectX 12 and Vulkan renderers now consistently show a "VRAM: CRITICAL" warning in the performance metrics (F1 menu). This occurs on the exact same graphical settings (all set to Low) that were perfectly stable and performant before this update.
This critical VRAM usage leads to severe micro-stuttering, texture streaming issues, and unstable framerates, making these renderers unplayable. The problem is isolated to DX12 and Vulkan; reverting to the DirectX 11 renderer immediately resolves the VRAM warning and restores game stability, although at a lower overall performance level.


Actual Result:
Despite all settings being at their minimum, both DX12 and Vulkan renderers consume an excessive amount of VRAM, triggering a critical warning. This results in significant performance degradation, including:
Micro-stuttering and freezes.
Visible texture pop-in and low-resolution textures failing to load.
General framerate instability.

Report Forum Post

Report Account:

Report Type

Additional Info