The problem is getting bigger - game crashes without error message

Mostly crashes for me on maps, like Mesa, Cold River, Fields and so on.
As of today its started to crash on Forest Encampment, cant enter. Happens even in Standard.

Great to not being able to enter game anymore....

AMD system
crashes in many zones, even in login menu without error message.
and cant run harbinger deli maps at all.

Operating System: Windows 10 Home 64-bit (10.0, Build 19045) (19041.vb_release.191206-1406)
Motherboard: ASUS TUF GAMING B760-PLUS WIFI
Processor: 13th Gen Intel(R) Core(TM) i9-13900KF (24 CPUs), ~3.0GHz
GPU: NVIDIA GeForce RTX 4090
Display Memory: 40432 MB
Dedicated Memory: 24142 MB
Shared Memory: 16290 MB
Current Mode: 3840 x 2160 (32 bit) (120Hz)

Ram: Kingston FURY Beast RGB DDR5 4800MHz 32GB


Tried: Update Bios, Start in stand alone client, Changed to older Nvidia drivers. changed performance core ratio on CPU from 55>54>53>52 no luck.

I'm running out of idea. also tried to have on 2 different hard drives.
Last edited by Grimstone on Aug 11, 2024, 8:50:23 AM
I have a lot of crashes and i need to restart whole computer cuz my screen goes black. Crashesh are random but can't do single map...
Ścieżka aplikacji powodującej błąd: C:\WINDOWS\system32\dwm.exe
Ścieżka modułu powodującego błąd: C:\WINDOWS\system32\dwmcore.dll

Nazwa aplikacji powodującej błąd: dwm.exe, wersja: 10.0.22621.3672, sygnatura czasowa: 0x85e98d33
Nazwa modułu powodującego błąd: dwmcore.dll, wersja: 10.0.22621.3810, sygnatura czasowa: 0x5ddf757a
Kod wyjątku: 0x8898008d
Przesunięcie błędu: 0x000000000011f611
Identyfikator procesu powodującego błąd: 0x0x4F04
Godzina uruchomienia aplikacji powodującej błąd: 0x0x1DAEBEAC967F277
Ścieżka aplikacji powodującej błąd: C:\WINDOWS\system32\dwm.exe
Ścieżka modułu powodującego błąd: C:\WINDOWS\system32\dwmcore.dll
Identyfikator raportu: 084344cc-622b-4e9e-ab68-ebac4667c9fa
Pełna nazwa pakietu powodującego błąd:
Identyfikator aplikacji względem pakietu powodującego błąd:
Crashing at the log in screen is ridiculous. Come on GGG, yall can definitely nail this one down before the season is over. PLEASE>
7800x3D and 4080, random crashes all the time to the point I can't get into my hideout. All suggestions are NOT helping. This is not 13-14 gen Intel issue, this is something else, so dont spam the tread with your retarded replies about the gen 13 and 14. It is obviously GGG issue because of the different type of hardware reported in multiple treads.
Hello, I'm here again,
I've checked everything thoroughly again and have the system/drivers/bios etc. up to date. Unfortunately, it doesn't help.

I think we'll have to wait for optimization from Intel or GGG.

I'll try a few more options and let you know if anything helps!

Until then, good loot!
Unfortunately, the cashes are now taking over. I can make a map if I manage to get into the game - then zone into my hideout and it crashes. I've tried DX11 / DX 12 / Vulcan. Compatibility mode in all variants. Lots of possible combinations of graphics settings. Rendering with upscaling programs and the error is always the same. It doesn't matter which area I zone into, the game often crashes on the loading screen. But often it also crashes when I open an interface like the inventory, skill tree, etc. After that I can hardly start the game properly. It usually crashes immediately in the intro or when logging in. After 3-5 attempts I'm usually back online for a short time until the next crash. But currently I have the feeling that it's getting worse and worse. Sometimes I've just lost the desire to play.

Since the last BIOS update, POE sometimes even displayed error messages like:

[TEXTURE] Invalid header version: 162

or

"Art/Models/NPC/TreasureHunter/rig.ast": Failed to uncompress animation 6

This uncompress error always occurs with different NPC names or animation numbers. But this error messages occurs very rarely anyway.

Just for your information, I have an ASUS Prime z790-p motherboard with an Intel i9-13900KF and an RTX4090. I've probably ruled out the RAM and hard drives as the cause.

Windows 11 is still high on my list of causes.
But I would hate to have to reinstall my system again...

On the other hand, many people with Win10 also have the problem. Some even have AMD. Often with fairly new hardware, though. I'm not deep enough into the subject to understand the background and dig deeper :(
Last edited by Xako1993 on Aug 12, 2024, 3:49:04 PM
I've never crashed before, and I've crashed 4 times today. The commonality in all of the logs is related to a pet audio trigger, but I'm not using a pet on this character. I am using other MTX though.

Update: In my case, I narrowed this down to the Pummeller Kaom Unique Finisher Effect. Once I removed the MTX, I was able to play for 3 hours without a single crash. My advice to anyone reading this is to try removing MTX systematically to see if that's what is causing the crash. A similar set of crashes happened to me last league with one of the currency pets, so I should've known better.

MTX:
- Voidborn Helmet
- Voidborn Body Armour
- Exile's Pilfering Ring
- Awakener's Ring Effect
- Heartcrusher Rare Finisher Effect
- Pummeler Kaom Unique Finisher Effect
- Luminary Charges
- Rogue Stalker Gloves
- Nethermancer Boots
- Nethermancer Cloak
- Nexus Utility Flask
- Searing Quicksilver Flask
- Stygian Frost Blades
- Illusionist Whirling Blades
- Primal Assassin's Mark
- Webbed Tendrils Footprints Effect

PC Specs:
- Windows 11 Pro 22631.3880
- Motherboard ASUS PRIME Z690-A
- Processor 13th Gen Intel(R) Core(TM) i7-13700K 3.40 GHz
- RAM 32.0 GB
- Storage Samsung 980 Pro 1TB
- System type 64-bit operating system, x64-based processor
- Video NVIDIA GeForce RTX 4090
- Steam Client

Output in the .dmp.txt files:

Area
KalguuranSettlersLeague
Seed
1457627862
Build
release tags/3.25.0d 247516
OSBits
64

Area
2_11_endgame_town
Seed
1
Build
release tags/3.25.0d 247516
OSBits
64


Area
KalguuranSettlersLeague
Seed
1457627862
Build
release tags/3.25.0d 247516
OSBits
64

Area
KalguuranSettlersLeague
Seed
2417590909
Build
release tags/3.25.0d 247516
OSBits
64


Snippets of the logs just before the crashes:

2024/08/09 14:11:44 353972109 19dc40 [DEBUG Client 7176] [InGameAudioManager] TalkingPetAudioEvent 'LevelUp' triggered
2024/08/09 14:11:44 353972328 cff94598 [INFO Client 7176] : You have entered Bog.
2024/08/09 14:11:45 353972906 d5c98b06 [INFO Client 7176] [SHADER] Delay: ON
2024/08/09 14:12:12 ***** LOG FILE OPENING *****

2024/08/12 10:49:31 601044921 19dc40 [DEBUG Client 27832] [InGameAudioManager] TalkingPetAudioEvent 'LevelUp' triggered
2024/08/12 10:49:31 601045093 cff94598 [INFO Client 27832] : You have entered Kingsmarch.
2024/08/12 10:49:32 601045859 d5c98b06 [INFO Client 27832] [SHADER] Delay: ON
2024/08/12 10:49:34 601048406 cff94598 [INFO Client 27832] Tujen, the Harbourmaster: You should check out what came in from Riben Fell.
2024/08/12 10:49:56 601070031 cff94598 [INFO Client 27832] Rog, the Disenchanter: Could really use more items to disenchant. At the moment, we're idle.
2024/08/12 10:50:06 601079906 cff94598 [INFO Client 27832] Rog, the Disenchanter: Not bad, not bad.
2024/08/12 10:50:10 601084125 cff94598 [INFO Client 27832] Rog, the Disenchanter: Not bad, not bad.
2024/08/12 10:50:22 601096562 cff94598 [INFO Client 27832] Rog, the Disenchanter: Let's make some dust.
2024/08/12 10:50:27 601100828 cff94598 [INFO Client 27832] Rog, the Disenchanter: Hoh hoh, Let's make some dust.
2024/08/12 10:51:01 601134921 19dc40 [DEBUG Client 27832] [InGameAudioManager] TalkingPetAudioEvent 'Bored' triggered
2024/08/12 10:51:13 ***** LOG FILE OPENING *****

2024/08/12 13:30:24 610697937 19dc40 [DEBUG Client 29836] [InGameAudioManager] TalkingPetAudioEvent 'LevelUp' triggered
2024/08/12 13:30:24 610698093 cff94598 [INFO Client 29836] : You have entered Kingsmarch.
2024/08/12 13:30:25 610698906 d5c98b06 [INFO Client 29836] [SHADER] Delay: ON
2024/08/12 13:30:27 610701265 cff94598 [INFO Client 29836] Tujen, the Harbourmaster: Oh good, more work.
2024/08/12 13:31:00 ***** LOG FILE OPENING *****

2024/08/12 13:49:13 611827203 19dc40 [DEBUG Client 25452] [InGameAudioManager] TalkingPetAudioEvent 'LevelUp' triggered
2024/08/12 13:49:13 611827343 cff94598 [INFO Client 25452] : You have entered Kingsmarch.
2024/08/12 13:49:14 611827921 d5c98b06 [INFO Client 25452] [SHADER] Delay: ON
2024/08/12 13:49:16 611829843 cff94598 [INFO Client 25452] Rog, the Disenchanter: We're always open.
2024/08/12 13:50:27 ***** LOG FILE OPENING *****

2024/08/12 13:50:50 611924187 19dc40 [DEBUG Client 13400] [InGameAudioManager] TalkingPetAudioEvent 'LevelUp' triggered
2024/08/12 13:50:52 611925875 19dc40 [DEBUG Client 13400] [InGameAudioManager] TalkingPetAudioEvent 'LevelUp' triggered
2024/08/12 13:51:38 611972671 19dc40 [DEBUG Client 13400] [InGameAudioManager] TalkingPetAudioEvent 'Idle3MinuteCooldown' triggered
2024/08/12 13:51:38 611972671 19dc40 [DEBUG Client 13400] [InGameAudioManager] TalkingPetAudioEvent 'Idle1MinuteCooldown' triggered
2024/08/12 13:52:08 612001734 19dc40 [DEBUG Client 13400] [InGameAudioManager] TalkingPetAudioEvent 'Bored' triggered
2024/08/12 13:52:38 612032671 19dc40 [DEBUG Client 13400] [InGameAudioManager] TalkingPetAudioEvent 'Idle3MinuteCooldown' triggered
2024/08/12 13:52:38 612032671 19dc40 [DEBUG Client 13400] [InGameAudioManager] TalkingPetAudioEvent 'Idle1MinuteCooldown' triggered

Hope this helps!
Last edited by DallasNChains on Aug 12, 2024, 7:09:21 PM
"
DallasNChains wrote:
I've never crashed before, and I've crashed 4 times today. The commonality in all of the logs is related to a pet audio trigger, but I'm not using a pet on this character. I am using other MTX though.

1 - Try taking off all MTX
2 - Completely shut down and exit Steam
3 - Test Standalone Client no Steam running AT ALL
4 - Disable all overlays
5 - Possible Nvidia rollback to driver 552.22 <<< NOT NEWER DRIVERS!

Rule out all of that before it's associated with the Intel 13th/14th gen issues.
Last edited by ps7ekken on Aug 12, 2024, 4:26:21 PM
I've had the crashes as explained earlier; I -DO- have an Intel gen 14 CPU.
I have taken this to the shop and had the BIOS flashed with the Intel recommended fix.

Will this work?
I'm not sure, but I will post back later with information about what happened.
Newevil

Report Forum Post

Report Account:

Report Type

Additional Info