Constant, random crashes

Myself and my girlfriend are getting random CTDs during gameplay on similar hardware and software configurations. They always occur outside of town, but cannot be reliably replicated. Crashes occur while playing alone and together.

- Tried disabling multithreading. Caused extremely volatile framerate, did not play with this setting.
- Tried all three networking types.
- Tried using no loot filter.
- Tried without screen sharing via Discord.

In-game settings:
- Graphics settings maxed
- DX11
- Variable framerate disabled
- Multithreading: enabled
- Sound channels: high

Background processes:
- Discord w/ voice chat and/or screen sharing active
- RivaTuner Statistics Server w/ 60 FPS limit enforced
- MSI Afterburner

CPU is modestly overclocked (6700K @ 4.5 GHz). RAM is overclocked to 3200 MHz. No GPU overclock.

DxDiag
Spoiler
---------------
Diagnostics
---------------

Windows Error Reporting:
+++ WER0 +++:
Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: PathOfExile_x64Steam.exe
P2: 0.0.0.0
P3: 5aa07446
P4: StackHash_111d
P5: 10.0.16299.248
P6: effc9126
P7: c0000374
P8: PCH_D0_FROM_ntdll+0x00000000000A09D4
P9:
P10:


+++ WER1 +++:
Fault bucket 1174597841391878439, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: PathOfExile_x64Steam.exe
P2: 0.0.0.0
P3: 5aa07446
P4: PathOfExile_x64Steam.exe
P5: 0.0.0.0
P6: 5aa07446
P7: c0000005
P8: 0000000000126d93
P9:
P10:


+++ WER2 +++:
Fault bucket 129570975297, type 5
Event Name: RADAR_PRE_LEAK_64
Response: Not available
Cab Id: 0

Problem signature:
P1: PathOfExile_x64Steam.exe
P2: 0.0.0.0
P3: 10.0.16299.2.0.0
P4:
P5:
P6:
P7:
P8:
P9:
P10:


+++ WER3 +++:
Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: PathOfExile_x64Steam.exe
P2: 0.0.0.0
P3: 5a9cce3d
P4: PathOfExile_x64Steam.exe
P5: 0.0.0.0
P6: 5a9cce3d
P7: c0000005
P8: 0000000000126cca
P9:
P10:


+++ WER4 +++:
Fault bucket 1940738774653535136, type 5
Event Name: RADAR_PRE_LEAK_64
Response: Not available
Cab Id: 0

Problem signature:
P1: Wow-64.exe
P2: 7.3.5.26124
P3: 10.0.16299.2.0.0
P4:
P5:
P6:
P7:
P8:
P9:
P10:


+++ WER5 +++:
No Data
+++ WER6 +++:
No Data
+++ WER7 +++:
No Data
+++ WER8 +++:
No Data
+++ WER9 +++:
No Data


Win10 event viewer log
Spoiler
Faulting application name: PathOfExile_x64Steam.exe, version: 0.0.0.0, time stamp: 0x5aa07446
Faulting module name: ntdll.dll, version: 10.0.16299.248, time stamp: 0xeffc9126
Exception code: 0xc0000374
Fault offset: 0x00000000000f87bb
Faulting process id: 0x2f84
Faulting application start time: 0x01d3b6ed82d7c6a0
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\Path of Exile\PathOfExile_x64Steam.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 55d374e4-af56-4570-82df-a672650cfdda
Faulting package full name:
Faulting package-relative application ID:

PathOfExile_x64Steam.exe
0.0.0.0
5aa07446
ntdll.dll
10.0.16299.248
effc9126
c0000374
00000000000f87bb
2f84
01d3b6ed82d7c6a0
C:\Program Files (x86)\Steam\steamapps\common\Path of Exile\PathOfExile_x64Steam.exe
C:\Windows\SYSTEM32\ntdll.dll
55d374e4-af56-4570-82df-a672650cfdda
Last edited by Dune144 on Mar 8, 2018, 11:00:04 AM
Last bumped on Mar 14, 2018, 12:22:09 PM
This thread has been automatically archived. Replies are disabled.
It seems the problem may relate to being in a Discord call while playing PoE. With or without screen sharing, the game went crash-less for a day while not using Discord, but crashed after 60 seconds when a Discord call started.
"
It seems the problem may relate to being in a Discord call while playing PoE. With or without screen sharing, the game went crash-less for a day while not using Discord, but crashed after 60 seconds when a Discord call started.


Interesting. Do you use a discord overlay to put call information, etc, on screen on top of the game? If so, does the crash also go away if you run discord, make a call, but do not have the overlay enabled?

(The way that overlay stuff often works is they inject extra code into the rendering path of the game, which means if they have a bug, or do something that causes unexpected state changes, or whatever, it can cause a crash - and things PoE do can cause the same in the Discord code. Which all sucks.)
"
SlippyCheeze wrote:
"
It seems the problem may relate to being in a Discord call while playing PoE. With or without screen sharing, the game went crash-less for a day while not using Discord, but crashed after 60 seconds when a Discord call started.


Interesting. Do you use a discord overlay to put call information, etc, on screen on top of the game? If so, does the crash also go away if you run discord, make a call, but do not have the overlay enabled?


Nope. Discord's overlay is disabled, as is Steam's, but I do use RivaTuner's overlay to display my framerate/frametime (not the cause).
Last edited by Dune144 on Mar 14, 2018, 4:42:44 AM
"
"
SlippyCheeze wrote:
"
It seems the problem may relate to being in a Discord call while playing PoE. With or without screen sharing, the game went crash-less for a day while not using Discord, but crashed after 60 seconds when a Discord call started.


Interesting. Do you use a discord overlay to put call information, etc, on screen on top of the game? If so, does the crash also go away if you run discord, make a call, but do not have the overlay enabled?


Nope. Discord's overlay is disabled, as is Steam's, but I do use RivaTuner's overlay to display my framerate/frametime (not the cause).


Huh. That is interesting. Could you grab listdlls, and run it against poe while not in a Discord call, but after you enter a map or regular zone? (eg: leave town / hideout, then run it)

I'm just curious to know if Discord is still injecting code into the application to make it possible to show the overlay, even if it is disabled, or if it is completely out of the rendering path. That'll tell us what is loaded in-process, which gives a concrete answer to the question.

Report Forum Post

Report Account:

Report Type

Additional Info