abbeybas

Driver crash in Godhood

Discussion created by abbeybas on Jul 15, 2019
Latest reply on Jul 15, 2019 by abbeybas

I'm a developer on the game Godhood and we're having some issues with a crash in the AMD driver. Our game starts, but during loading the game crashes reliably. I've not been able to reproduce this issue locally. I have stacktraces of the crashes but no symbols so it's quite hard to figure out what the issue is. The crash also happens in a separate thread so I don't really know what triggers it.

 

I'm looking for some help to solve this issue. I would very much like to get in contact with a QA team or someone from AMD.

 

Information related to the crash (I can provide more on request, including dumps):

 

The crash so far happens on these graphics cards:

 

AMD Radeon HD 8670D
AMD Radeon HD 8400 / R3 Series
AMD Mobility Radeon HD 4650/5165
AMD Radeon HD 4890
AMD Radeon HD 4670
AMD Radeon HD 6290
AMD Radeon HD 7470M
AMD Radeon HD 6950
AMD Radeon HD 6620G
AMD Radeon HD 4710
AMD Mobility Radeon HD 4225/4250
AMD Radeon HD 6380G
AMD Radeon HD 5770
AMD Radeon HD 7660G
AMD Radeon HD 6570/7570/8550
AMD Radeon HD 7550M/7570M/7650M
AMD Radeon HD 6870

 

And with these OS'es:

 

Microsoft Windows 7 Home Basic EditionService Pack 1
Microsoft Windows 7 Ultimate EditionService Pack 1
Microsoft Windows 8.1 Home Edition (build 9600)
Microsoft Windows 8.1 Home Edition (build 9600)
Microsoft Windows 10 Education Edition (build 17763)
Microsoft Windows 10 Professional (build 17134)
Microsoft Windows 10 Home Edition (build 17763)

 

A typical crash stackframe looks like this:

0atidxx64.dllatidxx64.dll@0x13b8d9
1atidxx64.dllatidxx64.dll@0xe9091
2atidxx64.dllatidxx64.dll@0x945e5
3ntdll.dllntdll.dll@0x2a76e
4atidxx64.dllatidxx64.dll@0x55627
5atidxx64.dllatidxx64.dll@0x157249
6atidxx64.dllatidxx64.dll@0x157444
7atidxx64.dllatidxx64.dll@0x93984
8atidxx64.dllatidxx64.dll@0x91d00
9atidxx64.dllatidxx64.dll@0x53ab8
10atidxx64.dllatidxx64.dll@0x282eb1
11atidxx64.dllatidxx64.dll@0x27f3e5

 

The stackframe is always the same on the same machine but it can differ between different machines.

 

I've asked people to update their drivers, and it also happens with the latest drivers.

Outcomes