Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

GygaBat

macrumors newbie
Original poster
Sep 29, 2020
18
2
Italy
Hello !

First of all I'd like to thank this community for the very great tips I've learned so far. I've read hundreds of pages but yet I'm not tired to learn from such experts.

So I've actually upgraded my system to a Mac Pro 5.1 (2010) dual hex X5690 @3.46 GHz, 128 Gb ram, and to get the 144.0.0.0.0 boot rom and Mojave I've replaced the stock ATI HD 5770 and bought a refurbished (AMD Radeon) Gigabyte HD 7950 rev 2.0

GV-R795WF3-3GD(rev2.0)

GV-R795WF3-3GD(rev1.0/2.0) | Graphics Card - GIGABYTE Italy

the one with 6 + 8 pins cables, just to have the possibility to kick in a Sonnet M.2 4x4 Silent PCIe NVMe card with 4 blades (3 for data RAID plus the bootable OS one of course) to max out this machine and, why not, to take advantage of the supposed improvements of an APFS more mature Mojave OS.

I'm doing some tests before installing the SSD blades system , on a 64 Gb SSD drive, where I've installed a clean install of Mojave 10.14.6 and the suppletive Apple update I've read is meant to solve graphic issues and stuffs. The GPU, as told, is the Gigabyte HD 7950, connected (through 2x Apple MiniDisplay to VGA adapters, adapter version 1,03) to two relatively ancestral VGA monitors (a Samsung SMS24A350H and a LG E1911S).


I premise the followings:

1 - I've regularly flashed the 144 boot rom on the Mac Pro, NOT from bootable Mojave USB installer but from the App folder installer application, as instructed, with no issues detected in the process.

2 - The GPU I've bought is told to be flashed for mac, in order to get the boot screen and full compatibility, and indeed this is true. It's regularly recognized by the system report as "AMD Radeon HD 7950" , both in the graphic/monitor page and in the PCI page (tho the "ATY, HamachiParent" driver thingy appears to be missing) and even both the VGA monitors are seen, with specs and all. The GPU effectively displays both the monitors, either in High Sierra 13.6 (which is the "native" OS I was using before, with the latest boot rom available before the 144 one) and in Mojave, with no issues the eye can detect.

3 - After acquiring the 144 boot rom, I've tried any possible solution of installation in order to solve my issues: Mojave clean install to newly formatted SSD, to HDD, over High Sierra 13.6 from the app, from USB stick, tried the 10.14.4 in place of the 10.14.6 installer, updated from Software Updates to the latest update, disabled SIP, but nothing worked, as the issues I'm going to talk about keep returning, with flavored variations, but with pretty defined common aspects to all the diagnostic logs I've collected. I've also tried installing Mojave on a HFS+ HD, but no go. Not to say I've applied SMC and NVRAM resets a thousand times my fingers will be stretched forever in that position.

4 - Since 3 days, I'm testing the system stripped down to the minimum, only 4 Gigs of factory ram, only the GPU no extra PCI cards, no extra HDD, just the original keyboard and mouse in different usb ports and either 1 or 2 monitors connected, which actually is the fact that triggers the issues.

5 - In High Sierra, I have none of the following issues.


These are the problems in Mojave:

With 2 monitors connected, when I shut down the system from the Apple menu (not rebooting), at the next startup by pushing the power button I get NO kernel panics, but I get the ".shutdownStall" diagnostic message in the Logs folder because of the previous shut downs, while if I reboot from the Apple menu, at reboot I always get the multi-language white screen of Death, telling me “my computer has rebooted because of a problem”, even though I've not heard any reboot chime after the regular one, plus the consequent kernel panic message in the Logs folder I'm going to report in the shortest time.

In this very case, I've notice the boot screen shows the Apple and the progress bar, then just past the half of the loading some purple-line glitches, then a black screen, and only then the multi-language WSOD. When the desktop appears, I am suddenly informed again of the issue with the diagnostic log.

Putting the mac pro to screensaver, to sleep, to stop, programming these or less, does not give back any diagnostic issue, just the shut down gives the ".shutdownStall" and the reboot the kernel panic.

And, magically, when I boot in safe mode all is fine, although I always see some artifacts during the boot loading, purple lines, sometimes grey squares and rarely the Apple logo distorted in its white screen with grey stripes crossing vertically . . a sign of good health of course . .

Now the funny thing is that if I connect only one monitor, irrelevant which one, doesn’t matter the output mini dp port I choose , I get none of the mentioned issues (apart some purple tiny lines at about half-boot),and I love to stress the fact that in High Sierra 10.13.6 with single or dual display my Logs folder remains crystal clean.

If boot the mac with the GPU bios switch positioned on PC I get the same results already explained, but with no boot screen as expected, hence fully working with one monitor, but these issues with dual setup.

In other words it seems like 2 monitors (max resolution is 1920x1080 cause the monitors are old and crappy) are too much to handle in Mojave, but one’s still good.

Among all, I’ve collected for you the following reports, choosing the ones I reputed the nicest and most “expressive” profiles, in fact they are all the same to me.


I really hope some expert here could help me sorting out this thing and I’m sorry for the long post and all the words, but I wanted to be precise at best, before contacting the vendor for an eventual refund. Thank you !
 

Attachments

  • Kernel_2020-09-30-052004_Mac-Pro-di-TESTHD.txt
    9.4 KB · Views: 226
  • Kernel_2020-09-30-115548_Mac-Pro-di-TESTHD.txt
    9.4 KB · Views: 167
  • Kernel_2020-10-01-041054_Mac-Pro-di-TESTHD.txt
    9.5 KB · Views: 230
  • Kernel_2020-10-01-041422_Mac-Pro-di-TESTHD.txt
    9.1 KB · Views: 226
  • Kernel_2020-10-01-044101_Mac-Pro-di-TESTHD.txt
    9.1 KB · Views: 231
Last edited:

h9826790

macrumors P6
Apr 3, 2014
16,656
8,587
Hong Kong
Hello !

First of all I'd like to thank this community for the very great tips I've learned so far. I've read hundreds of pages but yet I'm not tired to learn from such experts.

So I've actually upgraded my system to a Mac Pro 5.1 (2010) dual hex X5690 @3.46 GHz, 128 Gb ram, and to get the 144.0.0.0.0 boot rom and Mojave I've replaced the stock ATI HD 5770 and bought a refurbished (AMD Radeon) Gigabyte HD 7950 rev 2.0, the one with 6 + 8 pins cable, just to have the possibility to kick in a Sonnet M.2 4x4 Silent PCIe NVMe card with 4 blades (3 for data RAID plus the bootable OS one of course) to max out this machine and, why not, to take advantage of the supposed improvements of an APFS more mature Mojave OS.

I'm doing some tests before installing the SSD blades system , on a 64 Gb SSD drive, where I've installed a clean install of Mojave 10.14.6 and the suppletive Apple update I've read is meant to solve graphic issues and stuffs. The GPU, as told, is the Gigabyte HD 7950, connected (through 2x Apple MiniDisplay to VGA adapters, adapter version 1,03) to two relatively ancestral VGA monitors (a Samsung SMS24A350H and a LG E1911S).


I premise the followings:

1 - I've regularly flashed the 144 boot rom on the Mac Pro, NOT from bootable Mojave USB installer but from the App folder installer application, as instructed, with no issues detected in the process.

2 - The GPU I've bought is told to be flashed for mac, in order to get the boot screen and full compatibility, and indeed this is true. It's regularly recognized by the system report as "AMD Radeon HD 7950" , both in the graphic/monitor page and in the PCI page (tho the "ATY, HamachiParent" driver thingy appears to be missing) and even both the VGA monitors are seen, with specs and all. The GPU effectively displays both the monitors, either in High Sierra 13.6 (which is the "native" OS I was using before, with the latest boot rom available before the 144 one) and in Mojave, with no issues the eye can detect.

3 - After acquiring the 144 boot rom, I've tried any possible solution of installation in order to solve my issues: Mojave clean install to newly formatted SSD, to HDD, over High Sierra 13.6 from the app, from USB stick, tried the 10.14.4 in place of the 10.14.6 installer, updated from Software Updates to the latest update, disabled SIP, but nothing worked, as the issues I'm going to talk about keep returning, with flavored variations, but with pretty defined common aspects to all the diagnostic logs I've collected. I've also tried installing Mojave on a HFS+ HD, but no go. Not to say I've applied SMC and NVRAM resets a thousand times my fingers will be stretched forever in that position.

4 - Since 2 days, I'm testing the system stripped down to the minimum, only 4 Gigs of factory ram, only the GPU no extra PCI cards, no extra HDD, just the original keyboard and mouse in different usb ports and either 1 or 2 monitors connected, which actually is the fact that triggers the issues.

5 - In High Sierra, I have none of the following issues.


These are the problems in Mojave:

With 2 monitors connected, when I shut down the system from the Apple menu (not rebooting), at the next startup by pushing the power button I get NO kernel panics, but I get the ".shutdownStall" diagnostic message in the Logs folder because of the previous shut downs, while if I reboot from the Apple menu, at reboot I always get the multi-language white screen of Death, telling me “my computer has rebooted because of a problem”, even though I've not heard any reboot chime after the regular one, plus the consequent kernel panic message in the Logs folder I'm going to report in the shortest time.

In this very case, I've notice the boot screen shows the Apple and the progress bar, then just past the half of the loading some purple-line glitches, then a black screen, and only then the multi-language WSOD. When the desktop appears, I am suddenly informed again of the issue with the diagnostic log.

Putting the mac pro to screensaver, to sleep, to stop, programming these or less, does not give back any diagnostic issue, just the shut down gives the ".shutdownStall" and the reboot the kernel panic.

And, magically, when I boot in safe mode all is fine, although I always see some artifacts during the boot loading, purple lines, sometimes grey squares and rarely the Apple logo distorted in its white screen with grey stripes crossing vertically . . a sign of good health of course . .

Now the funny thing is that if I connect only one monitor, irrelevant which one, doesn’t matter the output mini dp port I choose , I get none of the mentioned issues (apart some purple tiny lines at about half-boot),and I love to stress the fact that in High Sierra 10.13.6 with single or dual display my Logs folder remains crystal clean.

If boot the mac with the GPU bios switch positioned on PC I get the same results already explained, but with no boot screen as expected, hence fully working with one monitor, but these issues with dual setup.

In other words it seems like 2 monitors (max resolution is 1920x1080 cause the monitors are old and crappy) are too much to handle in Mojave, but one’s still good.

Among all, I’ve collected for you the following reports, choosing the ones I reputed the nicest and most “expressive” profiles, in fact they are all the same to me.


I really hope some expert here could help me sorting out this thing and I’m sorry for the long post and all the words, but I wanted to be precise at best, before contacting the vendor for an eventual refund. Thank you !
Sounds like "flashed" 7950 is the problem.

Any details of the graphic card? Is it really a HD7950? Cross flashing the HD7950 Mac EFI to other HD7xxx series GPU may crash in Mojave (but not HS) is a known issue.

If you put your HD5770 back in, most likely you can boot Mojave (BOOT, not install).

And if you boot your "HD7950" from the non flashed ROM (reference HD7950 should has a ROM switch onboard. In most cases, the other ROM should not be flashed), most likely you can also boot to Mojave flawlessly.
 
  • Like
Reactions: GygaBat

GygaBat

macrumors newbie
Original poster
Sep 29, 2020
18
2
Italy
Hello Macschrauber & h9826790, thanks for your replies and help.

I vote for a defective GPU.

Retry those tests with another gpu.

Test this gpu with a pc or another mac.

Unfortunately I don't have a spare PC desktop to operate a test, apart a Pleistocene AMD "Palomino" cpu of the 1999 which refuses to turn on since eons and however I don't believe it could ever have the pci slot's teeth to install the card lol.
But in regards to testing another card I can tell you (without knowing how it have could possibly worked) that I kicked back in the ATI HD 5770 and it unpredictably worked with Mojave, even though the mac refused to go to sleep and there was just that bit of stuttering feeling over the whole system and graphics, with delays and so on, that makes you think it's better not to go along with that ...but not a single shutdown stall or kernel panic detected with it.
But of course this is not a valid way to test this issue and unfortunately I don't have a spare metal card to test in place of the Gigabyte HD 7950.
What I'm struggling to get is why with HS all is really fine, and with Mojave not so fine...what I can think of is, on the basis that the discriminant factor from HS to Mojave is the "Metal Thing" enabling (if I understand it correctly), that there is something wrong with "Metal" in that card.

Any details of the graphic card? Is it really a HD7950? Cross flashing the HD7950 Mac EFI to other HD7xxx series GPU may crash in Mojave (but not HS) is a known issue.

If you put your HD5770 back in, most likely you can boot Mojave (BOOT, not install).

Here you explain the weird things I've just noticed and asked myself, in reply to the previous quote ,and I admit I was not aware of these facts because I haven't yet learned them by checking the forum.

The details are the followings:

GENERAL:
  • · Interface Type PCI Express 3.0 x16
  • · Max Resolution 4096 x 2160
  • · Interfaces 2 x Mini DisplayPort
  • · DP*2 (Max resolution: 4096*2160 @60Hz)
  • HDMI*1 (Max resolution: 4096*2160 @30Hz)
  • DualLink DVI*1 (Max resolution: 2560*1600 @60Hz)
  • · VGA - with a adapter
  • · Graphics Engine AMD Radeon HD 7950
  • · Bus Type PCI Express 3.0 x16
  • · API Supported DirectX 11, OpenGL 4.2
  • · Core Clock 900 MHz
  • · RAMDAC 400 MHz
  • · ManufacturerMSI Computer Corp.



And if you boot your "HD7950" from the non flashed ROM (reference HD7950 should has a ROM switch onboard. In most cases, the other ROM should not be flashed), most likely you can also boot to Mojave flawlessly.

In fact it works with the non flashed rom, but the kernel panics and shutdown stalls still remains once you check for them.

Sounds like "flashed" 7950 is the problem.

I already have the tools downloaded, do you think I could try to re-flash it?
 

GygaBat

macrumors newbie
Original poster
Sep 29, 2020
18
2
Italy
Why do you need to flash the HD7950 while you already have HD5770 for boot picker screen (rarely used)?

Well, because if a re-flash can solve the kernel panic issues I have then I can forget the HD 5770 and continue working in Mojave with the HD 7950, as actually with the errors I've reported I feel something is not properly working.
Then I'm tired to stick with HS and I want to work with the latest Pro Tools in a relatively newer OS, for the updates, for the always improving audio world and afaik the metal card has to work fine for that. As it is, I don't want it to cause issues to the whole audio rig, that's why I'd like to find a definitive solution.
 

Nguyen Duc Hieu

macrumors 68040
Jul 5, 2020
3,018
1,006
Ho Chi Minh City, Vietnam
Well, because if a re-flash can solve the kernel panic issues I have then I can forget the HD 5770 and continue working in Mojave with the HD 7950, as actually with the errors I've reported I feel something is not properly working.
Then I'm tired to stick with HS and I want to work with the latest Pro Tools in a relatively newer OS, for the updates, for the always improving audio world and afaik the metal card has to work fine for that. As it is, I don't want it to cause issues to the whole audio rig, that's why I'd like to find a definitive solution.

How about Opencore for the boot screen?
And ditching the old HD7950 to get a brand new RX560, 580, VEGA... for HEVC encode/decode support that required for 4K HDR video?
I thought HD7950 or R9 280x or older card are only meant for cMP 2,1 and OSX El Capitan by this time of the year.
cMP 4,1 and 5,1 can go much further up the line of supporting VGA cards.
 

GygaBat

macrumors newbie
Original poster
Sep 29, 2020
18
2
Italy
How about Opencore for the boot screen?
And ditching the old HD7950 to get a brand new RX560, 580, VEGA... for HEVC encode/decode support that required for 4K HDR video?
I thought HD7950 or R9 280x or older card are only meant for cMP 2,1 and OSX El Capitan by this time of the year.
cMP 4,1 and 5,1 can go much further up the line of supporting VGA cards.

But the point is not the boot screen, I can live without that, the point is the kernel panic.
Anyway forget the re-flash, I think it would be useless as the kernel panics are still there with the non flashed bios counterpart, hence the bad flashed card is probably not the issue, it's the card itself, if it is so...
About other cards, I don't make videos, just some music, so I don't need great graphic performances. I just need a fully working metal card to support the D.A.W.
 

GygaBat

macrumors newbie
Original poster
Sep 29, 2020
18
2
Italy
I mean...I just bought the cheapest one just to run the new Pro Tools on Mojave haha
 

tsialex

Contributor
Jun 13, 2016
13,455
13,602
The question here is what is the card that you bought. It's a real HD 7950/7970?

Please upload a picture of the card label, usually on the back of the card.
 
  • Like
Reactions: h9826790

MIKX

macrumors 68000
Dec 16, 2004
1,815
691
Japan
But the point is not the boot screen, I can live without that, the point is the kernel panic.
If you end up wanting to re-EFI flash the 7950 head over to the Netkas site

With some experience, caution and profuse note taking EFI flashing can become pretty easy.

Don't use ROMs from different branded or other people's GPUs

Personally, I rate the Sapphire Dual X 7970 3gb ( I have one) I EFI flashed and downvolted it - great backup GPU indeed.
 

GygaBat

macrumors newbie
Original poster
Sep 29, 2020
18
2
Italy
Thanks MIKX for the link, I was already aware of it and already have the tools ready for an eventual flashing...but I'm unsure if it's going to work or not. I think I'm going to hear the vendor asking him what kind of flashing he made, what bios and everything. I mean, it probably would be useless to repeat the same steps with the same tools he used, just to end with the same issues, risking in the worst case to brick everything. But of course if he tells me he did that in a non-approved way, it worths to try the re-flash.
 
  • Like
Reactions: Nguyen Duc Hieu

GygaBat

macrumors newbie
Original poster
Sep 29, 2020
18
2
Italy
UPDATE:

I did the Apple Hardware Test, using the HD 5770 no problems found, using the HD7950 I got the following error:

4SNS/1/C0000008: Te1S--124

that has to do with temperature sensors.

But I recall to have read somewhere the AHT has to be done with the original equipment, can you confirm?
Thanks
 

GygaBat

macrumors newbie
Original poster
Sep 29, 2020
18
2
Italy
***EDITED first post adding GPU card label reference and link to the card brand, as suggested***

Just another question:

to flash a card is an original pc hardware absolutely required or is it fine as well from a bootcamp Windows 7 made with High Sierra?
Thanks guys
 
Last edited:

MIKX

macrumors 68000
Dec 16, 2004
1,815
691
Japan
No, in the past I have flashed quite a few cards on my 4,1>5,1 using Windows 7 and more recently Win 10 which I installed on their own dedicated spinner HDDs ( no Bootcamp ).
 
  • Like
Reactions: GygaBat

GygaBat

macrumors newbie
Original poster
Sep 29, 2020
18
2
Italy
No, in the past I have flashed quite a few cards on my 4,1>5,1 using Windows 7 and more recently Win 10 which I installed on their own dedicated spinner HDDs ( no Bootcamp ).

I've tried to install Win 7 64 bit without bootcamp using the disk from the mac boot, but after the win registry update the setup can't go on, black screen with some flashings every 10 seconds and a message to reinstall everything from scratch cause something went wrong in the installation, this happens with both bios switches on the GPU card, hence now I'm bootcamping HS.
 

GygaBat

macrumors newbie
Original poster
Sep 29, 2020
18
2
Italy
I'm actually in bootcamp win 7.
The only thing I'm sure of now is that I've to backup the rom of the card on the win 7 desktop, and I did that successfully with an application I dunno if I can name here...anyway a file named "Tahiti.rom" has appeared on the desktop.
But I've no pale idea of what to do next.
 

GygaBat

macrumors newbie
Original poster
Sep 29, 2020
18
2
Italy
Alternative test method is Stress test the 7950 with High Sierra. For example with the heaven benchmark.

Yeah I've DLed that and I'm going to try a stress over the card for sure, I would have done it even without the kernel panics, just for the sake of curiosity.
But I've a great update to tell...I've managed to reflash the card with the netkas universal rom, and lost the boot screen, but managed to reflash again the original rom.
I think I've understood a little of the whole thing !
 
  • Like
Reactions: Nguyen Duc Hieu

h9826790

macrumors P6
Apr 3, 2014
16,656
8,587
Hong Kong
GV-R795WF3-3GD(rev2.0)
this is what is written in the label, and this is my card:

I suggest you go to TechPowerUp to download the original factory ROM that's for this card. Then flash it onto your card, and see if it will fix the issues.

So far, it looks like a badly flashed card (e.g. cross flashed another ROM onto this card).
 

GygaBat

macrumors newbie
Original poster
Sep 29, 2020
18
2
Italy
I suggest you go to TechPowerUp to download the original factory ROM that's for this card. Then flash it onto your card, and see if it will fix the issues.

So far, it looks like a badly flashed card (e.g. cross flashed another ROM onto this card).

And I've even DLed it yesterday already, and was just keeping it for the last test because probably as you say that one may be the good one, even tho it has the exact same size of the one loaded by the vendor...which makes me think there's a possibility the ROM you're referring to I haven't yet tried, is the original faulty one with the kernel panics.

UPDATE

"This VBIOS is already installed"...I will try other ones from TechPowerUp.
 
Last edited:

GygaBat

macrumors newbie
Original poster
Sep 29, 2020
18
2
Italy
Believe me I've tried everything but the same issue represents continuously:

"type 14=page fault, registers:"

and:

"Kernel Extensions in backtrace:
com.apple.iokit.IOAcceleratorFamily2(404.14)[618B24B5-1387-31FD-A7F7-53283E2C3FEA]@0xffffff7f89fc7000->0xffffff7f8a06dfff
dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[1D716047-7F62-3FFA-8C01-26C166B3739A]@0xffffff7f8858d000
dependency: com.apple.iokit.IOSurface(255.6.1)[263BDC28-38C8-3995-BB6B-AD419E41C2DC]@0xffffff7f89fa3000
dependency: com.apple.iokit.IOPCIFamily(2.9)[BFDEB8D4-50FE-3DDB-87B7-F6A504393830]@0xffffff7f88095000
dependency: com.apple.iokit.IOGraphicsFamily(530.66)[373EAB85-2C5F-3B84-B86D-421F79C47DF2]@0xffffff7f8882f000
dependency: com.apple.iokit.IOReportFamily(47)[0BC9F93B-456A-3D97-BE4C-69DCBB5E8A3C]@0xffffff7f88be6000
com.apple.kext.AMDRadeonX4000(2.1.1)[25F10272-62BF-31EF-813B-A3622258B230]@0xffffff7f8a07e000->0xffffff7f8a4bdfff
dependency: com.apple.iokit.IOSurface(255.6.1)[263BDC28-38C8-3995-BB6B-AD419E41C2DC]@0xffffff7f89fa3000
dependency: com.apple.iokit.IOPCIFamily(2.9)[BFDEB8D4-50FE-3DDB-87B7-F6A504393830]@0xffffff7f88095000
dependency: com.apple.iokit.IOGraphicsFamily(530.66)[373EAB85-2C5F-3B84-B86D-421F79C47DF2]@0xffffff7f8882f000
dependency: com.apple.iokit.IOAcceleratorFamily2(404.14)[618B24B5-1387-31FD-A7F7-53283E2C3FEA]@0xffffff7f89fc7000"

These are the fixed errors.
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.