Constant crashing today

"

Fault bucket 2201534150709660612, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: PathOfExile_x64.exe
P2: 0.0.0.0
P3: 5c1b713a
P4: PathOfExile_x64.exe
P5: 0.0.0.0
P6: 5c1b713a
P7: c0000005
P8: 0000000000c07e56
P9:
P10:

"

Faulting application name: PathOfExile_x64.exe, version: 0.0.0.0, time stamp: 0x5c1b713a
Faulting module name: d3d11.dll, version: 10.0.17134.441, time stamp: 0x17eeea7e
Exception code: 0xc0000005
Fault offset: 0x0000000000185c89
Faulting process ID: 0x1408
Faulting application start time: 0x01d4a4577ce36758
Faulting application path: C:\Program Files (x86)\Grinding Gear Games\Path of Exile\PathOfExile_x64.exe
Faulting module path: C:\WINDOWS\SYSTEM32\d3d11.dll
Report ID: 1b93b36c-4457-4dd3-a101-65f382c6aa77
Faulting package full name:
Faulting package-relative application ID:

"

Faulting application name: PathOfExile.exe, version: 0.0.0.0, time stamp: 0x5c1b6fbb
Faulting module name: PathOfExile.exe, version: 0.0.0.0, time stamp: 0x5c1b6fbb
Exception code: 0xc0000005
Fault offset: 0x00875223
Faulting process ID: 0xb0c
Faulting application start time: 0x01d4a45a2c4f6fe8
Faulting application path: C:\Program Files (x86)\Grinding Gear Games\Path of Exile\PathOfExile.exe
Faulting module path: C:\Program Files (x86)\Grinding Gear Games\Path of Exile\PathOfExile.exe
Report ID: 5fa16add-218d-4710-91c3-4c58fb266a8d
Faulting package full name:
Faulting package-relative application ID:

"

Faulting application name: PathOfExile_x64.exe, version: 0.0.0.0, time stamp: 0x5c1b713a
Faulting module name: nvwgf2umx.dll, version: 25.21.14.1735, time stamp: 0x5c0f6b7f
Exception code: 0xc0000005
Fault offset: 0x0000000000c7e830
Faulting process ID: 0x19f4
Faulting application start time: 0x01d4a45e112408e0
Faulting application path: C:\Program Files (x86)\Grinding Gear Games\Path of Exile\PathOfExile_x64.exe
Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e7b3660b4830c245\nvwgf2umx.dll
Report ID: d3006e2c-40ef-4782-86e7-6272dd30fdb5
Faulting package full name:
Faulting package-relative application ID:

"

It's not a new problem.

https://forums.battlefield.com/en-us/search?adv=&search=0xc0000005&title=&author=&cat=all&tags=&discussion_d=1&discussion_poll=1&comment_c=1&group_group=1&within=1+day&date=

Even though it sometimes shows the nvidia .dll as the module that "faults", on other times may show the "bf1.exe", or even the origin.exe. But an access violation is nearly always caused by logic errors of the program in use, rather than by faulty hardware. (Although can be faulty RAM) It can also be caused by software conflicts. Asus audio drivers "hsmgr.exe" running in memory have caused this in previous frostbite games.

You can google "segmentation fault" if you want to learn about it, but basically BF1 is trying to access restricted memory addresses resulting in null pointers, and reading outside the bounds of a memory array. Windows doesn't allow this, so unless the process has a failsafe coded then Windows just crashes the program. They're very difficult problems to solve for developers, because you have to run a debugger and sometimes the errors only happen with certain memory addresses that might only happen once in a while, and sometimes only affect certain configurations, but it's highly unlikely there is anything wrong with your particular rig and it is still "a problem with the game".

You can try stress testing your system with RealBench, memtest and Prime 95 (version 26.6) to rule out hardware problems. But apart from that, it's just a case of waiting for DICE to fix.

I got the crash very rarely, although not yet had it in CTE or the new build, but I had it rarely on the Winter patch build.

"

Exception code c0000005 is the code for an access violation. That means that your program is accessing (either reading or writing) a memory address to which it does not have rights. Most commonly this is caused by:
Accessing a stale pointer. That is accessing memory that has already been deallocated. Note that such stale pointer accesses do not always result in access violations. Only if the memory manager has returned the memory to the system do you get an access violation.
Reading off the end of an array. This is when you have an array of length N and you access elements with index >=N.
To solve the problem you'll need to do some debugging. If you are not in a position to get the fault to occur under your debugger on your development machine you should get a crash dump file and load it into your debugger. This will allow you to see where in the code the problem occurred and hopefully lead you to the solution. You'll need to have the debugging symbols associated with the executable in order to see meaningful stack traces.

"

ildegardo a écrit :

Yo pude solucionarlo reinstalando el directx. Este está en la carpeta del juego, en mi caso C:\Program Files (x86)\Steam\steamapps\common\Path of Exile\_CommonRedist\DirectX\Jun2010. Hay que abrir el ejecutable dentro de esa ruta.

"

azurstreams a écrit :

"

ildegardo a écrit :

Yo pude solucionarlo reinstalando el directx. Este está en la carpeta del juego, en mi caso C:\Program Files (x86)\Steam\steamapps\common\Path of Exile\_CommonRedist\DirectX\Jun2010. Hay que abrir el ejecutable dentro de esa ruta.

from post: https://www.pathofexile.com/forum/view-thread/2238846

I went to Program files, GGG Redist, and reinstalled DXsetup

I will check tomorrow if it is fixed.