Windows 10: Computer with New M.2 gets stuck at reboot even on a fresh install

HP Envy 750-247c i7-6700/24gb ram/nvidia 980ti/700W psu/SATA Sandisk SSD 960G/m.2 nvme Silicon Power gen3x4 1TB ECFM12.2.

If I use the M.2 as the boot drive (with or without SATA SSD as second drive) the computer won't reboot properly, either gets stuck just before showing the bios screen or just after. Usually allows me to hit control+alt+delete, sometimes requires me to power off completely. Either way, it will boot up fine after. Even during the install process it will hang. Tried a fresh install of win10 1909 & 2004 + latest drivers for all devices, even tried Intel's nvme drivers rst17.7 and other various drivers chipset10.1.1.18/wifi/bluetooth/realtek nic/etc. Latest bios (ROM Family SSID 2B4B A0.59 Rev.A Feb 12, 2018). Reset bios to defaults, tried AHCI & RAID (which probably doesn't matter for M.2 use). Passes HP uefi/windows diagnostics. Disabled fastboot, no change. Stuck as to what to try next within reason (not in the market for motherboard/CPU replacement currently).

Computer works just fine if I use the SATA Sandisk SSD 960G (sandisk tools says latest firmware/healthy) by itself or as the primary and the M.2 as the secondary, so it "seems" to be M.2 related. Halt on reboot wouldn't be that big of a deal, but I have this machine joined to the Windows Insider Program fast ring so it gets constant build updates & needs to reboot a good deal with those updates.

Crystal Disk Info reports health status 100% Good, CDM speeds report pretty close to what I would expect (using Windows nvme or Intel nvme driver, no real change) -

[Read]

Sequential 1MiB (Q= 8, T= 1): 3240.976 MB/s [ 3090.8 IOPS] < 2576.77 us>

Sequential 1MiB (Q= 1, T= 1): 1954.816 MB/s [ 1864.3 IOPS] < 535.73 us>

Random 4KiB (Q= 32, T=16): 1653.361 MB/s [ 403652.6 IOPS] < 1218.68 us>

Random 4KiB (Q= 1, T= 1): 41.517 MB/s [ 10136.0 IOPS] < 98.32 us>

[Write]

Sequential 1MiB (Q= 8, T= 1): 3028.067 MB/s [ 2887.8 IOPS] < 2758.53 us>

Sequential 1MiB (Q= 1, T= 1): 2415.482 MB/s [ 2303.6 IOPS] < 432.95 us>

Random 4KiB (Q= 32, T=16): 1301.872 MB/s [ 317839.8 IOPS] < 1583.47 us>

Random 4KiB (Q= 1, T= 1): 137.311 MB/s [ 33523.2 IOPS] < 29.58 us>

submitted by /u/abeNdorg
[link] [comments]

:)

 

Computer Won't Reboot - AMD Data Change...Updata New Data to DMI

If he is getting stuck at verifying DMI pool data, that means his BIOS isn't finishing the POST process before it's hanging up. Although I'm confused now because he said he tried re-installing windows which would indicate that the machine is getting through the entire POST process.

I'm confused now. I think we need a better, more descriptive version of what exactly is happening.

Maybe a full step by step process of what is happening?

 

M-Audio M-Track 2x2 Not Recognized by my computer.

Hi,



Thank you for writing to Microsoft Community Forums.



We appreciate the research and troubleshooting you have done, this issue could be from the software end or from the hardware itself.



Please try few of the troubleshooting below to further eliminate the root cause of the issue.

1. Try to connect the device with a different USB and check if that helps.
   
2. Connect the M-track to different computer and check if you still face the issue there, if the issue persists, it could be caused by hardware.
   

Method 1:

1. Press Windows + R key on your keyboard together, and type
   control printers.
   
2. You will see list of all the devices and printers connected to your computer.
   
3. Click on Add a device and follow the onscreen instruction and add your device.
   

Method 2:

1. Uninstall
   all the M-Track drivers from device manager.
   
2. Reboot the computer and check.
   

Method 3:



I suggest you login to the manufacturer site,
download the drivers for your registered device and
install it.



If you still face the issue, I suggest you to get in touch with the
manufacturer and get the hardware checked once.



Hope it helps.

Amit Sunar

Microsoft Community – Moderator

 

Stuck in Automatic Repair Loop after fresh install onto new M.2

I recently installed an M.2 SSD into my Alienware Aurora R6 and reinstalled Windows 10 from scratch onto it. The operating system installed as normal, but whenever I reboot my computer, I get kicked into Automatic Repair. If I jam on the F12 button and manually boot from the hard drive I installed windows to (HDD2 - the M.2 SSD), it boots into Windows fine. I'm pulling my hair out here. How can I get this to stop? Isn't there anyway to have Windows Boot Manager automatically select the correct hard drive? On a side note, there is no way for me to just select the boot hard drive from BIOS. I have to select Windows Boot Manager. Anyone know what to do? Thanks in advance.