64bit client crashing

Formatted and still crush, GG GGG.

Dont know whats the problem but is a your problem not mine.

Still crashing pls fix!!! it was smooth before

"

PxDGaming wrote:

I use the term "BSD" quite lose here. Computer just shuts down, reboots itself with no warning, no error, no nothing. I've ran different programs to try and see if it can catch anything before reboot happens but nope. Monitors just go dark and PC reboots.

That is absolutely, without question, a hardware problem.

"

PxDGaming wrote:

So far it's happened everywhere out of town/hideout but never when in town/hideout.

PC temps are normal, all fans are running, PC is nice and cool. It wasn't an issue in 3.0 but it is an issue in 3.1. It happens to people with high end gaming PC's too, not just mid tier like me. I've tuned everything down to minimum but it still happens.

Every other game works fine, this is an issue that only happens when playing Path of Exile so it's not my hardware that's faulty. Nice try tho.

It is entirely possible that something in PoE 3.1 changed, leading to it triggering a hardware issue that isn't showing up somewhere else, or a driver bug that is resulting in causing enough hardware badness that the system instantly reboots.

It is not actually possible, in theory, for any application running under Windows to cause the reboot behaviour you describe. Windows itself is specifically designed to prevent applications having this sort of hardware access.

The reason all y'all hardware monitors and stuff ask for admin rights? Specifically because without them you can't grant yourself permission to interrogate the Windows drivers (which, of course, should prevent you doing anything disastrously bad, like causing an instant reboot) without it.

So, if you currently run PoE with admin privileges, stop that, and run it as a normal unprivileged user.

If you still get the instant reboot, you have a hardware or driver problem, as it is literally impossible for PoE to cause that to happen without admin privileges other than a hardware or drive problem being triggered.

PoE is also known for being, shall we say, GPU and GPU heavy with burning ground, etc. Perhaps your problem is that the power supply to your graphics card is right on the edge, so only something that absolutely slams the system causes voltage drop leading to a reset. PoE might be guilty there, in the sense of being demanding, but the root cause is the hardware issue.

I know it is nice to think that because PoE is what changed, PoE must be the root cause of the problem, but it cannot be. Instant reboots do not happen because of unprivileged user processes.

"

Ygidua wrote:

I have not crashed since the last patch, so it seems they fixed that particular issue. I still DC a lot when changing maps though, it is only starting around afternoon and is worst in the evening.

Clearly a server issue on GGG´s end.

It is entirely possible it is a GGG server issue, but have you checked your network connection first? If you have, email support along with the proof that the network connection is entirely stable and functional, and they should be able to get the devs to investigate what is going on with the server to cause the disconnects.

If you don't supply that proof, they will just ask you for it, because of course, most of the time it is the network. I believe you when you say it isn't in your case, but you have to understand: all the people who insist it isn't their system, and flat out refuse to test it and show proof, mean that support can't believe you. Those fools ruined it for everyone else.

Constantly crashing says exe stopped working. Never had crashes before all harbinger. Let me know when you get this fixed then I will come back to the game.

Good evening,
my game crashes every 2th or 3th zoneport.

I have controlled my new router and my old computersettings.
The computersetting didn´t change since my last gametime.

So im one ppl more with problems.

This happening to me since I started playing the game back in Legacy. But it seems now my game crashing more frequently, I get "PoE stopped working_64bit.exe" 3-4times per map all day long. I've reinstalled the game, and the OS, updated drivers. I cant do lab runs because I crash ALWAYS before I can finish. Playing without Multithreading makes the game unplayable with low fps (under 100) and its very choppy.

I have
i7 7700K and a GTX 1080ti with 16GB DDR4, game is played from a SSD. I assume this is an issue with DX11.

"

NobodyEpic_Neko wrote:

add me to the crash list , havent had any issues yet and with this league

This is the same error code I'm getting. For me it's only crashing when changing zones

same problem here... could run the game fine last leagues. This league was also fine at the beginning until it started crashing constantly.

Disabling Enginge Multithreading solved this, but now, its barely playable. Many stutters and low fps... When i leave it enabled, the game crashes every few minutes. Thats insane...

My system is powerful and i have zero problems in other applications and games.

core i5 6600k
16gb ddr4
gtx1080ti

.. i can even run pubg flawlessly - and that means something :D

Recently I started to see this as well:

"

Art/2DItems/Weapons/OneHandWeapon/Claw/Claw4.dds
In source code filef:\buildslave\build\production\source\windows\wisual\device\d3d11\TextureD3D11.cpp at line 152 processing file Error -2005270523

I believe that it is related to the facts that:
- I am using an SSD for few days (have moved the game to SSD from HDD)
- I am using x86_64 version
- I am using Windows 10 x64
- I have multithread feature on

I have checked files for corruption (executed successfully patchcheck.exe) - everything is OK.

Possible cause? Maybe some internal race condition within the app. Might be related to the multithreading. Can be even related to some buffers and things in the OS itself. But that is up to the devs to investigate. Possibly they could run the game from a ramdrive to minimize I/O bottlenecks.

Possible solution for you:
- Move game to HDD (but it will run much slower)
- Disable multithreading in the app
- Set all the graphic options to low/lower/lowest and try again