[1.1.87] Crash in AMD graphics driver (MR)

[FuryoftheStars]

Hey All,

Tldr at bottom.

So, I was having a similar problem on my computer for a while and I was getting sick of it so I decided to send AMD an email myself, and this was their response:

[...]

Based on this, it doesn't seem like they are even working on a fix or think its a fault with their drivers in the first place.

This is all just their standard/canned response. The CS agent that received your message, etc probably isn't even aware of a wider issue, and even if you mentioned it in your message with a link to this thread, they likely didn't read it, or AMD has some kind of policy in place for CS that requires them sending that canned message anyway. The only way you're really going to get them to proceed further and escalate the issue is by emailing them back and saying "nope, that didn't work".

[EmileSonneveld]

I got this error sometimes when I disconnect from my docking station where my secondary display is connected.
factorio-current.log in attachment

[craftingk1]

I think I have the same crash [1.1.109] also running AMD I created the dump right after factorio crashed but I had to restart the game to do it as it was not in task manager anymore but do I have to create it when the error pops up and I haven't pressed anything? I also play with mods. Let me know if you need anything and as soon as i get the error again I'll create the dump. It's very weird as I can not reproduce it easily it just happens sometimes when you close or open the game? Also the dump is 3 GB so I'll create a google drive link if you need it. (First time on the forum btw)

System:
Processor AMD Ryzen 7 7700X 8-Core Processor 4.50 GHz
GPU AMD Radeon RX 7900 XT
Installed RAM 32,0 GB (31,1 GB usable)
System type 64-bit operating system, x64-based processor

[Pho-Enix]

Same crash probably.
Version 1.1.109
But it only happens when i click [ Quit game ] in main menu, never elsewhere.
Also it happens only in Factorio, i play a lot of games and no crashes. I also have monitor attached to laptop.
GPU: AMD Radeon 780M

[Rseding91]

At this point, I don't think this will ever be fixed. AMD's graphics driver appears to be broken, and they have no idea how/why it's broken, and so have no plans to fix it.

At best maybe we could detect this specific crash happening and simply not show the crashed dialog, instead exiting the game silently.

[Enderdraak]

10-06-2024, 00-53-09.png (327.83 KiB) Viewed 613 times

A screen shot of my current settings. As I think I got this crash as well.

As well as the normal Factorio dump As I could not reproduce the crash.

A few things I remember from playing:
* I played for a long while (2 to 3 hours)
* it became midnight
* it crashed when I pressed exit.
I did lost the file (while attempting to reproduce) of the `factorio-previous.log`
But I do recall it seeing the `Quitting: user-quit.` and crashing after. But it not having `Steam API shutdown.`

[Heinermann]

Hello, I was about to post a new topic but since all the other "AMD crash on exit" topics redirect here, I will post it here:

Just started a multiplayer save with a friend on 2.0.8 today. After we finished our session, saving, and quitting the game were fine, but Exit from the main menu led to a crash (SIGSEGV). I was not able to reproduce. I will see if it happens again following our next session.

Seems driver related given the stack trace, but I haven't ever had a crash popup when closing other games. I realized that the graphics drivers are outdated (but still as recent as earlier this year), I have updated them and will post back if it happens again. Please let me know if there is anything else I can provide.

Mods enabled:

• Base mod 2.0.8
• Elevated Rails 2.0.8
• Quality 2.0.8
• Space Age 2.0.8

AMD Software: Adrenalin Edition Version
24.8.1
Driver Version
24.10.37.04-240823a-407010C-AMD-Software-Adrenalin-Edition
AMD Windows Driver Version
32.0.11037.4004

factorio-crash-on-exit.log

(21.45 KiB) Downloaded 8 times

to the moon.zip

(7.97 MiB) Downloaded 4 times

EDIT: I just randomly got it to happen again with updated driver, I did not really do anything besides load the most recent save, walk up and down to test changed video settings, and quit.

AMD Software: Adrenalin Edition Version
24.10.1
Driver Version
24.20.19.01-241011a-408380C-AMD-Software-Adrenalin-Edition
AMD Windows Driver Version
32.0.12019.1028

factorio-current.log

(18.07 KiB) Downloaded 4 times

factorio-dump-current.dmp

(570.23 KiB) Downloaded 4 times

[posila]

Ref: 116676

Since this is still happening, we are gonna leak D3D swap chain, device and some other core engine graphics resources when closing the game in 2.0.10 as an attempt to avoid the crash during game shutdown. I don't know how to try to workaround the crash when just playing the game (which I see is also happening from reports in this thread)

[Drackmore]

Unless I'm misreading my log I think mine is also an AMD related crash if you need more of those.
It crashed on exit, nothing odd happened ingame or anything else. No mods except for Quality, Elevated Rails, and Space Age.

factorio-current.log

(19.35 KiB) Downloaded 11 times

factorio-dump-current.dmp

(619.94 KiB) Downloaded 3 times

dunno which one you want so there's both the files it generated.

Its funny though, my friend was hosting the game last night and played it just fine and exited just fine. And I don't think he's had any issues either and I believe he's running a similar rig with AMD as I am.

Maybe playing 8+ hours in one session is probably a bit to much.

[Dimava]

I can more or less reliably reproduce crashes by ALT+F4 (that's how I generally close the game, I get popups every time)

I'll post here if it works on experimental

[johnLate]

I'm doing game dev as well and had issues with AMD drivers before. Maybe it is not related at all, maybe it can be a hint:

In my case it was OpenGL code and the game crashed during startup. When I tried to narrow it down I noticed the crash happened in a driver thread, so the crashes were async to the thread doing the GL calls. I was able to disable different parts of the game to stop the issue (but the game was not playable in that state). It looked like it was not releated to what the game was doing but to how much it was doing. In the end I assumed that the driver had trouble to correctly schedule some combinations of work. I was able to work around it by forcing it to complete some steps on my schedule (I placed a few calls to glFinish at strategic places in the games initialization code, when textures and meshes were prepared).

So, if I had to debug this issue, I would try to place the equivalent of glFinish for D3D at a few strategic places in the startup and shutdown code of the game.

[Eiermann]

No crashes since 2.0.10