Game crashes to desktop with no error - UNPLAYABLE
Damn add me to the list! I'm on playstation but crashing every five minutes.
How can someone fuck up this bad?! The developers are bad and should feel bad, this is absolute inexcusable bullshit. |
![]() |
" I have moved to laptop (i7-9750H, GTX 1660Ti, 16GB) and not only it works nearly perfect (no crashes for ~1h) but I noticed much smoother textures loading when i.e. entering new map/area. Both my systems have NVMe SSD ofc. |
![]() |
Ryzen 1600X, GTX 1060, 32 GB RAM
Like everyone else, my game has been randomly crashing to desktop with no error message. The crashes have become more frequent recently to the point of making the game unplayable. The funny thing is performance was flawless for me at the start of this league - one of the minor patches majorly fucked something up. Pretty bummed I haven't been able to play recently, I'm not going to tank my PC's performance and disable SMT just to play PoE. Really disappointed to see GGG not even acknowledging this issue. |
![]() |
Hi
I have the same problem, I can neither route nor map solution please. System: Rayzen 1800x 16gb Ram RTX 2060 |
![]() |
I get both, wit and without error msgs. Some happen in maps, hideouts, even in the login screen.
In the Application Event Viewer I find these: Faulting application name: PathOfExile_x64.exe, version: 0.0.0.0, time stamp: 0x60110795 Faulting module name: PathOfExile_x64.exe, version: 0.0.0.0, time stamp: 0x60110795 Exception code: 0xc0000005 Fault offset: 0x000000000127fcb4 Faulting process ID: 0x2418 Faulting application start time: 0x01d6f74bbbff6cbe Faulting application path: D:\Program Files\Path of Exile\PathOfExile_x64.exe Faulting module path: D:\Program Files\Path of Exile\PathOfExile_x64.exe Report ID: bec40fe3-26a5-48be-8745-265da74ab393 Faulting package full name: Faulting package-relative application ID: Faulting application name: PathOfExile_x64.exe, version: 0.0.0.0, time stamp: 0x60110795 Faulting module name: ntdll.dll, version: 10.0.16299.492, time stamp: 0x1ef3a73c Exception code: 0xc0000005 Fault offset: 0x0000000000041a4b Faulting process ID: 0x1218 Faulting application start time: 0x01d6f74af62b26a7 Faulting application path: D:\Program Files\Path of Exile\PathOfExile_x64.exe Faulting module path: C:\Windows\SYSTEM32\ntdll.dll Report ID: c82adc39-3625-4a03-82bb-0b935db0e528 Faulting package full name: Faulting package-relative application ID: Faulting application name: PathOfExile_x64.exe, version: 0.0.0.0, time stamp: 0x60110795 Faulting module name: ntdll.dll, version: 10.0.16299.492, time stamp: 0x1ef3a73c Exception code: 0xc0000005 Fault offset: 0x0000000000041a4b Faulting process ID: 0x770 Faulting application start time: 0x01d6f73d617ce42a Faulting application path: D:\Program Files\Path of Exile\PathOfExile_x64.exe Faulting module path: C:\Windows\SYSTEM32\ntdll.dll Report ID: acc5adb6-172c-4ea5-9c2b-3421b5ab9dbd Faulting package full name: Faulting package-relative application ID: Faulting application name: PathOfExile_x64.exe, version: 0.0.0.0, time stamp: 0x60110795 Faulting module name: ntdll.dll, version: 10.0.16299.492, time stamp: 0x1ef3a73c Exception code: 0xc0000005 Fault offset: 0x0000000000041a4b Faulting process ID: 0x1278 Faulting application start time: 0x01d6f738dd2643e8 Faulting application path: D:\Program Files\Path of Exile\PathOfExile_x64.exe Faulting module path: C:\Windows\SYSTEM32\ntdll.dll Report ID: 57f35eed-9a9a-4cbc-a084-5768e96c91ef Faulting package full name: Faulting package-relative application ID: Faulting application name: PathOfExile_x64.exe, version: 0.0.0.0, time stamp: 0x60110795 Faulting module name: PathOfExile_x64.exe, version: 0.0.0.0, time stamp: 0x60110795 Exception code: 0xc0000005 Fault offset: 0x0000000000e979f7 Faulting process ID: 0x1a94 Faulting application start time: 0x01d6f68693f11ab2 Faulting application path: D:\Program Files\Path of Exile\PathOfExile_x64.exe Faulting module path: D:\Program Files\Path of Exile\PathOfExile_x64.exe Report ID: f508dfc8-9f29-455a-9070-219676498a7a Faulting package full name: Faulting package-relative application ID: Faulting application name: PathOfExile_x64.exe, version: 0.0.0.0, time stamp: 0x60110795 Faulting module name: PathOfExile_x64.exe, version: 0.0.0.0, time stamp: 0x60110795 Exception code: 0xc0000005 Fault offset: 0x0000000000e979f7 Faulting process ID: 0x1564 Faulting application start time: 0x01d6f62fbc8a2511 Faulting application path: D:\Program Files\Path of Exile\PathOfExile_x64.exe Faulting module path: D:\Program Files\Path of Exile\PathOfExile_x64.exe Report ID: e7b7f019-79ad-4ddf-872d-907d7173cd0d Faulting package full name: Faulting package-relative application ID: Faulting application name: PathOfExile_x64.exe, version: 0.0.0.0, time stamp: 0x60110795 Faulting module name: PathOfExile_x64.exe, version: 0.0.0.0, time stamp: 0x60110795 Exception code: 0xc0000005 Fault offset: 0x0000000000e979f7 Faulting process ID: 0x94 Faulting application start time: 0x01d6f62e6c5d5bd9 Faulting application path: D:\Program Files\Path of Exile\PathOfExile_x64.exe Faulting module path: D:\Program Files\Path of Exile\PathOfExile_x64.exe Report ID: 2c4d789a-eba9-4210-aedf-ab3b6cedf508 Faulting package full name: Faulting package-relative application ID: Faulting application name: PathOfExile_x64.exe, version: 0.0.0.0, time stamp: 0x60110795 Faulting module name: ntdll.dll, version: 10.0.16299.492, time stamp: 0x1ef3a73c Exception code: 0xc0000005 Fault offset: 0x0000000000041a4b Faulting process ID: 0x508 Faulting application start time: 0x01d6f61a6ba85c17 Faulting application path: D:\Program Files\Path of Exile\PathOfExile_x64.exe Faulting module path: C:\Windows\SYSTEM32\ntdll.dll Report ID: b1cc3169-b230-4bc2-b0b1-7f3d18951ad1 Faulting package full name: Faulting package-relative application ID: |
![]() |
I just confirmed that packet loss is causing crashes for me.
|
![]() |
" This doesn't work for me. I have a Ryzen 7 1700 as well. Doesn't matter if I'm on Vulkan or DX11. All disabling SMT in Process Lasso seems to do is delay my crashing by about 20 minutes. Does it anywhere, while I'm doing anything - even when I'm not moving at all. I have also deleted the MOTDCache etc. folders in My Documents/My Games/Path of Exile. Verified Game Cache integrity in Steam. People have recommended uninstalling a specific Windows update, which I've also done. I seem to be running out of options other than giving the standalone client a shot. It's worth noting that I played this game completely fine with very minimal crashing (maybe once or twice every few days) prior to this patch. I was willing to put up with that. But I can't do anything now because I crash every half hour or so. I refuse to disable SMT in my BIOS just to play this game. I am a new player, only been playing for a couple weeks, but this makes me want to stop continuing to take the game seriously. The LEAST the company can do is acknowledge the problem. UPDATE: I have downloaded the standalone client and enabled SMT on the process in Process Lasso. I have yet to crash after about an hour of play, however I can see all the cores that are utilized maxed out pretty consistently. So it's really just a bandaid solution. I have also seen people suggest disabling Engine Multithreading. While it seems to work, I'm not terribly interested in playing Microsoft PowerPoint. Last edited by komaeda#1632 on Jan 30, 2021, 8:02:01 PM
|
![]() |
I just don't get it: Before the patch I never had any problems. May be some 10 crashes in 2k hours... Why in gods name did GGG change anything. Not only I got chrashes every abaout 30mins, perfomance is worse than ever! I never had problems that textures were loading on entering any instance. It's just ridicilous seeing RAM usage "growing" 10th of mb per second in Aferburner whilst knowing, that the SSD would like to pump a gb per second to the memory.
In fact: They could force the whole game into the 32+8gb vram while the game showing the ggg intro. And what I really do not get: Why force this mess to reality when it must have been an issue during testing. ps: 2070s, 3600x, 32gb |
![]() |
Crashing as well. Every .dump file produces this line
"The thread tried to read from or write to a virtual address for which it does not have the appropriate access." |
![]() |
I seem to be crashing in specific places, certain maps, some times lab.
I'm guaranteed to crash in outdoor Act 10 areas but not indoor. I can also run blood aqueducts as long as i want. hope this helps them narrow the problem down I can't get to maps on my new character. |
![]() |