WHEN IS THE UNITY BUG GOING TO BE ACKNOWLEDGED / FIXED ?

January 20

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!

January 20

If this was major issue, a lot of people would report it. Its something on your PC.

I will not post links to websites, but google for:

AppHangB1

BlueScreen Code: 133

or

Few years ago I was debugging crash memory dump for one video game and it showed me video driver file, you need some microsoft software to open dump file google "crash memory dump"... You can also go in that direction, but must wait for app to crash to create dump files.

Edited January 20 by orion310591

January 20

3 hours ago, orion310591 said:

If this was major issue, a lot of people would report it. Its something on your PC.

January 20

4 hours ago, orion310591 said:

AppHangB1

BlueScreen Code: 133

"crash memory dump"

#1 is a all over the place. From Steam bug, to suggestions of malicious code. So I'm completely removing steam + downloading malwarebytes + some antivirus. I suspect this will be clean, but who knows.

#2

#3 Now there we have something! THX! This is leading somewhere. Reading up on it. Will update.

Updating as soon as I finish 2 and 3.

January 21

This is a deep one...

Virus clear.

Some tracking cookies.

Then I saw this:

ntoskrnl.exe? Okay... kept digging... everywhere it's saying it's either 1- Bad memory, 2- Mismatched memory, or 3- out dated drivers.

Tbh, I'm 100% lost here. I do see a lot of differences from what should be the same stick. Does that mean I have mismatched ram sticks? There's no fix to that? Could that be it? Because I did a couple of ram tests and it seams fine:

Edited January 21 by untagatnu

January 21

it has something to do with the new version of unity engine, tarkov recently upgraded to the newer version, and if you go search online you can find thousands of things talking about how every new unity version has crashing problems, so tbh with you in a couple weeks it will be fixed... unfortunately we just have to suffer lol, its not even a tarkov thing its unity itself, go download another unity game and you will have the same issues lol, or at least thru my research and trial and errors that's what i have found...

oh and for the people who say its not a wide spread problem... KEKW

Edited January 21 by Whiskey_Bandit

January 21

As I said above everywhere I searched it kept saying the root of the issue is either: 1- Bad memory, 2- Mismatched memory, or 3- out dated drivers. That plus what you wrote here:

Quote

@Whiskey_Bandit

Hey everyone, here is the response back from the dev team, i hope im not violating any rules here posting this, im just trying to see if this will help anyone/myself lol

It seams that tech support is also hinting at out dated drivers, but his entire reply was all over the place.

From what I read of your tech support, and from what I'd had to see from my tech support. I'm pretty confident there is no in-house tech support. It feels like they out sourced their tech support to a tech support farm somewhere in a third world country and whoever is sitting on the other side of the desk has a script. You know the type: "PROBLEM #362 ---> Solution ---> Turn off your router and turn it on again".

Everything he wrote and everything I've seen so far is just carpet bombing 'solutions' & generic replies.

This is a learning experience for me. I will most likely never support a game (early access / open beta) if they don't have an in-house game engine. I will also be less inclined to support BSG further.

I also agree with you. If there is any solution to be had it will probably not come from BSG. It will most likely be from another player and/or unity dev team. So until then...

January 21

I have this bug too, despite updating all my drivers and reinstalling the game. I am able to play though and the error comes up occationally.

January 21

26 minutes ago, Chinjangs said:

I am able to play though and the error comes up occasionally*.

My PMC is still level 3.

January 21

5 hours ago, Whiskey_Bandit said:

it has something to do with the new version of unity engine, tarkov recently upgraded to the newer version, and if you go search online you can find thousands of things talking about how every new unity version has crashing problems, so tbh with you in a couple weeks it will be fixed... unfortunately we just have to suffer lol, its not even a tarkov thing its unity itself, go download another unity game and you will have the same issues lol, or at least thru my research and trial and errors that's what i have found...

oh and for the people who say its not a wide spread problem... KEKW

can confirm that im also getting random crashes on rust, another game i used to NEVER crash on and is on the unity engine

January 21

33 minutes ago, zmccarter93 said:

can confirm that im also getting random crashes on rust, another game i used to NEVER crash on and is on the unity engine

yea, man kinda sucks unity is the way it is with new versions but what can we do, thats why i said it may very well be out of tarkov devs hands and it solely will rely on the unity engine devs to come up with a fix, time will tell

January 21

Hi @untagatnu,

I can see from your screenshots you're running Windows 10, can you tell me what's your current build? You can check it by running the winver command.

I can see that you have an Nvidia graphics card, can you tell me what's the current drivers version? You can check it by opening Nvidia GeForce Experience app under the "Drivers" tab.

Have you submitted a request to the support team? if so, can you please tell me the request ID?

Thanks.

January 21

6 hours ago, andresto said:

can you tell me what's your current build?

6 hours ago, andresto said:

can you tell me what's the current drivers version?

Driver 461.09 released 01.07.2021

6 hours ago, andresto said:

Have you submitted a request to the support team? if so, can you please tell me the request ID?

Tech support tickets:

#9029789
#9007150
#8964556
#8950396
#8949653
#8820499
#8812155
#8787179
#8756822
#8756678
#8741566
#8552923
#8492377

Edited January 21 by untagatnu

January 21

Thanks @untagatnu, I'll do my best to forward this to the support team. Please make sure to only reply tickets once you have a response, bumping won't help.

For now, try to perform a clean reinstallation of your Nvidia drivers, you can do that by following this simple steps:

Open Nvidia GeForce Experience, click on the three dots context menu and select "Reinstall driver"
Select "Custom installation".
Make sure to check the "Clean installation" checkbox and Install.

This solution fixed the issue for many users in my community, hope it helps you too. Also, please notice that I'm from the community team and I'm not part of the support team, so further assistance should come from the latter if this doesn't fix your problem.

Cheers.

January 21

The best way to fix this issue is to uninstall Tarkov and move on to a different, better game.

January 21

I tried this before. Using the Display Driver Uninstaller (DDU). To my knowledge DDU is deeper. It takes you into Safe Mode and completely uninstalls the drivers + remaining files + unpacked files + installation files. Regardless, I will try it this way again.

6 hours ago, andresto said:

Please make sure to only reply tickets once you have a response, bumping won't help.

I disagree. It does help. It helps in various ways to be honest. Here is my top 5 ways this post helps:

It's gotten your attention and help. So thank you!
Debunking the myth that this issue is only affecting me.
Sheading light into the Ticket system. Which usually takes way more than 4-5 business days and it's usually accompanied by either a generic reply (Disconnect your modem to fix all the things). In one of the posts above you see someone having this exact issue + tech support response.
Just in case tech support won't help... at least we are getting other players to pitch in with possible research alternatives / solutions.
It's serves as a collection of everything we have tried so far... so when tech support asks me for the 11th time to check my ram or get better drivers or refresh windows or any of the things we've already tried... I can just show them this post.

I mean... BSG / this forum can pursue me. Ban me. Silence me. Read the rules in such a way that I'll be forced to be quiet or be banned... You know... the typical abusive egotistical response... or they can do as you did... and actually fix the issue in hand.

Heck if BSG can't solve the issue. They can at the very least make a mailing list. Get our emails and let us know when we can come back. That's how you deal with something you can't solve atm. Not like this. Not hiding it. Not censoring it. Not with harassments. Not with trolls:

4 hours ago, Vindsvept said:

The best way to fix this issue is to uninstall Tarkov and move on to a different, better game.

Actual human empathy + Real effort to find the bug and work on it. Whatever BSG needs... you need remote access / streaming of my PC? You got it. You need full logs and complete access to my PC? You got it. You need me to send my entire PC to BSG? You got it.

January 22

I'm sorry to hear your are having issues with this.

We pretty much have the same setup for PC:
Intel Core i7-7700K Kaby Lake Prosessor
Deepcool Captain 240 EX CPU Kjøler
MSI Z270 Gaming Pro Carbon, Socket-1151
Corsair Vengeance LED DDR4 3200MHz 16GB
MSI GeForce GTX 1080 Gaming X

I do not experience the same issue as you do.

Could I suggest you try a friends GPU to see if the problem goes away? This worked for someone that had the same issue earlier. I also recommend turning on you windows update.. Over the years I've been surprises how many problems it has solved for people I know with various issues.

I'm sure you have already done this but I would recommend flashing BIOS, installing chipset-drivers for your motherboard.

January 22

Quick one.

Are you running any type of overclock?

January 22

23 hours ago, untagatnu said:

Regardless, I will try it this way again.

Thanks, sometimes the propietary software can do things that broader tools doesnt' take into count so it's worth to try.

23 hours ago, untagatnu said:

I disagree. It does help. It helps in various ways to be honest. Here is my top 5 ways this post helps

Sorry if it wasn't clear enough, I meant the support tickets! You can posts here and discuss your issue with other people as much as you like in order to get a better idea of what's happening.

From my experience, this seems to be a system missconfiguration or hardware related incompatibility. I suggest everyone who has this problem to post their specs and possible windows tweaks made so you it will be easier to see the classic "if you have this particular graphics card series and you have this windows configuration enabled and this game setting disabled the game crashes" pattern.

But please, remember that everyone should fill their corresponding bug report so the support team can quantify specific issues. The forum is not a proper place to receive official technical support for the game.

Have a nice weekend folks!

January 24

What I do is I split my hard drive in two partitions and any time things are going odd I install a fresh windows on the spare partition and try a fresh Tarkov install from there while retaining my old install and files fully...

...you have a common system and meet recommended requirements, if you do a fresh windows 10 install and carefully understand your temps and there is STILL a problem, I'd look at memory or PSU being the obvious issue, although it could also be a motherboard issue or rarer still a CPU issue. Swapping out parts would be the next step in troubleshooting, it could be any part that has some flaw including hard-drive or even faulty connectors that can be cleaned, although for me these problems (past a fresh OS install) have always been heat/dust and PSU.

Often these problems only come about in one game that happens to be very taxing and troubleshooting can be hard, there is a tendency to blame the game. I remember Crysis back in the day would bring out massive heat problems that no other game would bring out. People would massively UNDERCLOCK to prove that the game was faulty... guess what happened?... The game ran without crashing.

There's four possible issues that this process will go over in order of more common occurrence first:

1. Non BSG Software; full new OS install solves it entirely, all this "driver cleaner" fix stuff won't help if you have some broken registry issues, broken supporting software like ".net framework", directx, etc...

2. Hardware; test temps on everything at all times (should be easy to google best method for this). After that, troubleshoot by swapping parts, if you can't swap out parts you can take it in to a PC repair place for under $50 and get them to troubleshoot for you.

3. Some obscure Unity error that doesn't work with your hardware, searching for Unity issues might find your issue, highly unlikely since it's not universal.

4. Actually BSG at fault, very rarely is this the cause, all the problems this game does have, your issue isn't that common, which means this is highly unlikely as much as it seems to be the case.

The odds are everyone with this error broke their supporting software/drivers in a similar way due to a faulty coded piece of software randomly used on every machine with the error, BSG is the least likely candidate.

January 25

12 hours ago, Redangelguts said:

What I do is I split my hard drive in two partitions and any time things are going odd I install a fresh windows on the spare partition and try a fresh Tarkov install from there while retaining my old install and files fully...

...you have a common system and meet recommended requirements, if you do a fresh windows 10 install and carefully understand your temps and there is STILL a problem, I'd look at memory or PSU being the obvious issue, although it could also be a motherboard issue or rarer still a CPU issue. Swapping out parts would be the next step in troubleshooting, it could be any part that has some flaw including hard-drive or even faulty connectors that can be cleaned, although for me these problems (past a fresh OS install) have always been heat/dust and PSU.

Often these problems only come about in one game that happens to be very taxing and troubleshooting can be hard, there is a tendency to blame the game. I remember Crysis back in the day would bring out massive heat problems that no other game would bring out. People would massively UNDERCLOCK to prove that the game was faulty... guess what happened?... The game ran without crashing.

There's four possible issues that this process will go over in order of more common occurrence first:

1. Non BSG Software; full new OS install solves it entirely, all this "driver cleaner" fix stuff won't help if you have some broken registry issues, broken supporting software like ".net framework", directx, etc...

2. Hardware; test temps on everything at all times (should be easy to google best method for this). After that, troubleshoot by swapping parts, if you can't swap out parts you can take it in to a PC repair place for under $50 and get them to troubleshoot for you.

3. Some obscure Unity error that doesn't work with your hardware, searching for Unity issues might find your issue, highly unlikely since it's not universal.

4. Actually BSG at fault, very rarely is this the cause, all the problems this game does have, your issue isn't that common, which means this is highly unlikely as much as it seems to be the case.

The odds are everyone with this error broke their supporting software/drivers in a similar way due to a faulty coded piece of software randomly used on every machine with the error, BSG is the least likely candidate.

it happens only on unity 19, people are saying rust does the same thing... i truely dont believe its a bsg problem, its simply a unity 19 problem, i have already tried a fresh windows install but i will be doing it again JUST TO MAKE SURE later today, and also this error we are suffering from literally never was a thing for us until unity 19, it is the only change and a common denominator even when testing another game on same unity version... NOTE: no other issues with any other programs, just unity 19

January 29

I was struggling with this issue for a long time, I had basically just uninstalled Tarkov and gave up after days upon days of troubleshooting and trying little fixes.

I recently got the itch and tried again and, of course, the same UnityPlayer.dll crashes started happening. I jumped back into the rabbithole of troubleshooting this issue and think I finally found a solution. At least, I haven't had a crash in about 20+ hours or so.

I had to completely revert all OC settings for my GPU, CPU, and RAM. I have a 2080ti, an i9 9900K, and 64 GB of dual-channel 3600 RAM. I went into the BIOs and turned back all the AI OC settings there, then used Intel Extreme Utility to reset my CPU to the base clock (from 4.8 down to 3.6), then used MSI to set my GPU to base clock -100. My RAM is currently running at ~ 1100. So, I actually had to pretty massively downgrade the performance of my system just to play this game. I am not 100% sure I have completely solved the problem, but I have never gone more than 2 or so raids in a row without Unity crashing, and now I've gone probably 20+ raids without a crash.

For what it's worth, I believe it is absolutely comical and unacceptable that I need to go to these lengths to play one game. Unity is absolute trash.

February 2

I installed a new GPU and no difference, I can see how this could be the UNity update issue as Kerbal space programme now has a unity isssue which I never had before.

I am curios why some can play and others not, I was doing at least 50 hours a week on eft so upset I cant play at all now. I have had my IT guy completely reinstall my PC for a nice £150 in labour

no change

So I feel there must be more some one can do than keep saying its our fault

the game used to work new patch now it dosnt

February 2

Literally every raid for me. Been only for two days tho, not since Dec. 2020. But it's literally the same screenshots from the original post up top.

Monday at 02:36 AM

i have this problem now. ive done everything recommended to me and nothing has fixed it. all my other games work fine. done every driver scan and system check possible.

The bugcheck was: 0x00000139 (0x0000000000000003, 0xffffa90c8aab3380, 0xffffa90c8aab32d8, 0x0000000000000000