CitizenK

It's not the location at the start of the issue, PC's been wiped and the install has been relocated multiple times to fault find, some of those crash dumps are from those changes but are essentially the same as the first error when the issue started. The first round of fault finding was done with Steam and DayZ installed on the HDD secondary drive, no issues with the dayz.exe for approx 24 months in that configuration. Issue started when re-joining game via an open DZSA launcher, no known game, steam or pc updates occurred at the time the issues started. The problem started about 2 weeks after the major game update had happened but only for DayZ and not the experimental install. Mod issues have been ruled out as since the fresh install none are subscribed/installed and the error persists unchanged.

Fault bucket 1951822678014217305, type 5 Event Name: AppHangB1 Response: Not available Cab Id: 0 Problem signature: P1: DayZ_x64.exe P2: 1.4.152.50 P3: 5d1b6273 P4: 0000 P5: 134217728 P6: P7: P8: P9: P10: Attached files: \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5A24.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5A35.tmp.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5A44.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5A54.tmp.txt \\?\C:\Users\****\AppData\Local\Temp\WER64E4.tmp.appcompat.txt These files may be available here: \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppHang_DayZ_x64.exe_292835eee32522b2459e6b89ff7bddc2d4066d_6610ade6_d8672631-d7db-46d6-a942-a3decd8d0240 Analysis symbol: Rechecking for solution: 0 Report Id: 52e66b2d-0629-41e9-a013-209c4e413480 Report Status: 268435456 Hashed bucket: 3a6d8ca6d43940e71b1644626b96cc59 Cab Guid: 0 ===================== I've made a tracker item a few days back on the official Bohemia bug site, waiting for more feedback after the first round of things they asked me to look at.

Description A problem caused this program to stop interacting with Windows. Faulting Application Path: C:\Program Files (x86)\Steam\steamapps\common\DayZ\DayZ_x64.exe Problem signature Problem Event Name: AppHangB1 Application Name: DayZ_x64.exe Application Version: 1.4.152.50 Application Timestamp: 5d1b6273 Hang Signature: 0000 Hang Type: 134217728 OS Version: 10.0.18362.2.0.0.256.48 Locale ID: 2057 Additional Hang Signature 1: 00000000000000000000000000000000 Additional Hang Signature 2: 0000 Additional Hang Signature 3: 00000000000000000000000000000000 Additional Hang Signature 4: 0000 Additional Hang Signature 5: 00000000000000000000000000000000 Additional Hang Signature 6: 0000 Additional Hang Signature 7: 00000000000000000000000000000000 Extra information about the problem Bucket ID: 3a6d8ca6d43940e71b1644626b96cc59 (1951822678014217305)

The program DayZ_x64.exe version 1.4.152.50 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel. Process ID: 23ec Start Time: 01d534b31763b394 Termination Time: 3 Application Path: D:\Program Files (x86)\Steam\steamapps\common\DayZ\DayZ_x64.exe Report Id: ff588bbb-8d8a-45b8-87a3-5fad6e6eda27 Faulting package full name: Faulting package-relative application ID: Hang type: Unknown

As i only just re-installed, should be feasible to try out the win 7 route just out of interest, to be honest even if that fixes it, I don't intend to run win 7 just for one game out of all the games I have, might consider a dual boot if this issue persists in the long term. Once I've done that I'll add all of this into the tracker ticket and go back to win 10, I'll just have to play other games in the meantime until whatever the issue it get's figured out or resolved by a game update. I can still play the experimental client so it's not a complete loss. My PC was probably due a fresh install by now anyway, plus I found out that after my last bios update the memory has defaulted to a lower clock speed, set it back to what it should be! Does not affect this issue but still at least its something positive from the troubleshooting exercise.

Additonal test, -booted in safe mode, loaded up the dayz launcher dialogue, tried to launch without battleye, I got the same system error message with some additional details mainly related to no gfx in safe mode I guess, not sure I have not had much to do with safemode on any of my pc's previously. -game does not load, no change in memory usage in safe mode, instant error box appears ==== Battleye cannot load, etc etc in small box (the one usually seen as battle eye loads up, oddly don't think I'm seeing that in normal boot prior to the game screen loading, I don't normally notice it though, that goes followed by a second dialogue box: ==== *GPU not supported *GPU drivers not up to dage 8DirectX not up to date *other kind of error ==== DayZ exit message in safe mode *DayZ has exited in an unusual manner *Launcher has detected that DayZ was closed unusually. If you encounter an error that you cannot solve by yourself, please report it to our feedback tracketror contact our support team. *Exit code: 0x00000001 - UNABLE_TO_INIT-DXGI ==== -Tried going into the DayZ launcher, uninstalling battleye and attempting to start the game without it when prompted to install, same error present, game hangs, mem usage maxes out. -Tried forcing DX11 using --dxlevel 11 on the dayz launch commands, went via the dayz launcher, tried with and without battleye activated on force window, same error both times. Tried again on full screen, PC completely locked out even though I'd alt tabbed, after 4-5 min new error seen *NVIDIA Share.exe -System Error Unknown Hard Error.* Game window auto closed as did the launcher, memory back to normal and unfrozen. Checked all shadowplay/recording functionality is disabled in experience, xbox record etc is all disabled. -Might have needed to use -dxlevel110, tried that, no change.

When I search for AppHangB1, it seems to be more of a steam related issue, not sure why it's only a problem for this game and no others and not many people are having the issue. -Repeated virus/malware scan, no threats detected. -Tried launching the game with AV closed and windows firewalls disabled, same game hanging/error, no change. -Added -dx9 to the steam shortcut and game launch options, no change in problem.

Fair shout not done that specific activity yet, the format of the HDD and fresh windows install on the SSD followed by install of the latest driver from experience should have covered it though. -Removed all drivers using DDU in safe mode, re-booted, re-installed the drivers via experience to current version. Same DayZ stable client issue present. DayZ experimental still working without issue No change in behaviour of the DayZ_x64.exe file, program not responding again after game window (black) opens, memory usage increasing to system max before crashing. ====== The program DayZ_x64.exe version 1.4.152.50 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel. Process ID: 23ec Start Time: 01d534b31763b394 Termination Time: 3 Application Path: D:\Program Files (x86)\Steam\steamapps\common\DayZ\DayZ_x64.exe Report Id: ff588bbb-8d8a-45b8-87a3-5fad6e6eda27 Faulting package full name: Faulting package-relative application ID: Hang type: Unknown ====== Description A problem caused this program to stop interacting with Windows. Faulting Application Path: C:\Program Files (x86)\Steam\steamapps\common\DayZ\DayZ_x64.exe Problem signature Problem Event Name: AppHangB1 Application Name: DayZ_x64.exe Application Version: 1.4.152.50 Application Timestamp: 5d1b6273 Hang Signature: 0000 Hang Type: 134217728 OS Version: 10.0.18362.2.0.0.256.48 Locale ID: 2057 Additional Hang Signature 1: 00000000000000000000000000000000 Additional Hang Signature 2: 0000 Additional Hang Signature 3: 00000000000000000000000000000000 Additional Hang Signature 4: 0000 Additional Hang Signature 5: 00000000000000000000000000000000 Additional Hang Signature 6: 0000 Additional Hang Signature 7: 00000000000000000000000000000000 Extra information about the problem Bucket ID: 3a6d8ca6d43940e71b1644626b96cc59 (1951822678014217305) ====== System temps and airflow are all fine, the only thing spiking is the RAM usage, although interestingly when the RAM usage ramps up the CPU usage also rises a bit, the game does not get to the point of being loaded so the GPU is not involved at that point. I'm running out of options to check now, someone suggested I try switching out DDR modules in rotation e to see if that affects anything, all 4 modules have passed multiple mem check passes without comment, but I'll give it a go. I'm kind of getting down the list to changing out the memory modules or the GFX card as part of the troubleshooting checklist, I have the card from my old PC still lying around I think, spec might be high enough to run DayZ just to rule out the current one. One other avenue would be installing windows 7 from my old discs see if that works with the same hardware set up. Just trying to isolate it to one area in particular if it's hardware or software related.

Corrected, i posted the wrong set from my previous pc. Making a bug tracker post now I've checked everything I can check.

Running Kingston Fury Black 16GB (2x8GB) DDR4 PC4-19200C15 2400MHz Dual Channel Ki In DayZ experimental menu now 7.2 GB of memory in use.

Other people having same problem see other threads.

Same, I've been through everything, 32GB RAM here and decent page file set up, I'm way down at the stage of clean re-install with system updated and only dayz/steam installed, still upon starting the game in steam the icon appears on the taskbar but in a 'not responding' state, game window is maximised but black screen, if you tab out you see system RAM then ramps up from baseline of ~4GB usage up to maxed out at 32GB over around 20-30 seconds, the os then hangs and dayz.exe and steam crash. The first few times it happened I had to power cycle the pc to unfreeze the OS. Later, once I alt tabbed I was able to close the process before the system hung or even if it did as long as the task manger was up and the game was tabbed it was recoverable for the OS. Experimental DayZ works as the stable install did last Saturday, no problems, only the stable dayz install hangs and trashes the system memory % without getting to the game menu. No stepwise changes have affected the issue at all, it's the same in each test. Validated files, clear files, re-install game, change page file, re-install game on SSD (was on HDD for over 1000 hours gameplay), clean install of windows etc.

If this is due to RAM maxing out I've just posted on another thread for this, seems some people are suddenly having an issue with DayZ ripping all of the RAM up until the system crashes with the game stuck in a 'not responding' state, never makes it to the game menu. I've stepwise troubleshooted it from install, game files, hardware, software, clean install etc, no joy. It's some kind of issue between dayz stable, steam and windows from what I can tell, it's loading the system RAM to max without initiating the game properly, if you don't alt tab out and end the process the OS hangs. Experimental version is still working. Issue is (for those that have it) present whether playing on modded or vanilla.

Last saturday I was playing on a modded server, the server reset, when I closed the game and tried to re-launch through DZSA launcher the game was in a 'not responding' state which I couldnt see as it was in full screen, the only way to reset was power cycle at that point. After a two more tries I alt tabbed out and saw that my 32GB of RAM was gradually being maxed out by the DayZ executable, it would steadily climb until the system/steam hung, all the time the game never got to the start screen and the process icon said 'not responding'. All other games worked fine including those which use battleye. Oddly when the issue started, DayZ experimental install still worked fine as before. Page file checked/adjusted for effect, no change, RAM checked, no issues, system verifed as up to date. Over 1000 hours of game time with current rig, no upgrades made to system or software changes the day of the issue. As far as I'm aware the only change to the PC between re-connecting to the game when the problem started was a server reset, no steam or pc updates would have occurred due to system settings, with dzsa launcher still up steam would no update anything unless prompted to do so as it sees DayZ as still running. Modded server side scheduled reset should not have impacted anything,t the admins on that server post in world chat when they are uploading new mod updates. I've been through a long list of trouble shooting exercises, tried various things. Finally moved onto clean wipe of windows, with system full updated to latest drivers, only steam and dayz installed (no mods, unsubscribed all), the same memory max out happened, no difference from before. In this clean system state I also tried switching the install from my HDD 3TB drive (formatted prior to DL of steam.day z) over to the SSD, identical failure to start the game, maxed out memory. This has to be some kind of specific glitch between the SSD/page file/RAM and the way the game is working, other than the game hanging and consuming all of the physical memory the OS/hardware/game files are all as expected, no issues. It's almost like the game is suddenly putting everything through the RAM, ignoring the page file, no accessing the CPU/GPU, it's just getting stuck initiating the game until RAM is depleted and the OS crashes. Copy of the last event after full re-install with updated system drivers and only steam/dayz installed (no mods). TLDR, memory max out, randomly started last Saturday on Modded Day Z server, no changes to hardware or software between normal operation and issue present, is 100% reproducible, no fixes worked as of yet. Focus on hardware check of RAM, page file and game files. ========= Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: DayZ_x64.exe (7976) consumed 88151642112 bytes, MsMpEng.exe (3800) consumed 174497792 bytes, and SearchUI.exe (6932) consumed 144093184 bytes. Resource Exhaustion Diagnosis Events Events related to exhaustion of system commit limit (virtual memory). ========== System info ========== OS Name Microsoft Windows 10 Pro Version 10.0.18362 Build 18362 Other OS Description Not Available OS Manufacturer Microsoft Corporation System Name - System Manufacturer System manufacturer System Model System Product Name System Type x64-based PC System SKU SKU Processor Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz, 4008 Mhz, 4 Core(s), 8 Logical Processor(s) BIOS Version/Date American Megatrends Inc. 3801, 14/03/2018 SMBIOS Version 3.0 Embedded Controller Version 255.255 BIOS Mode UEFI BaseBoard Manufacturer ASUSTeK COMPUTER INC. BaseBoard Product Z170-E BaseBoard Version Rev 1.xx Platform Role Desktop Secure Boot State Off PCR7 Configuration Binding Not Possible Windows Directory C:\WINDOWS System Directory C:\WINDOWS\system32 Boot Device \Device\HarddiskVolume4 Locale - Hardware Abstraction Layer Version = "10.0.18362.145" Username - Time Zone - Installed Physical Memory (RAM) 32.0 GB Total Physical Memory 31.9 GB Available Physical Memory 28.5 GB Total Virtual Memory 36.9 GB Available Virtual Memory 31.5 GB Page File Space 5.00 GB Page File C:\pagefile.sys Kernel DMA Protection Off Virtualisation-based security Not enabled Device Encryption Support Reasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and the device is not Modern Standby, Un-allowed DMA-capable bus/device(s) detected, TPM is not usable Hyper-V - VM Monitor Mode Extensions Yes Hyper-V - Second Level Address Translation Extensions Yes Hyper-V - Virtualisation Enabled in Firmware No Hyper-V - Data Execution Protection Yes ========= Name NVIDIA GeForce GTX 1080 PNP Device ID PCI\VEN_10DE&DEV_1B80&SUBSYS_33661462&REV_A1\4&2D78AB8F&0&0008 Adapter Type GeForce GTX 1080, NVIDIA compatible Adapter Description NVIDIA GeForce GTX 1080 Adapter RAM (1,048,576) bytes Installed Drivers C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_b49751b9038af669\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_b49751b9038af669\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_b49751b9038af669\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_b49751b9038af669\nvldumdx.dll Driver Version 26.21.14.3086 INF File oem37.inf (Section094 section) Colour Planes Not Available Colour Table Entries 4294967296 Resolution 2560 x 1440 x 59 hertz Bits/Pixel 32 Memory Address 0xDE000000-0xDEFFFFFF Memory Address 0xC0000000-0xCFFFFFFF Memory Address 0xD0000000-0xD1FFFFFF I/O Port 0x0000E000-0x0000E07F IRQ Channel IRQ 16 I/O Port 0x000003B0-0x000003BB I/O Port 0x000003C0-0x000003DF Memory Address 0xA0000-0xBFFFF Driver C:\WINDOWS\SYSTEM32\DRIVERSTORE\FILEREPOSITORY\NV_DISPI.INF_AMD64_B49751B9038AF669\NVLDDMKM.SYS (26.21.14.3086, 20.82 MB (21,836,032 bytes), 29/05/2019 19:00) ============== Drive Description Local Fixed Disk Compressed No File System NTFS Size 464.69 GB (498,955,042,816 bytes) Free Space 413.30 GB (443,772,223,488 bytes) Volume Name Volume Serial Number 48CE44C8 Drive Description Local Fixed Disk Compressed No File System NTFS Size 2.73 TB (3,000,457,228,288 bytes) Free Space 2.71 TB (2,979,528,830,976 bytes) Volume Name HDD Volume Serial Number 3837A1C6 ============ Description Disk drive Manufacturer (Standard disk drives) Model ST3000DM001-1ER166 Bytes/Sector 512 Media Loaded Yes Media Type Fixed hard disk Partitions 1 SCSI Bus 4 SCSI Logical Unit 0 SCSI Port 0 SCSI Target ID 0 Sectors/Track 63 Size 2.73 TB (3,000,590,369,280 bytes) Total Cylinders 364,801 Total Sectors 5,860,528,065 Total Tracks 93,024,255 Tracks/Cylinder 255 Partition Disk #0, Partition #0 Partition Size 2.73 TB (3,000,457,232,384 bytes) Partition Starting Offset 135,266,304 bytes Description Disk drive Manufacturer (Standard disk drives) Model Samsung SSD 850 EVO 500GB Bytes/Sector 512 Media Loaded Yes Media Type Fixed hard disk Partitions 4 SCSI Bus 5 SCSI Logical Unit 0 SCSI Port 0 SCSI Target ID 0 Sectors/Track 63 Size 465.76 GB (500,105,249,280 bytes) Total Cylinders 60,801 Total Sectors 976,768,065 Total Tracks 15,504,255 Tracks/Cylinder 255 Partition Disk #1, Partition #0 Partition Size 450.00 MB (471,859,200 bytes) Partition Starting Offset 1,048,576 bytes Partition Disk #1, Partition #1 Partition Size 99.00 MB (103,809,024 bytes) Partition Starting Offset 472,907,776 bytes Partition Disk #1, Partition #2 Partition Size 464.69 GB (498,955,044,352 bytes) Partition Starting Offset 593,494,016 bytes Partition Disk #1, Partition #3 Partition Size 532.00 MB (557,842,432 bytes) Partition Starting Offset 499,548,946,432 bytes =========== 0xFED10000-0xFED17FFF Motherboard resources OK 0xFED18000-0xFED18FFF Motherboard resources OK 0xFED19000-0xFED19FFF Motherboard resources OK 0xE0000000-0xEFFFFFFF Motherboard resources OK 0xFED20000-0xFED3FFFF Motherboard resources OK 0xFED90000-0xFED93FFF Motherboard resources OK 0xFED45000-0xFED8FFFF Motherboard resources OK 0xFF000000-0xFFFFFFFF Motherboard resources OK 0xFF000000-0xFFFFFFFF Legacy device OK 0xFEE00000-0xFEEFFFFF Motherboard resources OK 0xDFFC0000-0xDFFDFFFF Motherboard resources OK 0xFDAF0000-0xFDAFFFFF Motherboard resources OK 0xFDAF0000-0xFDAFFFFF Motherboard resources OK 0xFDAE0000-0xFDAEFFFF Motherboard resources OK 0xFDAE0000-0xFDAEFFFF Motherboard resources OK 0xFDAC0000-0xFDACFFFF Motherboard resources OK 0xFDAC0000-0xFDACFFFF Motherboard resources OK 0xDF248000-0xDF249FFF Intel(R) 100 Series/C230 Chipset Family SATA AHCI Controller OK 0xDF24C000-0xDF24C0FF Intel(R) 100 Series/C230 Chipset Family SATA AHCI Controller OK 0xDF24B000-0xDF24B7FF Intel(R) 100 Series/C230 Chipset Family SATA AHCI Controller OK 0xDE000000-0xDEFFFFFF NVIDIA GeForce GTX 1080 OK 0xDE000000-0xDEFFFFFF Intel(R) Xeon(R) E3 - 1200/1500 v5/6th Gen Intel(R) Core(TM) PCIe Controller (x16) - 1901 OK 0xC0000000-0xCFFFFFFF NVIDIA GeForce GTX 1080 OK 0xC0000000-0xCFFFFFFF Intel(R) Xeon(R) E3 - 1200/1500 v5/6th Gen Intel(R) Core(TM) PCIe Controller (x16) - 1901 OK 0xD0000000-0xD1FFFFFF NVIDIA GeForce GTX 1080 OK 0xFED00000-0xFED003FF High precision event timer OK 0xFD000000-0xFDABFFFF Motherboard resources OK 0xFD000000-0xFDABFFFF PCI Express Root Complex OK 0xFDAD0000-0xFDADFFFF Motherboard resources OK 0xFDB00000-0xFDFFFFFF Motherboard resources OK 0xFE000000-0xFE01FFFF Motherboard resources OK 0xFE036000-0xFE03BFFF Motherboard resources OK 0xFE03D000-0xFE3FFFFF Motherboard resources OK 0xFE410000-0xFE7FFFFF Motherboard resources OK 0xDF230000-0xDF23FFFF Intel(R) USB 3.0 eXtensible Host Controller - 1.0 (Microsoft) OK 0xDFFE0000-0xDFFFFFFF Intel(R) Ethernet Connection (2) I219-V OK 0xDF24A000-0xDF24A0FF Intel(R) 100 Series/C230 Series Chipset Family SMBus - A123 OK 0x90000000-0xDFFFFFFF PCI Express Root Complex OK 0xDF080000-0xDF083FFF High Definition Audio Controller OK 0xDF100000-0xDF107FFF ASMedia USB 3.1 eXtensible Host Controller - 1.10 (Microsoft) OK 0xDF100000-0xDF107FFF Intel(R) 100 Series/C230 Series Chipset Family PCI Express Root Port #1 - A110 OK 0xFE03C000-0xFE03CFFF Intel(R) Management Engine Interface OK 0xFE030000-0xFE033FFF High Definition Audio Controller OK 0xFE400000-0xFE40FFFF High Definition Audio Controller OK 0xA0000-0xBFFFF NVIDIA GeForce GTX 1080 OK 0xA0000-0xBFFFF PCI Express Root Complex OK 0xA0000-0xBFFFF Intel(R) Xeon(R) E3 - 1200/1500 v5/6th Gen Intel(R) Core(TM) PCIe Controller (x16) - 1901 OK ============ Judging by the small quantity of this issue present online I suspect it's quite a limited issue at the moment, it may be a case of playing other games or experimental until more people get this issue or something is updated which removes the issue. I'll just post what I find in the hope it's useful to someone to pick apart what's causing this issue. The bit which I find the most strange is how the base experimental version works but the stable branch with or without mods does not now when I did with no obvious changes to the game, very weird. It must be a windows or steam background change which isn't clear. Incidentally, without day started, memory usage is baselining at 3.4 GB or 11% of my RAM. Other theories were some kind of malware or virus, but why they would only apply when dayz were started dosnt make sense, kaspersky running throughout, active protection, no issues detected while running or after scan.