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.
Is it possible to install an older OS X.5 Leopard or OS X.6 Snow Leopard Hackintosh system on a modern i7 processor PC?
I need to to run either of those systems using an Intel Core i7-4770K Quad-Core Desktop Processor on a Gigabyte GA-Z87MX-D3H motherboard.
I saw this post where someone said “Clover 32Bit should boot Leopard as well, using Legacy mode. You will need 32bit kexts as well.” https://www.insanelymac.com/forum/topic/331457-bootloader-for-leopard/ .. Would that be valid advice for me to follow up on for my configuration? I see that Clover 32 bit is no longer in development.. https://www.insanelymac.com/forum/topic/317521-good-bye-clover-32/
Salve a tutti, sono nuovo
Ho un problema per installare il mio primo hackintosh
le mie spec sono: i7 720qm , gt730 2 gb ddr3, 8 gb di ram e una motherboard che non si capisce modello sia(perchè? perchè è un preassemblato a cui ho modificato i componenti mi lascio anche uno screen di cpuid se può essere utile comunque è legacy,comunque la motherboard è intel. )
Comunque ho creato un boot usb con clever per installare Sierra e tutto va okay fin quiando vado in kernel panic, ho provato diverse boot flags ma non riesco ad arrivare all'installer di Cupertino
CHIEDO AIUTO,grazie ancora aspetto risposte
Hello everyone, ever since installing the security update at the end of January, I've been having two issues.
The first is the kernel panic that happens every time I try to boot. After much research, here and elsewhere, I learned that the issue is Lilu.kext which I did not update prior to installing the security update. So now I have the latest version downloaded to a USB drive, but I cannot copy it to the hackintosh...
Every time I try to boot into Recovery, the system just locks up. So I tried replacing the file via the UEFI shell and again from Kali, and in both cases I couldn't because both OS's see the Mac's file system as "read-only." I did some research on how to fix Recovery and found that I need to put FakeSMC.kext in the /EFI/CLOVER/Kexts/Other directory on the Recovery HD, which I cannot do for the same reason I can't replace the Lilu file (the HD is read-only to all other OS's).
I tried booting off my old Snow Leopard CD, and that doesn't work either; every time I try it just quits mid-boot, resets the computer and reboots into Clover.
Can anyone give me any suggestions? I'm out of ideas at this point.