Jump to content
5 posts in this topic

Recommended Posts

So I bought a corsair af120, I plugged it in, started windows 10, things were working fine, I realized I have to exchange this fan so I unplugged it, tried to boot sierra but on the apple logo screen and load bar ,it gets halfway until it powers off (not restarts) my pc. I booted in verbose mode and took photos. (sierra was loading fine before this)

 

Also another problem I have is, sierra wont boot (just stays hung on the apple logo) unless I hit space in clover and chose (load with selected kexts) screenshot for that as well

 

http://imgur.com/a/hBGsz

 

http://imgur.com/a/hBGsz

 

http://imgur.com/a/CIwBS

 

System specs

motherboard: asus p8z 77v lx

cpu: i5 3570k

ram: corsair vengeance 8gigs

gpu: nvidia gtx 1060 (although im using intel onboard graphics for sierra)

Very strange that you're getting that even though you did nothing to the hard disk itself I assume. What happens if you boot into single user mode and run these commands: 

fsck_hfs -y -Rc -d /dev/disk0s2

See if that fixes anything. -d will print out debug info so see if there's anything relevant mentioned. 

 

A temporary fix you can try is in single user mode:

mount -uw /
exit

That'll skip the fsck check and will boot up but whatever issue it's complaining about isn't going away.

 

As for the Clover settings, "Boot macOS with injected kexts" is the equivalent to having InjectKexts set to true in your config.plist which most people usually have enabled.

 

Other than that, that error is pretty much saying there's filesystem issues, even though you did nothing to it. 

  • Like 2

Very strange that you're getting that even though you did nothing to the hard disk itself I assume. What happens if you boot into single user mode and run these commands: 

fsck_hfs -y -Rc -d /dev/disk0s2

See if that fixes anything. -d will print out debug info so see if there's anything relevant mentioned. 

 

A temporary fix you can try is in single user mode:

mount -uw /
exit

That'll skip the fsck check and will boot up but whatever issue it's complaining about isn't going away.

 

As for the Clover settings, "Boot macOS with injected kexts" is the equivalent to having InjectKexts set to true in your config.plist which most people usually have enabled.

 

Other than that, that error is pretty much saying there's filesystem issues, even though you did nothing to it. 

I got it working again thanks, now whats happening is I installed a few kexts, cpumonitor gpumonitor and acpimonitor and now osx restarts on boot. verbose mode doesnt work, single user mode doesnt work, safe mode doesnt work, they all reboot. Heres a screenshot

 

http://i.imgur.com/p7xQuBG.jpg

You'll get that kp if you don't have a functional SSDT.aml you made for your CPU. It can also happen with systems that restrict an MSR register that AppleIntelCPUPowerManagement.kext tries to access and you can fix that with enabling AsusAICPUPM in your Clover config.plist.

 

If this just started up after you installed these kexts and things were working fine before, then you should undo what you did and figure out what change caused it. To be honest if it had to do with one of those FakeSMC sub kexts that you say you installed the kernel panic usually traces back to it.

 

If all else fails, install NullCPUPowerManagement.kext until you figure out what's causing it.

×
×
  • Create New...