Noticed this mainly on Sa-Matra's wastelands with most recent server binaries. Usually occurs when a helicopter does a flyby. All clients in vicinity crash and drop clients.
Description
Details
- Legacy ID
- 3333799676
- Severity
- None
- Resolution
- Open
- Reproducibility
- Random
- Category
- Game Crash
- Log in to MP server.
- Play as usual.
- Crash;
Faulting application name: arma3.exe, version: 1.22.125.469, time stamp: 0x53ac2896
Faulting module name: PhysX3_x86.dll, version: 3.2.4.1, time stamp: 0x5164246f
Exception code: 0xc0000005
Fault offset: 0x001521cb
Faulting process id: 0x6f8
Faulting application start time: 0x01cf9c72a422a873
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\Arma 3\arma3.exe
Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\Arma 3\PhysX3_x86.dll
Report Id: 159ae73e-0877-11e4-bf14-b00594ed2ac1
Faulting package full name:
Faulting package-relative application ID:
Confirmed crashes on 3 pc's that crashed simultaneous application failures with similar event logs.
RPT ends with a long line of various;
"GetObjectLocked: Accessing static object outside landscape (Obj-519,680:287 in 32,32)
GetObjectLocked: Accessing static object outside landscape (Obj-519,680:288 in 32,32)
GetObjectLocked: Accessing static object outside landscape (Obj-519,679:280 in 32,32)
Subgroup R Alpha 4-3:<No leader> (0x32a9c9a0) - network ID 0:0"
Event Timeline
Hello,
can you please confirm that this is fixed with the Bootcamp update? (should be released soon)
Thank you.
Yes I can confirm it is still occurring.
Just uploaded another RPT from another client to help track it down.
I have deleted the obsolete crashes and assigned the actual ones. Please keep adding them, your help is much appreciated.
Uploaded tonight's crash. Noticed that we crashed when AA was fired at a hummingbird in the distance.
Feels like the old physx bug.
Faulting application name: arma3.exe, version: 1.24.125.979, time stamp: 0x53bea38c
Faulting module name: PhysX3_x86.dll, version: 3.2.4.1, time stamp: 0x5164246f
Exception code: 0xc0000005
Fault offset: 0x001521cb
Faulting process id: 0x1900
Faulting application start time: 0x01cfa92529385958
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\Arma 3\arma3.exe
Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\Arma 3\PhysX3_x86.dll
Report Id: 0c9e14f1-1531-11e4-bf1d-b00594ed2ac1
Faulting package full name:
Faulting package-relative application ID:
uploaded associated rpt 0xc0000005 error, this time, its physx again.
I am having this same issue. Mostly on King of the Hill servers. Some servers I can't load at all, some I can but I end up crashing anywhere between 20 minutes to 2 hours. Here is my post with more information:
http://feedback.arma3.com/view.php?id=19719
This post helped me as a temporary bandaid fix to at least get into a server:
http://steamcommunity.com/app/107410/discussions/1/46476691927706859/
If you preload the map you're trying to play with the editor, it helps you to not crash.
Please look into this issue Iceman.
We are finding the crash occurs mostly with explosions. All clients in the vicinity get the crash
I have also had some success with running different memory allocator launch options. Try these and see if anything helps, and let me know if it does.
https://community.bistudio.com/wiki/Arma_3:_Custom_Memory_Allocator
Currently the one I've had most success with is -malloc=system
Keep in mind that Iceman and the devs don't like these to be enabled if they're checking your crash dumps. They want default options only. Don't submit crash dumps that you've obtained while using these.
incident 1;
Faulting application name: arma3.exe, version: 1.24.125.979, time stamp: 0x53bea38c
Faulting module name: PhysX3_x86.dll, version: 3.2.4.1, time stamp: 0x5164246f
Exception code: 0xc0000005
Faulting application name: arma3.exe, version: 1.24.125.979, time stamp: 0x53bea38c
Faulting module name: PhysX3_x86.dll, version: 3.2.4.1, time stamp: 0x5164246f
Exception code: 0xc0000005
Fault offset: 0x0013039f
Faulting process id: 0x42e68
Faulting application start time: 0x01cfb768b1901ab0
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\Arma 3\arma3.exe
Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\Arma 3\PhysX3_x86.dll
Report Id: 708cf774-237a-11e4-bf1f-b00594ed2ac1
Faulting package full name:
Faulting package-relative application ID: ;
incident 2;
Fault offset: 0x001521cb
Faulting process id: 0xd6bc
Faulting application start time: 0x01cfb7874a3d7c8e
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\Arma 3\arma3.exe
Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\Arma 3\PhysX3_x86.dll
Report Id: b003c483-2383-11e4-bf1f-b00594ed2ac1
Faulting package full name:
Faulting package-relative application ID: