Recent content by Homar9

Ok. I'm trying that next. Thanks! EDIT: I reset my mobo settings, then reinstalled Mavericks. I couldn't boot with dart=0 after the reinstall, so I booted in safe mode, and fixed all my settings again, removed the previous additions to boot plist, leaving only yours, but that still didn't...

Thanks again, Insanity83NL. I just tried that, but it didn't work. I'm still getting that memory error code 51 on the mobo, while I get stuck at the the gray apple screen. Should I remove what JBamford told me to add?

I added it to the boot.plist.. I just noticed that EvOreboot was no longer selected. Trying an install now... EDIT: I still have the error 51

GraphicsEnabler=Yes is disabled and IGPEnabler=No is not selected

Ok. Done. Thanks! Now I'm stuck on the boot up page with a 51 error code.

Ok. I'm still new to this, so you'll have to bear with a couple of questions (sorry). How do I add that to my boot.plist? EDIT: Ok, I found a video showing me how.

Hey jbamford, Yes, I updated to F4

Hey Insanity83NL, Thanks for the help. Ok, I tried it, and I was able to boot up. Thanks. Then I tried to boot up normally, and it gave me the D1 error code. Should I maybe select NullCPUPowerManagement in MultiBeast?

Thanks for replying. Yeah, I only did the boot with -v afterwards. I just grabbed it with my phone quickly (sorry). Looks like the CPU isn't recognized, or a BootCacheControl problem, or a SMC mode limit issue, or a problem with my power management settings. I was going to try adjusting some...

Hi. I'm still new to all this. I'm stuck at the first boot following MultiBeast setup--I have the grey Apple logo screen with the cycling circle. Any suggestions? Components CPU: Intel Core i7-4790K (4,0 GHz) Motherboard: GA-Z97X-UD7 TH Graphics: Integrated Ram: Crucial Ballistix Tactical...

skinsfan317: I'm a first-time Hackintosh builder, with pretty much the same specs (Z97x-UD7-TH, i4790K), and I've run into the same problem of it hanging on the white Apple screen when trying to boot off the SSD for the first time. The motherboard is telling me it's a memory-related problem...