Valheim ошибка unityplayer dll

Обновлено: 28.01.2023

14 фев в 6:47

I have a problem to run this game more than 20 minutes.
Every time I get a crash with this message:
<<Valheim — Unity 2019.4.16f1_e05b6e02d63e>>
After rejoining my world with my character it is like to load a old save game.
The completely process from the last time is away!

What I have tried to fix this Problem:
— Reinstallation of Windoof 10
— Switching the GPU (2080ti to 1070)
— Nvidia driver update
— Nvidia Control Panel settings switching
— Physix
— Vsync
— Tripple Buffering

Nothing helped me. The problem still remains.

System:
CPU: Intel I7 3770K
RAM: 16GB DDR3
GPU: 2080ti / 1070

Thanks for your help!

14 фев в 8:00

I have a problem to run this game more than 20 minutes.
Every time I get a crash with this message:
<<Valheim — Unity 2019.4.16f1_e05b6e02d63e>>
After rejoining my world with my character it is like to load a old save game.
The completely process from the last time is away!

What I have tried to fix this Problem:
— Reinstallation of Windoof 10
— Switching the GPU (2080ti to 1070)
— Nvidia driver update
— Nvidia Control Panel settings switching
— Physix
— Vsync
— Tripple Buffering

Nothing helped me. The problem still remains.

System:
CPU: Intel I7 3770K
RAM: 16GB DDR3
GPU: 2080ti / 1070

Thanks for your help!

Googled that error message for couple minutes and it could be caused by your gpu being overclocked, even with stock overclock. or caused by 3rd party applications like geforce now or msi afterburner etc.
Also someone fixed issue with this error by turning off their vpn.

14 фев в 8:43

I have a problem to run this game more than 20 minutes.
Every time I get a crash with this message:
<<Valheim — Unity 2019.4.16f1_e05b6e02d63e>>
After rejoining my world with my character it is like to load a old save game.
The completely process from the last time is away!

What I have tried to fix this Problem:
— Reinstallation of Windoof 10
— Switching the GPU (2080ti to 1070)
— Nvidia driver update
— Nvidia Control Panel settings switching
— Physix
— Vsync
— Tripple Buffering

Nothing helped me. The problem still remains.

System:
CPU: Intel I7 3770K
RAM: 16GB DDR3
GPU: 2080ti / 1070

Thanks for your help!

Googled that error message for couple minutes and it could be caused by your gpu being overclocked, even with stock overclock. or caused by 3rd party applications like geforce now or msi afterburner etc.
Also someone fixed issue with this error by turning off their vpn.

14 фев в 8:48

Googled that error message for couple minutes and it could be caused by your gpu being overclocked, even with stock overclock. or caused by 3rd party applications like geforce now or msi afterburner etc.
Also someone fixed issue with this error by turning off their vpn.

All this do not fixed the problem. I have the same issue, also found the descriptions by google and more as you listed here (I listed it in an other thread on the next page). Even a clear Windwos 10 re-install did not fix it.
Did you play with executables and compatibilities?
Did you try older gpu drivers/updates motherboard/cpu etc?

Which version of windows 10 are you both running?
Think there were some updates released recently, might be linked to that.. perhaps try to uninstall couple latest w10 updates, think they auto install during initial installation as a default

14 фев в 9:17

I have the same issue using Win7.

Things I am currently trying (I tried most everything found on Google searches already, including nvidia control panel tweaks): I am currently trying out a -opengl switch in launcher parameters in case it is a dx11 issue, and found a 2020 realtek driver some computermaker (dell or levovo or someone) tweaked for their users (latest official realtek is 2017). Set max framerates at 30, running offline mode with fullscreen, installed k-lites codec fixes, i usually «logout» every 15 minutes or so to save progress and check for any suggestions again.

This latest run, I haven’t «yet» rebooted, but everytime i thought I had a fix it eventually resatarted my computer again 🙁 so i am not that optimistic that it is something we can fix on our end, but I am really motivated to keep trying. Everytime I find another «solution» on google search, I try that but they never work for me 🙁

14 фев в 9:20

I have a problem to run this game more than 20 minutes.
Every time I get a crash with this message:
<<Valheim — Unity 2019.4.16f1_e05b6e02d63e>>
After rejoining my world with my character it is like to load a old save game.
The completely process from the last time is away!

What I have tried to fix this Problem:
— Reinstallation of Windoof 10
— Switching the GPU (2080ti to 1070)
— Nvidia driver update
— Nvidia Control Panel settings switching
— Physix
— Vsync
— Tripple Buffering

Nothing helped me. The problem still remains.

System:
CPU: Intel I7 3770K
RAM: 16GB DDR3
GPU: 2080ti / 1070

Thanks for your help!

Googled that error message for couple minutes and it could be caused by your gpu being overclocked, even with stock overclock. or caused by 3rd party applications like geforce now or msi afterburner etc.
Also someone fixed issue with this error by turning off their vpn.

VPN is deactivated. The OS is up to date and the ,Net frameworks too.
And it is not working for me.

14 фев в 9:36

All this do not fixed the problem. I have the same issue, also found the descriptions by google and more as you listed here (I listed it in an other thread on the next page). Even a clear Windwos 10 re-install did not fix it.

Did you play with executables and compatibilities?
Did you try older gpu drivers/updates motherboard/cpu etc?

Which version of windows 10 are you both running?
Think there were some updates released recently, might be linked to that.. perhaps try to uninstall couple latest w10 updates, think they auto install during initial installation as a default
First of all, thank you for your help and advices, you are the first one who replies to this topic!

Its Windows 10 Pro and there are no executables in the background. First after the clean re-install, I installed the necassary graphic driver followed by the steam client and finally Valheim, so just the pre-installed system-drivers were installed, to test whether it works or not . Even after a new crash I did install the rest of the current drivers. VPN is disabled.

First I will choose your advice to run it in compatibility mode, thats what I have not tried untill now. If this do not work I will check the latest windows updates.

I have a problem to run this game more than 20 minutes.
Every time I get a crash with this message:
<<Valheim — Unity 2019.4.16f1_e05b6e02d63e>>
After rejoining my world with my character it is like to load a old save game.
The completely process from the last time is away!

What I have tried to fix this Problem:
— Reinstallation of Windoof 10
— Switching the GPU (2080ti to 1070)
— Nvidia driver update
— Nvidia Control Panel settings switching
— Physix
— Vsync
— Tripple Buffering

Nothing helped me. The problem still remains.

System:
CPU: Intel I7 3770K
RAM: 16GB DDR3
GPU: 2080ti / 1070

Thanks for your help!

I have the same problem. The game starts only if the drivers are completely removed. Through the DDU application, but when you install the driver, the problem remains
14 фев в 11:37

Wish I knew hot to help. will try to think of some other stuff that often causes issues in games.

Just checked their official bug list and i couldnt see this error there- would strongly recommend to submit it there asap to get this issue exposed to devs:

Edit: Btw, if you go to C:UsersusernameAppDataLocalLowIronGateValheim
There should be a player.log — does it show any error messages there?

Alternatively, there is a path for error log:

Maybe post some of the errors here so we can see and try to narrow down root cause?

14 фев в 13:26

Wish I knew hot to help. will try to think of some other stuff that often causes issues in games.

Just checked their official bug list and i couldnt see this error there- would strongly recommend to submit it there asap to get this issue exposed to devs:

Edit: Btw, if you go to C:UsersusernameAppDataLocalLowIronGateValheim
There should be a player.log — does it show any error messages there?

Alternatively, there is a path for error log:

Maybe post some of the errors here so we can see and try to narrow down root cause?

Firstly, sorry for the long message!

Ok, I have not played scince noon, so I cannot tell you about crash fix but I followd your instructions to find the crash report! Its following below but its a very long text file, so I cut it. If you need the rest I will post it too, but this is quite to deep to my knowledge.

Valheim by IronGate [version: Unity 2019.4.16f1_e05b6e02d63e]

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

Error occurred at 2021-02-14_153624.
D:GamesSteamsteamappscommonValheimvalheim.exe, run by username.

39% physical memory in use.
16303 MB physical memory [9847 MB free].
3570 MB process peak paging file [3367 MB used].
2654 MB process peak working set [2475 MB used].
System Commit Total/Limit/Peak: 10098MB/19247MB/10515MB
System Physical Total/Available: 16303MB/9847MB
System Process Count: 176
System Thread Count: 2340
System Handle Count: 79772
Disk space data for ‘C:UsersusernameAppDataLocalTempIronGateValheimCrashesCrash_2021-02-14_143617263’: 201330589696 bytes free of 239384428544 total.

Read from location FFFFFFFFFFFFFFFF caused an access violation.

Context:
RDI: 0x000001db7ceae188 RSI: 0x000001daaec4ec68 RAX: 0x0100000000000018
RBX: 0x000001db7ceae180 RCX: 0x000001daaec4ec68 RDX: 0x000001db7ceae190
RIP: 0x00007ffcfc81a08b RBP: 0x00007ffcfd1f6140 SegCs: 0x000001db00000033
EFlags: 0x0000000000010206 RSP: 0x00000057f85eed90 SegSs: 0x000001db0000002b
R8: 0x0000000000000000 R9: 0x000001da8d220160 R10: 0x00007ffcfd1e93e8
R11: 0x000001daaec4ec68 R12: 0x000001da8d1f3801 R13: 0x0000000000000002
R14: 0x000001db7ceae190 R15: 0x0000000000000000

Bytes at CS:EIP:
48 83 4c 18 10 02 48 89 5c 18 08 48 83 0f 01 f6

Mono DLL loaded successfully at ‘D:GamesSteamsteamappscommonValheimMonoBleedingEdgeEmbedRuntimemono-2.0-bdwgc.dll’.

Stack Trace of Crashed Thread 16776:
0x00007FFCFC81A08B (UnityPlayer) UnityMain
0x00007FFCFBFB895D (UnityPlayer) UnityMain
0x00007FFCFBFB718E (UnityPlayer) UnityMain
0x00007FFCFBFB2890 (UnityPlayer) UnityMain
0x00007FFCFBFB5619 (UnityPlayer) UnityMain
ERROR: SymGetSymFromAddr64, GetLastError: ‘Es wurde versucht, auf eine unzulässige Adresse zuzugreifen.’ (Address: 00007FFCFBB5E9DE)
0x00007FFCFBB5E9DE (UnityPlayer) (function-name not available)
ERROR: SymGetSymFromAddr64, GetLastError: ‘Es wurde versucht, auf eine unzulässige Adresse zuzugreifen.’ (Address: 00007FFCFBB3E771)
0x00007FFCFBB3E771 (UnityPlayer) (function-name not available)
ERROR: SymGetSymFromAddr64, GetLastError: ‘Es wurde versucht, auf eine unzulässige Adresse zuzugreifen.’ (Address: 00007FFCFBAE69A3)
0x00007FFCFBAE69A3 (UnityPlayer) (function-name not available)
ERROR: SymGetSymFromAddr64, GetLastError: ‘Es wurde versucht, auf eine unzulässige Adresse zuzugreifen.’ (Address: 00007FFCFBAE7A66)
0x00007FFCFBAE7A66 (UnityPlayer) (function-name not available)
0x00007FFCFBFC7C9F (UnityPlayer) UnityMain
0x00007FFCFBFC7C07 (UnityPlayer) UnityMain
0x00007FFCFBFC7A41 (UnityPlayer) UnityMain
0x00007FFCFBFC9039 (UnityPlayer) UnityMain
0x00007FFCFC1AD13F (UnityPlayer) UnityMain
0x00007FFCFC1ACF94 (UnityPlayer) UnityMain
0x00007FFCFC06F75B (UnityPlayer) UnityMain
0x00007FFCFC07087D (UnityPlayer) UnityMain
0x00007FFCFC1B9037 (UnityPlayer) UnityMain
0x00007FFCFC1B90D3 (UnityPlayer) UnityMain
0x00007FFCFC1BB50C (UnityPlayer) UnityMain
ERROR: SymGetSymFromAddr64, GetLastError: ‘Es wurde versucht, auf eine unzulässige Adresse zuzugreifen.’ (Address: 00007FFCFBF70CEE)
0x00007FFCFBF70CEE (UnityPlayer) (function-name not available)
ERROR: SymGetSymFromAddr64, GetLastError: ‘Es wurde versucht, auf eine unzulässige Adresse zuzugreifen.’ (Address: 00007FFCFBF6FA4A)
0x00007FFCFBF6FA4A (UnityPlayer) (function-name not available)
ERROR: SymGetSymFromAddr64, GetLastError: ‘Es wurde versucht, auf eine unzulässige Adresse zuzugreifen.’ (Address: 00007FFCFBF73AFC)
0x00007FFCFBF73AFC (UnityPlayer) (function-name not available)
0x00007FFCFBF775EB (UnityPlayer) UnityMain
ERROR: SymGetSymFromAddr64, GetLastError: ‘Es wurde versucht, auf eine unzulässige Adresse zuzugreifen.’ (Address: 00007FF72FFB11F2)
0x00007FF72FFB11F2 (valheim) (function-name not available)
0x00007FFD5FD87034 (KERNEL32) BaseThreadInitThunk
0x00007FFD612BD0D1 (ntdll) RtlUserThreadStart

Valheim might be one of the hottest games on the market at the moment but sometimes it can be unplayable due to Unity engine crashing bug. Luckily, it seems that the fix for this one is pretty easy.

Valheim took Steam by the storm, selling more than 6 million copies since its launch in Early Access. We have to say, it’s one of those games that nailed the gameplay perfectly, which is not an easy task, especially for survival games.

Iron Gate’s title is currently in the Steam Early Access phase, which means it’s nowhere near its final release. You’ll encounter plenty of bugs, crashing and other issues and one of these is Unity engine crash, which can make the game unplayable at times.

If you are experiencing this issue, fear not, the fix is pretty easy but as always, it might not work on every single PC. Here’s how to fix Unity engine crashing in Valheim:

1. Right-click on Valheim in your Steam library
2. Click Properties
3. Uncheck «Enable the Steam overlay while in-game»
4. Uncheck «Use Desktop Game Theatre while Steam VR is active»

As we already mentioned, this fix may not work on every PC but as soon as we unchecked both of these options, the crashing actually stopped so it’s definitely something you should at least try until the devs release a patch with a fix for this particular issue.

Играю в нее 2й день и на 2й день после 2 часа игры в какой-то момент зависла картинка и выскочила эта ошибка, после повторного захода в игру она появляется почти сразу (игру переустанавливал, unity обновлял)

У меня такое появилось после какого-то обновления. Запускаю игру — во время заставки появляется окошко Unity — игра сворачивается.
Помогло только вручную удалить игру из папки стима. Я предполагаю, что это был конфликт версии мода с версией игры. Сперва удалял через библиотеку Стима, но Стим не удаляет пользовательские файлы. Т.ч. пробуй

Game that use the Unity Engine often lead to crashing problem with the error Unity. The same engine is used by Valheim and users are reporting of seeing persistent crashing that’s preventing them from progressing. The game crashes unannounced wiping any progress and completely hampers the experience of such an amazing game. If you are encountering the problem, the issue needs to be fixed before you can play without having to revisit the same stage all over again. Keep scrolling and we will show you how to fix Valheim Unity error – crashing with error Unity.

The error message appears as Valheim – Unity 2019.4.16f1_e05b6e02d63e. There can be a slight variation in the code, but the error is the same. The most common reason why the Valheim Unity error occurs is due to overclocked GPU or RAM. This includes the factory overclocking or the Intel Turbo Boost.

1. Right-click on Valheim.exe and click on Properties
2. Go to the Compatibility tab
3. Check Disable fullscreen optimizations and Run this program as an administrator.

Revert Overclocking

Once of the main causes of the Valheim Unity error is overclocking of the CPU or GPU. If you are using third-party software like MSI Afterburner to overclock the CPU or GPU, it must be disabled. Turbo boosting features need to be disabled as well from the BIOS. Ensure that the game runs without overclocking.

Go to the computers BIOS settings and disable the ‘Intel Turbo Booster’ if you have it enabled. To prevent the game from crashing, you should reset the CPU and GPU to chipset manufacturer specifications.

Underclock RAM & GPU

You must note that even when you have not manually overclocked the GPU or RAM, it may still be factory overclocked. Hence, you must Underclock the RAM and GPU. If you are using a software to overclock the GPU, disable the software and revert the settings. To Underclock the RAM, you can do it via the BIOS. A user that resolved the problem under clocked his 8GB RAM from 2000 MHz to 1600 MHz and it fixed the Valheim crashing with Unity error. You may have to tinker a bit to find the ideal setting. This fix is for advanced users and if you don’t know what you are doing, don’t try it.

Alter the Power Options in Window 10

For users who do not have an effective CPU cooler, you may want to skip this step as it would increase the CPU temperature by a few degrees. Without proper cooling, it may harm your system. Here are the steps to follow.

1. Click on the battery icon in the System Tray and drag the button to Best Performance
2. Right-click on the battery icon and select Power Options
3. Click on the Change plan settings link
4. Click on Change advanced power settings
5. Locate Processor power management and click on the plus sign to expand
6. Expand Minimum processor state and set it to 100%, next expand Maximum processor state and set it to 100%
7. Click on Apply and OK to save the changes.

At the moment, we only have these fixes to recommend, but if they don’t work let us know in the comments and we will try to help you. Hope your Valheim Unity Error is fixed.

Читайте также:

  

• Snowrunner системные требования

  

• Bfori замена самп

  

• Don t starve системные требования

  

• Transport fever 2 системные требования

  

• Замена на танк самп