Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
If that's the case, then there must be some process on your PC that is currupting the libraries somehow.
it only seems to crash now if i start the engine on a vehicle or try to launch a drone. or in this last instance another player started a vehicle within close proximity of me and my game crashed
OS is Windows 10 Professional x64.
All updates for everything (OS, drivers, game) are installed.
On Windows 7 I did not have such weird game crashes.
---------------------------------------------------------------------------------
Faulting application name: bad_module_info, version: 0.0.0.0, time stamp: 0x00000000
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0x00000000
Fault offset: 0x0000000000000000
Faulting process ID: 0x249c
Faulting application start time: 0x01d6d0ce64e00410
Faulting application path: bad_module_info
Faulting module path: unknown
Report ID: 850b05c3-f0df-49d2-b1af-31269442649d
Faulting package full name:
Faulting package-relative application ID:
---------------------------------------------------------------------------------
The System log has 3 records related to this issue.
1. 7 minutes before the crash it logged:
---------------------------------------------------------------------------------
Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: arma3_x64.exe (9372) consumed 10500616192 bytes, steamwebhelper.exe (1392) consumed 401113088 bytes, and MsMpEng.exe (4740) consumed 288456704 bytes.
---------------------------------------------------------------------------------
2. Two minutes before the crash:
---------------------------------------------------------------------------------
Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: arma3_x64.exe (9372) consumed 10765832192 bytes, steamwebhelper.exe (1392) consumed 401113088 bytes, and MsMpEng.exe (4740) consumed 288444416 bytes.
---------------------------------------------------------------------------------
3. 0 minutes before the crash:
---------------------------------------------------------------------------------
The BattlEye Service service terminated unexpectedly. It has done this 1 time(s).
---------------------------------------------------------------------------------
P. S.
"10765832192 bytes" is something about 10 GB. Since when is Arma 3 consuming so much memory ? I have got 16 GB installed now with 1 GB page file for emergency scenarios. When the OS is idle it consumes about 3.5GB out of 15.9GB.
It is either a memory leak in Arma or a Windows 10's bug.
If you use pc with internal / eksternal graphic card, try experiment running arma with internal graphic card and see the performance.
the other option you need to set your windows os "virtual paging file" to automatic.
The result is below.
13:04
Application ("C:\Program Files\WindowsApps\Microsoft.XboxGamingOverlay_5.420.11102.0_x64__8wekyb3d8bbwe\GameBarFTServer.exe" -Embedding) (PID: 11872) has failed to complete a COM/RPC call because of an invalid message from server. User Action Try the operation again. If the problem persists, contact your system administrator.
13:17
The Desktop Window Manager process has exited. (Process exit code: 0xc00001ad, Restart count: 1, Primary display device ID: Radeon RX 570 Series)
13:17
Faulting application name: dwm.exe, version: 10.0.19041.508, time stamp: 0xcd97c98b
Faulting module name: KERNELBASE.dll, version: 10.0.19041.662, time stamp: 0xec58f015
Exception code: 0xc00001ad
Fault offset: 0x000000000010bd5c
Faulting process ID: 0x1fe8
Faulting application start time: 0x01d6d139193d848f
Faulting application path: C:\Windows\system32\dwm.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report ID: 1424465f-3a68-4113-a0bf-e57a164cdd44
Faulting package full name:
Faulting package-relative application ID:
13:17
The Desktop Window Manager process has exited. (Process exit code: 0xc00001ad, Restart count: 2, Primary display device ID: Radeon RX 570 Series)
13:17
The Desktop Window Manager process has exited. (Process exit code: 0xc00001ad, Restart count: 3, Primary display device ID: Radeon RX 570 Series)
13:17
Faulting application name: dwm.exe, version: 10.0.19041.508, time stamp: 0xcd97c98b
Faulting module name: KERNELBASE.dll, version: 10.0.19041.662, time stamp: 0xec58f015
Exception code: 0xc00001ad
Fault offset: 0x000000000010bd5c
Faulting process ID: 0x1d84
Faulting application start time: 0x01d6d1391aa52f52
Faulting application path: C:\Windows\system32\dwm.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report ID: d051b235-85f9-4358-bc75-5df43f2159fe
Faulting package full name:
Faulting package-relative application ID:
13:17
The Desktop Window Manager process has exited. (Process exit code: 0xc00001ad, Restart count: 4, Primary display device ID: Radeon RX 570 Series)
13:17
Arma 3 crashed with an error:
DX11 error: CreateTexture failed: E_OUTOFMEMORY
FPS Monitor showed that ãbout 7.8 GB of RAM were used and about 8GB were free !
What the f*ck ?!
Will try a system controlled paging file.
13:32
: The embedded controller (EC) returned data when none was requested. The BIOS might be trying to access the EC without synchronizing with the operating system. This data will be ignored. No further action is necessary; however, you should check with your computer manufacturer for an upgraded BIOS.
14:14
Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: arma3_x64.exe (8552) consumed 12466290688 bytes, steamwebhelper.exe (11192) consumed 455454720 bytes, and MsMpEng.exe (3928) consumed 277422080 bytes.
14:19
Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: arma3_x64.exe (8552) consumed 12567744512 bytes, steamwebhelper.exe (11192) consumed 455454720 bytes, and MsMpEng.exe (3928) consumed 277430272 bytes.
14:24
Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: arma3_x64.exe (8552) consumed 12671430656 bytes, steamwebhelper.exe (11192) consumed 455454720 bytes, and MsMpEng.exe (3928) consumed 277446656 bytes.
14:25
The server Microsoft.XboxGamingOverlay_5.420.11102.0_x64__8wekyb3d8bbwe!App.AppXrfdt3p0f38tc4nxz7ajrd5as6ctb0dck.mca did not register with DCOM within the required timeout.
14:25
Faulting application name: GameBar.exe, version: 5.420.11102.0, time stamp: 0x5faaa7cb
Faulting module name: KERNELBASE.dll, version: 10.0.19041.662, time stamp: 0xec58f015
Exception code: 0xe06d7363
Fault offset: 0x000000000002d759
Faulting process ID: 0x24fc
Faulting application start time: 0x01d6d142971ab927
Faulting application path: C:\Program Files\WindowsApps\Microsoft.XboxGamingOverlay_5.420.11102.0_x64__8wekyb3d8bbwe\GameBar.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report ID: 213e2682-7f0f-4710-94a6-a3a8d3368d67
Faulting package full name: Microsoft.XboxGamingOverlay_5.420.11102.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
14:25
Arma 3
DX11 error: CreateTexture failed : E_OUTOFMEMORY
14:25 or 14:26 (do not exactly remember)
WerFault.exe - Application Error
The application was unable to start correctly (0xc000012d).
Click OK to close the application.
14:28
Faulting application name: bad_module_info, version: 0.0.0.0, time stamp: 0x00000000
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0x00000000
Fault offset: 0x0000000000000000
Faulting process ID: 0x2168
Faulting application start time: 0x01d6d13b16e18f8e
Faulting application path: bad_module_info
Faulting module path: unknown
Report ID: bff67e77-acab-4118-b937-942dc3373396
Faulting package full name:
Faulting package-relative application ID:
14:28
Faulting application name: ArmouryCrate.UserSessionHelper.exe, version: 3.0.0.0, time stamp: 0x5f9149ba
Faulting module name: ucrtbase.dll, version: 10.0.19041.546, time stamp: 0x43cbc11d
Exception code: 0xc0000409
Fault offset: 0x000000000007287e
Faulting process ID: 0xd40
Faulting application start time: 0x01d6d1430845659b
Faulting application path: C:\Program Files\ASUS\ARMOURY CRATE Lite Service\ArmouryCrate.UserSessionHelper.exe
Faulting module path: C:\Windows\System32\ucrtbase.dll
Report ID: 8c37e10b-f73b-4b08-a373-29944bb7c1c3
Faulting package full name:
Faulting package-relative application ID:
I do not understand how it could consume more than 12 GB when the FPS Monitor says that it used only 7.5GB and more than 8GB were free.
This is nonsense.
Now the effects are different.
The game window has disappeared, I can not alt-tab to it, but the process is running and using about 4 GB of RAM.
In two minutes the application has been closed by OS.
14:46
Application ("C:\Program Files\WindowsApps\Microsoft.XboxGamingOverlay_5.420.11102.0_x64__8wekyb3d8bbwe\GameBarFTServer.exe" -Embedding) (PID: 7736) has failed to complete a COM/RPC call because of an invalid message from server. User Action Try the operation again. If the problem persists, contact your system administrator.
15:34
Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: arma3_x64.exe (12272) consumed 12616028160 bytes, steamwebhelper.exe (11192) consumed 426983424 bytes, and MsMpEng.exe (3928) consumed 288530432 bytes.
15:37
Unable to start a DCOM Server: {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54} as Unavailable/Unavailable. The error:
"2147943855"
Happened while starting this command:
C:\Windows\System32\RuntimeBroker.exe -Embedding
15:37
The Windows Error Reporting Service service terminated with the following error:
The paging file is too small for this operation to complete.
15:37
A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect.
15:37
The Microsoft Account Sign-in Assistant service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.
15:37
Faulting application name: HxTsr.exe, version: 16.0.13426.20316, time stamp: 0x5fc90895
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc000012d
Fault offset: 0x0000000000000000
Faulting process ID: 0x2fec
Faulting application start time: 0x01d6d14cc670dd40
Faulting application path: C:\Program Files\WindowsApps\microsoft.windowscommunicationsapps_16005.13426.20316.0_x64__8wekyb3d8bbwe\HxTsr.exe
Faulting module path: unknown
Report ID: 9853de84-60c8-4fdf-90db-74a5a8ad8bba
Faulting package full name: microsoft.windowscommunicationsapps_16005.13426.20316.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: ppleae38af2e007f4358a809ac99a64a67c1
15:37
Faulting application name: bad_module_info, version: 0.0.0.0, time stamp: 0x00000000
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0x00000000
Fault offset: 0x0000000000000000
Faulting process ID: 0x2ff0
Faulting application start time: 0x01d6d1458d9ef510
Faulting application path: bad_module_info
Faulting module path: unknown
Report ID: ce17fed5-44b8-4e3d-9aa1-8f4118585bea
Faulting package full name:
Faulting package-relative application ID:
15:37
Faulting application name: NisSrv.exe, version: 4.18.2011.6, time stamp: 0x434b819b
Faulting module name: ucrtbase.dll, version: 10.0.19041.546, time stamp: 0x43cbc11d
Exception code: 0xc0000409
Fault offset: 0x000000000007287e
Faulting process ID: 0x14a4
Faulting application start time: 0x01d6d136fb94bbc3
Faulting application path: C:\ProgramData\Microsoft\Windows Defender\platform\4.18.2011.6-0\NisSrv.exe
Faulting module path: C:\Windows\System32\ucrtbase.dll
Report ID: e04ad3cc-c494-440c-91df-cdc65a42a932
Faulting package full name:
Faulting package-relative application ID:
15:38
The Microsoft Defender Antivirus Network Inspection Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
15:39
Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: arma3_x64.exe (12272) consumed 12372013056 bytes, steamwebhelper.exe (11192) consumed 426983424 bytes, and MsMpEng.exe (3928) consumed 289034240 bytes.
15:42
Faulting application name: bad_module_info, version: 0.0.0.0, time stamp: 0x00000000
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc000041d
Fault offset: 0x00007ff742d4affd
Faulting process ID: 0x2ff0
Faulting application start time: 0x01d6d1458d9ef510
Faulting application path: bad_module_info
Faulting module path: unknown
Report ID: 7515aedc-0ac3-493d-bfb6-53a4443e5765
Faulting package full name:
Faulting package-relative application ID:
15:43
File System Filter 'BEDaisy' (Version 10.0, 2020-11-26T14:41:34.000000000Z) unloaded successfully.
Arma 3
0xC000041D - STATUS_FATAL_USER_CALLBACK_EXCEPTION
According to BIS Wiki, https://community.bistudio.com/wiki/Arma_3_Unusual_process_exit#0xC000041D_-_STATUS_FATAL_USER_CALLBACK_EXCEPTION, There is a multiple reasons for this error... Damn...
If I have dual GPUs (Dual Radeon RX 570 8GB), do I have to set the video memory limit in Arma 3 launcher's parameters to 8192 ?
You don't have to set the memory limit for 8192 though that should prevent the GPU taking system memory for texture storage, well, maybe not entirely as the 8gb listed might actually be 8000mb and not 8192mb because manufacturers decided to.