X99-WS, SM951 NVMe, Windows 10 Oddities
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=1805
Printed Date: 15 Jul 2025 at 4:31pm
Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com
Topic: X99-WS, SM951 NVMe, Windows 10 Oddities
Posted By: GuruNot
Subject: X99-WS, SM951 NVMe, Windows 10 Oddities
Date Posted: 23 Jan 2016 at 10:02pm
|
I have logged a ticket about this but I thought I would ask the forums to see if anyone has any thoughts. There is a fair bit to go through so please hang in there. My setup is as follows: i7-5930k (Stock) Asrock X99-WS now running Bios 2.10 (Was Running 1.95) 32GB RAM - Corsair Vengance LPX DDR4 2666Mhz - Currently at 2133Mhz (not enabled XMP) EVGA 980Ti Classified (Stock) 256GB PLEXTOR PX-256M5Pro (SSD) - \\?\GLOBALROOT\device\harddisk0\ 2TB Hitachi HDS5C3020ALA632 (SATA) - \\?\GLOBALROOT\device\harddisk1\ 1TB Hitachi HDT721010SLA360 (SATA) -\\?\GLOBALROOT\device\harddisk2\ 512GB NVMe SAMSUNG MZVPV512 - \\?\GLOBALROOT\device\harddisk3\ OS is Windows 10 build 10240 installed in UEFI mode and booting fine from the Samsung NVMe Drive. DISKPART> list disk Disk ### Status Size Free Dyn Gpt -------- ------------- ------- ------- --- --- Disk 0 Online 238 GB 0 B Disk 1 Online 1863 GB 1024 KB * Disk 2 Online 931 GB 1024 KB Disk 3 Online 476 GB 0 B * DISKPART> select disk 3 Disk 3 is now the selected disk. DISKPART> list partition Partition ### Type Size Offset ------------- ---------------- ------- ------- Partition 1 Recovery 450 MB 1024 KB Partition 2 System 100 MB 451 MB Partition 3 Reserved 16 MB 551 MB Partition 4 Primary 476 GB 567 MB So my C: Drive is Partition 4 on Disk 3, UEFI Boot Partition is Partition 2 on Disk 3 and my Windows Recovery Partition is partition 1 on Disk 3. And the (WinRE) recovery environment seemed to be configured as it should: C:\Windows\system32>reagentc /info Windows Recovery Environment (Windows RE) and system reset configuration Information: Windows RE status: Enabled Windows RE location: \\?\GLOBALROOT\device\harddisk3\partition1\Recovery\WindowsRE Boot Configuration Data (BCD) identifier: {BCDGUID1} Recovery image location: Recovery image index: 0 Custom image location: Custom image index: 0 REAGENTC.EXE: Operation Successful. Ok roll on to November and Microsoft release Version 1511 (Build 10586) and I go to install it .... I do this via windows updates which seems to go well, but on the first reboot I am met with a Windows error 0xc00000bb "Required Device isnt connected or cant be accessed" ... when I get back in to windows after it has rolled back I am greeted by the 0XC190010 0x20017 error "installation failed in the SAFE_OS phase with an error during Boot operation". I tried several times over the next few weeks all with the same error. In January 2016 I use the media creation tool and try the upgrade from the pen and the local ESD folder all fail with the same error on that first reboot. So having done some more digging I release that during that first reboot it tries to reboot in to a recovery environment to replace a bunch of windows files. With that in mind from my operational 10240 build I try and reboot in to RE, I tried both the shift method during reboot and bcdedit boottore . Amazingly it failed with exactly the same error. 0xc00000bb "Required Device isnt connected or cant be accessed" for some reason the PC will not access either winre.wim or boot.sdi on Harddisk3 (the Samsung NVMe M.2 Drive) ... Using information found at https://social.technet.microsoft.com/Forums/en-US/9801aa0a-d876-4699-a31d-ba4ca08eea50/solved-how-do-i-prepare-windows-recovery-environment-on-windows-10-taking-backup-measures-on-your?forum=WinPreview2014Setup I move the recovery environment to harddisk0 my Plextor SSD and much to my surprise it no longer generated the error, it still did not load however and seemed to crash my PC. So I moved WinRE to harddisk1, the 2TB normal HD and it worked fine!!!! C:\Windows\system32>reagentc /info Windows Recovery Environment (Windows RE) and system reset configuration Information: Windows RE status: Enabled Windows RE location: \\?\GLOBALROOT\device\harddisk1\partition2\Recovery\WindowsRE Boot Configuration Data (BCD) identifier: {BCDGUID1} Recovery image location: Recovery image index: 0 Custom image location: Custom image index: 0 REAGENTC.EXE: Operation Successful. Thinking this may be a bios related issue, I upgrade to 2.10 and moved winre envrionment back to the dedicated partition but it still errored. As I have a working WinRE environment off the SATA drive I am about to re-attempt the upgrade, I have a nasty feeling however that as part of the upgrade it refers/links to the WinRE/Ramdisk in $Windows.~BT which always gets created on C (M2) and therefore will not work on the reboot!! I have not been able to find a way to get that directory created on another drive. Does anyone know why the machine will not reboot in to a winre environment located on the M.2 NVMe SSD - yet it will boot in to an operating system on the device. I have tried all the permutations for CSM in the Bios and the only thing listed my bootlist in Bios is Windows Boot Manager. Has anyone else had the same issue ? ------------- Intel Core i7 5930K | ASRock X99 WS | 32GB Corsair Vengeance LPX EVGA GTX 980 Ti Classified ACX 2.0+ | SM951 M2 NVMe | QPAD MK-85 DeathAdder Chroma | Phanteks Enthoo Primo | AX860i | Win 10 Pro x64 |
Replies:
Posted By: GuruNot
Date Posted: 23 Jan 2016 at 11:20pm
|
With the native recovery environment working I just tried the upgrade again using the USB pen, this failed with the same 0xc00000bb error, it seems the "upgrade Reboot" winre.wim/boot.sdi is on the C: Drive which is not accessible to the bios!! ------------- Intel Core i7 5930K | ASRock X99 WS | 32GB Corsair Vengeance LPX EVGA GTX 980 Ti Classified ACX 2.0+ | SM951 M2 NVMe | QPAD MK-85 DeathAdder Chroma | Phanteks Enthoo Primo | AX860i | Win 10 Pro x64 |
Posted By: parsec
Date Posted: 23 Jan 2016 at 11:50pm
|
To (not) answer your specific question, no I don't know why. But if you installed Windows 10 on your SM951 with even one other drive connected to the PC at that time, then the System partition in use could be on another drive. Actually that is a given if more than the target OS drive was powered on during the Win 10 installation. Or, if any of your other drives have a left over System partition on it, that could be causing the confusion. Given the fix you came up with, moving a partition to the Plextor SSD, there seemed to be some type of confusion like I described, or possibly a corruption of a partition on the SM951. You should run Diskpart and examine the partitions on all of your drives. But at this point that may not provide an answer. I recently installed Win 10 10240 on a RAID 0 array of two 950 Pros, in UEFI mode. I updated to 10586 via Windows Update just two days ago, by coincidence. I did not have the problem you had. I'm using that PC now. It is a different platform (Z170), and I did not check the UEFI versions for your board. I don't know how this could be caused by a BIOS problem. Given all you've done to fix your issue, it may be impossible to show it is a BIOS problem. A UEFI booting Windows installation on a SATA SSD can boot with CSM Enabled, but I doubt a PCIe SSD can, since it should require the EFI boot loader. That is not used when CSM is Enabled. ------------- http://valid.x86.fr/48rujh" rel="nofollow"> 
|
Posted By: GuruNot
Date Posted: 24 Jan 2016 at 12:09am
|
Just to clarify, moving the Recovery environment to the SSD did stop the error, but it did not load the recovery environment, it crashed. It was not successful until i moved it to the 2TB GPT Disk. No evidence of any other system partitions, only the ones on the sm951: DISKPART> select disk 0 Disk 0 is now the selected disk. DISKPART> list partition Partition ### Type Size Offset ------------- ---------------- ------- ------- Partition 1 Primary 238 GB 1024 KB DISKPART> select disk 1 Disk 1 is now the selected disk. DISKPART> list partition Partition ### Type Size Offset ------------- ---------------- ------- ------- Partition 1 Reserved 128 MB 17 KB Partition 2 Primary 1862 GB 129 MB DISKPART> select disk 2 Disk 2 is now the selected disk. DISKPART> list partition Partition ### Type Size Offset ------------- ---------------- ------- ------- Partition 1 Primary 292 GB 31 KB Partition 2 Primary 638 GB 292 GB DISKPART> select disk 3 Disk 3 is now the selected disk. DISKPART> list partition Partition ### Type Size Offset ------------- ---------------- ------- ------- Partition 1 Recovery 450 MB 1024 KB Partition 2 System 100 MB 451 MB Partition 3 Reserved 16 MB 551 MB Partition 4 Primary 476 GB 567 MB I am a bit baffled to say the least. ------------- Intel Core i7 5930K | ASRock X99 WS | 32GB Corsair Vengeance LPX EVGA GTX 980 Ti Classified ACX 2.0+ | SM951 M2 NVMe | QPAD MK-85 DeathAdder Chroma | Phanteks Enthoo Primo | AX860i | Win 10 Pro x64 |
Posted By: GuruNot
Date Posted: 24 Jan 2016 at 12:24am
|
Is defo looks like it is uefi booting off the sm951 System Partition. Msinfo shows: OS Name Microsoft Windows 10 Pro Version 10.0.10240 Build 10240 Other OS Description Not Available OS Manufacturer Microsoft Corporation System Name Blank System Manufacturer To Be Filled By O.E.M. System Model To Be Filled By O.E.M. System Type x64-based PC System SKU To Be Filled By O.E.M. Processor Intel(R) Core(TM) i7-5930K CPU @ 3.50GHz, 3501 Mhz, 6 Core(s), 12 Logical Processor(s) BIOS Version/Date American Megatrends Inc. P2.10, 07/01/2016 SMBIOS Version 2.8 Embedded Controller Version 255.255 BIOS Mode UEFI BaseBoard Manufacturer ASRock BaseBoard Model Not Available BaseBoard Name Base Board Platform Role Desktop Secure Boot State Off PCR7 Configuration Binding Not Possible Windows Directory C:\Windows System Directory C:\Windows\system32 Boot Device \Device\HarddiskVolume2 Locale United Kingdom Hardware Abstraction Layer Version = "10.0.10240.16392" And using WinObj to check the translation for \Device\HarddiskVolume2 shows it equates to Harddisk3partition2 ------------- Intel Core i7 5930K | ASRock X99 WS | 32GB Corsair Vengeance LPX EVGA GTX 980 Ti Classified ACX 2.0+ | SM951 M2 NVMe | QPAD MK-85 DeathAdder Chroma | Phanteks Enthoo Primo | AX860i | Win 10 Pro x64 |
Posted By: ASRock_TSD
Date Posted: 26 Jan 2016 at 8:07pm
|
Dear customer, This is ASRock Technical Support Department. Thank you for the query. On your case, we recommend you to remove another HDD/SSD, install only SM951 to reinstall the Windows 10 for try. If the BSOD screen still, please use another SSD/HDD to verify. Kindest Regards, ASRock TSD |
Posted By: GuruNot
Date Posted: 27 Jan 2016 at 7:32am
|
Exactly the same issue when installing with just the M.2 connected. I did a clean install, as soon as configured attempted to reboot in to the recovery environment and was greeted with the 0xc00000bb error. I will try installing the SSD tomorrow. ------------- Intel Core i7 5930K | ASRock X99 WS | 32GB Corsair Vengeance LPX EVGA GTX 980 Ti Classified ACX 2.0+ | SM951 M2 NVMe | QPAD MK-85 DeathAdder Chroma | Phanteks Enthoo Primo | AX860i | Win 10 Pro x64 |
Posted By: parsec
Date Posted: 27 Jan 2016 at 12:38pm
|
I agree your system seems to be free of rogue system (boot) partitions. The question now is why does it seem that the recovery partition is corrupted. Or perhaps there is an issue with the RE and the Samsung NVMe driver, which I assume you have installed? How do you boot into the RE? What is the procedure? Do you use a recovery USB flash drive, for example, with the reagentc command? FYI, when I run reagentc /info, the Boot Configuration Data (BSD) identifier is shown as a full GUID string, not an environment variable. You might want to check the procedure for using the RE environment, since it is easy to make a mistake attempting to use it. Are you planning on just putting the SSD back in the PC, or installing Win 10 on it for a test? It would be interesting if the SSD's recovery environment worked for you. ------------- http://valid.x86.fr/48rujh" rel="nofollow">
|
Posted By: GuruNot
Date Posted: 28 Jan 2016 at 3:39am
|
I did not have the Samsung NVMe driver loaded I was using the Native Microsoft one , I have since installed Versions 1.1 of the Samsung Driver and that has made no difference. To be honest I am not sure that it even comes in to play at that point. I have tried both ways to the boot in to WinRE , running the command line: reagentc.exe /boottore and then rebooting. Or Following Step 2 at http://www.digitalcitizen.life/4-ways-boot-safe-mode-windows-10 choosing startup repair under Advanced options. This launches winre just like a build upgrade does. Neither method works, I still get the 0xc00000bb error. With regards to the part of the post with the BCD Data, I do a get a string there too, I chose not to post it for privacy reasons. The SSD is one of the drives that is already in the PC I will flatten the OS on the SM951 and do a UEFI Install of Windows 10 to that to see if things work. ------------- Intel Core i7 5930K | ASRock X99 WS | 32GB Corsair Vengeance LPX EVGA GTX 980 Ti Classified ACX 2.0+ | SM951 M2 NVMe | QPAD MK-85 DeathAdder Chroma | Phanteks Enthoo Primo | AX860i | Win 10 Pro x64 |
Posted By: GuruNot
Date Posted: 28 Jan 2016 at 3:46am
|
Just for info, if I follow Step 2 at http://www.digitalcitizen.life/4-ways-boot-safe-mode-windows-10 all the way through as stated in the article after rebooting I get to the to startup settings screen as shown. If i press F10 for more options it displays the option to reboot in to the Recovery Environment. If i choose that option it also crashes out with 0xc00000bb So I am off to reinstall Windows 10 again on my System, this time to my Plextor SSD. ------------- Intel Core i7 5930K | ASRock X99 WS | 32GB Corsair Vengeance LPX EVGA GTX 980 Ti Classified ACX 2.0+ | SM951 M2 NVMe | QPAD MK-85 DeathAdder Chroma | Phanteks Enthoo Primo | AX860i | Win 10 Pro x64 |
Posted By: GuruNot
Date Posted: 28 Jan 2016 at 6:27am
|
Ok .... UEFI Install to Plextor SSD worked absolutely fine. Rebooted with absolutely no issue in to the Recovery Environment. The makes it pretty clear the issue is NVMe SM951 specific, but could still either be a Windows or Motherbaord/UEFI issue. I have blown everything away again and I am back with my OS and Recovery partition on the NVMe SM951. Which still fails to reboot in to WinRE with 0xc00000bb . ------------- Intel Core i7 5930K | ASRock X99 WS | 32GB Corsair Vengeance LPX EVGA GTX 980 Ti Classified ACX 2.0+ | SM951 M2 NVMe | QPAD MK-85 DeathAdder Chroma | Phanteks Enthoo Primo | AX860i | Win 10 Pro x64 |
Posted By: GuruNot
Date Posted: 29 Jan 2016 at 5:59am
|
Ok, in one last attempt to try and get the WinRE image booting from my SM951 NVMe drive , I wondered if the winre.wim was missing some drivers (I can dream) ... So i thought I would create a custom winre.wim and see if the helped. First off, to create some folders: md e:\mount md e:\mount\drivers md e:\mount\drivers\1 md e:\mount\drivers\2 md e:\mount\drivers\3 md e:\mount\drivers\4 md e:\mount\drivers\5 md e:\mount\drivers\6 md e:\mount\winre I Put Winre.wim in e:\mount, I put a clean copy of REAgent.xml in e:\mount, I put the Samsung NVMe drivers in e:\mount\drivers, as I could not be bothered to work out which was required, I took the six sets of drivers from the Samsung NVMe Driver 1.1 Exe and put them in individual folders, hence the folders 1 to 6. I then mounted the winre image: Dism /mount-image /imagefile:e:\mount\winre.wim /index:1 /mountdir:e:\mount\winre Deployment Image Servicing and Management tool Version: 10.0.10586.0 Mounting image [==========================100.0%==========================] The operation completed successfully. Added the unsigned Samsung NVMe drivers: E:\mount>Dism /Image:e:\mount\winre /Add-Driver /Driver:e:\Mount\Drivers /forceunsigned /recurse Deployment Image Servicing and Management tool Version: 10.0.10586.0 Image Version: 10.0.10586.0 Searching for driver packages to install... Found 6 driver package(s) to install. Installing 1 of 6 - e:\Mount\Drivers\1\nvme.inf: The driver package was successfully installed. Installing 2 of 6 - e:\Mount\Drivers\2\nvme.inf: The driver package was successfully installed. Installing 3 of 6 - e:\Mount\Drivers\3\nvme.inf: The driver package was successfully installed. Installing 4 of 6 - e:\Mount\Drivers\4\nvme.inf: The driver package was successfully installed. Installing 5 of 6 - e:\Mount\Drivers\5\nvme.inf: The driver package was successfully installed. Installing 6 of 6 - e:\Mount\Drivers\6\nvme.inf: The driver package was successfully installed. The operation completed successfully. Once complete, I unmounted the modified wim: E:\mount>DISM /Unmount-Wim /MountDir:e:\Mount\winre /Commit Deployment Image Servicing and Management tool Version: 10.0.10586.0 Image File : e:\mount\winre.wim Image Index : 1 Saving image [==========================100.0%==========================] Unmounting image [==========================100.0%==========================] The operation completed successfully. Ok now time to get the new modified WinRE.wim on to the dedicated recovery partition: DISKPART> list disk Disk ### Status Size Free Dyn Gpt -------- ------------- ------- ------- --- --- Disk 0 Online 476 GB 0 B * Disk 1 Online 238 GB 0 B Disk 2 Online 1863 GB 1024 KB * Disk 3 Online 931 GB 1024 KB Disk 4 No Media 0 B 0 B DISKPART> select disk 0 Disk 0 is now the selected disk. DISKPART> list partition Partition ### Type Size Offset ------------- ---------------- ------- ------- Partition 1 Recovery 450 MB 1024 KB Partition 2 System 100 MB 451 MB Partition 3 Reserved 16 MB 551 MB Partition 4 Primary 476 GB 567 MB DISKPART> select partition 1 Partition 1 is now the selected partition. DISKPART> assign letter="R" DiskPart successfully assigned the drive letter or mount point. DISKPART> exit Leaving DiskPart... E:\mount>r: Disable WinRE: R:\>reagentc /disable REAGENTC.EXE: Operation Successful. Get rid of the Existing Recovery Files: R:\>rd Recovery /q /s Recreate the WinRE Directories: R:\>mkdir Recovery R:\>mkdir Recovery\WindowsRE Copy across the modified wim: R:\>xcopy /H e:\Mount\Winre.wim R:\Recovery\WindowsRE\ E:\Mount\winre.wim 1 File(s) copied And the clean xml: R:\>xcopy /H e:\mount\ReAgent.xml R:\Recovery\WindowsRE\ E:\mount\ReAgent.xml 1 File(s) copied Set the path to winre.wim: R:\>Reagentc /setreimage /path r:\Recovery\WindowsRE Directory set to: \\?\GLOBALROOT\device\harddisk0\partition1\Recovery\WindowsRE REAGENTC.EXE: Operation Successful. Re-enable: R:\>Reagentc /enable REAGENTC.EXE: Operation Successful. And then i tried to reboot in to winre ............. But failed , with exactly the same 0xc00000bb error. I really have tried as much as I can , so can ASROCK Tech support please come up with some ideas. Windows 10 installs to and runs fine from the SM951 .... it is just this WinRE Environment that fails to work. ------------- Intel Core i7 5930K | ASRock X99 WS | 32GB Corsair Vengeance LPX EVGA GTX 980 Ti Classified ACX 2.0+ | SM951 M2 NVMe | QPAD MK-85 DeathAdder Chroma | Phanteks Enthoo Primo | AX860i | Win 10 Pro x64 |
Posted By: GuruNot
Date Posted: 23 Feb 2016 at 12:08am
|
I has been almost a month since my last post with the various results, any chance of a reply from ASRock tech support ? ------------- Intel Core i7 5930K | ASRock X99 WS | 32GB Corsair Vengeance LPX EVGA GTX 980 Ti Classified ACX 2.0+ | SM951 M2 NVMe | QPAD MK-85 DeathAdder Chroma | Phanteks Enthoo Primo | AX860i | Win 10 Pro x64 |
Posted By: parsec
Date Posted: 24 Feb 2016 at 3:23pm
|
An SM951, or any NVMe PCIe SSD runs with a UEFI rather than a Legacy boot loader. You have either Launch Storage OpROM Policy set to UEFI Only, or CSM set to Disabled, in order to be able to install Windows and boot from an NVMe SSD. Among the four partitions on your SM951 is a semi-hidden Legacy MBR partition that Windows includes along with the UEFI GPT partition. That is included so legacy Windows utilities like the Windows memory test will still run. This configuration works with SATA drives, since a SATA drive can boot in both a Legacy and UEFI environment. An NVMe SSD cannot boot in a Legacy environment, only in a UEFI environment. My question is, does the Windows RE software need to run in the legacy environment? Or put another way, can it run in the UEFI environment? I don't know if it can or not. This is the question that needs an answer from MS, to either stop you from wasting your time (if it cannot) or to find another answer (if it can.) ------------- http://valid.x86.fr/48rujh" rel="nofollow">
|
Posted By: GuruNot
Date Posted: 25 Feb 2016 at 3:54am
|
Hi Parsec, CSM was set to disabled during my testing to ensure UEFI mode was being used. I am no expert, but I believe your statement "Among the four partitions on your SM951 is a semi-hidden Legacy MBR partition that Windows includes along with the UEFI GPT partition. That is included so legacy Windows utilities like the Windows memory test will still run." is wrong. The use of GUID Partition Table (GPT) or Master Boot Record (MBR) is defined at a disk level. With Windows 10 if you want to install to a UEFI device you have to use GPT. Windows does not support GPT Partitions for BIOS/Legacy installs. Disks that use GPT for storing partition info can be seen in diskpart: DISKPART> list disk Disk ### Status Size Free Dyn Gpt -------- ------------- ------- ------- --- --- Disk 0 Online 476 GB 0 B * Disk 1 Online 238 GB 0 B Disk 2 Online 1863 GB 1024 KB * Disk 3 Online 931 GB 1024 KB Looking at the disk the is indeed a small reserved partition: DISKPART> select disk 0 Disk 0 is now the selected disk. DISKPART> list partition Partition ### Type Size Offset ------------- ---------------- ------- ------- Partition 1 Recovery 450 MB 1024 KB <== WinRE Parttion Partition 2 System 100 MB 451 MB <== U/EFI System Partition Partition 3 Reserved 16 MB 551 MB <== MSR Partition Partition 4 Primary 476 GB 567 MB <== Windows Partition But the 16MB Reserved MSR partition is not a legacy MBR Partition. See http://msdn.microsoft.com/en-us/library/windows/hardware/dn898510%28v=vs.85%29.aspx" rel="nofollow - here for explanation. Looking at bcdedit, memcheck actually runs from the UEFI System Partition: C:\Windows\system32>bcdedit /enum all Firmware Boot Manager --------------------- identifier {fwbootmgr} displayorder {bootmgr} timeout 1 Windows Boot Manager -------------------- identifier {bootmgr} device partition=\Device\HarddiskVolume2 path \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI description Windows Boot Manager locale en-GB inherit {globalsettings} default {current} resumeobject {ce8bbc28-c537-11e5-883c-b72214bc5514} displayorder {current} toolsdisplayorder {memdiag} timeout 30 (More Stuff) Windows Memory Tester --------------------- identifier {memdiag} device partition=\Device\HarddiskVolume2 path \EFI\Microsoft\Boot\memtest.efi description Windows Memory Diagnostic locale en-GB inherit {globalsettings} badmemoryaccess Yes (More Stuff) I am not wasting much time on this anymore, but I was hoping to get a bit more of a response from ASRock than "See if it works with a normal SSD" .... Which it did. The next time Microsoft release a major build , as opposed to an incremental update, is the next time it will cause me issues. ------------- Intel Core i7 5930K | ASRock X99 WS | 32GB Corsair Vengeance LPX EVGA GTX 980 Ti Classified ACX 2.0+ | SM951 M2 NVMe | QPAD MK-85 DeathAdder Chroma | Phanteks Enthoo Primo | AX860i | Win 10 Pro x64 |
Posted By: GuruNot
Date Posted: 28 Mar 2016 at 7:21pm
|
Just a little update, I still have heard nothing back from ASRock tech support whether it be an email or via this forum post. But I did notice recently, from Parsec's forum post, that the new BIOSes for the soon to be released Broadwell-E CPUs have arrived. Even though I do not intend to replace my Haswell-E with a Broadwell-E , I thought I would update the BIOS to 3.10 in another attempt to get my issue resolved. So, I downloaded and extracted the ROM to a USB Pen, rebooted into UEFI and did an instant flash update. A couple of reboots later having put my BIOS settings back to how they were, I was in Windows 10 again. I disabled the existing recovery environment and ran through the config again to ensure it was set to use a partition on my NVMe drive. The moment of truth, I ran "reagentc.exe /boottore" from an elevated command prompt and rebooted............ And what do you know it worked. It booted in to the recovery options absolutely fine. As there have been some Windows 10 rollups released which I have applied , I cannot for certain say whether it was just down to the bios update. But my NVMe and ASRock X99 WS seem to be working as they should at the moment , my issue is resolved. ------------- Intel Core i7 5930K | ASRock X99 WS | 32GB Corsair Vengeance LPX EVGA GTX 980 Ti Classified ACX 2.0+ | SM951 M2 NVMe | QPAD MK-85 DeathAdder Chroma | Phanteks Enthoo Primo | AX860i | Win 10 Pro x64 |