PoE Client Crashing straight to Desktop: No Error Message

Path of Exile would just randomly crash upon loading a new instance or while clearing an instance.

It would completely quite and close down. All I could find was this bit in log files. Some of the log doesn't show the out of memory error while some do.

"
2019/09/06 16:49:19 ***** LOG FILE OPENING *****
2019/09/06 16:49:21 185870265 18d [INFO Client 1188] Changing to device "2 - Digital Display Audio (AMD High Definition Audio Device)"
2019/09/06 17:02:55 186684500 89 [INFO Client 1188] Tile hash: 3812000742
2019/09/06 17:02:55 186684500 8a [INFO Client 1188] Doodad hash: 0
2019/09/06 17:30:22 ***** LOG FILE OPENING *****
2019/09/06 17:45:51 189260843 89 [INFO Client 8880] Tile hash: 85271688
2019/09/06 17:45:51 189260843 8a [INFO Client 8880] Doodad hash: 3536561602
2019/09/06 17:46:38 189307062 89 [INFO Client 8880] Tile hash: 2418708214
2019/09/06 17:46:38 189307062 8a [INFO Client 8880] Doodad hash: 4190490534
2019/09/06 17:48:50 189439609 89 [INFO Client 8880] Tile hash: 85271688
2019/09/06 17:48:50 189439609 8a [INFO Client 8880] Doodad hash: 3536561602
2019/09/06 19:08:59 194248718 89 [INFO Client 8880] Tile hash: 3965872426
2019/09/06 19:08:59 194248718 8a [INFO Client 8880] Doodad hash: 147206869
2019/09/06 19:14:51 194600796 a6 [CRIT Client 8880] [D3D11] CreateShaderResourceViewEx
2019/09/06 19:14:51 194600796 a6 [CRIT Client 8880] [D3D11] CreateShaderResourceViewEx
2019/09/06 19:14:51 194600812 a6 [CRIT Client 8880] [D3D11] CreateShaderResourceViewEx
2019/09/06 19:14:51 194600812 a6 [CRIT Client 8880] [D3D11] CreateShaderResourceViewEx
2019/09/06 19:14:51 194600828 a6 [CRIT Client 8880] [D3D11] CreateShaderResourceViewEx
2019/09/06 19:14:51 194600843 a6 [CRIT Client 8880] [D3D11] CreateShaderResourceViewEx
2019/09/06 19:14:51 194600843 a6 [CRIT Client 8880] [D3D11] CreateShaderResourceViewEx
2019/09/06 19:14:51 194600843 a6 [CRIT Client 8880] [D3D11] CreateShaderResourceViewEx
2019/09/06 19:14:51 194600843 a6 [CRIT Client 8880] [D3D11] CreateShaderResourceViewEx
2019/09/06 19:14:51 194600859 4b [CRIT Client 8880] Failed to allocate 349680 bytes (with alignment 16)
2019/09/06 19:14:51 194600859 ab [CRIT Client 8880] Out-of-memory
2019/09/06 19:15:10 ***** LOG FILE OPENING *****


The thing is I have 16 GB of RAM so PoE shouldn't be running out of memory.

It happened like 5 time or so today after Blight launch. It even happened right smack in middle of the long queue right after launch.

After it happens it goes straight to desktop.

My setup is Windows 10, Ryzen 1700X, 16 GB of ram, AMD Vega 64 GPU, and SSD for PoE install.

Edit: Forget to mention that I am using Steam version of PoE but I can switch to stand alone if need to.
Last edited by Vyndicu#2221 on Sep 6, 2019, 8:35:56 PM
Last bumped on Sep 10, 2019, 7:57:44 PM
This thread has been automatically archived. Replies are disabled.
Are you playing with the 32 or 64 bit version of POE, cause Steam uses (as I've read) per default the 32 bit version of POE (and so the used memory is limited to 4 GB)?

But you could use "-gc 2" as Launch options.

Edit: Look in Version 2.4.2.:
"
If you're using Steam, right click on Path of Exile in your library and click "Play 64-bit DX11 Version".


I also get crashes to desktop while loading in a new area (log file with "Out-of-memory" entry), and I'm using the 32 bit standalone client (on a Win7 32-bit OS, so I can't switch to 64 bit POE client version).
And I've seen in the Task Manager that the used memory has grown to ~2.5 GB, before this update to 3.8 it was max. 2 GB (I use "-gc 2 --noasync" as command line parameters). Isn't the garbage collector (gc) working correctly (or are there internally too many pinned objects in memory)?
Last edited by Th69#3281 on Sep 7, 2019, 5:12:57 AM
As far I can tell that right click on steam library info is outdate as it doesn't give you any option beside launch option. I don't think it crashed from the 4 GB limit as there were other application having graph issue at the same time. Primarily youtube running in chrome.

This issue went away on it's own as soon I updated video driver and reboot. So I am not sure where the issue came from.

Report Forum Post

Report Account:

Report Type

Additional Info