Jump to content

astroguy

Members
  • Content count

    30
  • Joined

  • Last visited

About astroguy

  • Rank
    InsanelyMac Protégé
  1. A final update: The computer has been running continuously for about two weeks now, though I will need to replace the motherboard, I got an RMA and will be replacing the RAM, while I'm replacing the motherboard I might as well replace the CPU (upgrade), and because of what might have happened, I'll be replacing the PSU. What I think happened: A surge in the motherboard, either due to a fault in it or the PSU, blew out the connector to the CPU pump, and the CPU pump. It also blew out one or two RAM slots and at least one of the RAM modules. Replacing the CPU cooler worked, once I moved the hookups around, and going back to my original RAM before my upgrade has allowed the computer to run without crashing, though the OS thinks half the RAM is used up upon startup which is why I think the RAM sockets are also borked.
  2. Okay, it shut down at 4pm today and would not boot. RAM check cycling on the motherboard, then 00 and 19 (CPU and RAM, per before). Took all new RAM out, put in old, same thing. Then worked in single-module mode. Worked in dual. And ... then worked in quad. However, 17GB is taken up by "Wired" memory, instead of ~3GB per usual. Now I'm starting to wonder if there was that motherboard surge and it fried not only the old CPU cooler pump, but also fried one of the RAM slots. Here's the kernel panic report this time:
  3. The computer was still going when I got home, but about 10 minutes ago, it froze and restarted and booted fine. I finally captured the report that Apple generates:
  4. Okay, was able to change that in the BIOS, and it booted into macOS. Ran the diagnostic, and I've sent you a private message asking how to get it to you. The computer was up for about 3 hours and shut down again overnight. Restarted this morning perfectly fine. I have it up now, but I'm at work for 14 hours today in meetings. I have a MINIMUM of stuff going on: E-mail checking, Skype is up, weather server running, and a few downloads. Other things not needed, like USB external drives, are disconnected. Will see if it's still up when I get home tonight and will post here regardless.
  5. So ... did you ever get this motherboard to work correctly? I'm looking at getting this exact motherboard and CPU, so I wanted to check.
  6. Will try. I had to leave for a week-long trip just a few hours after the computer died, I get home late Sunday. Two questions to hopefully head off a delay: (a) Do you know how to disable the serial port in the BIIOS, but chance? (b) Your application clearly requires the macOS to boot ... if I do disable the serial ports and it still doesn't boot, what should I do?
  7. 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.) Hardware: 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.
  8. Thanks! Looks like it was not easy but eventually worked out. I will likely wait until the iMac refresh on the off-chance that Apple uses an i9 chip in that sucker. It's a cheaper chip with more threads ... but it's good to know this is a viable alternative.
  9. I built my first Hackintosh two years ago, and I'm looking at a potential upgrade. In particular, one capable of running a lot of threads simultaneously. I am pretty unhappy with Apple's deliberate throttling of the W-2155 CPU in the iMac (specs: 3.3GHz which Apple throttles to 3.0GHz, and under heavy loads it's supposed to turbo up to 4.5GHz but to save a few dB on fan speed Apple throttles it >10% down). My understanding is that Hackintosh building is much, much easier when you're using a CPU that Apple uses in its line, so I'm looking at the W-2155 as opposed to the i9-7940X (though I would prefer to use the i9 based on cost, threads, and OC ability). I did a forum search and couldn't find any mention of using this CPU -- has anyone had success with it?
  10. Hey folks, new guy here, new build, everything working lovely except same problem: when the screen goes black (display sleep or display off), computer likes to shut down that registers as a crash, and my error codes look much like the first post. I'm also using an ASRock OC Formula board and Skylake 6700K CPU, I have an NVIDIA 960 in my primary PCIe slot. I'm incredibly new to hackintoshing (can it be a verb?) and I'm interested in the "quick fix" of hibernatemode=25 ... um, how do I do that and where? Okay, just did one thing that appears to have helped -- System Preferences > Energy Saver > Prevent computer from sleeping automatically when the display is off. That may actually be a mid-term solution for me since this is going to be a computer that will likely always be on, but knowing about hibernate would be good ...
  11. In the version of Clover that I have (which is the latest based on its auto-update), I can only do iMac 15,1. If you're willing to create a config.plist file for me, I'll take it! The final parts list: http://pcpartpicker.com/p/pvdvwP
  12. Okay, so ... Step 3, need to check the box that says DataHubDxe-64 and check the box that says OsxAptioFix2Drv-64, in Drivers64UEFI as opposed to OsxAptioFixDrv-64. Step 4, I don't see where to get files like FakeSMC.kext for El Capitan (I found the one for 10.10 and another for 10.9 in the Downloads section of this site). Step 5, I figured out that I get HFSPlus-64.efi through the Tools > Install Drivers. I went to the Home screen and selected the /Volumes/EFI/EFI/CLOVER/config.plist to edit. In Boot, checked the Verbose option. Gui, changed screen resolution to HD. SMBIOS, selected the magic wand, iMac (15,1), and shaked the week and unit to generate a serial. Also entered the RAM (4 slots, 8GB, 2400MHz, G.SKILL for the vendor, DDR4 Type). My likely incorrect understanding from at least working through the Pandora video is that most of these fields I shouldn't have to actually fill out, that they will populate when I boot? Unless there's a problem in which case the -v (verbose) command will tell me where it crashed and I can try to figure out what I need to fill out.
  13. Nah, I can make the USB. I'm at least capable of doing that step. It's the later tweaking if things don't work that I have a bit more trepidation about, but fortunately my 2008 Mac Pro is still holding up (though now besides the ethernet ports and optical drives going bad, the GPU is showing signs of failure).
×