Jump to content
7 posts in this topic

Recommended Posts

For a month now i am getting a random reboot when i am starting my Sierra 10.12.6 hackintosh and after that this black screen appears.

 

Any clue whats that? Do you think that it's a hardware issue , i mean RAM-Mobo-HDD or it's a software one? Please any help because it's very very annoying

 

Thanks

 

 

post-572805-0-20327700-1513344400_thumb.jpg

hello

 

every time I see that screen is about amd cpu ..

 

post ur hardware specs

 

boot loader u are using , version

 

good hack

 

 

Thanks for answering, Sierra 10.12.6 (MacPro5,1)

Gigabyte Ex58 ud3r

Clover4243

Nvidia GTX 285

Intel Core i7-920 2.66 Ghz LGA 1366

Ram Corsair 1600Mhz 10GB

Samsung SSD 850 EVO

@iceage2609,

 

Did the red screens appear when you updated to official Clover r4243 from SourceForge (or switched from using custom dsdt to Clover dsdt patches)?

 

That looks a lot like the red screen bug I mentioned here, due to official Clover r4061-r4264 being compiled with XCODE using -fno-common flag.  It will occur if you use Clover's auto dsdt patching instead of a custom dsdt in the affected releases.

 

Bug was fixed in r4265+.  Try to update Clover to latest - attached r4359 compiled with GCC  :).

Clover_v2.4k_r4359.pkg.zip

@iceage2609,

 

Did the red screens appear when you updated to official Clover r4243 from SourceForge (or switched from using custom dsdt to Clover dsdt patches)?

 

That looks a lot like the red screen bug I mentioned here, due to official Clover r4061-r4264 being compiled with XCODE using -fno-common flag.  It will occur if you use Clover's auto dsdt patching instead of a custom dsdt in the affected releases.

 

Bug was fixed in r4265+.  Try to update Clover to latest - attached r4359 compiled with GCC  :).

Hmm i am not sure but the whole reboot issue started with the last update.( 10.12.6) From the biggening i was using custom dsdt file (not Clover's auto dsdt though) inside the patches file.

Unfortunately updating the Clover bootloader didin't fix the problem ...

I used disk utility and verify disk and that's the respond error. Any clue if it has anything to do with the problem or its a accidentally error.

post-572805-0-49697400-1513631041_thumb.png

post-572805-0-32070000-1513631052_thumb.png

post-572805-0-34776300-1513631063_thumb.png

×
×
  • Create New...