Jump to content

UNITY BUG. NO SUPPORT. NO ACKNOWLEDGEMENT. NO SOLUTION.


Recommended Posts

untagatnu

Hi,
I've had issues with EFT since the last wipe (dec 2020). The bug is sudden and happens randomly. I could be running, prone, opening a container, getting killed, dying, killing, extracting, right after the extraction... It doesn't matter. I will eventually get a unity error.

Since december 2020 I have refreshed my computer. I have a firewall so that windows update does not install new drivers. I have tested my ram (no issues). I have uninstalled / reinstalled my graphics card driver (no effect). Increased my page file to 30GB (no effect).

This is my PC:
Intel Core i7-7700K 4.2 GHz Quad-Core Processor
Thermaltake Water 3.0 Ultimate 99 CFM Liquid CPU Cooler
Asus STRIX Z270-E GAMING ATX LGA1151 Motherboard
G.Skill Ripjaws V 32 GB (2 x 16 GB) DDR4-3600 CL18 Memory
TCSunBow X3 1 TB 2.5" Solid State Drive
Asus GeForce GTX 1080 8 GB ROG STRIX Video Card
Thermaltake Core X9 ATX Desktop Case
EVGA P2 750 W 80+ Platinum Certified Fully Modular ATX Power Supply

Support is non existant and certainly not '4-5 business days'. There is at least 9 more posts with dozens of players complaining and being absolutely ignored. Or at best, mislead. Community managers often 'check' and tell us to 'submit a report', but they already know that won't work... and in case they didn't know. I guess, by now after reading this they know.

There is no acknowledgement of a bug. There is no solution. Support is non-existant... so I'm asking you... in the community... Please check the screenshots / logs posted below. Let me know if you can think of anything that might help.

Source
Windows

Summary
Shut down unexpectedly

Date
‎1/‎19/‎2021 4:13 PM

Status
Not reported

Problem signature
Problem Event Name:    BlueScreen
Code:    133
Parameter 1:    1
Parameter 2:    1e00
Parameter 3:    fffff807536fb320
Parameter 4:    0
OS version:    10_0_19042
Service Pack:    0_0
Product:    256_1
OS Version:    10.0.19042.2.0.0.256.49
Locale ID:    1033

The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000133 (0x0000000000000001, 0x0000000000001e00, 0xfffff807536fb320, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 3e1e9dd8-8137-4c63-9968-9ee75fcd6fcd.


Source
EscapeFromTarkov.exe

Summary
Stopped working

Date
‎1/‎10/‎2021 8:28 PM

Status
Not reported

Description
Faulting Application Path:	C:\Battlestate Games\EFT\EscapeFromTarkov.exe

Problem signature
Problem Event Name:	APPCRASH
Application Name:	EscapeFromTarkov.exe
Application Version:	0.12.9.10532
Application Timestamp:	5fa91549
Fault Module Name:	UnityPlayer.dll
Fault Module Version:	2018.4.28.28878
Fault Module Timestamp:	5fa9161b
Exception Code:	c0000005
Exception Offset:	0000000000c25e0b
OS Version:	10.0.19042.2.0.0.256.49
Locale ID:	1033
Additional Information 1:	5f16
Additional Information 2:	5f16a064a1d87c4a8499178a8dfe40ef
Additional Information 3:	7113
Additional Information 4:	711386b9760b3d4316243c7550ae3d57

Files that help describe the problem
WERInternalMetadata.xml

Source
EscapeFromTarkov.exe

Summary
Stopped responding and was closed

Date
‎1/‎6/‎2021 3:21 PM

Status
Not reported

Description
A problem caused this program to stop interacting with Windows.
Faulting Application Path:	D:\Games\Battlestate Games\EFT (live)\EscapeFromTarkov.exe

Problem signature
Problem Event Name:	AppHangB1
Application Name:	EscapeFromTarkov.exe
Application Version:	0.12.9.10519
Application Timestamp:	5fa91549
Hang Signature:	0000
Hang Type:	134217728
OS Version:	10.0.19042.2.0.0.256.49
Locale ID:	1033
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

Files that help describe the problem
WERInternalMetadata.xml


Source
EscapeFromTarkov.exe

Summary
Stopped responding and was closed

Date
‎1/‎5/‎2021 1:02 PM

Status
Not reported

Description
A problem caused this program to stop interacting with Windows.
Faulting Application Path:	D:\Games\Battlestate Games\EFT (live)\EscapeFromTarkov.exe

Problem signature
Problem Event Name:	AppHangB1
Application Name:	EscapeFromTarkov.exe
Application Version:	0.12.9.10519
Application Timestamp:	5fa91549
Hang Signature:	0000
Hang Type:	134217728
OS Version:	10.0.19042.2.0.0.256.49
Locale ID:	1033
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

Files that help describe the problem
WERInternalMetadata.xml



Source
EscapeFromTarkov.exe

Summary
Stopped responding and was closed

Date
‎1/‎2/‎2021 11:25 AM

Status
Report sent

Description
A problem caused this program to stop interacting with Windows.
Faulting Application Path:	D:\Games\Battlestate Games\EFT (live)\EscapeFromTarkov.exe

Problem signature
Problem Event Name:	AppHangB1
Application Name:	EscapeFromTarkov.exe
Application Version:	0.12.9.10519
Application Timestamp:	5fa91549
Hang Signature:	0000
Hang Type:	134217728
OS Version:	10.0.19042.2.0.0.256.49
Locale ID:	1033
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:	0c08f381922fa1f3ff1f3b1b6750a8d9 (2242576128337291481)


Log Name:      System
Source:        Microsoft-Windows-MemoryDiagnostics-Results
Date:          1/20/2021 8:17:03 AM
Event ID:      1201
Task Category: None
Level:         Information
Keywords:      
User:          SYSTEM
Computer:      DESKTOP-UEV4C6S
Description:
The Windows Memory Diagnostic tested the computer's memory and detected no errors
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-MemoryDiagnostics-Results" Guid="{5f92bc59-248f-4111-86a9-e393e12c6139}" />
    <EventID>1201</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2021-01-20T12:17:03.7709631Z" />
    <EventRecordID>3821</EventRecordID>
    <Correlation />
    <Execution ProcessID="7272" ThreadID="7276" />
    <Channel>System</Channel>
    <Computer>DESKTOP-UEV4C6S</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <UserData>
    <Results xmlns="http://manifests.microsoft.com/win/2005/08/windows/Reliability/Postboot/Events">
      <CompletionType>Pass</CompletionType>
    </Results>
  </UserData>
</Event>


Source
EscapeFromTarkov.exe

Summary
Stopped working

Date
‎1/‎20/‎2021 2:39 PM

Status
Not reported

Description
Faulting Application Path:	C:\Battlestate Games\EFT\EscapeFromTarkov.exe

Problem signature
Problem Event Name:	APPCRASH
Application Name:	EscapeFromTarkov.exe
Application Version:	0.12.9.10532
Application Timestamp:	5fa91549
Fault Module Name:	UnityPlayer.dll
Fault Module Version:	2018.4.28.28878
Fault Module Timestamp:	5fa9161b
Exception Code:	c0000005
Exception Offset:	00000000008ff8c6
OS Version:	10.0.19042.2.0.0.256.49
Locale ID:	1033
Additional Information 1:	3510
Additional Information 2:	3510e8e75ab60ad7b9c8563182cebe79
Additional Information 3:	6242
Additional Information 4:	6242e9307ec8ab52a49a72454a47ccab

Files that help describe the problem
WERInternalMetadata.xml


<?xml version="1.0" encoding="UTF-16"?>

-<WERReportMetadata>


-<OSVersionInformation>

<WindowsNTVersion>10.0</WindowsNTVersion>

<Build>19042</Build>

<Product>(0x31): Windows 10 Pro N</Product>

<Edition>ProfessionalN</Edition>

<BuildString>19041.631.amd64fre.vb_release.191206-1406</BuildString>

<Revision>631</Revision>

<Flavor>Multiprocessor Free</Flavor>

<Architecture>X64</Architecture>

<LCID>1033</LCID>

</OSVersionInformation>


-<ProblemSignatures>

<EventType>APPCRASH</EventType>

<Parameter0>EscapeFromTarkov.exe</Parameter0>

<Parameter1>0.12.9.10532</Parameter1>

<Parameter2>5fa91549</Parameter2>

<Parameter3>UnityPlayer.dll</Parameter3>

<Parameter4>2018.4.28.28878</Parameter4>

<Parameter5>5fa9161b</Parameter5>

<Parameter6>c0000005</Parameter6>

<Parameter7>00000000008ff8c6</Parameter7>

</ProblemSignatures>


-<DynamicSignatures>

<Parameter1>10.0.19042.2.0.0.256.49</Parameter1>

<Parameter2>1033</Parameter2>

<Parameter22>3510</Parameter22>

<Parameter23>3510e8e75ab60ad7b9c8563182cebe79</Parameter23>

<Parameter24>6242</Parameter24>

<Parameter25>6242e9307ec8ab52a49a72454a47ccab</Parameter25>

</DynamicSignatures>


-<SystemInformation>

<MID>20ECDB7B-28E6-476E-AF26-164ADDB6615F</MID>

<SystemManufacturer>System manufacturer</SystemManufacturer>

<SystemProductName>System Product Name</SystemProductName>

<BIOSVersion>1302</BIOSVersion>

<OSInstallDate>1609183944</OSInstallDate>

<OSInstallTime>2020-12-28T19:32:24Z</OSInstallTime>

<TimeZoneBias>04:00</TimeZoneBias>

</SystemInformation>


-<SecureBootState>

<UEFISecureBootEnabled>0</UEFISecureBootEnabled>

</SecureBootState>


-<ReportInformation>

<Guid>28c69ed6-9824-47a1-ba3c-efbd90e8b04f</Guid>

<CreationTime>2021-01-20T18:39:46Z</CreationTime>

</ReportInformation>

</WERReportMetadata>



If you can spot an error or have any suggestions on how to fix this... let me know!

1610836100.png

1610845123.png

1610894126.png

1610896075.png

1611067084.png

1611087042.png

1611145242.png

1611167971.png

  • Upvote 1
Link to post
Share on other sites
untagatnu

Tech support tickets:

  1. #9029789
  2. #9007150
  3. #8964556
  4. #8950396
  5. #8949653
  6. #8820499
  7. #8812155
  8. #8787179
  9. #8756822
  10. #8756678
  11. #8741566
  12. #8552923
  13. #8492377
Link to post
Share on other sites
untagatnu

Untitled.thumb.png.48e67d9c7a46bf57755188435a729a79.png

Welp, there we go. That's the real issue here. We are on Unity 2018. They are planning to move to Unity 2019. So no resources will be allocated into solving this issue at all. 

Barack Obama Mic Drop GIF

angry fuck me GIF

 

  • Sad 1
Link to post
Share on other sites
ThatGuy2119

A few things to try.

1. open task manager and set it high priory. 

2.  run the game on admin. Do this on the launcher and also the  EscapeFromtarkov.exe 

 3. deleting EVERYTHING related to tarkov. Not just uninstall but also delete everything in your users.  You should be able to find it in in your C drive under users or whatever drive has your Users on. Legit ANYTHING related to BSG or Tarkov. if you attempt this take pictures of your settings! They will  be wiped if you do this. 

 4.  Lastly try installing the game on another Hard drive or SSD. Maybe there is a problem with information being transferred from the SSD that tarkov is currently on. I would attempt to do this as a VERY last step because this requires money and with covid prices on tech are $$$

After that im out of guesses but hope that ANY of this helps.  I dont fully understand code hopefully someone else that see's this is. Do you have any other problems with other games or is it just tarkov?

 

Also try a search on  riddit. There could be something there. 

Link to post
Share on other sites
Dainsleif88

Had this problem for ages.  I've tried dozens of fixes.  CTD every other raid or so, event viewer shows UnityPlayer.dll is the faulting item.  

 

I've run chckdsk, scndsk, memchk, all with not errors.  Removed any OC from CPU and GPU.  Screwed around with BIOS settings.  Everything is up to date.  Removed and reinstalled all drivers.  Removed and reinstalled the entire game.  Countless other tests and fixes...

 

Nothing works.  

Link to post
Share on other sites
Slander

I never had any issues like this with Tarkov and I've been playing a few years now. But since last patch I have the exact problem, that and that Tarkov cant create (or use?) virtual memory. And there is a lot of space on my C drive. 

Only solution I found is to restart the game every third round to avoid it.

 

 

Edit: I send bug reports every time and always reach daily limit, cause I forget to restart every so often.

Edited by Slander
Link to post
Share on other sites
sightseeer
1 hour ago, Slander said:

I never had any issues like this with Tarkov and I've been playing a few years now. But since last patch I have the exact problem, that and that Tarkov cant create (or use?) virtual memory. And there is a lot of space on my C drive. 

Only solution I found is to restart the game every third round to avoid it.

 

 

Edit: I send bug reports every time and always reach daily limit, cause I forget to restart every so often.

What are your windows page file settings?

Link to post
Share on other sites
sightseeer

I would try one thing: disable page file and use the ingame RAM cleaner in OPTIONS>GAME.

Just making sure: when uninstalling and installing the GPU driver, you should use DDU when being in safe mode, I assume and hope you did that.

Also I would cap FPS to something like 60 FPS for testing purposes within your GPU driver. 

When the game has started, go to Options and click on fullscreen and click save, even when you think it was already fullscreen. Do the same for the Game-Options with the RAM cleaner. Why? A few settings seem to "reset" to default when starting the game again, even when it lists something else.

For even further testing I would reduce ingame resolution, disable every unnecessary background application and service  to narrow down the problem.

Link to post
Share on other sites
metkiyprizrak

Good solution ideas overall.

I only want to add that changing pagefile may help, not just removing it.

Pagefile is storage that is being used like slow ram. It'll be in windows settings somewhere, how much hdd is used for pagefile.

SSD's have bad compatibility with pagefile because pagefile acts as slow ram, it involves lots of swapping and moving around data. Better off buying more ram if windows/game is on an SSD. You can set pagefile on any and every storage drive in a system.

 

Free (money) solutions are:

memtest - check ram for faults

Ram channels- if you have more than 1 stick of ram, ensure you're using more than 1 ram channel. This usually looks like an empty ram slot between each stick. If you're changing/moving ram- ensure to not change the orientation. The gap in the ram contacts matches a bump in the ram slot. It will only fit one way without breaking something.

increase page file. An old rule of thumb is set pagefile to 2x your ram capacity. I'm not up to date with any potential differences in windows10/ram interactions and pagefile.

Download fresh drivers before completely uninstalling the current ones. After uninstalling, use something like ccleaner to purge registry entries. Find the file location and delete remnants. Then reboot. This will remove all current settings active (such as resolution). The goal is to erase as much as possible from system before rebooting. Then after reboot you'll (in theory) have a clean slate when installing drivers/software.

 

Non-free solutions:

Buy more ram to increase capacity. A common reason why pagefile is used, is if ram is full. So have enough ram for your OS+all software/games to use. Windows 7-10 likes 4 gig all to itself. Tarkov wants 6-8.

8+4=12. So have 16-32 gig ram. It's an oversimplification, but it's a simple solution.

Buy another storage drive. Put windows on 1, games on another. This is a more technical solution, where if everything is on the same drive, the OS/games/graphics drives/ etc/ are all competing with each other for the use of ssd/hdd controllers/headers.

 

Final note. The above solutions are not solutions for buggy or faulty "insert software name here".

Many problems happen due to a lack of resources. Like a human trying to run a marathon without any water or salts/sugars. So the above solutions can not only make your system run smoother/more responsive- but can mitigate problems that are not caused by faulty coding or bugs.

Edited by metkiyprizrak
Clarifying ram and pagefile.
Link to post
Share on other sites
Streetlight_
3 hours ago, sightseeer said:

I would try one thing: disable page file and use the ingame RAM cleaner in OPTIONS>GAME.

 

Normally you should disable RAM cleaner if you have 16+ GB's of ram, because it can cause micro stutters, they may have fixed it though so i may be wrong

Link to post
Share on other sites
sightseeer
8 hours ago, Streetlight_ said:

Normally you should disable RAM cleaner if you have 16+ GB's of ram, because it can cause micro stutters, they may have fixed it though so i may be wrong

Well the Tarkov RAM cleaner ist kind of too simplistic, as it just purges the RAM when 80% (?) of total capacity has been allocated. For example I play on 32 GB of decently overclocked RAM (3800 CL16) and Tarkov takes more and more RAM up to 16 GB which is insane. Even I on a kind of high end system have to restart the game after a few hours of gaming, which always improves performance.

But overall it should be better to have a really small page file such that it actually gets full and the RAM cleaner can do its thing. I my opinion it would be better to be able to set the RAM cleaner to some fixed value, for example 12 GB and if Tarkov reaches to use up that 12 GB it should purge everything unnecessary.

@OP: I would also suggest to load offline on a map first before playing it online. That way it can have better performance as everything was already loaded once and stays mostly in the cache. Only for testing purposes. The goal here is to narrow down the problem and to see "what happens" when you "press specific buttons".

Link to post
Share on other sites
  • 1 month later...
CMDR_CODY

Have you tried fixing unity? I feel like it has something to do with bad references or something. The thing that is confusing is that I had two people with the same PC setup install and run the game and one guy got the unity error and the other did not. Now I know there a lot of software variables but that seems to rule out hardware issues which some people have eluded to.

2021-03-2100-52_172.8_4.2_182.4_0.2_-0.5_0.1_0.8_13.09_0-1.thumb.png.b7bfbd1452eafa03a689599bfb72170d.pngAlso it has definitely been acknowledged they just don't seem to care. See screenshot. 

Link to post
Share on other sites
-CosmiK-

If you encountered BSOD, that's most probably hardware issue. Since you upgraded your PC when things starts to crash, i would dig in that way. Do you use any overclock or undervoltage ?

Link to post
Share on other sites
-_X_-

I had this problem. Found some blog that said to use Mem Reduct. 
It kinda worked for a while but after a while just bought 2x 32gig RAM sticks. 
Now it runs fine, but yes the game like to use 16 to 18 gigs of RAM.
Hope that helps.

Edited by -_X_-
Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...