Page MenuHomeFeedback Tracker

Status Access Violation Crash on Modded Namalsk Server if DayZ is installed on C:\ Default Steam directory
Assigned, NormalPublic

Description

I operate SCARS of Namalsk with more SCARS servers planned for the future. It is a heavily modded server and I understand that's undoubtedly a contributing factor to this issue. Players on my server that have multiple volumes / drives and have their steam games installed to a volume other than the default path in C:\ drive can connect and play on my server no problem. However anyone that has the game installed to the default C:\ path for steam experiences a Status Access Violation crash upon connection using the default game launcher or DZSA. If there is any additional information I can provide please don't hesitate to ask.

Details

Severity
Crash
Resolution
Open
Reproducibility
Always
Operating System
Windows 11 x64
Operating System Version
23H2
Category
Game Crash
Steps To Reproduce

I was able to reproduce this error on one of my own systems, all of which have 2 m2 SSD drives each, one for system/os the other for games. I used my daughter's 12th Gen i5, 32gb that has 2 Samsung Evo M2s, one 500gb for system and 1tb for games and moved steam and DayZ to the C:\ 500gb volume to reproduce this issue. I also have several users unable to play on either my live server hosted with GamingDeluxe.co.uk or my test server hosted on my Lan/Broadband connection on top of Omega Manager, Test and live servers are currently identical.

I was able to walk 3 of my users through the process of uninstalling DayZ and steam, shrinking their C:\ volume in Disk Management, creating another volume (one used D:\ the other two liked my personal choice of X:\ and did that). Then they reinstalled steam and DayZ, downloaded all mods and were able to connect and play just fine. Ultimately this work around / fix was discovered by a few of my friends who are also players on the server and refused to give up and experimented until it worked then we figured out what change they all had in common.

Additional Information

One of my players did discover that dragging DayZ out of the default steam path and to their desktop and running it from there allowed them to connect and play the game, so the issue isn't just being in the C:\ or system volume but seems to be related to the full default steam path.

Event Timeline

MiMuFPV created this task.Mon, Sep 9, 4:10 PM
Geez changed the task status from New to Need More Info.Mon, Sep 9, 4:36 PM
Geez added a subscriber: Geez.

Hello MimuFPV.
Can you please provide us with the modlist?

Yes, here's the complete list

@CF (1559212036)
@Namalsk Island (2289456201)
@Namalsk Survival (2289461232)
@SCARS Server Pack 1 (3287763876)
@VPPAdminTools (1828439124)
@Dabs Framework (2545327648)
@Armor Stats Display (2890146920)
@basic Map (2270215132)
@basic Map Namalsk Addon (2312374525)
@Dayz Editor Loader (2276010135)
@JMod (2125823097)
@dbo_surfaces_nam (2311951200)
@Autorun Mod (2313173630)
@BetterSmalleritems_2.0 (2684394542)
@Combinable Items (3133577751)
@Server_Information_Panel (1680019590)
@SchanaModParty (2075831381)
@SchanaModGlobalChat (2115602332)
@BuildEverywhereV2 (3257424504)
@Tombstone Basic Map (2442126356)
@Survivor Animations (2918418331)
@No Fall Damage (3166814349)
@No Force Weapon Raise (2098390861)
@No Vehicle Damage Complete (3166815421)
@PristineRepair+ (3079031467)
@SearchInventory (2936585965)
@SF_Core (2559539076)
@Ear-Plugs (1819514788)
@FlipTransport (1832448183)
@InventoryInCar (2361330944)
@PvZmoD_CustomisableZombies (2051775667)
@PvZmoD_TheDarkHorde (2007900691)
@PvZmoD_Spawn_System (1772776141)
@TraderPlus (2458896948)
@PlagueZ Helipad Collection (2513964121)
@Paragon Vending Machines (3117188869)
@BaseBuildingPlus (1710977250)
@BBPItemPack (2794690371)
@Code Lock (1646187754)
@Fishy Buildings (2572501944)
@BuilderItems (1565871491)
@JPJ_TraderPlus_PackingOverride (2994559750)
@Krak3nsAmmoStacks250 (3155027090)
@Dayz-Cat (2947349326)
@MMG - Mightys Military Gear (2663169692)
@CarVanillaPlus (2757657387)
@SCARS Transport NoBang (3288358741)
@MMG-Inventory++ (3058085616)
@DBN_FordRaptor_Scorpio (2809757799)
@Snafu Weapons (2443122116)
@RedFalcon Flight System Heliz (2692979668)
@BallerZ Gear (3025712002)
@BallerZ SNAFU Weapons Upgrades and Retexture (3038215705)
@BallerZ Teddys (3027721512)
@MuchDecos (1967655509)
@MuchDecos_Codelock (1984056101)
@MuchStuffPack (1991570984)
@MuchFramework (3171576913)
@Paragon Storage (3010267444)
@RaG_BaseItems (2878980498)
@BoomLays Things (2860643107)
@Fallout Trading Card Collectables (3008260735)
@Fallout Collectables (3043818313)
@Skyrim Trading Card Collectables (3008727680)
@Stuffed Animals (3148000323)
@CBD Wooden Vehicles Collectables (3237820366)
@Drippy Sneakers (2931436407)
@NERV_Gaming (3219973018)
@Mp3_RadioZ (2922036083)
@MagazineLoading (2912554819)
@RedFalcon Trash (2887408858)
@Party On ! (2260671430)
@FoXyVinyls (2860947857)
@C10 CHEVROLET (3251662876)
@Mystery Box (2574104127)
@RoadTripNG (2354568600)
@DDW-Star_Wars_Props (1896744112)
@SPBuilding (2177232791)
@Lightsword (1964490092)
@No Blood Splatter (3166813020)
@THYER5 Stims (3037211157)
@Dayz Mining System with Ores and Gems (2794626429)
@CannabisPlus (1932611410)
@DrugsPLUS (2170927235)
@UnCivilized Barrels (3003011666)
@Blacks Alpha Armor (3002946084)
@Blacks Containers (2957823412)
@UnCivilized Billboards (3035369739)
@Blacks DBN Raptor RTX (2968110772)
@Blacks RFFS Helis Retex (2957812943)
@DiscordChat (2787928901)
@gebsfish (2757509117)
@DBR_LittleBird_RFFSHeli_Skins (3279783147)
@BallerZ Kronic Heli Retextures (3030813297)
@AJs Creatures (2978547763)
@PseudoGiant (2847957663)
@Z_Alien (3017273820)
@Z_Predator (3036319373)
@BaseballCards (3048696887)
@ZeroWaifuTCGCollection_1 (2981098551)
@Collectable Items (2575183443)
@ArrakisDongs (2635717357)
@BallerZ Kronic Bears (3028253343)
@BallerZ Kronic Wolves (3029434339)
@Hitmarker (2903723881)
@SchanaModCompass (2067834152)
@Basic_Territories_Updated (2999534116)
@GameLabs (2464526692)
@Namalsk_Submarine_Journey (2531955350)
@RaG_Dragons (3310715247)
@Zens Zippo Lighter (3170285574)
@CBD Invasions (3221373203)
@Namalsk Builderitems (3192333926)
@Stargate Teleporters Complete (2933015619)
@DnA Keycards (2714183642)
@CJ187-LootChest (2345073965)
@SCARS CJ187 Loot Chest Capacity Increase (3313817161)
@Jiggles Signs (3114325820)
@NERV_Comics (3119668672)
@SpawnerBubaku (2482312670)
@Extended Inventory for Namalsk Suit (3152580779)
@MBM_ChevySuburban1989 (3320564967)
@Blacks BBP Interior (2957760073)

Oh no, I didn't realize that the mod names with @ would subscribe all those people to the ticket :O

DnA removed a subscriber: DnA.Tue, Sep 10, 9:59 AM
Geez added a comment.Tue, Sep 10, 11:18 AM

Thank you. Can you also provide a .mdmp file from the crashes?

Yes, I do want to clarify you're referring to the mdmp file from the server? I don't believe there is a local mdmp file. If so I should be able to get you one later today once I reconfigure to repeat the issue, but I don't believe that those experiencing the crash ever actually connect to the server, it crashes before that.

Geez added a comment.Tue, Sep 10, 3:25 PM

Client .mdmp is the one we would like to see

These are the two files generated in the \users\username\appdata\local\dayz folder when it crashes. I just reproduced this on my laptop by installing steam on C:\ in the default directory and DayZ in the default steamapps folder. Immediately prior to this I confirmed no issue with DayZ installed on a different volume (X:)

Geez added a comment.Wed, Sep 11, 10:48 AM

Hello MimuFPV.
We require a .mdmp file from the occurrence to analyse the issue

Is there another location I need to look because this is a clean install to reproduce the issue and those are the only 2 files in the typical crash folder. In fact I did a search and there are no mdmp files on the system at all. Is there something I need to do for the crash to create one, a launch parameter perhaps? I went through the process of saving the zip file of logs and it's attached.

Geez added a comment.Thu, Sep 12, 11:03 AM

Does the game freeze by any chance instead of crashing?

Nope, not at all. Attached are a couple of captures of me launching the game and experiencing the crash. The first one is with the native launcher the second DZSA. The crash with DZSA doesn't give the same dialog but it generates the same crash log and you can see I'm able to relaunch it at the end because it's no longer attempting to run.

Geez changed the task status from Need More Info to Assigned.Thu, Sep 12, 2:34 PM
Agr0na added a subscriber: Agr0na.Thu, Sep 12, 10:22 PM

I have the same problem

Agr0na added a comment.EditedThu, Sep 12, 10:25 PM

But my crash happens a few seconds after I connect to the server

Do you have an idea how to fix this?
Every other server works just fine its just on the one im playing on.

That's exactly why I've opened this ticket up. I'm not sure if you read the whole thing but I'd be curious if you move DayZ to another location / volume if that solves it like it does for my players. What is the server, I would be curious to look at their mods.

I also have this problem

but i have only two mods
Gamelabs and CodeLock installed

Geez, I hope you have a good weekend, ty for your continuing assistance with this issue!

I spent several hours last night and this morning trying to further isolate this trouble and I wanted to share what I've found. In my test environment I started with a vanilla Namalsk mission server and I started installing all the mods in the above list a few at a time, in that order. The client system is my Asus TUF F15 laptop with a clean windows 11 installation with both steam and dayz installed in the default c:\ path. Prior to doing this I copied over the profiles folder containing all the configs for the mods that required them on the server. When I got to Hitmarker (2903723881) I got an access violation crash. Adding this group also included BallerZ Kronic Wolves, BallerZ Kronic Bears, AJs Creatures, and PseudoGaint, z_alien and z_predator. So I began removing these one at a time starting with hitmarker, then the bears, wolves, etc. With all of them removed I was still getting the crash. For each step I was shutting down the server, removing a single mod, starting the server back up, then restarting steam and attempting to reconnect to the server from my laptop.

At this point I am confused because the server is exactly how it was working just an hour or so earlier, right before adding the animals, monsters and hitmarker mod. I went ahead and deleted the storage_1 to see if that made a difference and it did not. So I began removing more mods, one at a time. Shut down, remove a mod, restart the server. I removed a couple of heli retexture mods, and 3 collectable item mods and I was suddenly able to connect once more without the crash. I then began adding mods back one at a time and I was able to get the above mentioned wolves, bears, z_alien and z_predator added back and when I added AJs Creatures the crash came back. I started removing mods again, first AJs Creatures, still crashing after that, then z_alien then z_predator, then the wolves and bears. Crash seemed to go away again at this point. I Decided to try adding back mods in a slightly different order, added z_alien back, crash came back. At this point I don't believe the crash is related to any one specific mod, it can't be, it starts to happen after a mod is added but remains until half a dozen or more are removed only to return when a completely different mod is added on. Attached is the more recent crash zip. Please let me know if there is anything else I can provide up to and including access to my test server if you need it.

Michael{F4390665}

but i have only two mods
Gamelabs and CodeLock installed

Does the crash persist if you put steam and dayz somewhere other than the default c:\ path? All of my systems have a separate drive called X:\ that I install steam along with other game stores as well as the games themselves. That includes my laptop, but I currently have it configured to reproduce this crash by having everything on the default c:\ path.

What is your server info, I can attempt to connect and see what happens.