stuck bios unable to start hell
Printed From: ASRock.com
Category: Technical Support
Forum Name: Intel Motherboards
Forum Description: Question about ASRock Intel Motherboards
URL: https://forum.asrock.com/forum_posts.asp?TID=5600
Printed Date: 27 Jul 2025 at 12:02pm
Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com
Topic: stuck bios unable to start hell
Posted By: SAVVAGE61
Subject: stuck bios unable to start hell
Date Posted: 16 Jul 2017 at 6:50am
|
" rel="nofollow - z270 bios p2.10 windows 10 pro 64 bit Samsung 960 EVO m.2 pcie was booting to m.2 just fine I did something stupid just not sure what MS is default boot 1st in order everytime I start my machine I get the bios warning system has tried to boot and failed sevral time system guard message tells me to to go to set up or boot manager counts down goes to boot manager shows my ssd and my hdd storage I click on ssd in boot manger(on screen) or menu boots right up restart and go thru the same thing everytime. it like it doesnt reconize my m.2 pcie until I select it even though it is default boot. does anyone know what I did and how to fix it? I am so stressedafter4 hrs of this Asrock z270 tiachi I7 7700K
|
Replies:
Posted By: parsec
Date Posted: 16 Jul 2017 at 9:39am
Did you try clearing the UEFI/BIOS? If you installed Windows 10 correctly for an NVMe SSD (960 EVO), the entry in the boot order should be, "Windows Boot Manager: Samsung 960 EVO". Other entries for the 960 EVO, if present, are not the right ones. Did you install Windows with any other drives powered up during the installation? If you did, the System/Boot partition was written to another drive, a known behavior of the Windows installer. That makes booting Windows dependent on the other drive. If the other drive had something done to it, it could affect booting. Did you configure anything in the UEFI when you installed Windows on the 960 EVO? Specifically, the CSM option, or its sub-option, Launch Storage OpROM Policy? You told me you changed to a new UEFI version, did you check your settings after doing that? They were all set to their defaults after the update. ------------- http://valid.x86.fr/48rujh" rel="nofollow"> 
|
SAVVAGE61 wrote: