Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
It seems computer freeze due Firefox HW Acceleration is common problem and may present on macOS, Win and Linux. Also seems it may happened due multiple sources, like bugs in specific GPU driver, OS version, Firefox version and even browser extensions. So it is not surprise that problem happened on my legacy 10.14.6 hackintosh system with GPU that was formally not supported at all (Radeon Pro VII flashed with Radeon VII bios). But i am still interested to fix this problem because things works smoother when HW acceleration is enabled.
One of the possible problem fixes is to increase lowest clock speed I done some unsuccessful tests:

Test 1. Set FreqTableGFX1,2,3,4,5,6,7,8,9,Max clocks to same 1801 value and min/max voltages to same value (1000mV) as well.
Result: Fan spins very very fast, LuxBall test 25000 instead of 50000

Test 2. Set FreqTableGFX1 to same value as FreqTableGFX2 (808), min/max voltages to same value (1000mV)
Result: OpenCore bootloader starts, but then screen flashes with artifacts and macOS can't boot.

Test 3. Set Max Core Clock to 700.
Result: LuxBall test 50000, seems Max Core Clock value don't decrease performance.

So i have a question. Is there some manual or explanation for relation between Max Core Clock, and FreqTableGFX1,2,3,4,5,6,7,8,9, and maybe to some hardcoded values in OS for this card? Same question about HBM clocks. Where those values for FreqTableGFX came from?

P.S. Currently i got stable performance with default clock 1801MHz and 981mV. Hotspot temp still 90-93. LuxBall near 52000
 

Attachments

  • Screen Shot 2025-09-13 at 4.40.31 AM.jpg
    Screen Shot 2025-09-13 at 4.40.31 AM.jpg
    555.5 KB · Views: 19
Last edited:
So it is not surprise that problem happened on my legacy 10.6.8 hackintosh system with GPU that was formally not supported at all (Radeon Pro VII flashed with Radeon VII bios).

This is a typo, no? Radeon VII is only supported with 10.14.5 and later macOS releases.
 
It needs more testing, but i am almost sure that source of Firefox system freeze was overclocked and undervolted HBM. Tests like LuxMark use GPU cores but don't stress memory. Same time Ventusky website behave like gaming test. During map movements and zooming it instantly uploads/offloads new data into GPU memory, so memory controller stressed a lot with small but very strong data splashes, especially if increase animation settings. Also once i got same system freeze in Indigo Benchmark during scene loading. Many online overclocking guides describe system freeze as GPU memory related problem.

So i underclock/undervolt Core but set HBM clock FreqTableUclk3 and FreqTableUclk4 to default 1000 and MaxVoltageSoc to 1168mV and during last day it was no system freeze anymore.

Also it make sense to experiment with Memory Timing Level setting which adjust memory latency settings, which can offer performance improvements or stability issues:
Level 1 - slower timings but more stable performance.
Level 2 - faster timings but lass stable performance.
 

Attachments

  • Screen Shot 2025-09-17 at 2.18.15 AM.jpg
    Screen Shot 2025-09-17 at 2.18.15 AM.jpg
    677.9 KB · Views: 11
  • Screen Shot 2025-09-17 at 1.41.31 AM.jpg
    Screen Shot 2025-09-17 at 1.41.31 AM.jpg
    562.6 KB · Views: 10
  • Screen Shot 2025-09-17 at 2.33.51 AM.jpg
    Screen Shot 2025-09-17 at 2.33.51 AM.jpg
    110.2 KB · Views: 11
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.