Windows 10 unable to boot in random moments

You can mark this thread as "solved"
It was a pleasure

Pentagon said:

You can mark this thread as "solved"
It was a pleasure

Done!
I also proceeded to install both the old nvme (which was installed) and the new one.
The old one (which we messed up until now) is now able to boot properly even when the other is installed!

Before I forget: Screenshots can be uploaded as well.

Pentagon said:

I do not have access to your srt.7z Message: do not have permission to access this page?.
The "DPC_WATCHDOG_VIOLATION" can be disabled in BIOS and is not the problem.

Right now I have no idea about your current config old/new. Post a screenshot of your "Diskmanagement"
Expand the first column in the upper field that everything is readable.

Weird I attached the file here in the forum, let me provide you another link: srt.7z - Google Drive

Config is the same, just on the old ssd (which we fixed this morning) is installed windows 10 pro N (with all the updates). On the new ssd I opted for Windows 10 ltsc N 21H2.

Here is the screen:


Bigger ssd is the new (C), older is the 1tb (drive letter F), huge storage is raid 1.
Expanded first column:

Disk 0 is the new one
Disk 1 is the old from this morning
Disk 2 is the Data (Raid 1 with 2 disks?)
Is that correct?

Pentagon said:

Disk 0 is the new one
Disk 1 is the old from this morning
Disk 2 is the Data (Raid 1 with 2 disks?)
Is that correct?

yes, tip-top
Some more details:
The old one worked "fine" (random boot locks up in it's whole life) this morning in the first m2 slot, it also worked fine once (but it did the same the other day) when i moved it to the second m2 slot and installed the new one in the first one.
I now also noticed that when I get into the uefi I get a very quick freeze of 1-2 seconds when it looks for drives.

OK, now we are in/on disk 0
Run bcdedit /enum all

Your attached bcdinfo is from the booted recovery

Pentagon said:

OK, now we are in/on disk 0
Run bcdedit /enum all

Your attached bcdinfo is from the booted recovery

Yes it's from booted recovery of the old hard drive since it's unable to boot properly.

Here is the output bcdedit /enum all from the new hard drive:

Code:

Microsoft Windows [Versione 10.0.19044.4170]
(c) Microsoft Corporation. Tutti i diritti sono riservati.

C:\Windows\system32> bcdedit /enum all

Boot Manager per firmware
---------------------
identificatore          {fwbootmgr}
displayorder            {ff565201-ef4e-11ee-ba87-806e6f6e6963}
                        {bootmgr}
timeout                 1

Windows Boot Manager
--------------------
identificatore          {bootmgr}
device                  partition=\Device\HarddiskVolume5
path                    \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI
description             Windows Boot Manager
locale                  it-IT
inherit                 {globalsettings}
default                 {current}
resumeobject            {aad5c7b3-ece2-11ee-a7cc-f231abc32698}
displayorder            {current}
toolsdisplayorder       {memdiag}
timeout                 30

Applicazione firmware (101fffff)
-------------------------------
identificatore          {ff565201-ef4e-11ee-ba87-806e6f6e6963}
device                  partition=\Device\HarddiskVolume1
path                    \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI
description             Windows Boot Manager

Caricatore di avvio di Windows
-------------------
identificatore          {current}
device                  partition=C:
path                    \Windows\system32\winload.efi
description             Windows 10
locale                  it-IT
inherit                 {bootloadersettings}
recoverysequence        {aad5c7b5-ece2-11ee-a7cc-f231abc32698}
displaymessageoverride  CommandPrompt
recoveryenabled         Yes
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
osdevice                partition=C:
systemroot              \Windows
resumeobject            {aad5c7b3-ece2-11ee-a7cc-f231abc32698}
nx                      OptIn
bootmenupolicy          Standard

Caricatore di avvio di Windows
-------------------
identificatore          {aad5c7b5-ece2-11ee-a7cc-f231abc32698}
device                  ramdisk=[\Device\HarddiskVolume4]\Recovery\WindowsRE\Winre.wim,{aad5c7b6-ece2-11ee-a7cc-f231abc32698}
path                    \windows\system32\winload.efi
description             Windows Recovery Environment
locale                  it-it
inherit                 {bootloadersettings}
displaymessage          Recovery
osdevice                ramdisk=[\Device\HarddiskVolume4]\Recovery\WindowsRE\Winre.wim,{aad5c7b6-ece2-11ee-a7cc-f231abc32698}
systemroot              \windows
nx                      OptIn
bootmenupolicy          Standard
winpe                   Yes

Ripresa da modalità di ibernazione
---------------------
identificatore          {aad5c7b3-ece2-11ee-a7cc-f231abc32698}
device                  partition=C:
path                    \Windows\system32\winresume.efi
description             Windows Resume Application
locale                  it-IT
inherit                 {resumeloadersettings}
recoverysequence        {aad5c7b5-ece2-11ee-a7cc-f231abc32698}
recoveryenabled         Yes
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
filedevice              partition=C:
filepath                \hiberfil.sys
bootmenupolicy          Standard
debugoptionenabled      No

Tester memoria di Windows
---------------------
identificatore          {memdiag}
device                  partition=\Device\HarddiskVolume1
path                    \EFI\Microsoft\Boot\memtest.efi
description             Diagnostica memoria Windows
locale                  it-IT
inherit                 {globalsettings}
badmemoryaccess         Yes

Impostazioni Servizi di gestione emergenze
------------
identificatore          {emssettings}
bootems                 No

Impostazioni debugger
-----------------
identificatore          {dbgsettings}
debugtype               Local

Problemi RAM
-----------
identificatore          {badmemory}

Impostazioni globali
---------------
identificatore          {globalsettings}
inherit                 {dbgsettings}
                        {emssettings}
                        {badmemory}

Impostazioni caricatore di avvio
-------------------
identificatore          {bootloadersettings}
inherit                 {globalsettings}
                        {hypervisorsettings}

Impostazioni hypervisor
-------------------
identificatore          {hypervisorsettings}
hypervisordebugtype     Serial
hypervisordebugport     1
hypervisorbaudrate      115200

Impostazioni Resume Loader
----------------------
identificatore          {resumeloadersettings}
inherit                 {globalsettings}

Opzioni dispositivo
--------------
identificatore          {aad5c7b6-ece2-11ee-a7cc-f231abc32698}
description             Windows Recovery
ramdisksdidevice        partition=\Device\HarddiskVolume4
ramdisksdipath          \Recovery\WindowsRE\boot.sdi

C:\Windows\system32>

The two hard drives are installed separately, when I want to choose from which one to boot I modify the order on uefi\bios.