solved computeOptimalBarriers crash bug

[Flappie]

I'm sorry to hear that. Please attach the latest ZIP file from your "Saved Games/DCS.../Logs" folder.

I need a fresh one to report this.

[Rapierarch]

1 minute ago, Amarok_73 said:

After today's patch, the error still causing the CTDs. 

Damn. Remove that solved tag than.

[Amarok_73]

Here's today's report.dcs.log-20230413-193322.zip

 

EDIT:

I've noticed, that directory metashaders2 contains quite old files, so I've deleted this directory and fxo, then gave a try, and so far, there was no CTD.

Edited April 13, 2023 by Amarok_73

[Flappie]

1 hour ago, Amarok_73 said:

EDIT:

I've noticed, that directory metashaders2 contains quite old files, so I've deleted this directory and fxo, then gave a try, and so far, there was no CTD.

OK, let me know how it goes.

In case the crash goes on, another thing to try is the DCS repair.

[Amarok_73]

21 minutes ago, Flappie said:

OK, let me know how it goes.

Well, another CTD, not directly coming from computeOptimalBarriers, but looking into the crash log, seems to be related. I've sent it already with the crash dialog, but just for information, here's the crash log package: dcs.log-20230413-221712.zip

[Flappie]

It looks like a GPU issue. Here are threads with the exact same crash symptoms:

You should try what was suggested in all these cases.

[Amarok_73]

@Flappie I tried different approaches according to the suggested lecture, all the time having the CTD related to the "DX device removed. Reason: 0x887A0006", then finally got back to the "computeOptimalBarriers"

What makes me wonder, regarding the DX device removed crash is, that this one is usually preceded with large number of these errors from the screenshot.

Anyway, I sent all the errors immediately after crash, but attaching them here for the record.

dcs.log-20230414-060542.zip dcs.log-20230414-062052.zip dcs.log-20230414-074518.zip dcs.log-20230414-063148.zip

Edited April 14, 2023 by Amarok_73

[Hip Hind]

2.8.4.38947 still has 'computeOptimalBarriers' error.

32GB swap file. Last version shaders were removed, launching dcs, working in editor - ok. Launching mission - ok. After a few minutes - crash. Rolling back to 2.8.3.37556 - everything works just fine, no lags or crashes.

Crashes I have started with version 2.8.3.38090, there was information that on April 14 will be released fix for this bug, but as you can see, this either does not help or not yet fix.

dcs.log-20230416-155202.zip

[BIGNEWY]

1 hour ago, by Robert Weide said:

2.8.4.38947 still has 'computeOptimalBarriers' error.

32GB swap file. Last version shaders were removed, launching dcs, working in editor - ok. Launching mission - ok. After a few minutes - crash. Rolling back to 2.8.3.37556 - everything works just fine, no lags or crashes.

Crashes I have started with version 2.8.3.38090, there was information that on April 14 will be released fix for this bug, but as you can see, this either does not help or not yet fix.

dcs.log-20230416-155202.zip 2.9 MB · 0 downloads

Hi we are looking into it, this one is taking longer. 

thank you for being patient 

[BIGNEWY]

Update on issue:

there is not a lot we can do reference the computeOptimalBarriers crash, it comes after the TDR and GPU crash, so its a consequence of the GPU crash. 

We will continue to look at the reports auto and manual ones here. 

If you have not already please consider

Fresh driver install for the GPU 

update windows

if you overclock consider trying stock values 

please continue to make crash reports or use our auto report in game. 

thank you

 

[Hip Hind]

49 минут назад, BIGNEWY сказал:

Update on issue:

....

The drivers are all the latest, Windows is up to date. CPU stock, no overclock.
There are no crashes on version 2.8.3.37556, so in this version the GPU does not fail?

Edited April 17, 2023 by by Robert Weide

[BIGNEWY]

2 minutes ago, by Robert Weide said:

The drivers are all the latest, Windows is up to date. CPU stock, no overclock.
There are no crashes on version 2.8.3.37556, so in this version the GPU does not fail?

 

If you are not getting any crash in the latest version that is good news. Hopefully the issue that was creating your crash was fixed. Keep us informed 

thanks

[Hip Hind]

1 минуту назад, BIGNEWY сказал:

If you are not getting any crash in the latest version that is good news. Hopefully the issue that was creating your crash was fixed. Keep us informed 

thanks

You don't get it. Crashes started with version 2.8.3.38090 and are still going on. When I roll back to OB 2.8.3.37556 (MT) the crashes disappear. It turns out that I cannot update to the latest current version of OB.

[BIGNEWY]

4 minutes ago, by Robert Weide said:

You don't get it. Crashes started with version 2.8.3.38090 and are still going on. When I roll back to OB 2.8.3.37556 (MT) the crashes disappear. It turns out that I cannot update to the latest current version of OB.

Apologies, we will continue to investigate all crashes and collect data, please use the auto crash report in game it is a big help for crash collection 

thanks

[Amarok_73]

I keep all drivers and system updated, no overclocking at all, tried some underclocking as @Flappiesuggested, but CTDs still happens.

 

[Hip Hind]

27 минут назад, Amarok_73 сказал:

I keep all drivers and system updated, no overclocking at all, tried some underclocking as @Flappiesuggested, but CTDs still happens.

 

Wow! RX 5700 XT! Maybe it's because of AMD? I have the same GPU.

Edited April 17, 2023 by by Robert Weide

[Amarok_73]

1 minute ago, by Robert Weide said:

What kind of GPU do you have?

Everything is in my footer
AMD Ryzen 5 3600, AMD Fatal1ty B450 Gaming K4, AMD Radeon RX 5700 XT, 32 GB RAM Corsair Vengeance LPX, PSU Modecom Volcano 750W, Logitech G940 HOTAS

[Hip Hind]

5 минут назад, Amarok_73 сказал:

Everything is in my footer
AMD Ryzen 5 3600, AMD Fatal1ty B450 Gaming K4, AMD Radeon RX 5700 XT, 32 GB RAM Corsair Vengeance LPX, PSU Modecom Volcano 750W, Logitech G940 HOTAS

saw)

Can you roll back to version 2.8.3.37556 OB? I don't have any problems with MT on it. Starting with version 2.8.3.38090, the failures start.

Edited April 17, 2023 by by Robert Weide

[WWSmith]

12 minutes ago, by Robert Weide said:

Wow! RX 5700 XT! Maybe it's because of AMD? I have the same GPU.

 

Very interesting. I also have a 5700 XT, and have been getting an insane number of "DX device removed. Reason: 0x887A0006" CTDs with multithreading. This was never a problem for me before MT. To troubleshoot, I have thus far:

-removed all mods

-updated graphics driver

-uninstalled and reinstalled graphics driver

-run a full (slow) repair of DCS

-rolled back to the original MT OB version

-rolling back didn't help so updated to latest version

-disabled all automatic features of AMD's Adrenalin Software

-not overclocking

-set Windows power plan to "performance"

-turned up GPU fan speeds (it wasn't overheating to begin with, but better safe than sorry)

-played with just about every graphics setting in DCS

-added TdrDelay and TdrDdiDelay registry keys

This last one seems to have fixed the problem...maybe. I just tried that yesterday, so I can't say whether it's really fixed the problem or merely reduced the frequency of crashes to a somewhat-acceptable level. I've uploaded a heap of crash logs, but can post some here, too, if anyone wants.

[Amarok_73]

2 minutes ago, WWSmith said:

-added TdrDelay and TdrDdiDelay registry keys

I did it already, and still CTD happens. However, I've not enabled yet VSYNC and now thinking, that maybe forcing the slow down of graphics generation with this parameter may have some positive effect...

 

[BIGNEWY]

4 minutes ago, WWSmith said:

This last one seems to have fixed the problem...maybe. I just tried that yesterday, so I can't say whether it's really fixed the problem or merely reduced the frequency of crashes to a somewhat-acceptable level. I've uploaded a heap of crash logs, but can post some here, too, if anyone wants.

That has helped others in the past also with the TDR 

[Hip Hind]

@BIGNEWY I have the same video card as Amarok_73 users who created this thread and WWSmith. Can you check the assumption that it is the AMD driver that causes the crash since OB 2.8.3.38090? 

6 минут назад, WWSmith сказал:

Very interesting. I also have a 5700 XT, and have been getting an insane number of "DX device removed. Reason: 0x887A0006" CTDs with multithreading. This was never a problem for me before MT.

I have problems with MT started with version 2.8.3.38090, on the first version of MT 2.8.3.37556 no problems at all. Also everything is standard, all drivers updated, system updated, swap file to 32GB. Did both slow restores, deleted all mods and so on. I get crashes anyway. I will roll back to my mt 2.8.3.37556 and all the problems disappear, everything works fine and stable. 

[BIGNEWY]

9 minutes ago, by Robert Weide said:

@BIGNEWY I have the same video card as Amarok_73 users who created this thread and WWSmith. Can you check the assumption that it is the AMD driver that causes the crash since OB 2.8.3.38090? 

I have problems with MT started with version 2.8.3.38090, on the first version of MT 2.8.3.37556 no problems at all. Also everything is standard, all drivers updated, system updated, swap file to 32GB. Did both slow restores, deleted all mods and so on. I get crashes anyway. I will roll back to my mt 2.8.3.37556 and all the problems disappear, everything works fine and stable. 

I will ask if there are any 5700 XT owners on the testing team.

 

[Amarok_73]

1 minute ago, BIGNEWY said:

I will ask if there are any 5700 XT owners on the testing team.

Flappie may have such information, as he was actively supporting other thread about the black rectangles issue, which seems to hit mostly 5700XT owners...

 

[Hip Hind]

@Amarok_73 OB MT version 2.8.3.37556 also causing CTD?