Jump to content
XTuga

Clover mess up my motherboard?

11 posts in this topic

Recommended Posts

Hi everyone

 

Even if I remover all my HDD and don't have any device connected to my motherboard, I still get those two entries, on the boot menu or in the BIOS.

 

SRkOt87.jpg

 

Why and how do why remove it?

 

Same happen with Gigabyte and ASUS motherboards.

 

Already try flash the BIOS, put a older or newer version and even remove the battery from the motherboard. Nothing work...

Share this post


Link to post
Share on other sites
Advertisement

I will give it a try. Btw, is normal that I end up in a situation where my hackintosh boot normally but my Windows only can boot if the Mac OSX HDD is connected? Is because of the use of the UEFI from Clover?

Share this post


Link to post
Share on other sites

You can reflash your board and it will fix it. My Asus did this with only a certain UEFI version. Asus boards are so easy with BIOS Flash Back 

Share this post


Link to post
Share on other sites

Sorry @vusun123, you're right.. Reinstalling it again just to make sure, appear only affected some versions of Windows

 

48qYFIe.png

Windows Enterprise Edition needs the paid version

Share this post


Link to post
Share on other sites

I have the same issue, but for now I am just content to live with it as it does not seem to cause any problems for me (other than looks). I have other issues that are causing problems.

Share this post


Link to post
Share on other sites

O.K., this may occasionally cause problems. It seems that the Mac OS is using this for storage to remember Kernel panics and the like. I was troubleshooting my non-working build (Gigabyte GA-Z68MZ-D2H-B3, i7-2600) . With only a single SSD connected and running the (Clover EFI USB stick) installer, I reformatted the drive and began to install. On the restart, I got the message about the last Kernel panic. Since the install didn't work, I tried again. This time I downloaded a fresh copy of the U1c bios from Gigabyte and unpacked the .exe file using Keka so that I could extract the U1c BIOS file. I then used the Gigabyte Q-Flash utility to reflash the BIOS. Next time I ran the installer, I got no message about a Kernel panic. I think that reflashing the BIOS is probably the easiest way to solve this issue.

 

[ultimately I determined that I had an unsolvable (for me) hardware problem after several more install attempts, and attempts to use backup copies that I had made when the system was working and decided to buy a newer system.]

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

×