pastrychef's Asus ROG Strix Z370-G Gaming (WI-FI AC) build w/ i9-9900K + AMD 6600 XT

[pastrychef]

I'm having a bit of an issue with my Z370-G / MSI 580:

In a game (let's just call it SC2..) when I am scrolling around, I can make the Mac hang in about 10-15 minutes of play. Scrolling around on the "board" is a key part of the game, so after scrolling for a bit, the Mac will appear to hang - I see disk activity still, but the screen, graphically, is completely frozen; moving the mouse shows and does nothing. My fans don't go crazy, this happens OC'd or not OC'd, and so far I have done the following:

1. It started around 10.15 or so timeframe. It has happened in all the .1, .2, and .3 updates.
2. It took place with what was (up until then) a "known-good" Z370-G setup from back in the early days of this thread that I've been updating with the latest KEXTs and Clovers, but didn't go 'back to the source' to re-download the current setups.
3. That said, something obviously changed, and naturally I'm the main culprit.
4. I keep current on Clover (5103) and my Kexts, using Kext Updater v3.3.6 to stay current with kexts.
5. I can reproduce the problem with your v5.1.7 EFI folder and no customizations on my part - no SSDT, etc. - USB remains unpatched.
6. After mild customizations to your EFI folder (v5.1.7, switching from 18,3 iMac to iMacPro), updating to USBInjectAll.73, and nothing else, the problem persists.
7. In Windows, with either older or the latest AMD drivers and Windows 1909 fully patched to January 2020, it's perfect; no crashing whatsoever in full games, including SC2.
8. I can't make it crash any other time (in MacOS or Windows), but I really don't do anything else that would graphically stretch the machine & GPU.

The next thing I can think of to try is to pull an AMD 570 from a nearby computer and plug it into this to see if I can reproduce the problem. I could also try using the OpenCore folder... Are there any other suggestions?

To me, it sounds like some sort of issue with the RX 580 and Catalina... I don't know if there were any changes made to the drivers or fan curve. Are you able to see GPU temps?

If you can test with the RX 570, it would be great.

 

[Shlonakzeen]

Hi
Just managed to install Catalina , all USB ports no working except USB 3.1 Gen 2 Type A
Tried to use Hackintool to see which ports available ( plug/unplug USB ) but no ports available.
IOREG show no HS or SS ports on XHCI@14

any ideas ?

 

[pastrychef]

Hi
Just managed to install Catalina , all USB ports no working except USB 3.1 Gen 2 Type A
Tried to use Hackintool to see which ports available ( plug/unplug USB ) but no ports available.
IOREG show no HS or SS ports on XHCI@14

any ideas ?

The USB 3.1 gen 2 ports on Z370 are all on a separate ASM2142 controller and do not need any configuring.

How do you have your USB configured? Are you suing the KextsToPatch? Do you have USBInjectAll installed?

 

[dclive]

To me, it sounds like some sort of issue with the RX 580 and Catalina... I don't know if there were any changes made to the drivers or fan curve. Are you able to see GPU temps?

If you can test with the RX 570, it would be great.

I moved the RX580 to another "Mac" - no issues.
I moved the RX570 into this Mac - same issue, hang and crash.

So there's something about this Mac (motherboard, RAM, etc.) that causes a hang in graphics-heavy (games) software. I'll reset all OC'ing to defaults (again) and retest. Any other items to try? Seems unlikely both cards are running hot (particularly just a RX570) and the case has plenty of cooling and moving air. The CPU isn't getting hot. It's frustrating.

 

[pastrychef]

I moved the RX580 to another "Mac" - no issues.
I moved the RX570 into this Mac - same issue, hang and crash.

So there's something about this Mac (motherboard, RAM, etc.) that causes a hang in graphics-heavy (games) software. I'll reset all OC'ing to defaults (again) and retest. Any other items to try? Seems unlikely both cards are running hot (particularly just a RX570) and the case has plenty of cooling and moving air. The CPU isn't getting hot. It's frustrating.

Yeah, if both cards are exhibiting the same behavior, the build or configuration is probably the problem.

Yes, please test with all overclocking disabled including XMP.

 

[dclive]

Yeah, if both cards are exhibiting the same behavior, the build or configuration is probably the problem.

Yes, please test with all overclocking disabled including XMP.

I did a "Load optimized defaults", which removed all OC'ing including XMP.
I then printed out from your guide the exact BIOS changes to make and did those.
I then rebooted, and was able to reproduce the error again within minutes of starting gameplay.

The stack on both says somewhat similar things; on the other it's cpu0 but otherwise similar:

panic(cpu 6 caller 0xffffff8018c652fa): Kernel trap at 0xffffff7f9befce97, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0xffffff81def77004, CR3: 0x0000000024934000, CR4: 0x00000000003626e0
RAX: 0x0000000000000331, RBX: 0x0000000000000331, RCX: 0xffffff821227bcc4, RDX: 0x0000000000000340
RSP: 0xffffff821227bc78, RBP: 0xffffff821227bc80, RSI: 0xffffff81def76340, RDI: 0x0000000000000331
R8: 0x0000000000000001, R9: 0x0000000000000003, R10: 0x0000000000000000, R11: 0x0000000000000000
R12: 0xffffff821227bdd8, R13: 0xffffff8211008f48, R14: 0xffffff81def76340, R15: 0xffffff821227bde4
RFL: 0x0000000000010283, RIP: 0xffffff7f9befce97, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0xffffff81def77004, Error code: 0x0000000000000000, Fault CPU: 0x6, PL: 0, VF: 1

Backtrace (CPU 6), Frame : Return Address
0xffffff821227b6d0 : 0xffffff8018b3bb2b mach_kernel : _handle_debugger_trap + 0x47b
0xffffff821227b720 : 0xffffff8018c734d5 mach_kernel : _kdp_i386_trap + 0x155
0xffffff821227b760 : 0xffffff8018c64f4e mach_kernel : _kernel_trap + 0x4ee
0xffffff821227b7b0 : 0xffffff8018ae2a40 mach_kernel : _return_from_trap + 0xe0
0xffffff821227b7d0 : 0xffffff8018b3b217 mach_kernel : _DebuggerTrapWithState + 0x17
0xffffff821227b8d0 : 0xffffff8018b3b5fb mach_kernel : _panic_trap_to_debugger + 0x21b
0xffffff821227b920 : 0xffffff80192d2aa9 mach_kernel : _panic + 0x61
0xffffff821227b990 : 0xffffff8018c652fa mach_kernel : _sync_iss_to_iks + 0x2aa
0xffffff821227bb10 : 0xffffff8018c64ff8 mach_kernel : _kernel_trap + 0x598
0xffffff821227bb60 : 0xffffff8018ae2a40 mach_kernel : _return_from_trap + 0xe0
0xffffff821227bb80 : 0xffffff7f9befce97 com.apple.kext.AMDRadeonX4000 : __ZN29AMDRadeonX4000_AMDVIPM4Engine21validateCommandBufferEPjjS0_ + 0x19
0xffffff821227bc80 : 0xffffff7f9be62df1 com.apple.kext.AMDRadeonX4000 : __ZN30AMDRadeonX4000_AMDAccelChannel38writePendingCommandInfoDiagnosisReportERPcRjP18AMD_COMMAND_BUFFERP11IOAccelTask + 0x1cd
0xffffff821227bcf0 : 0xffffff7f9be62bcb com.apple.kext.AMDRadeonX4000 : __ZN30AMDRadeonX4000_AMDAccelChannel20writeDiagnosisReportERPcRj + 0x715
0xffffff821227bd80 : 0xffffff7f9be5e40a com.apple.kext.AMDRadeonX4000 : __ZN37AMDRadeonX4000_AMDGraphicsAccelerator20writeDiagnosisReportERPcRj + 0x168
0xffffff821227bdc0 : 0xffffff7f9be62432 com.apple.kext.AMDRadeonX4000 : __ZN30AMDRadeonX4000_AMDAccelChannel26getHardwareDiagnosisReportEPj + 0x192
0xffffff821227be10 : 0xffffff7f9bc3f877 com.apple.iokit.IOAcceleratorFamily2 : __ZN19IOAccelFIFOChannel27restartEv + 0x10f
0xffffff821227be60 : 0xffffff7f9bc4d438 com.apple.iokit.IOAcceleratorFamily2 : __ZN20IOAccelEventMachine215restart_channelEv + 0xe8
0xffffff821227bea0 : 0xffffff7f9bc4cbf8 com.apple.iokit.IOAcceleratorFamily2 : __ZN20IOAccelEventMachine218hardwareErrorEventEv + 0x206
0xffffff821227bee0 : 0xffffff801924109d mach_kernel : __ZN22IOInterruptEventSource12checkForWorkEv + 0x17d
0xffffff821227bf30 : 0xffffff801923f9e2 mach_kernel : __ZN10IOWorkLoop15runEventSourcesEv + 0x192
0xffffff821227bf70 : 0xffffff801923ef6c mach_kernel : __ZN10IOWorkLoop10threadMainEv + 0x2c
0xffffff821227bfa0 : 0xffffff8018ae213e mach_kernel : _call_continuation + 0x2e
Kernel Extensions in backtrace:
com.apple.iokit.IOAcceleratorFamily2(438.3.1)[66992525-3204-3CB0-8F03-4B70031B1CF2]@0xffffff7f9bc3b000->0xffffff7f9bcfefff
dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[A243D030-19AC-30AA-AC70-6C786DF9E6CE]@0xffffff7f99bf7000
dependency: com.apple.iokit.IOPCIFamily(2.9)[ADD485B5-3EF8-37C4-B3C5-F86326E497A4]@0xffffff7f9952f000
dependency: com.apple.iokit.IOSurface(269.6)[42377B3B-D14A-368E-820F-07E7EA666198]@0xffffff7f9bc0a000
dependency: com.apple.iokit.IOGraphicsFamily(569.4)[1F9B5D88-52DB-3A16-8373-4F608A3CB2D8]@0xffffff7f99f18000
dependency: com.apple.iokit.IOReportFamily(47)[988360A2-2E10-3014-A119-BE81BC045A10]@0xffffff7f9992c000
com.apple.kext.AMDRadeonX4000(3.0.5)[5FD7AE5F-C03C-34A1-803F-ACA9B68524D0]@0xffffff7f9be58000->0xffffff7f9c39cfff
dependency: com.apple.iokit.IOPCIFamily(2.9)[ADD485B5-3EF8-37C4-B3C5-F86326E497A4]@0xffffff7f9952f000
dependency: com.apple.iokit.IOSurface(269.6)[42377B3B-D14A-368E-820F-07E7EA666198]@0xffffff7f9bc0a000
dependency: com.apple.iokit.IOGraphicsFamily(569.4)[1F9B5D88-52DB-3A16-8373-4F608A3CB2D8]@0xffffff7f99f18000
dependency: com.apple.iokit.IOAcceleratorFamily2(438.3.1)[66992525-3204-3CB0-8F03-4B70031B1CF2]@0xffffff7f9bc3b000

The other backtrace (from another crash this morning) is similar:
Kernel Extensions in backtrace:
com.apple.iokit.IOAcceleratorFamily2(438.3.1)[66992525-3204-3CB0-8F03-4B70031B1CF2]@0xffffff7f8ee3b000->0xffffff7f8eefefff
dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[A243D030-19AC-30AA-AC70-6C786DF9E6CE]@0xffffff7f8cdf7000
dependency: com.apple.iokit.IOPCIFamily(2.9)[ADD485B5-3EF8-37C4-B3C5-F86326E497A4]@0xffffff7f8c72f000
dependency: com.apple.iokit.IOSurface(269.6)[42377B3B-D14A-368E-820F-07E7EA666198]@0xffffff7f8ee0a000
dependency: com.apple.iokit.IOGraphicsFamily(569.4)[1F9B5D88-52DB-3A16-8373-4F608A3CB2D8]@0xffffff7f8d118000
dependency: com.apple.iokit.IOReportFamily(47)[988360A2-2E10-3014-A119-BE81BC045A10]@0xffffff7f8cb2c000
com.apple.kext.AMDRadeonX4000(3.0.5)[5FD7AE5F-C03C-34A1-803F-ACA9B68524D0]@0xffffff7f8f058000->0xffffff7f8f59cfff
dependency: com.apple.iokit.IOPCIFamily(2.9)[ADD485B5-3EF8-37C4-B3C5-F86326E497A4]@0xffffff7f8c72f000
dependency: com.apple.iokit.IOSurface(269.6)[42377B3B-D14A-368E-820F-07E7EA666198]@0xffffff7f8ee0a000
dependency: com.apple.iokit.IOGraphicsFamily(569.4)[1F9B5D88-52DB-3A16-8373-4F608A3CB2D8]@0xffffff7f8d118000
dependency: com.apple.iokit.IOAcceleratorFamily2(438.3.1)[66992525-3204-3CB0-8F03-4B70031B1CF2]@0xffffff7f8ee3b000

Without access to a debugger (windbg, anyone?) it's tough for me to do more with this, but I do note a panic file (memory dump describing the kernel memory at the time of the crash, hopefully) was written.

 

[Shlonakzeen]

The USB 3.1 gen 2 ports on Z370 are all on a separate ASM2142 controller and do not need any configuring.

How do you have your USB configured? Are you suing the KextsToPatch? Do you have USBInjectAll installed?

Hi PastryChef
I have tried to follow KGP guide for specific board kext creation / and Rehab Custom SSDT for USBInjectAll.kext specific to my board but both of these guide requires IOREG to come up with XHCI@14 USB port report , which has failed so far as you can see from attached photos.
I am using USBInjectAll.kext on EFI folder on clover EFI/Clover/kexts/other , and also on Library/Extension of main drive.

I tried with and without usb injected kexts but alway IOREG not showing XHCI@14 USB port report.
please see attached EFI folder

many thanks

 

[Loloflatsix]

Hi PastryChef
I have tried to follow KGP guide for specific board kext creation / and Rehab Custom SSDT for USBInjectAll.kext specific to my board but both of these guide requires IOREG to come up with XHCI@14 USB port report , which has failed so far as you can see from attached photos.
I am using USBInjectAll.kext on EFI folder on clover EFI/Clover/kexts/other , and also on Library/Extension of main drive.

I tried with and without usb injected kexts but alway IOREG not showing XHCI@14 USB port report.
please see attached EFI folder

many thanks

You can create your own USB.kext XHC USB Kext Creation Guideline

 

[dclive]

I'm a bit lost on the work required to get USB working seamlessly:

Here are the Hackintool 3.0x directions:

1. Place the USBInjectAll.kext (for port discovery) into EFI/CLOVER/kexts/Other
2. USBInjectAll.kext Requirements:
3. Clover->DSDT Renames (if detected)
   • XHCI -> XHC
   • XHC1 -> XHC
   • EHC1 -> EH01
   • EHC2 -> EH02
4. Reboot
5. Run Hackintool then go to General->Installed to check USBInjectAll is installed correctly
   • Eg. USBInjectAll: Yes (Release-0.7.1)

So do we need to focus on only using .71, or is .73 or .74 OK nowadays?

1. Go to the General->USB tab to check your USB Controllers list. Based on your USB Controller you may need to install additional kexts:
   • 8086:8CB1 and macOS < 10.11.1 -> XHCI-9-series.kext
   • 8086:8D31, 8086:A2AF, 8086:A36D, 8086:9DED -> XHCI-unsupported.kext
   • 8086:1E31, 8086:8C31, 8086:8CB1, 8086:8D31, 8086:9C31, 8086:9CB1 -> FakePCIID.kext + FakePCIID_XHCIMux.kext

......so this means we need to include XHCI-unsupported.kext, because 8086-A2AF appears in General/USB. No worries, I found it somewhere (is it the right one, right version? Who knows...) .... moving on...

1. Reboot if you need to install one of the additional kexts then run Hackintool again
2. Go to the General->USB tab
3. Select all items in the USB Ports list and select the “Delete” then the “Refresh” button
4. Reboot with -uia_exclude_ss uia_include=HS01,HS02 boot flags
   • Change the HS01,HS02 ports to the ones you have your mouse and keyboard attached
5. Run Hackintool and go to the General->USB tab
6. Plug and unplug a USB 2.0 device into all ports on your system
   • The ports that are active will remain highlighted green
   • Delete all ports that are not highlighted green

Fine to this point. Mouse and keyboard work as I've excluded those ports successfully in boot args. I do take this to mean "Plug in something USB2 to ALL available USB ports" - which strikes me as odd due to the 15 port limit... (why enable what you know you won't use as a USB2 port, after all?)

1. Reboot with -uia_exclude_hs boot flag and remove the -uia_exclude_ss boot flag

First point of confusion. I noticed when I rebooted that Clover Configurator shows the two items I added in step 4 above as two distinct lines. So do I remove .. both? Just the -uia_exclude_ss line? If I remove both, won't I lose mouse/keyboard control?

1. Run Hackintool and go to the General->USB tab
   • Plug and unplug a USB 3.0 device into all ports on your system
   • Plug and unplug a TypeC device into all ports (in both orientations)
   • The ports that are active will remain highlighted green
   • Delete all ports that are not highlighted green
2. Set each port to the appropriate Connector using the drop down list
   • USB ports with devices permanently attached (eg. M.2 Bluetooth card) should be set to “Internal”
   • HSxx ports connected to USB3 ports should be set to USB3
   • Internal HUBs are typically connected to ports PR11 and PR21 and therefore should be set to “Internal”
   • TypeC:
     • If it uses the same HSxx/SSxx in both orientations, then it has an internal switch (use “TypeC+Sw”)
     • If it uses a different HSxx/SSxx in each orientation, then it has no switch (use “TypeC”)

So I'm confused here. How do I know what the appropriate connector is? Remember, I'm looking at Hackintool where only the USB3 devices are showing; everything else is green-but-blank or green-but-showing-"AppleUSBXHCI Root Hub Simulation". Was I supposed to write down the previous page (during the USB2 test) to see what devices were in use in which ports? So confused here...

1. Use the “Export” button to generate files to your Desktop
   • Copy SSDT-EC.aml (if created) to EFI/CLOVER/ACPI/patched
   • Choose one of the following two:
     1. Copy USBPorts.kext to EFI/CLOVER/kexts/Other or;
     2. Copy SSDT-UIAC.aml and SSDT-USBX.aml (if created) to EFI/CLOVER/ACPI/patched
2. You can now perform a clean up and remove unnecessary files:
   • Remove custom boot flags (-uia_exclude_ss -uia_exclude_hs uia_include=x)
   • Remove USBInjectAll.kext (if using USBPorts.kext)

So what about the XHCI-unsupported.kext? Does that stay, or do we get rid of that, too?

1. Reboot
2. Run Hackintool and go to the General->USB tab
3. Select all items in the USB Ports list and select the “Delete” then the “Refresh” button
   • Now you can check all ports are working correctly
   • If you need to change a Connector type you will need to export your USBPorts.kext over the current one
   • If you made a mistake delete USBPorts.kext and start from the beginning of the instructions again

What's the overall goal - to only test USB3 and USB2 devices in the ports in which we expect to use them? So it behooves us to put USB2 *AND* USB3 devices into the front ports (where assumedly we will plug in many things over the course of device ownership) but for the back ports, perhaps we only enable the HS/SS ports with the USB2/USB3 devices located where we expect to use them? (In other words, for the back ports, make some ports USB2 or USB3 only, to keep under the 15 device limit) ?

USB setup is still a touch messy.

 

[pastrychef]

I did a "Load optimized defaults", which removed all OC'ing including XMP.
I then printed out from your guide the exact BIOS changes to make and did those.
I then rebooted, and was able to reproduce the error again within minutes of starting gameplay.

The stack on both says somewhat similar things; on the other it's cpu0 but otherwise similar:

panic(cpu 6 caller 0xffffff8018c652fa): Kernel trap at 0xffffff7f9befce97, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0xffffff81def77004, CR3: 0x0000000024934000, CR4: 0x00000000003626e0
RAX: 0x0000000000000331, RBX: 0x0000000000000331, RCX: 0xffffff821227bcc4, RDX: 0x0000000000000340
RSP: 0xffffff821227bc78, RBP: 0xffffff821227bc80, RSI: 0xffffff81def76340, RDI: 0x0000000000000331
R8: 0x0000000000000001, R9: 0x0000000000000003, R10: 0x0000000000000000, R11: 0x0000000000000000
R12: 0xffffff821227bdd8, R13: 0xffffff8211008f48, R14: 0xffffff81def76340, R15: 0xffffff821227bde4
RFL: 0x0000000000010283, RIP: 0xffffff7f9befce97, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0xffffff81def77004, Error code: 0x0000000000000000, Fault CPU: 0x6, PL: 0, VF: 1

Backtrace (CPU 6), Frame : Return Address
0xffffff821227b6d0 : 0xffffff8018b3bb2b mach_kernel : _handle_debugger_trap + 0x47b
0xffffff821227b720 : 0xffffff8018c734d5 mach_kernel : _kdp_i386_trap + 0x155
0xffffff821227b760 : 0xffffff8018c64f4e mach_kernel : _kernel_trap + 0x4ee
0xffffff821227b7b0 : 0xffffff8018ae2a40 mach_kernel : _return_from_trap + 0xe0
0xffffff821227b7d0 : 0xffffff8018b3b217 mach_kernel : _DebuggerTrapWithState + 0x17
0xffffff821227b8d0 : 0xffffff8018b3b5fb mach_kernel : _panic_trap_to_debugger + 0x21b
0xffffff821227b920 : 0xffffff80192d2aa9 mach_kernel : _panic + 0x61
0xffffff821227b990 : 0xffffff8018c652fa mach_kernel : _sync_iss_to_iks + 0x2aa
0xffffff821227bb10 : 0xffffff8018c64ff8 mach_kernel : _kernel_trap + 0x598
0xffffff821227bb60 : 0xffffff8018ae2a40 mach_kernel : _return_from_trap + 0xe0
0xffffff821227bb80 : 0xffffff7f9befce97 com.apple.kext.AMDRadeonX4000 : __ZN29AMDRadeonX4000_AMDVIPM4Engine21validateCommandBufferEPjjS0_ + 0x19
0xffffff821227bc80 : 0xffffff7f9be62df1 com.apple.kext.AMDRadeonX4000 : __ZN30AMDRadeonX4000_AMDAccelChannel38writePendingCommandInfoDiagnosisReportERPcRjP18AMD_COMMAND_BUFFERP11IOAccelTask + 0x1cd
0xffffff821227bcf0 : 0xffffff7f9be62bcb com.apple.kext.AMDRadeonX4000 : __ZN30AMDRadeonX4000_AMDAccelChannel20writeDiagnosisReportERPcRj + 0x715
0xffffff821227bd80 : 0xffffff7f9be5e40a com.apple.kext.AMDRadeonX4000 : __ZN37AMDRadeonX4000_AMDGraphicsAccelerator20writeDiagnosisReportERPcRj + 0x168
0xffffff821227bdc0 : 0xffffff7f9be62432 com.apple.kext.AMDRadeonX4000 : __ZN30AMDRadeonX4000_AMDAccelChannel26getHardwareDiagnosisReportEPj + 0x192
0xffffff821227be10 : 0xffffff7f9bc3f877 com.apple.iokit.IOAcceleratorFamily2 : __ZN19IOAccelFIFOChannel27restartEv + 0x10f
0xffffff821227be60 : 0xffffff7f9bc4d438 com.apple.iokit.IOAcceleratorFamily2 : __ZN20IOAccelEventMachine215restart_channelEv + 0xe8
0xffffff821227bea0 : 0xffffff7f9bc4cbf8 com.apple.iokit.IOAcceleratorFamily2 : __ZN20IOAccelEventMachine218hardwareErrorEventEv + 0x206
0xffffff821227bee0 : 0xffffff801924109d mach_kernel : __ZN22IOInterruptEventSource12checkForWorkEv + 0x17d
0xffffff821227bf30 : 0xffffff801923f9e2 mach_kernel : __ZN10IOWorkLoop15runEventSourcesEv + 0x192
0xffffff821227bf70 : 0xffffff801923ef6c mach_kernel : __ZN10IOWorkLoop10threadMainEv + 0x2c
0xffffff821227bfa0 : 0xffffff8018ae213e mach_kernel : _call_continuation + 0x2e
Kernel Extensions in backtrace:
com.apple.iokit.IOAcceleratorFamily2(438.3.1)[66992525-3204-3CB0-8F03-4B70031B1CF2]@0xffffff7f9bc3b000->0xffffff7f9bcfefff
dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[A243D030-19AC-30AA-AC70-6C786DF9E6CE]@0xffffff7f99bf7000
dependency: com.apple.iokit.IOPCIFamily(2.9)[ADD485B5-3EF8-37C4-B3C5-F86326E497A4]@0xffffff7f9952f000
dependency: com.apple.iokit.IOSurface(269.6)[42377B3B-D14A-368E-820F-07E7EA666198]@0xffffff7f9bc0a000
dependency: com.apple.iokit.IOGraphicsFamily(569.4)[1F9B5D88-52DB-3A16-8373-4F608A3CB2D8]@0xffffff7f99f18000
dependency: com.apple.iokit.IOReportFamily(47)[988360A2-2E10-3014-A119-BE81BC045A10]@0xffffff7f9992c000
com.apple.kext.AMDRadeonX4000(3.0.5)[5FD7AE5F-C03C-34A1-803F-ACA9B68524D0]@0xffffff7f9be58000->0xffffff7f9c39cfff
dependency: com.apple.iokit.IOPCIFamily(2.9)[ADD485B5-3EF8-37C4-B3C5-F86326E497A4]@0xffffff7f9952f000
dependency: com.apple.iokit.IOSurface(269.6)[42377B3B-D14A-368E-820F-07E7EA666198]@0xffffff7f9bc0a000
dependency: com.apple.iokit.IOGraphicsFamily(569.4)[1F9B5D88-52DB-3A16-8373-4F608A3CB2D8]@0xffffff7f99f18000
dependency: com.apple.iokit.IOAcceleratorFamily2(438.3.1)[66992525-3204-3CB0-8F03-4B70031B1CF2]@0xffffff7f9bc3b000

The other backtrace (from another crash this morning) is similar:
Kernel Extensions in backtrace:
com.apple.iokit.IOAcceleratorFamily2(438.3.1)[66992525-3204-3CB0-8F03-4B70031B1CF2]@0xffffff7f8ee3b000->0xffffff7f8eefefff
dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[A243D030-19AC-30AA-AC70-6C786DF9E6CE]@0xffffff7f8cdf7000
dependency: com.apple.iokit.IOPCIFamily(2.9)[ADD485B5-3EF8-37C4-B3C5-F86326E497A4]@0xffffff7f8c72f000
dependency: com.apple.iokit.IOSurface(269.6)[42377B3B-D14A-368E-820F-07E7EA666198]@0xffffff7f8ee0a000
dependency: com.apple.iokit.IOGraphicsFamily(569.4)[1F9B5D88-52DB-3A16-8373-4F608A3CB2D8]@0xffffff7f8d118000
dependency: com.apple.iokit.IOReportFamily(47)[988360A2-2E10-3014-A119-BE81BC045A10]@0xffffff7f8cb2c000
com.apple.kext.AMDRadeonX4000(3.0.5)[5FD7AE5F-C03C-34A1-803F-ACA9B68524D0]@0xffffff7f8f058000->0xffffff7f8f59cfff
dependency: com.apple.iokit.IOPCIFamily(2.9)[ADD485B5-3EF8-37C4-B3C5-F86326E497A4]@0xffffff7f8c72f000
dependency: com.apple.iokit.IOSurface(269.6)[42377B3B-D14A-368E-820F-07E7EA666198]@0xffffff7f8ee0a000
dependency: com.apple.iokit.IOGraphicsFamily(569.4)[1F9B5D88-52DB-3A16-8373-4F608A3CB2D8]@0xffffff7f8d118000
dependency: com.apple.iokit.IOAcceleratorFamily2(438.3.1)[66992525-3204-3CB0-8F03-4B70031B1CF2]@0xffffff7f8ee3b000

Without access to a debugger (windbg, anyone?) it's tough for me to do more with this, but I do note a panic file (memory dump describing the kernel memory at the time of the crash, hopefully) was written.

Something is crashing the video drivers... This game runs fine in Mojave? Maybe the game itself needs updating?