Crashing on Radeon 680M

[fantstc]

I'm running on a Beelink, which I regularly use to play other games without any problems.

AMD Ryzen 7 7735HS(8C/16T up to 4.75GHz)
32GB DDR5
500GB
NVME SSD
Radeon 680M

Frequent crashes. At least 7-10 times in first hour.

Some of the bug reports were submitted via the automated client.

Happy to work with dev team for testing.

[h3r2tic]

Hey, do you have any crash codes so we can find the specific issue affecting you in our database?

[fantstc]

My son is the one playing, and I can get it. Standby.

[[STD]Random Lead]

What OS is it running. Their amazon page just says OS for OS.

https://www.amazon.com/Beelink-Computer-Display-Bluetooth-Ethernet/dp/B0DCBJBLXP?ref_=ast_sto_dp&th=1

[fantstc]

It's running windows 11.

In event viewer, I see this exception code:
C0000409

Then there seems to be a log.txt file when I click details... Some highlights of fails that I see in the log

Rejected obsolete Vulcan loader
Vulcan loaded ok from fallback
Failed to acquire main action set
Failed to set parameters "landing t" on FMOD event ... Ducks/flap
Failed to set parameters "is taking off"
Failed to set parameters "is on ground"
Delta time larger than maximum delta
Failed to set parameters "path size" .. "garden draw"
... Same for water draw

Failed to set "if window" ... "Building change height" and "building resize"

GPU device has been lost... With a bunch of subcodes for shadows and terrain lighting and g-buffer

Panic... Vulcan {err: error_device_lost}


Hopefully some of this helps?

[h3r2tic]

Thanks for retyping that, it would have been way less work for you if you shared the code that the crash reporter gives you at the end, but I think I found the matching crash in our database.

... and it looks rather odd :o GPU/driver randomly hanging... Hmmm, I wonder if perhaps 680M is affected by the same issue as Radeon RX 5x00 XT: https://steamcommunity.com/app/2198150/discussions/0/4844274022647304464/

Try the "rad5k" beta for Tiny Glade in Steam, maybe it will help (Right click Tiny Glade in your Steam Library → Properties → Betas → Beta Participation).

[fantstc]

Same error with the beta.

He was in first person, and had hit the "sun" button to change it to "full." (His words)

When he set it to full, it crashed.

[h3r2tic]

Originally posted by fantstc:

Same error with the beta.

He was in first person, and had hit the "sun" button to change it to "full." (His words)

When he set it to full, it crashed.

Thanks for testing the beta! At least we can rule that out :)

Does it always happen this way, or was it just random?
... and on a second thought, I'm not sure which crash is from you. I see three different crashes with three different people playing on a Ryzen 7735HS. If you get a crash again, please share the hexadecimal code that the window shows.

... but what I see as common between the reports is that they all have pretty old drivers for the integrated graphics, so I'd recommend updating those - it might fix the issue.

[fantstc]

All of my error info is in this thread, and I believe I am the only one reporting in this thread.

I will try to find a hex code for you.

I have updated the driver to 24.8.1

[h3r2tic]

You're the only one reporting in this thread, but this thread is not connected to our crash database - there's thousands of people playing, and if even a small fraction experience crashes, it's kinda hard to pinpoint which report comes from whom - that's why we have the crash codes. They allow us to instantly look up a specific issue in the database.

[fantstc]

Crashed again. Where do I find the hex code that you want?

[fantstc]

Got it ...

C89f011e-6854-4fc4-ac42-4243779265d9

[h3r2tic]

Originally posted by fantstc:

Got it ...

C89f011e-6854-4fc4-ac42-4243779265d9

Thanks for the data - now I can see where the GPU hang happens... but unfortunately I'm a bit stumped as to why it would hang where it does :< I found one other person in our crash database with the same issue as you, on the same processor - but at the same time the game runs just fine on other devices with the same RDNA 2.0 architecture, so I don't yet know what might be wrong. I've checked the location in the code, and there's nothing particularly suspicious there.
I've reached out to AMD a few days ago, and asked to have a look at the game - maybe in a few days I'll hear if they spot anything unusual that could potentially cause trouble. Until then all I have is my apologies for the game misbehaving for you.

[fantstc]

I understand, thank you. We'll just sit tight for now.

[fantstc]

Originally posted by h3r2tic:

Originally posted by fantstc:

Got it ...

C89f011e-6854-4fc4-ac42-4243779265d9

Thanks for the data - now I can see where the GPU hang happens... but unfortunately I'm a bit stumped as to why it would hang where it does :< I found one other person in our crash database with the same issue as you, on the same processor - but at the same time the game runs just fine on other devices with the same RDNA 2.0 architecture, so I don't yet know what might be wrong. I've checked the location in the code, and there's nothing particularly suspicious there.
I've reached out to AMD a few days ago, and asked to have a look at the game - maybe in a few days I'll hear if they spot anything unusual that could potentially cause trouble. Until then all I have is my apologies for the game misbehaving for you.

Just checking back on this. Were you able to find a way to stabilize for the integrated amd graphics?

[h3r2tic]

Originally posted by fantstc:

Originally posted by h3r2tic:

Thanks for the data - now I can see where the GPU hang happens... but unfortunately I'm a bit stumped as to why it would hang where it does :< I found one other person in our crash database with the same issue as you, on the same processor - but at the same time the game runs just fine on other devices with the same RDNA 2.0 architecture, so I don't yet know what might be wrong. I've checked the location in the code, and there's nothing particularly suspicious there.
I've reached out to AMD a few days ago, and asked to have a look at the game - maybe in a few days I'll hear if they spot anything unusual that could potentially cause trouble. Until then all I have is my apologies for the game misbehaving for you.

Just checking back on this. Were you able to find a way to stabilize for the integrated amd graphics?

Hey! Are you still getting the crashes with patch 1.10.2? I don't see any recent crash reports from you in our database :o (unless you've reinstalled the game or OS, and the game installation ID that we use to correlate crashes between players has changed).

AMD support engineers have given us nothing, then disappeared and don't respond to pings, so I don't have anything concrete unfortunately. We've since however implemented a number of workarounds for other driver issues, and also verified our graphics code using a number of diagnostic tools, fixing even benign-looking issues that we could spot - so I'd hope that whatever caused crashes for you might be fixed.