Hello everyone, it sure has been a while since I last posted here. I'm trying to upgrade my Hackintosh to High Sierra, and right now it's running Sierra which I installed last year. My hardware is a Gigabyte Z68MA-D2H-B3 mobo with Intel Core i5-2500K. Unfortunately, I can't even run the installer. I have an installer USB stick with Clover 4558 on it, and whenever I try to run the installer from it, I get a KP after an extremely long boot process. There are so many panic messages that flash by so fast, but I think I got everything relevant in these pics.
Sorry for the vague subject line, but I think I have a hardware issue and I'm having trouble diagnosing it. This is a LONG post because I'm trying to explain what I tried and to give you all the info that I do have.
History: This has been a successful Hackintosh for 2 years 2 months. I have not changed the OS (still running 10.11.4) just to avoid any problems. I have not changed the hardware other than GPU about a year ago, hard drives over time, and RAM about two weeks ago. (Keep that RAM in mind.)
Motherboard: ASRock Z170 OC Formula
CPU: Intel i7-6700K
RAM: G.SKILL Ripjaws V Series 32GB DDR4 @2400, replaced with Corsair 64GB DDR4 @2133 (but lower CAS latency)
GPU: MSI GeForce GTX 970
PSU: CORSAIR AX760 760W 80+ Platinum
CPU Heatsink: CORSAIR Hydro Series H105
Problem, Tuesday Night: Catastrophic death. Just shut down, couldn't get it up. I spent over two hours midnight–2am, then another hour after I got up in the AM, determining that the heatsink pump had died. To make a three hour story short, the errors on the motherboard were all related to RAM, but it had been running fine with the new RAM for 10 days. I put in the old RAM and got the computer to boot, and then I heard that the fans were going full-tilt and saw the CPU temperature at just under boiling. And it shut down. I determined it was the pump and not motherboard because the pump did not turn on when I moved it to a header on the motherboard that had just been powering a fan that was fine. So I ordered a new CPU cooler and installed it yesterday.
Problem, Sunday Night: It was running fine for a day, after installing the new CPU heat sink. We had a brown-out in the morning which apparently did NOT trip any UPS in the house, and the computer restarted. Seemed fine, then tonight (11 hrs after the brownout), I went to make dinner, came back and all the fans were going and the computer wasn't on. The light on the Corsair pump was flickering.
Trying to Diagnose: So, with the light flickering, I thought maybe it was the motherboard after all, and the CPU fan 1 was just dead (or dying). No problem, moved it to CPU fan 2 and moved the fans for the heatsink to chassis 2 and tweaked the fan speeds in the BIOS (I was able to boot to it) and ... couldn't boot. I can get to the BIOS. I can start getting to the Mac OS, but I can't actually boot fully. The motherboard is cycling between error codes 00 and 19, which from what I can find means CPU (00) or RAM (19). I have tried powering the whole system down (on the PSU) for awhile, going back to the old RAM (works but then same error code on reboot), and even going to a passive heatsink I had in storage.
Why this May Be a Hackintosh Question: I have a pattern now to diagnose. After hitting the restart a few times, I can get into the BIOS, no longer getting the 00/19 error on the motherboard. I can get to the Clover boot menu, at which point the diagnostic LED on the motherboard turns off. I can start the Mac OS, it spits out a bunch of diagnostic stuff, and then freezes, and the lights on the motherboard turn back on and flash between the 00 and 19 errors and the display shuts off. I get to the same spot in the Mac OS startup, and that's when it shuts down. To me, from the zero that I know about this, it looks like it's saying there's a CPU error. Meaning I may have fried the CPU (or motherboard? or both?) during that initial CPU cooler failure five days ago. I have attached a screenshot from the video I took of the screen while starting up the last time.
CMOS Reset: I tried doing this as an addendum, after taking pictures of every screen in the BIOS so I could restore. The reset definitely reset the BIOS, I got it to boot to the BIOS again, but I'm stuck at the same death point as in the screenshot. The ONLY difference is that now instead of just stopping there, it goes black for a few seconds and returns to the BIOS option screen (F2 for BIOS, F11 for Boot, etc.), and then tries to boot the Mac OS again. Fails at the same point again, the only difference each time is that in that "Backtrace (CPU #) ..." line, the # changes, and the com.apple.lokit.IOBluetoothHostController... hex stuff is different.
Help!? Do I need a new motherboard and CPU? Fortunately, everything is backed up hourly, and on my laptop, and the HDDs should still be fine.
How to make AppleHDAController load on Ryzen boards?
Rename(/add) your audio controller to your DSDT/SSDT as HDEF
Add a _DSM method to your HDEF device with layout id 1
Patch the AppleHDAController binary, because it has a static table containing the supported PCI Vendor/DeviceID pairs and it also checks the VendorID against known values. As an example I provide a dif file and patched 10.13.3 binary, but if you want to I can patch the binary for other versions.
After AppleHDAController loads to actually get sound working you need to patch AppleHDA.kext for the codec on your board. First I tried to use Lilu+AppleALC for this task, but for some reason it refused to work. (I might look into it later why) But for the time being it was easier to use toleda's cloverALC script for that, but to make it work I had to change(/remove) the specified location of the HDEF device from the script. And for some reason it also required me to mount the EFI partition manually.
if [[ $(cat /tmp/HDEF.txt | grep -c "HDEF@1") != 0 ]]; then
if [[ $(cat /tmp/HDEF.txt | grep -c "HDEF") != 0 ]]; then
Hi, I tried during last 4 days almost everything but now I call for help. I have RX560 running on 10.13.4. Previously I was running it on 10.12.6 and had the same problem, but after waking from sleep my thiord display came to life, but it is not working anymore on 10.13.4. Without or with Lilu & Whatewergreen my system correctly recognize my gpu as RX560 but only 2 of 3 displays are displaying content, third display is black but recieving some signal. When I change cabling and connect only two, any combination of 2 displays is working. System profiller and system preferences are sayin I have 3 displays connected.
Please can somebody help me to figure it out? Thanks a lot in advance. Tried to upload my ioreg but it is greater than 10MB allowed for me :(
Hi, i recently set up High Sierra on my AMD computer with the help of the amdosx community (i actually used an installer just to confirm that something would work in the first place before i spend hours for nothing, i can and could have downloaded High Sierra the "legal" way).
However the graphicscard is recognized properly, the 6gig are recognized and i have no artifacts and no screen tearing with the official nvidia webdriver,
but unfortunally, dark colors have horizontal dark stripes in them and specific bright colors like on left bar of system windows such as settings do flicker like low fps.
I only used the clover on the flash drive for now and i'd like if it's worth digging deeper of if i should just forget about it as it is a common nvidia problem on macOS.
Would be amazing to know.
Closer machine infos:
* High Sierra (misses a recent minor patch as my network is veeeery slow and i got this nvidia issue anyway so i mainly jumped back to linux)
* AMD fx8350
* Asus Sabertooth 990fx Ref. 2.0
* NVIDIA GeForce GTX 1060 6GB