XFX RX 6950 XT Crashing my System!

[Leesureone]

Here is the sanitized (removed SMBIOS) version of my config.plist. Anything that I can change that could help but won't hurt?
Thanks!!!

Uploading just the config.plist helps but its really best to zip and upload your entire EFI folder.

 

[kSilva]

Uploading just the config.plist helps but its really best to zip and upload your entire EFI folder.

As requested, here you go!
By the ways if you guys help me solve this problem I'll definitely give the page a $$$ contribution for all the help I have got.

Thank you!

 

[Leesureone]

As requested, here you go!
By the ways if you guys help me solve this problem I'll definitely give the page a $$$ contribution for all the help I have got.

Thank you!

Everything looks pretty good.
Question: If you run gfxutil do the values match the SSDT-BRG0 address (PEG0) and device-id (BF730000 ) in the Device Properties in your config.plist? Link to the utility below.
https://github.com/acidanthera/gfxutil/releases/tag/1.81b

#1,304 This post from Vandroiy helped me get my 6950 going.

Also do you need the boot argument -radcodec? I'd try without if the above is all correct.

 

[kSilva]

Everything looks pretty good.
Question: If you run gfxutil do the values match the SSDT-BRG0 address (PEG0) and device-id (BF730000 ) in the Device Properties in your config.plist? Link to the utility below.
https://github.com/acidanthera/gfxutil/releases/tag/1.81b

#1,304 This post from Vandroiy helped me get my 6950 going.

Also do you need the boot argument -radcodec? I'd try without if the above is all correct.

Yes, the values match the SSDT-BRG0 address.
I already tried without the boot argument -radcoedc. Still, same issue

 

[Leesureone]

Yes, the values match the SSDT-BRG0 address.
I already tried without the boot argument -radcoedc. Still, same issue

Well then, good job. My only other suggestion besides trying a fresh install is to see in your bios if you can set the PCIe Settings for the graphics card to 3.0 bandwidth. The card supports 4.0, probably, but your motherboard won't. Doubt that is the issue but if you want to give it a shot maybe it will help.

 

[Edhawk]

Ok, given all the information you have provided I would say your PNY NVME dive is likely to be the issue. It uses a Phison PS5016-E16 controller. Some other NVME drives using these cheaper Phison controllers are known to be problematic in macOS.

Logical step to test to see if this is the cause of your issues would be to remove your current PNY macOS drive and install macOS on another drive. Use an SSD or NVME, doesn’t matter which as long as the drive is one with a known compatibility for working with macOS. Western Digital/SanDisk are the most compatible as Apple use similar drives from this company in their systems.

 

[Leesureone]

Ok, given all the information you have provided I would say your PNY NVME dive is likely to be the issue. It uses a Phison PS5016-E16 controller. Some other NVME drives using these cheaper Phison controllers are known to be problematic in macOS.

Logical step to test to see if this is the cause of your issues would be to remove your current PNY macOS drive and install macOS on another drive. Use an SSD or NVME, doesn’t matter which as long as the drive is one with a known compatibility for working with macOS. Western Digital/SanDisk are the most compatible as Apple use similar drives from this company in their systems.

I assumed (oh dang) he was already using that SSD prior to this and all he changed was the graphics card.

 

[kSilva]

Ok, given all the information you have provided I would say your PNY NVME dive is likely to be the issue. It uses a Phison PS5016-E16 controller. Some other NVME drives using these cheaper Phison controllers are known to be problematic in macOS.

Logical step to test to see if this is the cause of your issues would be to remove your current PNY macOS drive and install macOS on another drive. Use an SSD or NVME, doesn’t matter which as long as the drive is one with a known compatibility for working with macOS. Western Digital/SanDisk are the most compatible as Apple use similar drives from this company in their systems.

Awesome, I'll do that and report back. It might take me a bit since I will need to find a spare drive, but give that a try and I'll report back as soon as I can. You guys are awesome!

 

[trs96]

I will need to find a spare drive

If you need a new NVMe the deals at Amazon are exceptional now. SN850X is the best you can get for performance per dollar.

 

[kSilva]

Ok, given all the information you have provided I would say your PNY NVME dive is likely to be the issue. It uses a Phison PS5016-E16 controller. Some other NVME drives using these cheaper Phison controllers are known to be problematic in macOS.

Logical step to test to see if this is the cause of your issues would be to remove your current PNY macOS drive and install macOS on another drive. Use an SSD or NVME, doesn’t matter which as long as the drive is one with a known compatibility for working with macOS. Western Digital/SanDisk are the most compatible as Apple use similar drives from this company in their systems.

Hey fellas, I found an M.2 drive (XPG 1TB SX8200PNP) that I used before in the same rig with Monterrey installed in it. Only reason I removed that drive was because I upgraded to the current 4TB PNY in which I did a clean install. So, I went ahead and booted it up with the EFI bootloader that I had setup for the 6950xt card. Everything loaded up fine, I updated Geekbench and Lightroom to the latest version, however when I ran Geekbench the computer crashed and rebooted. I also tried Lightroom and it also crashed.
Do you think the issue is still the M.2 Drive, does that XPG also have issues, should I still try to buy at WD_Black?