Repository: godot
Issue: Game Crash with AMD Processors
Labels: bug,needs testing,crash

### Tested versions

Godot 3.5.3 custom

### System information

AMD Ryzen 7, AMD Ryzen 5

### Issue description

**Summary**
My game crashes when run on computers with AMD Ryzen cards. 

Reducing the filesize, reverting to single threaded loading, and compatibility modes have failed to fix the issue. I believe the root cause is an engine incompatibility with AMD hardware.

Where the game crashes is variable for different computers. Most machines crash when the game is loaded and the title screen appears, but I've heard of a single case where a user crashes when the main map is instanced (after character select).

Removing the number of objects from the game's initial load will allow it to run on these machines, but it will then crash when trying to instance the next scenes.

**Full Context**
I'm the developer behind [Doomsday Paradise](https://store.steampowered.com/app/1603420/Doomsday_Paradise/). In November, I launched my game- and a user reported the game was crashing on startup. The user sent a list of specs over, which look like the following:
![ryzen1](https://github.com/godotengine/godot/assets/81896582/d5db9ada-12dc-4c1b-99c6-6c6122052c3b)
![ryzen2](https://github.com/godotengine/godot/assets/81896582/2675a174-7c6c-459e-9979-51c747c32860)

The user was on an older laptop, and eventually switched devices. The new device had no issues. At the time, I thought the issue might be RAM related.

Since then 3 other users have approached about game crashes. Mostly on game start. Every single one of them is using an AMD Ryzen processor. Specs attached. Here is a discussion thread on the [Steam Discussion Boards](https://steamcommunity.com/app/1603420/discussions/0/3958161899236416921/) about the issue.

![ryzen5](https://github.com/godotengine/godot/assets/81896582/b941131c-2476-4b88-897a-a89179f00a6e)
![ryzen6](https://github.com/godotengine/godot/assets/81896582/4da272ae-49cc-4db6-ad27-69b1337ec97d)
![ryzen3](https://github.com/godotengine/godot/assets/81896582/109f0806-fc91-4a1b-b3f7-875fa5616926)
![ryzen4](https://github.com/godotengine/godot/assets/81896582/f3ef96cb-3683-4241-a280-1903f24b46c9)

While most devices have only 8 GB of RAM, one device has 32 GB. The game shouldn't need more than about 300 MB of RAM. The VRAM requirement is higher- a little over 3 GB of VRAM.

In the Discussion Board I've tried my best to isolate the actual source by having some users test modified game builds. Things we've tried:

- Compressing every single image in the game, reducing the total size to 600 MB- smaller than the demo version. Notably, they can run the demo but they could not runt he compressed version of the game.

- Changing the objects loaded at startup. Different machines crash at different points. One machine is able to load through the title screen but crashes when the main map is instanced. One machine can get to the title screen, but only if I don't instance character select. Other machines crash if I try to instance the title screen.

- Deleting large swaths of content, adding additional logging to every single startup function, disabling background loading, etc.,

- Disabling multithreading and using single threaded loading.

- Enabling compatibility mode for rendering.

The issue seems to be related to object instancing, but because machines are crashing at different points I can't replicate it. In addition, I don't have a machine with an AMD Ryzen card- so I'm not easily able to create a repro project.

For purposes of debugging this, I can supply a game key. Alternatively, if anyone can help me figure out what logging / testing steps to take next, I'm happy to perform the relevant diagnostics myself and have a couple users who have been extremely patient and willing to help.

Currently, no issues appear in the logs. Users just experience a sudden termination.

### Steps to reproduce

1. Open my game with a computer using an AMD Ryzen card

### Minimal reproduction project (MRP)

Not available since I can't locally test it. I can try to reproduce a project with the current size profile if necessary.

During the title screen, the following are the game's stats:

- 240 MB Static Memory
- 15.7 MB Dynamic Memory
- 14,175 Objects
- 6,570 Resources
- 4,851 Nodes
- 189 Orphan Nodes
- 3.24 GB Video Memory