Page MenuHomeFeedback Tracker

Random Client + Server Crashes since BETA Release, Faulty Modul: PhysX3_x86.dll
Closed, ResolvedPublic


Server + Clients Crash randomly when playing on a larger mission. We are using the latest Ahoy World Invade & Annex Mission.

Server Box closes and gives out an ACCESS Violation (see attachments)

This happened AFTER the BETA Release. We had no crashing before. Lately we have to restart the Server 5 -10 Times a Day!

While playing the Mission, the Server FPS is under 5 most of the time!

The Dedicated Server has a 100MBit Full Duplex with unlimited Bandwith and meets the Requirements of ArmA 3.

Name der fehlerhaften Anwendung: arma3server.exe, Version:, Zeitstempel: 0x51c84181
Name des fehlerhaften Moduls: PhysX3_x86.dll, Version:, Zeitstempel: 0x5164246f
Ausnahmecode: 0xc0000005
Fehleroffset: 0x000dedb7
ID des fehlerhaften Prozesses: 0xbe4
Startzeit der fehlerhaften Anwendung: 0x01ce73483306d464
Pfad der fehlerhaften Anwendung: C:\Games\SteamApps\common\Vanilla\arma3server.exe
Pfad des fehlerhaften Moduls: C:\Games\SteamApps\common\Vanilla\PhysX3_x86.dll
Berichtskennung: ecd6d488-df4a-11e2-b21e-0019999c0a4e {F20462} {F20463} {F20464} {F20465}


Legacy ID
Game Crash
Steps To Reproduce
  1. Start the Mission Invade & Annex on your Dedicated Server
  2. have 20 - 40 Players
  3. Play
  4. Server + Client crash at a random Time

Event Timeline

ZASgtHammer edited Additional Information. (Show Details)
ZASgtHammer set Category to Game Crash.
ZASgtHammer set Reproducibility to Random.
ZASgtHammer set Severity to None.
ZASgtHammer set Resolution to Suspended.
ZASgtHammer set Legacy ID to 1543887985.May 7 2016, 3:05 PM

Do you have same issues with our official coop missions? Can you try it please? Thank you.

Prior to this crash I lost left channel sound - 30 seconds after loosing sound in that channel , the server and everyone attached crashed.

PS- no one plays the official coop missions.....

Do you have more crashdumps please?

Uploaded another Crashdumppack from the 3rd of July.

Removing HALO jumping from the mission seems to have increased the stability of the server. This crash would appear within 1 hour when Users would consistently use parachutes, with HALO jumping removed, and parachutes not being used, this crash is not present.

The Server crashes randomly.. It can reach from 1 hour to 6 Hours. I had the Server running once 6 Hours then it crashed again with the Faulty Modul. I don´t think that fixes it. I hope your Server lasts longer than this now with constant player counts!

I have had had crashes in the last week. We have also resurrected the Para jump and para drop within our Domination mission. Whilst i was thinking along the same lines as you and that the sound for the chute was the issue, and i have replaced the old sound with the new sound for the flapping. I did think that was it but...

I have experienced the crash in game also with out, i have had physX crashes regularly in the past week and the worst was when 5 of us crashed at the same time, we all believe to be linked to the old crash caused by certain explosions.
The common Para crash i have is I lose sound via a para jump from flag, screen freezes on opening of the chute and i get a grey screen. I then went back to the lobby and regained the sound, complete with the loud click. I rejoined and crashed as soon as i spawned in base.
Then i rejoined again, played a while (5mins), got killed and then had an artillery strike near my dead body, click lost sound and the game crashed to desktop. Will post RPTs when it happens again

Fore sure the old PhysX crash!

Fank added a subscriber: Fank.May 7 2016, 3:05 PM
Fank added a comment.May 13 2014, 6:03 PM

Issue closed as obsolete. If you encounter this problem again, please create another ticket. Thank you.