Jump to content
vinorraz

Error "Unity 2019.1.0f2_292b93d75a2c"

Recommended Posts

hello, my game has been showing constant crashes with the message "Unity 2019.1.0f2_292b93d75a2c", but I found no solution.

 

Things I have tried:

* GPU driver update

* Windows Update

* Microsoft Visual C ++

* reinstall the game on another HD

 

I have attached the logs.

I appreciate the help!

error1.log error2.log

Share this post


Link to post
Share on other sites

Supposedly, older versions of Citrix can cause this issue. Check if that's installed.

Share this post


Link to post
Share on other sites

Can happen with the Radeon overlay, and MSI Afterburner as well.

Try performing a clean installation of the GPU driver.

Share this post


Link to post
Share on other sites

I uninstalled the afterburner and used old versions of the GPU driver as the latest version, but with no solution. Decreases the resolution and changed the graphics to the minimum and ultra and continued crashing

Share this post


Link to post
Share on other sites
Posted (edited)

Now that you changed drivers and other stuff the logs may show messages they never showed before. In other words, post new logs.

 

 

Edited by meganoth (see edit history)

Share this post


Link to post
Share on other sites
Posted (edited)

I'm not very firm with windows, so I might be totally wrong here, but you seem to have windows 7 installed and a very old directx version. One of the files mentioned is

 

'C:\Windows\system32\xinput1_3.dll'. with version 9.18.944.0 and the file is dated from 2007-04-04

 

Isn't directx 11 available even on windows7 ? But it seems the program tries to use directx 9.

 

Recommendations:

1) Install a newer directx. Test if the game works, if not goto 2

2) Can two versions of directx exists in the same windows? If yes, remove directx9 for the moment to make sure the old version isn't used anymore. Test if the game works, if not got 3

3) Install windows 10. Yeah, well, this is the wrecking ball of a solution, but that step is inevitable. If your PC is too old for windows 10 then likely it is too old for 7D2D as well

 

Again, I'm not a windows users, someone else might shortly step in and ask me why I post such nonsense 😉

 

By the way, just to make sure: Your operating system is already 64bit, right? 32bit is a no-go.

Edited by meganoth (see edit history)

Share this post


Link to post
Share on other sites

My DirectX version is 12 and  I use Win10 64bits. Follow my system config:

Ryzen 2600

AsRock B450  Steel Legend

16gb RAM

image.png

Share this post


Link to post
Share on other sites

Mmmpf, mistrusting my own windows-fu was obviously warranted.

 

Share this post


Link to post
Share on other sites
Posted (edited)

Not important. I was only saying that I didn't trust my windows knowledge and that this mistrust was right.

 

 

Edited by meganoth (see edit history)

Share this post


Link to post
Share on other sites
Posted (edited)

That doesn't look like an output log. Looks like an error log.

I'm referring to the log found here:

/steam/steamapps/common/7 Days To Die/7DaysToDie_Data/output_log__2020-05-24__11-07-21.txt

Which is created each time you start the game.

Edited by Beelzybub (see edit history)

Share this post


Link to post
Share on other sites
Posted (edited)

In the log there is an error message "Loading assembly failed: "Managed/Assembly-CSharp.dll""

 

Searching the net for that error I only got one hit with an actual "solution":  https://steamcommunity.com/app/383120/discussions/2/355043117505214343/

 

In that thread (about a different Unity-based game) people got rid of the bug by reinstalling windows. The theory was that some wrong unity settings were stored somewhere deep in windows (probably in the registry) and could only be removed by a complete wipe of the PC.

 

This may not be the case here, but it might be your last option if everything else fails.

 

Things you can do first:

 

0) Make a backup of all your important data !!!!!!!!!!!!!!!!

1) First make sure you have only one copy of the game installed and in use. We don't want to inspect one copy and start another for example.

2) Check whether the file Assembly-CSharp.dll exists in ...\7 Days To Die\7DaysToDie_Data\Managed and is readable and has a size somewhere around 6Mbyte(?). Also validate the client through steam, even If you have done it before.

3) If you have some other unity games, update them and run them. Do they have problems too?

4) If you have very old unity-based games or programs (without any newer versions available) on the PC, try to delete them and their data as best as you can.

5) Search your harddisk for directories called "unity3d", "unity", Unity3D"... If you find them and they are not subdirectories of other games, change their names to "unity3d.off", "unity.off", "Unity3D.off". Start the game and see if it helps. If not, rename them back to "unity3d" ...

6) Wait for better ideas to surface. Someone else might have a better idea than what I posted here.

7) This is a very risky step with low chances of success: Use regedit to search your windows registry for settings with unity in the name. If you are brave, try to delete some of them and see if it helps. You could damage windows by doing this, so be prepared to reinstall if this doesn't work out.

 

 

Edited by meganoth (see edit history)

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...