Lord_OverKill

Yeah I noticed a similar thing. I modified the load out for a pilot and it crashed out, kept the stock load out, no crash for about 4 hours. Could be a coincidence, could be the upgrade/fresh install of Windows 8.1 RTM, could be that the cycle of the moon synchronised with the server clock :P

Now that we have moved to the final release, can anyone confirm what will be happening with existing tickets in the bug tracker? As it stands the "final" release is still presenting the same PhysX crashing issues that myself, and many others have been facing since 0.70 stable (obviously the DEV branch). Will BIS be moving into a holding pattern for major bugs, and just be working on new content? Should those of us with the issues just shelf the software and a pipe dream and move back to A2?

Issue still exists in "stable" release/Final release. Have opted out of the DEV branch, and the issue still exists. Additionally, I'm also now running the NV BETA drivers, and I am still having issues. EDIT: I can offload the PhysX to the CPU via. the NVCP, however the issue still remains. I was benching my system last night and have performed a full OS rebuild for that purpose, still the same thing. Purged the local cache, removed one of my 690's, still the same thing. Been playing since Alpha, and this has only become an issue since ~ ver. 0.74 or something

Hi Dwarden, I have uploaded my dumps before for this same issue and had the ticket closed with no resolution.. I will open a new ticket ;) Feedback added to existing issue posted by other. This appears to be ongoing across many versions of A3.

Still happening: Faulting application name: arma3.exe, version: 0.77.109.860, time stamp: 0x52296a4d Faulting module name: PhysX3_x86.dll, version: 3.2.4.1, time stamp: 0x5164246f Exception code: 0xc0000005 Fault offset: 0x001521cb Faulting process id: 0x1244 Faulting application start time: 0x01cead3927fc70c9 Faulting application path: %steamdirectory%\steamapps\common\Arma 3\arma3.exe Faulting module path: %steamdirectory%\steamapps\common\Arma 3\PhysX3_x86.dll Report Id: 515af216-1934-11e3-9bce-5404a64a837f EDIT: Using NV 314.07 (stable 690 drivers, 320.49 perform poorly and cause BSOD)

Taki, move all data in $userprofile%\Documents\ARMA 3\ to a new folder elsewhere, or delete, your choice. I would also suggest that you could also take the following steps. Update to the latest STABLE graphics driver version for your GPU/card (don't use the Windows Update driver, you will hate yourself) Perform a Windows Update including the most recent Recommended update (KB2670838), and any DirectX updates associated Remove any addons, specifically SweetFX if installed. Some ARMA2 ports of addons face issues. Enjoy. Let's know how you go.

New server browser, or extend server filtering

Try editing the following file %userprofile%\Documents\Arma 3 Alpha\Arma3Alpha.cfg #Note this file path will only work if you have not relocated your "My Docs" to an alternative file path, however I'm sure you can work out the file is in your documents directory. Have you tried running in Window Mode in place of full screen? Can be hard to submit bugs when it crashes to desktop with no crash report to submit ;) +1 to constant crashes from the steam version, system specs as in sig. Running NV301.42

*BUMP* +1 for me, running 2 monitors, ASUS GTX 690 w/ NV 301.42 drivers (due to crashing issues with later versions). EDIT: ARMA 3 can be forced to start on main monitor by turning off additional monitors, however the mouse still doesn't map. ---------- Post added at 11:44 ---------- Previous post was at 11:27 ---------- See above resolution from another thread.

Worked. Solid work around. +1