Windows 10 unable to boot in random moments

Page 2 of 8 FirstFirst 1234 ... LastLast

  1. Pentagon
    Posts : 722
    WIN 10 19045.4291
       New #11

    Very strange!
    1. usually the /enum firmware output looks different

    try
    bcdedit /enum all
      My Computer
    Quote Quote

  3. Nemo1985
    Posts : 40
    Windows 10 Pro N
    Thread Starter
       New #12

    Pentagon said:
    Very strange!
    1. usually the /enum firmware output looks different

    try
    bcdedit /enum all
    Yes it's weird.
    Also I have the 100mb partition (called efi) which isn't be used (but it should be).
    C: has efi directory:
    Code:
    c:\>DIR  C:\EFI  /a
 Il volume nell'unitą C č Windows 10
 Numero di serie del volume: 4E54-CDC0

 Directory di C:\EFI

24/09/2021  08:47    <DIR>          .
24/09/2021  08:47    <DIR>          ..
24/09/2021  08:47    <DIR>          Boot
24/09/2021  08:47    <DIR>          Microsoft
               0 File              0 byte
               4 Directory  571.653.767.168 byte disponibili

c:\>
    same has efi partition (100mb):
    Code:
    c:\>DIR  S:\EFI  /a
 Il volume nell'unitą S č EFI
 Numero di serie del volume: 7E79-EA93

 Directory di S:\EFI

30/03/2024  04:51    <DIR>          .
30/03/2024  04:51    <DIR>          ..
30/03/2024  04:51    <DIR>          Microsoft
30/03/2024  04:51    <DIR>          Boot
               0 File              0 byte
               4 Directory      76.092.416 byte disponibili

c:\>
    here is the output of the command:
    Code:
    c:\>bcdedit /enum all

Boot Manager per firmware
---------------------
identificatore          {fwbootmgr}
displayorder            {43b11d56-ef2c-11ee-ab49-806e6f6e6963}
                        {bootmgr}
timeout                 1

Windows Boot Manager
--------------------
identificatore          {bootmgr}
device                  partition=S:
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          {43b11d56-ef2c-11ee-ab49-806e6f6e6963}
device                  partition=C:
path                    \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI
description             Windows Boot Manager

Caricatore di avvio di Windows
-------------------
identificatore          {4a713fa1-ef2f-11ee-b80c-833d98dc321f}
device                  ramdisk=[\Device\HarddiskVolume4]\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\HarddiskVolume4]\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=C:
path                    \Windows\system32\winload.efi
description             Windows 10
locale                  en-us
inherit                 {bootloadersettings}
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
osdevice                partition=C:
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=C:
path                    \Windows\system32\winresume.efi
description             Windows Resume Application
locale                  en-us
inherit                 {resumeloadersettings}
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
filepath                \hiberfil.sys
bootmenupolicy          Standard

Tester memoria di Windows
---------------------
identificatore          {memdiag}
device                  partition=S:
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\HarddiskVolume4
ramdisksdipath          \Recovery\WindowsRE\boot.sdi
      My Computer
    Quote Quote

  4. Pentagon
    Posts : 722
    WIN 10 19045.4291
       New #13

    bcdedit /set {43b11d56-ef2c-11ee-ab49-806e6f6e6963} description "Windows Boot C"

    reboot and check the Bios entry. It should have changed. Try to boot from "Windows Boot C"

    There should not be this EFI-Folder on C:
      My Computer
    Quote Quote

  6. Nemo1985
    Posts : 40
    Windows 10 Pro N
    Thread Starter
       New #14

    Pentagon said:
    bcdedit /set {43b11d56-ef2c-11ee-ab49-806e6f6e6963} description "Windows Boot C"

    reboot and check the Bios entry. It should have changed. Try to boot from "Windows Boot C"

    There should not be this EFI-Folder on C:
    Done, here how it looks now:
    Imgur: The magic of the Internet
    It didn't rename correctly.
    bcdedit /enum all output:
    Code:
    C:\windows\system32>bcdedit /enum all

Boot Manager per firmware
---------------------
identificatore          {fwbootmgr}
displayorder            {43b11d56-ef2c-11ee-ab49-806e6f6e6963}
                        {7b70f410-ef31-11ee-ab4b-806e6f6e6963}
                        {bootmgr}
timeout                 1

Windows Boot Manager
--------------------
identificatore          {bootmgr}
device                  partition=\Device\HarddiskVolume1
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          {43b11d56-ef2c-11ee-ab49-806e6f6e6963}
device                  partition=C:
path                    \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI
description             UEFI: Sabrent, Partition 3

Applicazione firmware (101fffff)
-------------------------------
identificatore          {7b70f410-ef31-11ee-ab4b-806e6f6e6963}
device                  partition=C:
path                    \EFI\Microsoft\Boot\bootmgfw.efi
description             Windows Boot Manager

Caricatore di avvio di Windows
-------------------
identificatore          {4a713fa1-ef2f-11ee-b80c-833d98dc321f}
device                  ramdisk=[\Device\HarddiskVolume4]\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\HarddiskVolume4]\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=C:
path                    \Windows\system32\winload.efi
description             Windows 10
locale                  en-us
inherit                 {bootloadersettings}
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
osdevice                partition=C:
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=C:
path                    \Windows\system32\winresume.efi
description             Windows Resume Application
locale                  en-us
inherit                 {resumeloadersettings}
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
filepath                \hiberfil.sys
bootmenupolicy          Standard

Tester memoria di Windows
---------------------
identificatore          {memdiag}
device                  partition=\Device\HarddiskVolume1
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\HarddiskVolume4
ramdisksdipath          \Recovery\WindowsRE\boot.sdi

C:\windows\system32>
      My Computer
    Quote Quote

  7. Pentagon
    Posts : 722
    WIN 10 19045.4291
       New #15

    bcdedit /set {default} recoverysequence {4a713fa1-ef2f-11ee-b80c-833d98dc321f}

    The Recovery should work after this input
      My Computer
    Quote Quote

  8. Nemo1985
    Posts : 40
    Windows 10 Pro N
    Thread Starter
       New #16

    Pentagon said:
    bcdedit /set {default} recoverysequence {4a713fa1-ef2f-11ee-b80c-833d98dc321f}

    The Recovery should work after this input
    Recovery? Do you mean the recovery environment?
      My Computer
    Quote Quote

  9. Pentagon
    Posts : 722
    WIN 10 19045.4291
       New #17

    Nemo1985 said:
    Recovery? Do you mean the recovery environment?
    YES Sir

    Select: UEFI: Sabrent, Partition 3 in BIOS. Do you get a BSOD?
      My Computer
    Quote Quote

  10. Nemo1985
    Posts : 40
    Windows 10 Pro N
    Thread Starter
       New #18

    Pentagon said:
    YES Sir

    Select: UEFI: Sabrent, Partition 3 in BIOS. Do you get a BSOD?
    Nope, it booted on windows fine, but we have a new entry now:
    Imgur: The magic of the Internet
      My Computer
    Quote Quote

  12. Pentagon
    Posts : 722
    WIN 10 19045.4291
       New #19

    And a plain
    bcdedit
    shows what?
      My Computer
    Quote Quote

  13. Nemo1985
    Posts : 40
    Windows 10 Pro N
    Thread Starter
       New #20

    Pentagon said:
    And a plain
    bcdedit
    shows what?
    Oh sheep, they are multiplying like rabbits, here is the command output:
    Code:
    Microsoft Windows [Versione 10.0.19045.4170]
(c) Microsoft Corporation. Tutti i diritti sono riservati.

C:\windows\system32>bcdedit

Windows Boot Manager
--------------------
identificatore          {bootmgr}
device                  partition=\Device\HarddiskVolume1
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

Caricatore di avvio di Windows
-------------------
identificatore          {default}
device                  partition=C:
path                    \Windows\system32\winload.efi
description             Windows 10
locale                  en-us
inherit                 {bootloadersettings}
recoverysequence        {4a713fa1-ef2f-11ee-b80c-833d98dc321f}
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
osdevice                partition=C:
systemroot              \Windows
resumeobject            {4a713fa3-ef2f-11ee-b80c-833d98dc321f}
nx                      OptIn
bootmenupolicy          Standard

C:\windows\system32>
    but here is what the uefi shows now:
    Imgur: The magic of the Internet

    Could it be due to the double efi directory on C: and S:?
      My Computer
    Quote Quote

 

  Related Discussions
As the title says, I've been recently experiencing different kinds of BSoD (irql_not_less_or_equal, Critical_structure_corruption, etc.) while doing all kinds of things, from gaming to just browsing the web. I've been trying to fix it using google...
I bought an Inateck USB 3.0 hard drive enclosure to use with a SATA hard drive as a backup. I used it to put system image backups of my main C drive on (using Windows Backup and Restore, as well as Macrium Reflect). During one backup session with...
Hello, my PC (laptop, win10, about 3 years old) started to fall to BSOD quite often about month ago. It never did that before. The crashes happen mostly while doing some office work while having both Word and Excel 2016 open and also google...
BSOD at random(?) moments..
in BSOD Crashes and Debugging

Dear forum-reader, Recently I'm having quite often BSOD's.. Most of them are FAULTY_HARDWARE_CORRUPTED_PAGE, MEMORY_MANAGEMENT, CRITICAL_STRUCTURE_CORRUPTION or IRQL_NOT_LESS_OR_EQUAL.. I've already run memtest86+, from which I came to the...
Hi guys, so I've not experienced a BSOD in quite a while but yesterday I got a BAD_POOL_CALLER (while browsing the internet) and today I got a BAD_POOL_HEADER (while playing the good old Stronghold Crusader HD). I've got the necessary information...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

 © Designer Media Ltd
All times are GMT -5. The time now is 10:32.
Find Us




Windows 10 Forums