![]() It takes few restart to install bios wait for 1 or 2 min top. Then all will be crowbarska solved the problem it comes from nvram faulty you need to reflash your nvram but in asus devices bios upgrade installing into bios itself so if you want to reflash from windows you need to install it with ami bios toolħ-) Restart. BUT, if I rename HFSPlus.efi to HFSPlus so the driver is not loaded, then Clover 5070 starts fine The I can use Shell to load the HFSPlus and the driver loads just fine, no hang Then when I exit Shell, clover shows my Mac volumes and I can boot. It happens on me because of hackintosh for you reason might be different.ġ-) Download latest bios for your device from asus web siteĢ-) Download AMI bios tool from bios mods link is in here: AMI BIOSģ-) Open that with administrator privilages Aptio\afuwin\64\AfuWin64\AFUWINGUI.exeĤ-) Click open chose all files for file type from down right and select your ACCURATE BIOS FILE FOR YOUR DEVICE FROM ASUS.ĥ-) Click Setup Select Main Bios Image, Boot Block and NVRAM( You can choose just NVRAM but I dont recommended)Ħ-) Click Flash and make sure you have connected your PC to AC power.ħ-) Restart. With 5070 if I have HFSPlus.efi installed in drivers/UEFI, I hang at black screen. Please crowbarska solved the problem it comes from nvram faulty you need to reflash your nvram but in asus devices bios upgrade installing into bios itself so if you want to reflash from windows you need to install it with ami bios toolįirst of all its a reinstalling bios from AMI for all AMI bios devices if something goes wrong I am not responsible for any of that. But after the screen goes black at this moment, it stays black forever. I need to press F1 to do that, which works (that's how I know the keyboard still works). Now when I boot my PC I'm prompted to run Setup to recover BIOS settings. I've also tried unplugging the power and holding the power button for 30 seconds. I tried resetting the CMOS battery by taking it out for 5 minutes and replacing it again. Then all of a sudden, UEFI BIOS stopped loading too. I tried disabling and re-enabling the boot devices a few times, rebooting, etc. I can usually resolve the issue by powering down for a while, then booting into UEFI BIOS and making sure the boot order is correct. And UEFI BIOS has always worked whenever the SSD failed.Īnyway, I recently restarted my computer and my SSD failed, so I looked into the UEFI BIOS. I bought this PC pre-built but added the SSD myself, so maybe I did something wrong while installing it? I'm not sure, but it's been this way for about 3 years and fails intermittently. That's an old DELL Latitude 4310 laptop with a 500 Gbyte HDD from Toshiba (disk 0) in it: DISKPART> detail diskĭisk ID: But when I press F1 the screen goes black and nothing displays.Įvery now and then my SSD fails to boot into Windows 10. Possibly, somebody will going to pinpoint the right direction to solving this issue. Well this is the world we live in And these are the hands we're given. If using diskpart gives nothing, I plan to image that VHD using ImageX clean the VHD, convert it to GPT, and apply created image to its system partition 4. That was the part that I couldn't even imagine The boot entries will be autodetected but not saved. It looks like the boot code does not point to the boot manager on the partition 1 within the VHD drive! Clover emulates an UEFI environment, and it's able to load NvmExpressDxe.efi in its own environment, but not in the motherboard's UEFI environment. The boot code successfully executes and points to partition 4 on that hard drive. BIOS looks up for the boot code on the fist device: physical hard drive, partition 2Ģ. Where X is the VHD disk and its primary partition correspondingly.ġ. However, this does not work for me - I still get a black screen when it tries to boot up. Booting from Window Setup and patching the boot partition on the VHD disk using diskpart DISKPART>SELECT VDISK FILE=C:\WIN8.VHDX The typical recommendation I found from googling is: on the boot selector screen (Im using rEFInd) hold Shift and select grub options, then press e to edit the boot options and add nomodeset after where it says quiet splash. In fact, that VHD drive is not a GPT drive just but the reason I moved it from another non-UEFI PC.ġ. I have a similar setup where both the virtual and physical drives are GPT drives and everything works fine. That is the boot code and the boot manager are located on separate partitions. The VHD drive is located on the separate partition with the boot code. This PC is using native VHD boot from a GPT physical drive. It seems to me that the problem is with boot code that seems to contain reference to the boot manager that is missing from the partition it is referencing to.
0 Comments
Leave a Reply. |