A boot problem would result in a BSOD
strange noise in that video
If you are on (C:) Sabrent an (F:) is still visible type:
mkdir F:\scratch
Dism /image:F:\ /Cleanup-Image /RestoreHealth /ScratchDir:F:\scratch
sfc /scannow /offbootdir=F:\ /offwindir=F:\Windows /offlogfile=F:\sfc.txt
It takes a while, so be patient!
Yes, that's why I posted the DPC_WAtchdog_Violation blue screen before (it happens very rarely when I have boot issues), most of the times happens what I showed in the video.
Ok I'm going to execute those commands and post the log.
Results:
No errors found :\Code:Microsoft Windows [Versione 10.0.19044.4170] (c) Microsoft Corporation. Tutti i diritti sono riservati. C:\Windows\system32>mkdir F:\scratch C:\Windows\system32>Dism /image:F:\ /Cleanup-Image /RestoreHealth /ScratchDir:F:\scratch Strumento Gestione e manutenzione immagini distribuzione Versione: 10.0.19041.3636 Versione immagine: 10.0.19045.4170 [==========================100.0%==========================] Operazione di ripristino riuscita. Operazione completata. C:\Windows\system32>sfc /scannow /offbootdir=F:\ /offwindir=F:\Windows /offlogfile=F:\sfc.txt Avvio in corso dell'analisi del sistema. Attendere. L'operazione richiederą alcuni minuti. Protezione risorse di Windows: nessuna violazione di integritą trovata. C:\Windows\system32>
The sfc.txt file is 2.05mb, do you want to see it?
Relevant voices:
Code:00000001 Shim considered [l:126]'\??\F:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.4163_none_7e304ec47c735f2e\wcp.dll' : got STATUS_OBJECT_PATH_NOT_FOUND 00000002 Shim considered [l:123]'\??\F:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.4163_none_7e304ec47c735f2e\wcp.dll' : got STATUS_SUCCESS 00000001@2024/3/31:16:54:08.834 WcpInitialize: wcp.dll version 10.0.19041.4163 (WinBuild.160101.0800) 00000002 CSI Store 1499774330848 initialized Tons of: 00000003 [SR] Verifying 1 components 00000004 [SR] Beginning Verify and Repair transaction 00000005 [SR] Verify complete At the end: 0000cb18 Direct SIL provider: Number of files opened: 345225. 0000cb19 Direct SIL provider: Number of files opened: 4. 00000003 Servicing stack shim unable to mark handle 1dc ('\Device\HarddiskVolume3\Users\Nemo\AppData\Local\Temp\SSS_44b4660c8c83da01010000004806303e\msdelta.dll') for delete-on-close, error STATUS_CANNOT_DELETE 00000004 Servicing stack shim unable to mark handle 1a0 ('\Device\HarddiskVolume3\Users\Nemo\AppData\Local\Temp\SSS_44b4660c8c83da01010000004806303e') for delete-on-close, error STATUS_DIRECTORY_NOT_EMPTY
let's check the bootmanager on disk 1
cmd (admin)
diskpart
sel disk 1
sel par 1
assign letter=B
exit
bcdedit /store B:\EFI\Microsoft\Boot\BCD /enum all
nessuna violazione di integritą trovata. means what ?
Output:
Code:C:\Windows\system32>bcdedit /store B:\EFI\Microsoft\Boot\BCD /enum all Boot Manager per firmware --------------------- identificatore {fwbootmgr} displayorder {bootmgr} {28c48152-ef44-11ee-ab56-806e6f6e6963} timeout 1 Windows Boot Manager -------------------- identificatore {bootmgr} device partition=B: path \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI description Windows Boot Manager locale en-us inherit {globalsettings} default {default} resumeobject {4a713fa3-ef2f-11ee-b80c-833d98dc321f} displayorder {default} toolsdisplayorder {memdiag} timeout 30 Applicazione firmware (101fffff) ------------------------------- identificatore {28c48152-ef44-11ee-ab56-806e6f6e6963} device partition=\Device\HarddiskVolume1 path \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI description Windows Boot Manager Caricatore di avvio di Windows ------------------- identificatore {4a713fa1-ef2f-11ee-b80c-833d98dc321f} device ramdisk=[\Device\HarddiskVolume8]\Recovery\WindowsRE\Winre.wim,{4a713fa2-ef2f-11ee-b80c-833d98dc321f} path \windows\system32\winload.efi description Windows Recovery Environment locale it-IT inherit {bootloadersettings} displaymessage Recovery osdevice ramdisk=[\Device\HarddiskVolume8]\Recovery\WindowsRE\Winre.wim,{4a713fa2-ef2f-11ee-b80c-833d98dc321f} systemroot \windows nx OptIn bootmenupolicy Standard winpe Yes Caricatore di avvio di Windows ------------------- identificatore {default} device partition=F: path \Windows\system32\winload.efi description Windows 10 locale en-us inherit {bootloadersettings} recoverysequence {4a713fa1-ef2f-11ee-b80c-833d98dc321f} displaymessageoverride CommandPrompt isolatedcontext Yes allowedinmemorysettings 0x15000075 osdevice partition=F: systemroot \Windows resumeobject {4a713fa3-ef2f-11ee-b80c-833d98dc321f} nx OptIn bootmenupolicy Standard Ripresa da modalitą di ibernazione --------------------- identificatore {4a713fa3-ef2f-11ee-b80c-833d98dc321f} device partition=F: path \Windows\system32\winresume.efi description Windows Resume Application locale en-us inherit {resumeloadersettings} isolatedcontext Yes allowedinmemorysettings 0x15000075 filedevice partition=F: filepath \hiberfil.sys bootmenupolicy Standard debugoptionenabled No Tester memoria di Windows --------------------- identificatore {memdiag} device partition=B: path \EFI\Microsoft\Boot\memtest.efi description Windows Memory Diagnostic locale en-us 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 {4a713fa2-ef2f-11ee-b80c-833d98dc321f} description Windows Recovery ramdisksdidevice partition=\Device\HarddiskVolume8 ramdisksdipath \Recovery\WindowsRE\boot.sdi C:\Windows\system32>
partition=\Device\HarddiskVolume1
it should be HarddiskVolume5
Is the drive letter B: still mounted?
What should I do?
Plus now there is a double entry for the new ssd, it seems a curse:Code:DISKPART> list vol Volume ### Let. Etichetta Fs Tipo Dim. Stato Info --------- --- ----------- ----- ---------- ------- --------- -------- Volume 0 E DVD-ROM 0 b Nessun su Volume 1 C Windows 10 NTFS Partizione 1861 Gb Integro Avvio Volume 2 FAT32 Partizione 100 Mb Integro Sistema Volume 3 NTFS Partizione 1000 Mb Integro Nascosto Volume 4 F Windows 10 NTFS Partizione 952 Gb Integro Volume 5 EFI FAT32 Partizione 100 Mb Integro Nascosto Volume 6 Windows RE NTFS Partizione 1001 Mb Integro Nascosto Volume 7 D NTFS Partizione 7451 Gb Integro DISKPART>
Both entries boot fines to the new ssd.
one long command
If the drive letter B: is still mounted
bcdedit /store B:\EFI\Microsoft\Boot\BCD /set {28c48152-ef44-11ee-ab56-806e6f6e6963} device partition=\Device\HarddiskVolume5
Sometimes when the confusion is too big, it's better to rebuild the BCD completely new
Ahah no that wasn't but after that on the old ssd (mounted alone) everything was fine.
It seems pretty clear that the current boot issue with both drives installed is probably hardware now and playing with bcdedit from the new windows installation put it at risks (the entry is now doubled on uefi)
Here is what I tried and changed nothing:
1) Disconnect the Sound Blaster Z keeping both ssd connected.
2) Disconnect the new ssd and keep the old in the second position.
Then I decided to change the position of the old ssd on the nvme slot to the first one and guess what?
I'm in windows again (but now the array has gone critical, despite both hard drive are detected)!
Anyway... clearly something is wrong when both nvme ssd are connected, the next test I could do is to connect the new ssd to the second nvme slot and see if it boots fine. If it does the problem lies on the sabrent ssd or it's windows installation.
Do you agree?
Quote
