UnityPlayer.dll - Every games made with it are randomly crashing

Unity Engine
1

Hello there
This issue has been first reported at different games supports something like two years back, maybe three. I think three now. They never managed to find any solution despite getting all logs, informations and reports needed to. The Pathfinder: Kingmaker support stated it as solved and corrected by a new patch after investigating on this issue, but it changed nothing and I got no news from them since it.
By researching on internet, I know I’m far from being the only one to get this exact issue. But I know about many games which corrected those kind of crashes during the first months after their release, solving it for a large majority of players but sadly not all.
I managed to find many solutions (like disabling Citrix, which I do not have) but none worked… And I purchased a new game made with Unity just yesterday, which is For the King, and it happened again. Sigh

Well! So, this is the problem :
Every game using UnityPlayer.dll is crashing randomly - it can be twice in a minute or never in an hour and has nothing to do with a particular moment on the game, main menu, loading, sort of combat, multiplayer or solo are the exact same - and looks exactly the same. They got little to no error message and with a little of investigation, they all turn against that file causing access violation with the same error code.
With FTK, we got a message issue, and I got a crash log. I’ll upload those two, they really are similar to the others I get from differents games.

If you want to, and need to, I’ll give you some hardware/software informations to help.
I got no issues at all playing any other game. I’m using Razer stuff that I know can cause compatibility issues (but idk if it could be it, here), using a second display without any particular software for it (though I used to have Display Fusion, which is now gone from my computer), am running Win10 and… Well, this is a start.
Would you like to help?

There is many games made with Unity to be released during 2020. I really would like to test and play them a bit without getting constant crashes… And I’d be really glad to help devs and players finding the issue and a solution because we are many to be stuck with it and without anyone caring.

Thanks you very much
(Sorry for my approximative english, this is not my former language)
Have a good and nice day

5892224--628304--5ePPdZZ.png

Error Log from For the King:

FTK [version: Unity 2017.2.2p2 (32bc645ba6f6)]

UnityPlayer.dll caused an Access Violation (0xc0000005)
in module UnityPlayer.dll at 0033:3e2811a1.

Error occurred at 2020-05-23_232336.
E:\SteamLibrary\steamapps\common\For The King\FTK.exe, run by LeLoup.
57% memory in use.
16332 MB physical memory [6893 MB free].
32716 MB paging file [15665 MB free].
134217728 MB user address space [134209350 MB free].
Write to location f3d02008 caused an access violation.

Context:
RDI: 0xf3d01f88 RSI: 0xf3a31050 RAX: 0x000000a8
RBX: 0xf3d01f58 RCX: 0x00000460 RDX: 0xf3d01ea8
RIP: 0x3e2811a1 RBP: 0x3f682f90 SegCs: 0x00000033
EFlags: 0x00010202 RSP: 0xd8bff6c0 SegSs: 0x0000002b
R8: 0x00000000 R9: 0xf3a31050 R10: 0x00000023
R11: 0xf3d01f58 R12: 0x00000000 R13: 0x00000000
R14: 0x00000813 R15: 0x00000000

Bytes at CS:EIP:
48 89 5c 18 08 48 8b 43 08 48 83 e0 fc f6 44 18

Stack:
0xd8bff6c0: 7e88ffc8 00000239 3dec232d 00007ffe …~9…-#.=…
0xd8bff6d0: 00000000 00000000 22bf0c60 00000239 ….."9... 0xd8bff6e0: f3d01f90 00000239 3e2b6d7a 00007ffe ....9...zm+>.... 0xd8bff6f0: 3f682f00 00007ffe 50aa3540 00000239 ./h?....@5.P9... 0xd8bff700: 00000000 00000000 00007522 00000000 ........"u...... 0xd8bff710: 00000290 00000000 3e2b5811 00007ffe .........X+>.... 0xd8bff720: 3f682f90 00007ffe 709dd960 00000239 ./h?....…p9…
0xd8bff730: 00000006 00000000 00000052 00000000 …R…
0xd8bff740: 3f6830f0 00007ffe 3e2b7587 00007ffe .0h?..u+>…
0xd8bff750: 00000010 00000000 3f682f90 00007ffe …/h?..
0xd8bff760: 00000028 00000000 00000006 00000000 (…
0xd8bff770: 00000000 00000000 3e2bac88 00007ffe …+>…
0xd8bff780: 00000028 00000000 00000000 00000000 (…
0xd8bff790: 00000000 00000000 00000000 00000000 …
0xd8bff7a0: 000141b0 00000000 00000000 00000000 .A…
0xd8bff7b0: 00000001 00000000 00000000 00007ffe …
0xd8bff7c0: 3f2d81a2 00007ffe 0000020c 00000239 …-?..9…
0xd8bff7d0: d8bff8e8 00000060 3ea90555 00007ffe …...U..>.... 0xd8bff7e0: d8bff8e8 00000060 00000001 00000000 ....…
0xd8bff7f0: f3ab5960 00000239 3ebde7b3 00007ffe Y..9......>.... 0xd8bff800: a0e2caf0 00000239 00000000 00000000 ....9........... 0xd8bff810: 0000141b 00000000 709bbf80 00000239 ...........p9... 0xd8bff820: 04000000 00000000 3e561e49 00007ffe ........I.V>.... 0xd8bff830: 00000006 7fffffff 047341f0 00000239 .........As.9... 0xd8bff840: d8bff948 00000060 3e8cb107 00007ffe H...…>…
0xd8bff850: 00000000 00000000 00000000 00000000 …
0xd8bff860: 70fd2060 00000239 00000006 00000239 .p9.......9... 0xd8bff870: fffffffe ffffffff 00000000 00000000 ................ 0xd8bff880: a0e2caf0 00000239 3e8d659c 00007ffe ....9....e.>.... 0xd8bff890: a1651c00 00000239 709df120 00000239 ..e.9... ..p9... 0xd8bff8a0: d8bffd30 00000060 00000000 00000000 0...…
0xd8bff8b0: a0702790 00000239 00002c23 00000239 .'p.9…#,…9…
0xd8bff8c0: 00000000 00000000 0000000a 00000000 …
0xd8bff8d0: 9ded4e90 00000239 3e8cc32d 00007ffe .N…9…-…>…
0xd8bff8e0: 00000000 00000000 70fd2060 00000239 … .p9... 0xd8bff8f0: 00000001 00000060 00000006 00000000 ....…
0xd8bff900: 0000141b 00000000 00000001 00007ffe …
0xd8bff910: 00000000 00000000 00000000 00000000 …
0xd8bff920: 0000000a 00000000 9ded4e90 00000239 …N…9…
0xd8bff930: 00000000 00000000 3e8d7201 00007ffe …r.>…
0xd8bff940: 9ded4e90 00000239 f3ab5960 00000239 .N…9…Y..9... 0xd8bff950: a1651c00 00000239 d8bffd30 00000060 ..e.9...0...…
0xd8bff960: d8bff9d0 00000060 3e600680 00007ffe ….....>…
0xd8bff970: d8bffb18 00000060 d8bffb10 00000060 ….......…
0xd8bff980: 3f000000 00000000 00000000 00000000 …?..
0xd8bff990: 00000000 00000000 00000000 00000000 …
0xd8bff9a0: 709df120 00000239 3e8d73bf 00007ffe …p9…s.>…
0xd8bff9b0: a1651c00 00000239 00000000 00000000 …e.9…
0xd8bff9c0: 00000000 00000000 00000000 00000000 …
0xd8bff9d0: d8bffae0 00000060 3e8d370e 00007ffe …....7.>.... 0xd8bff9e0: 9ded4d60 00000239 00000000 00000000 M…9…
0xd8bff9f0: 9ded4e90 00000239 0000000a 00000000 .N…9…
0xd8bffa00: 44700000 44070000 00000000 00007ffe …pD…D…
0xd8bffa10: 44700000 44070000 00000000 00000000 …pD…D…
0xd8bffa20: 00000000 00000000 00000000 3f800000 …?
0xd8bffa30: 00000000 00000000 00000000 00000000 …
0xd8bffa40: 00000000 00000000 00000000 00000000 …
0xd8bffa50: 00000000 00000000 00000000 00000000 …
0xd8bffa60: 00000000 00000000 00000000 00000000 …
0xd8bffa70: 00000000 00000000 00000000 00000000 …
0xd8bffa80: 00000000 00000000 00000000 00000000 …
0xd8bffa90: 00000000 00000000 00000000 00000000 …
0xd8bffaa0: 00000000 00000000 00000000 00000000 …
0xd8bffab0: 00000000 00000000 00000000 00000000 …
0xd8bffac0: 00000000 00000000 003e03e8 00000239 …>.9…
0xd8bffad0: 00000000 00000000 00000000 00000000 …
0xd8bffae0: 00000000 00000000 00000000 00000000 …
0xd8bffaf0: 00000000 00000000 d8bf0101 00000060 …... 0xd8bffb00: 00000000 00000000 3e4c4660 00007ffe ........FL>…
0xd8bffb10: 00000000 00000000 00000000 00000000 …
0xd8bffb20: 00001008 00000000 44f00000 44870000 …D…D
0xd8bffb30: 00000000 00000000 3e4c4d6f 00007ffe …oML>…
0xd8bffb40: 00001008 00000000 00000002 00000000 …
0xd8bffb50: 00001008 00000000 00000000 00000000 …
0xd8bffb60: 00001008 00000000 00000000 00000000 …
0xd8bffb70: 00000000 00000000 4c8fa6dc 00007ffe …L…
0xd8bffb80: 00000e2c 00000000 3eb2a31b 00007ffe ,…>…
0xd8bffb90: 00000000 00000000 7f661e90 00000239 …f.9…
0xd8bffba0: 00000001 00000000 00000000 00000000 …
0xd8bffbb0: 00000000 00000000 3eb2a4ca 00007ffe …>…
0xd8bffbc0: 00001008 00000000 d8bffd30 00000060 …0…... 0xd8bffbd0: 00000000 00000000 00000000 00000000 ................ 0xd8bffbe0: 00000001 00007ffe 0000000b 00000000 ................ 0xd8bffbf0: 00050050 00000000 000014fe 00000000 P............... 0xd8bffc00: 138911bc 00000000 00000001 00000000 ................ 0xd8bffc10: 015b2255 00000359 000001af 00000000 U"[.Y........... 0xd8bffc20: 00000000 00000000 3eb3703d 00007ffe ........=p.>.... 0xd8bffc30: 00000004 00000000 d8bffd30 00000060 ........0...…
0xd8bffc40: 00000000 00000000 00000000 00000000 …
0xd8bffc50: 00000000 00000239 00000000 00000000 …9…
0xd8bffc60: 0000001d 006b0073 006f0056 0075006c …s.k.V.o.l.u.
0xd8bffc70: 00000000 005c0031 00000000 00000000 …1..…
0xd8bffc80: 65726170 5748746e 0000444e 00790072 parentHWND…r.y.
0xd8bffc90: 0000000a 00000000 00000044 00700041 …D…A.p.
0xd8bffca0: 00000000 00000000 65646968 646e6957 …hideWind
0xd8bffcb0: 0000776f 00720062 0000000a 00000000 ow…b.r…
0xd8bffcc0: 00000044 00610065 6f5ba4a0 00000239 D…e.a…[o9…
0xd8bffcd0: 6f5ba430 00000239 709b7940 00000239 0.[o9…@y.p9…
0xd8bffce0: 00000042 00000000 00540020 00650068 B… .T.h.e.
0xd8bffcf0: 00000042 00000000 00000044 00540046 B…D…F.T.
0xd8bffd00: 709ccc10 00000239 709ccc38 00000239 …p9…8…p9…
0xd8bffd10: 709ccc38 00000239 00001010 00000000 8…p9…
0xd8bffd20: 709cb750 00000239 00000036 00000000 P…p9…6…
0xd8bffd30: 6db60000 00000239 00000036 00000000 …m9…6…
0xd8bffd40: 00000044 00000000 709cb790 00000239 D…p9…
0xd8bffd50: 0000003e 00000000 d8bffe40 00000060 >…@…`…
0xd8bffd60: 0000003e 00000000 00000044 00007ff7 >…D…
0xd8bffd70: 709c26f0 00000239 00000012 00000000 .&.p9…
0xd8bffd80: 00000000 00000000 0000000d 00000000 …
0xd8bffd90: 00000044 00000239 00000000 00000000 D…9…
0xd8bffda0: 004b5446 6c502079 72657961 00000000 FTK.y Player…
0xd8bffdb0: 00000003 00000000 00000044 00000000 …D…
0xd8bffdc0: 6f5ba430 00000239 6f5ba430 00000239 0.[o9…0.[o9…
0xd8bffdd0: 709afc10 00000239 00000051 00000000 …p9…Q…
0xd8bffde0: 00000000 00000000 00000051 00000000 …Q…
0xd8bffdf0: 00000044 00000502 709cb710 00000239 D…p9…
0xd8bffe00: 0000003b 00000000 99ea4acd 00007ffe ;…J…
0xd8bffe10: 0000003b 00000000 00000044 00007ff7 ;…D…
0xd8bffe20: 709b78a0 00000239 00000041 00000000 .x.p9…A…
0xd8bffe30: 00000fa0 00000000 00000041 00000000 …A…
0xd8bffe40: 00000044 00000000 709b7850 00000239 D…Px.p9…
0xd8bffe50: 00000040 00000000 6db63cc0 00000239 @Anonymous_0dca7b137ad012aacdc583f42cd18201 .<.m9…
0xd8bffe60: 0000003f 00000000 00000044 00000239 ?..D…9…
0xd8bffe70: 00000000 00000000 00000000 00000000 …
0xd8bffe80: 00000000 00000000 00000000 00000000 …
0xd8bffe90: 00000000 00000000 00000000 00000000 …
0xd8bffea0: 00000000 00000000 00000000 00000000 …
0xd8bffeb0: 00000000 00000000 0000000a 00000000 …
0xd8bffec0: 00000000 00000000 471713ee 00007ff7 …G…
0xd8bffed0: 00000000 00000000 00000000 00000000 …
0xd8bffee0: 00000000 00000000 0000000a 00000000 …
0xd8bffef0: 00000000 00000000 00000000 00000000 …
0xd8bfff00: 00000000 00000000 9b517bd4 00007ffe …{Q…
0xd8bfff10: 00000000 00000000 00000000 00000000 …
0xd8bfff20: 00000000 00000000 4c860000 00007ffe …L…
0xd8bfff30: 00000000 00000000 9ceece51 00007ffe …Q…
0xd8bfff40: 00000000 00000000 00000000 00000000 …
0xd8bfff50: 00000000 00000000 00000000 00000000 …
0xd8bfff60: 00000000 00000000 00000000 00000000 …
0xd8bfff70: 00000000 8b05960c 00000000 00000000 …
0xd8bfff80: 00000000 00000000 99f3fd00 00007ffe …
0xd8bfff90: d8bfe840 00000060 ffe12f66 b0c00007 @…`…f/…
0xd8bfffa0: 12f66b0c 00007ffe d8bfe840 00000060 .k…@…`…
0xd8bfffb0: 00000202 00000000 00000000 00000000 …
0xd8bfffc0: 00000000 00000000 00000000 00000000 …
0xd8bfffd0: 00000000 00000000 00000000 00000000 …
0xd8bfffe0: 00000000 00000000 00000000 00000000 …
0xd8bffff0: 00000000 00000000 00000000 00000000 …

Module 1
C:\WINDOWS\SYSTEM32\xinput1_3.dll
Image Base: 0x00400000 Image Size: 0x0001e000
File Size: 107368 File Time: 2007-04-04_195422
Version:
Company: Microsoft Corporation
Product: Microsoft® DirectX for Windows®
FileDesc: Microsoft Common Controller API
FileVer: 9.18.944.0
ProdVer: 9.18.944.0

Module 2
C:\WINDOWS\SYSTEM32\xinput1_2.dll
Image Base: 0x00400000 Image Size: 0x00018000
File Size: 83736 File Time: 2006-07-28_103108
Version:
Company: Microsoft Corporation
Product: Microsoft® DirectX for Windows®
FileDesc: Microsoft Common Controller API
FileVer: 9.14.701.0
ProdVer: 9.14.701.0

Module 3
C:\WINDOWS\SYSTEM32\xinput1_1.dll
Image Base: 0x00400000 Image Size: 0x00018000
File Size: 83664 File Time: 2006-03-31_133948
Version:
Company: Microsoft Corporation
Product: Microsoft® DirectX for Windows®
FileDesc: Microsoft Common Controller API
FileVer: 9.12.589.0
ProdVer: 9.12.589.0

Module 4
E:\SteamLibrary\steamapps\common\For The King\FTK_Data\Plugins\steam_api64.dll
Image Base: 0x58910000 Image Size: 0x00040000
File Size: 245536 File Time: 2020-05-23_205516
Version:
Company: Valve Corporation
Product: Steam Client API
FileDesc: Steam Client API
FileVer: 3.92.72.58
ProdVer: 1.0.0.1

== [end of error.log] ==

2

Well.
We are many to face these issues. No one’s giving a shit about it. I have seen plenty of thread everywere. The only ones to receive any answer are the ones posted in little independant communities. At least, they try to help. But the ones working with Unity (or the devs from the applications concerned) are all mute.

This issue isn’t uncommon and it’s in your hands. Do something

1 Like
3

There should be a dump file with more useful debugging information in it. You can locate it with instructions here: Unity - Manual: Log files

Can you test these games on a different computer?

Upload that so someone can have a better look at the stack, and maybe guess as to the cause.

Keep in mind we do not have source access to Unity. In no way is it “on our hands”. In fact, our hands are often quite tied when it comes to internal engine issues.

4

Hi, thanks you very much, first. You’re trying to help and it’s a brave and kind move, I’d like to salute you for that.

I checked the instructions and locations found on your link but found absolutely nothing : I want you to be sure to understand that I do not use Unity as a tool myself but am experiencing issues coming from unity elements used by released games. I, myself, understand that you may not be the right hands to work on it, but where are they if it is not under these unity forums? That’s my proper statement and I’m sure you can hear it.

So, this is to clarify, just in case :stuck_out_tongue:

That being clear… Mh, I cannot myself test those games on another computer, but they’ve been released months and months ago, for some people they’re working great and it’s a majority. I’m playing with friends and they do not face those problems I’m facing, but I do know, searching on internet, other people stuck with 'em like I am actually. So it could be many things, maybe compatibility issues, I don’t know… I’m pretty sure I could play with tranquillity if I had to buy another new computer, but I’d rather not and find a good solution.
I can only rely on those crash logs, or pop some new logs.

I mean, that’s something I’ve never seen before. One kind of crash for multiple games, and one unique sentance “unityplayer.dll caused access violation”, many other people getting the exact same issue and zero solution (except the Citrix case). It could be something similar to this Citrix case, a software getting conflict and crashing the games using unityplayer.dll… But there’s 0 work around.

5

What are your computer specs? (OS, hardware etc)

How many other Unity games have you tried? Do they also produce crash reports?

Without a .dmp file, all I can say is that some routine in UnityPlayer.dll tried to write to memory that it doesn’t have access to. This could be caused by a countless number of things (bug in Unity, problems with other software, especially antivirus software, faulty RAM etc).

A .dmp file would really be needed to have any chance at guessing the cause beyond that. Perhaps one of the other games produce one when they crash.

I recommend disabling your antivirus, and also running a memory test (e.g. memtest86) to verify your RAM is stable. It might also be worth trying other stress tests (e.g. furmark, prime95) to verify the stability of your PC.

6

this thread is dead but i’d still like to get some help

6361896--707985--um.PNG

7

Problem Event Name: APPCRASH
Application Name: Among Us.exe
Application Version: 2019.4.9.65162
Application Timestamp: 5f3b453b
Fault Module Name: UnityPlayer.dll
Fault Module Version: 2019.4.9.65162
Fault Module Timestamp: 5f3b46de
Exception Code: c0000005
Exception Offset: 0024bf10
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

8

How would I go about getting this information

9

Im facing a similar issue, any one knows a workaround?

10

Bloons TD 6 on steam also keeps randomly crashing. I’ve tried RimWorld as well and it had the same error. Below are details for the most recent Bloons TD 6 crash.

Below are the event viewer details and my Windows 10 PC summary. I’ve uploaded a CrashDump from C:\Users<user>\AppData\Local\CrashDumps\BloonsTD6.exe.6336.dmp
And also DxDiag, don’t know if it’s useful.

I have recently bought a SAGER NP7958F1 (CLEVO NH58AF1), which includes NVIDIA GeForce RTX 2070 8GB GDDR6. Could this possibly be a hardware issue? I’ve downloaded the latest NVIDIA driver via GeForce Experience 460.79. Other drivers are also downloaded straight from Sager website. AMD drivers are downloaded via Radeon Software Adrenalin 2020 (their auto detect driver downloader).
I’ve done memtest86 and SSDLife, RAM and SSD seems fine. Also Cinebench for CPU and Unigine Heaven for GPU. I’ll try 3DMark Fire Strike benchmarks.

I’ve also read there are a lot of issues with Windows 10 20H1 and 20H2 releases. I might try rolling back to 1909 or earlier.
Please let me know if there are any other info needed to diagnose the issue.

EVENT VIEWER

Faulting application name: BloonsTD6.exe, version: 2019.4.1.49221, time stamp: 0x5eea88f6
Faulting module name: UnityPlayer.dll, version: 2019.4.1.49221, time stamp: 0x5eea8a56
Exception code: 0xc0000005
Fault offset: 0x00000000004f3faa
Faulting process ID: 0x18c0
Faulting application start time: 0x01d6cfc2150b872a
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\BloonsTD6\BloonsTD6.exe
Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\BloonsTD6\UnityPlayer.dll
Report ID: 684b01ce-7cc1-463c-9b73-421e6e3377cc
Faulting package full name:
Faulting package-relative application ID:

BloonsTD6.exe
2019.4.1.49221
5eea88f6
UnityPlayer.dll
2019.4.1.49221
5eea8a56
c0000005
00000000004f3faa
18c0
01d6cfc2150b872a
C:\Program Files (x86)\Steam\steamapps\common\BloonsTD6\BloonsTD6.exe
C:\Program Files (x86)\Steam\steamapps\common\BloonsTD6\UnityPlayer.dll
684b01ce-7cc1-463c-9b73-421e6e3377cc

WINDOWS 10 ABOUT YOUR PC

Device name DESKTOP-ELKMMNI
Processor AMD Ryzen 5 3600 6-Core Processor 3.59 GHz
Installed RAM 32.0 GB (31.9 GB usable)
Device ID 48522D3D-819F-4359-AD77-2FE4724CCE82
Product ID 00330-80000-00000-AA290
System type 64-bit operating system, x64-based processor
Pen and touch No pen or touch input is available for this display

Edition Windows 10 Pro
Version 20H2
Installed on ‎09/‎12/‎2020
OS build 19042.685
Experience Windows Feature Experience Pack 120.2212.551.0

EDIT!!!

By the way I’ve also included the Crash_2020* data. For some reason it was located in the temp folder C:\Users<user>\AppData\Local\Temp\Ninja Kiwi\BloonsTD6\Crashes

6612385–752518–DxDiag.txt (94.8 KB)
6612385–752524–BloonsTD6.exe.6336.zip (7.36 MB)
6612385–752548–Crash_2020-12-11_143205157.zip (44.8 KB)

11

I struggled with this issue for the better part of a year as far as I’m aware. Every single game made on Unity would crash in anywhere from 2 minutes to 12 hours of play (average 1/hr), with no indication it was happening in specific areas/scenarios within the games. Tarkov, Rimworld, Outward, Valheim were all games that had these random crashing issues(note different Unity Engine versions between these games). Battlefield 4,1,5/CallofDutyMW/Snowrunner are all games that I had zero issues with. No issues with other programs. The common thread among the ctds was the “0xc0000005” memory access violation, sometimes with unityplayer.dll, other times with other dlls, showing up in event viewer. Never had Citrix, no overclock, and tried every combination of GPU driver, Windows10 version, Audio driver, with loads of DDU, and anything else I could think of to no avail.

For some reason it seems that Unity doesn’t jive with my default XMP profile that has my RAM running at 3200mhz. I set the RAM to 3000mhz, leaving XMP ‘on’ and letting ratios auto-adjust. After a couple of weeks with ZERO crashes, I went back to the 3200mhz setting and crashed within 2 hours. I then set it to 3400mhz, still changing nothing but speed in the BIOS, and haven’t had a crash in another 2 weeks of gaming.

So anyone having this issue, try making adjustments to your RAM speed in BIOS and see if that helps you. Like I said all I adjusted was the speed away from the default DDR4-3200mhz. Maybe you’ll have to turn off XMP, adjust voltages/ratios, but it’s worth a shot.

I’m not the type to so much as show my face online, but seeing the way some people were treated here and other places while scouring around for answers left a sour enough taste in my mouth that I had to make a post.This issue may not be a common occurrence, but my experience is that this (still) is definitely a Unity Engine problem.

Specs for posterity:
CPU: Intel i5-9600k
RAM: Corsair Vengence DDR4-3200
MOBO: ASUS Prime Z390-A
GPU: MSI 1080ti Lightning Z

1 Like
12

XMP profile is overclocking. Your RAM was overclocked and not stable. This is consistent with the “memory access violation” error - it is likely that a pointer or something was being corrupted, and this caused Unity to try to access memory locations it can’t access.

It is possible that Unity is doing something in a unique-but-perfectly-valid way that other engines aren’t, and this is triggering the bug in your specific case. This is not something that Unity can fix.

1 Like
13

I’m aware of that fact. An overnight on Memtest and a litany of other stress tests seem to suggest otherwise. My issue is “fixed,” and I never turned XMP off. Currently running at 3400mhz, as opposed to the default 3200mhz, changing nothing with voltages, and have no ctds. If you’re saying Unity and only Unity is sussing out a memory instability while specifically clocked at 3200mhz, I wouldn’t have the knowledge to refute. Just seems a bit odd to me to say that everything is working as intended and it’s not even something that could be investigated.

14

Stress tests do not guarantee stability. Running your equipment within its rated specifications is the only way to guarantee stability (assuming that nothing is faulty). Bad RAM overclock can cause all sorts of strange, esoteric and rare problems. You are probably better off disabling XMP.

Yes

No - No one can run every piece of software in existence. It is likely other software out there would trigger a similar crash.

If overclocking your computer causes software crashes then there isn’t much any software developer can do about that, except tell you not to overclock your computer.

15

The RAM is well within ‘rated’ specifications of 3200mhz while running at 3200mhz I’d think, and as I said I’m currently at 3400mhz with no voltage or timing change, and free of any issues Unity or otherwise. If you’re suggesting I disable Intel Turbo Boost and run my RAM at 2133mhz just to make sure my Unity games run stable, I think I’ll pass.

Perhaps there are other pieces of software out there that would trigger this in my system, but I have yet to come across any. So in my vacuum, I see a problem that revolves solely around Unity.

My knowledge of software development is nowhere near sufficient to make any claims, but when I have 99 software developers say “overclock* away!” and 1 says “your hardware is unstable” it’s going to give regular old me pause as to where the problem lies.

Like I said the issue is resolved on my end. I get to play Unity games AND don’t have to take a not-insignificant performance hit disabling XMP or Turbo Boost. Chalking it up to an “island of instability” quirk at 3200mhz or other eGremlin beyond my scope and moving on.

The main focus of my post was to maybe help others who’ve run into a similar issue and exhausted all of the canned fixes. Apologies for getting off the rails.

1 Like
16

When you buy “3200Mhz” RAM with a JEDEC profile of 2133Mhz, you are buying 2133Mhz ram. I assume that the actual ram chips are pretty low-binned to have a rating that slow.

I have DDR3 Corsair Vengeance RAM in my PC, and it won’t even post with XMP turned on. They have a XMP profile of 1866, but a JEDEC profile of just 1333. I assume that the Vengeance line of modules are just basically cheap RAM “gamified” to sell them at a higher price.

Overclock away, but you must accept all the risks doing so.

17

You’re not giving us much to work with, even if the issue could be investigated. As @bobisgod234 said, overclocking issues can present themselves in either random or some very specific circumstances. If Unity is exercising the path that your RAM just doesn’t like at that frequency, and causes memory read errors, there’s literally nothing we can do about it. It’s not something you can detect programmatically and work around. However, if the timing issues expose race conditions in the engine and the crashes are not actually caused by memory errors, then it’s entirely different business. It’s impossible to tell between the two without seeing the crash dumps, though.

2 Likes
18

The Intel i5 9600k includes a memory controller rated to a maximum of DDR4 2666. Running memory higher, even within the memory’s own specs, is an overclock of the memory controller on the CPU and not guaranteed to be stable. In fact, Intel voids the warranty on this CPU if you run memory higher than the 2666MHz spec.

If anything in your computer is overclocked, the first thing you should do to test is stop overclocking and see if you can still reproduce the issue. That would mean you need to run your memory no higher than 2666 to run the memory controller within max spec.

The first Intel CPU’s to support 3200MHz memory without overclocking the memory controller actually is the brand new 11th gen parts. AMD has supported 3200MHz out of the box for a while though.

This isn’t about making it stable “with Unity”. Different software will have different access patterns on the hardware. Even though the access patterns are different, if your overclock is stable it shouldn’t have any problem. If your overclock is not stable, specific access patterns could result in a problem while you don’t see the problem running other software which uses an entirely different access pattern.

But it is your computer, do what you want.

2 Likes
19

This might be the most helpful post I have seen on this topic in months. I, like many other forums posters all over, have this UnityPlayer.dll access violation issue across many many unity games (Fall Guys, Valheim, Kingdom, Totally Reliable Delivery Service, Children of Morta, many many more). The problem started for me in August of 2020 when I first began playing fall guys. Prior to that, on the exact same hardware setup, I was putting hundreds of hours into games like Tarkov and other unity games with no issues at all.

In my case, most of the time I get this .dll error, but sometimes my computer deadlocks until I manually reboot.

I have tried “everything” (everything I know to do), including all sorts of driver wipes/upgrades/rollbacks, new RAM, new PSU, 2 fresh windows installs on different drives, stress testing everything with multiple tests for hours, much more, but most relevant: under clocking my RAM. My original RAM was 4x4GB 2133Hz RAM, that I manually clocked to 2133Hz and ensured XMP was off. My most recent RAM (bought just a couple of days ago to try and fix this) is 3600, but I have clocked it well below that for testing. I have also disabled any sort of CPU boosting, yet the problem persists very consistently.

I have a rather stupid theory, but the only change I can think of in August 2020 was that I began playing a lot of games using HDMI out using HDMI audio. Games like Phasmophobia and Golf with your Friends have never crashed for me, but I always exclusively used them over DisplayPort and a headset. The other games I mostly play on my TV. The biggest exception to this is Valheim, which is unplayable no matter what setup I use. This is really the only thing I know to test more and focus on, as I’ve done so much with everything else.

So far, I’ve been almost entirely convinced this is not a hardware issue from all the testing and reproducing I have done. But your point about the i5 memory controller rating has made me question if there are “overclocked” things in my set-up that I am totally unaware of. While I am somewhat experienced with builds, I definitely have almost no experience with overclocking. I just buy parts based on QVL lists mostly.

I would really love your insight on this, as you have brought the most concrete response to this that I have seen. I don’t want to blow up this thread with all my tests, logs, etc, but man I sure will if you have any interest in helping at all.

Edit to add: [Zerrbit]( https://discussions.unity.com/t/792491 members/zerrbit.7204369/)'s solution seemed like a god send; we have the exact same RAM, MOBO, and CPU currently. However I’m not having the same luck with the RAM speed settings

1 Like
20

Thanks for the kind words. Would you mind sharing your current computer specs? You said you switched to using HDMI instead of DisplayPort around the time this started. Have you reproduced this at all on DisplayPort? Is that with the same graphics card? You replaced the PSU, what wattage and is it a name brand?

I’m asking about specs and PSU, because when you run a Unity game (or really any game, but Unity is a popular game engine so you will commonly see general problems in Unity games just because many games are Unity games) it will use your hardware a lot harder than a typical application. This will use more power. If you’re pulling power to the limit of what the PSU can handle, this can manifest in voltage drops which can cause rare problems which don’t show up during synthetic stress tests. For example, you run a stress test on the CPU, then one on the RAM, then one on the graphics card, everything looks fine. But when you run a game you are stressing all at the same time, drawing more power than during the stress tests, and then the issue occurs.

The new higher end graphics cards from both Nvidia and AMD are known to cause periodic power draw spikes well above norm. Some reviewers are recommending 1k+ power supplies for this reason, even though the vast majority of the time you don’t come anywhere near that level of usage.