Intermitent Boot Up Failure

Page 1 of 2 12 LastLast

  1. Posts : 28
    Windows 10
       #1

    Intermitent Boot Up Failure


    I have intermittent boot up failures happening. Each time I fix it, it is a matter of days and then it happens again. This time all it took to "fix" it was changing the boot order in my BIOS settings. I'm very confused by what's happening.

    It's Windows 10, 1909 OS build 18363.836. 32 Gb RAM with 2 Tb NvME storage.
    Storage is Samsung SSD 970 EVO and the software for it shows no issues.
    The system was cloned from a hard drive to the SSD and over time was re-organized so it now has four partitions as follows.
    Intermitent Boot Up Failure-image.png
    The fourth partition is a Microsoft Reserved partition that is 1 Gb in size - Windows does not show it.
    Diskpart - list disk
    Intermitent Boot Up Failure-image.png
    Diskpart - list part
    Intermitent Boot Up Failure-image.png
    Diskpart - list vol
    Intermitent Boot Up Failure-image.png
    SAMSUNG Magician
    Intermitent Boot Up Failure-image.png

    MiniTool Partition Wizard
    Intermitent Boot Up Failure-image.png

    When the system fails to boot I can spend a day or an hour to get it running again. This morning it wouldn't boot, gives me that BSOD and recovery attempts fail. While in BIOS I noticed that my NvME is now showing up twice in it. So I switched the order of the two and the system booted. That is how I am here now!

    I'm trying to find someone that can guide me through correcting this as I've obviously done something in previous attempts to fix it that now has windows confused about boot. I don't know enough about it myself to figure out where I've gone wrong. I know that there is now multiple \EFI\... folders on different partitions. Which is windows using, which can I delete etc...

    I also have issues making recovery disk and using USB recovery to fix the bootup. I managed to fix it once with a windows media install startup repair. But this morning even that wouldn't fix it.

    Well, another update was just applied so I'll reboot now and see if I get back online! Let me know what you need to know to help me sort this out. Thanks for your help in advance.
    Last edited by kwgagel; 1 Week Ago at 11:25. Reason: Added MiniTool Partition Wizard Screen Shot
      My Computer


  2. Posts : 269
    Windows 10
       #2

    kwgagel said:
    The fourth partition is a Microsoft Reserved partition that is 1 Gb in size - Windows does not show it.
    I don´t know is this is related to your problems, but MSR is too big, should be 16 MB. How did you get it?
      My Computer


  3. Posts : 28
    Windows 10
    Thread Starter
       #3

    Anibor said:
    I don´t know is this is related to your problems, but MSR is too big, should be 16 MB. How did you get it?
    I made it manually using MiniTool Partition Wizard. It's 1Gb but it's full now.
    Intermitent Boot Up Failure-image.png

    I should also say that I added it after this problem started, my thinking was this might be a way to help windows. I also added the recovery partition manually and positioned them according to MS docs.

    Interesting, Macrium Reflect tells me a different story about the MSR partition.
    Intermitent Boot Up Failure-image.png
    Last edited by kwgagel; 1 Week Ago at 12:58.
      My Computer


  4. Posts : 269
    Windows 10
       #4

    The MSR partition is normally created automatically when a disk is initialized as GPT, or during a clean install. It´s not necessary to boot, neither to help Windows, and it´s not an NTFS partition, as appears in the Macrium image.

    It seems that your installation is corrupt. I´d back up the personal information and do a clean install. In case you decide to follow that route, there are good tutorials in this forum that can assist you. The existing partitions should be deleted at the beginning of the process, Windows creates the new partitions automatically.
      My Computer


  5. Posts : 32,373
    windows 10 professional version 1607 build 14393.969 64 bit
       #5

    Run each V2 and DM and upload results directly into this thread:
    BSOD - Posting Instructions
      My Computer


  6. Posts : 28
    Windows 10
    Thread Starter
       #6

    zbook said:
    Run each V2 and DM and upload results directly into this thread:
    BSOD - Posting Instructions
    Both have been run and the results are located here:
    Dropbox - LogFiles - Simplify your life
      My Computer



  7. Posts : 32,373
    windows 10 professional version 1607 build 14393.969 64 bit
       #7

    The logs displayed problems with the drive file system including corruption of the Master File Table (MFT).

    For all steps / tests please make sure images are posted into the thread:

    Take Screenshot in Windows 10
    https://support.microsoft.com/en-gb/...re-screenshots
    How to Upload and Post Screenshots and Files at Ten Forums


    1) Open administrative command prompt and type or copy and paste:
    2) sfc /scannow
    3) dism /online /cleanup-image /scanhealth
    4) dism /online /cleanup-image /restorehealth
    5) sfc /scannow
    6) wmic recoveros set autoreboot = false
    7) wmic recoveros set DebugInfoType = 7
    8) wmic recoveros get autoreboot
    9) wmic recoveros get DebugInfoType
    10) bcdedit /enum {badmemory}

    11) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

    Use this link as needed when posting results:
    How to Change Post Editor to Source or WYSIWYG Mode at TenForums.com


    12) Make sure that there is no over clocking while troubleshooting

    13) The computer is using a beta BIOS. Unless there is a specific indication please rollback to the most up to date non-beta BIOS:
    BIOS Version/Date American Megatrends Inc. F15a, 11/28/2019

    F15a > F14
    Z370 AORUS Gaming 5 (rev. 1.0) | Motherboard - GIGABYTE U.S.A.

    14) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings

    a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery window into the thread

    b) > on the advanced tab under performance > click on settings > on the performance options window > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory window into the thread

    15) Run HD Tune (free version) (all drives)
    HD Tune website
    Post images into the thread for results on these tabs:
    a) Health
    b) Benchmark
    c) Full error scan

    16) Run Sea Tools for Windows
    long generic test
    Post an image of the test result into the thread
    SeaTools for Windows |
    Seagate

    How to use SeaTools for Windows | Seagate Support US

    17) Open administrative command prompt and type or copy and paste:
    chkdsk /r /v
    This may take hours to run so plan to run overnight.
    Run on all drives using the syntax: chkdsk /r /v C: or chkdsk /r /v D: changing the drive letter to the applicable drive.

    C:\Windows\system32>chkdsk /r /v
    The type of the file system is NTFS.
    Cannot lock current drive.

    Chkdsk cannot run because the volume is in use by another
    process. Would you like to schedule this volume to be
    checked the next time the system restarts? (Y/N)

    Type: Y
    reboot


    18) Use the information in this link to find the chkdsk report in the event viewer.
    Copy and paste into notepad > save to desktop > post into the thread using one drive or drop box share link:
    Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials
    Read Chkdsk Log in Event Viewer in Windows 10


    19) These steps can be performed overnight:
    a) HD Tune full error scan
    b) Sea Tools for Windows long generic test
    c) Chkdsk /r /v
      My Computer


  8. Posts : 28
    Windows 10
    Thread Starter
       #8

    zbook said:
    The logs displayed problems with the drive file system including corruption of the Master File Table (MFT).
    Interesting...

    zbook said:
    ---snip---
    1) Open administrative command prompt and type or copy and paste:
    2) sfc /scannow
    3) dism /online /cleanup-image /scanhealth
    4) dism /online /cleanup-image /restorehealth
    5) sfc /scannow
    6) wmic recoveros set autoreboot = false
    7) wmic recoveros set DebugInfoType = 7
    8) wmic recoveros get autoreboot
    9) wmic recoveros get DebugInfoType
    10) bcdedit /enum {badmemory}
    Here are the results of 2 through 10:

    Microsoft Windows [Version 10.0.18363.836]
    (c) 2019 Microsoft Corporation. All rights reserved.

    C:\windows\system32>sfc /scannow

    Beginning system scan. This process will take some time.

    Beginning verification phase of system scan.
    Verification 100% complete.

    Windows Resource Protection found corrupt files and successfully repaired them.
    For online repairs, details are included in the CBS log file located at
    windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
    repairs, details are included in the log file provided by the /OFFLOGFILE flag.

    C:\windows\system32>dism /online /cleanup-image /scanhealth

    Deployment Image Servicing and Management tool
    Version: 10.0.18362.1

    Image Version: 10.0.18363.836

    [==========================100.0%==========================] The component store is repairable.
    The operation completed successfully.

    C:\windows\system32>dism /online /cleanup-image /restorehealth

    Deployment Image Servicing and Management tool
    Version: 10.0.18362.1

    Image Version: 10.0.18363.836

    [==========================100.0%==========================] The restore operation completed successfully.
    The operation completed successfully.

    C:\windows\system32>sfc /scannow

    Beginning system scan. This process will take some time.

    Beginning verification phase of system scan.
    Verification 100% complete.

    Windows Resource Protection did not find any integrity violations.

    C:\windows\system32>wmic recoveros set autoreboot = false
    Updating property(s) of '\\SOUTHONE\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Home|C:\\windows|\\Device\\Harddisk0\\Partition3"'
    Property(s) update successful.

    C:\windows\system32>wmic recoveros set DebugInfoType = 7
    Updating property(s) of '\\SOUTHONE\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Home|C:\\windows|\\Device\\Harddisk0\\Partition3"'
    Property(s) update successful.

    C:\windows\system32>wmic recoveros get autoreboot
    AutoReboot
    FALSE


    C:\windows\system32>wmic recoveros get DebugInfoType
    DebugInfoType
    7


    C:\windows\system32>bcdedit /enum {badmemory}

    RAM Defects
    -----------
    identifier {badmemory}

    C:\windows\system32>


    zbook said:
    ---snip---

    12) Make sure that there is no over clocking while troubleshooting
    There is no over clocking and there never has been.

    zbook said:
    13) The computer is using a beta BIOS. Unless there is a specific indication please rollback to the most up to date non-beta BIOS:
    BIOS Version/Date American Megatrends Inc. F15a, 11/28/2019

    F15a > F14
    ---snip---
    The site says nothing about the BIOS being beta. None the less the next thing I'll do is step it back down to F14.
    zbook said:
    14) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings

    a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery window into the thread
    OK, here it is:
    Intermitent Boot Up Failure-image.png

    zbook said:
    b) > on the advanced tab under performance > click on settings > on the performance options window > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory window into the thread
    Here it is:
    Intermitent Boot Up Failure-image.png

    I'll work on the rest of these and post when completed.
    zbook said:
    15) Run HD Tune (free version) (all drives)
    HD Tune website
    Post images into the thread for results on these tabs:
    a) Health
    b) Benchmark
    c) Full error scan

    16) Run Sea Tools for Windows
    long generic test
    Post an image of the test result into the thread
    SeaTools for Windows |
    Seagate

    How to use SeaTools for Windows | Seagate Support US

    17) Open administrative command prompt and type or copy and paste:
    chkdsk /r /v
    This may take hours to run so plan to run overnight.
    Run on all drives using the syntax: chkdsk /r /v C: or chkdsk /r /v D: changing the drive letter to the applicable drive.

    C:\Windows\system32>chkdsk /r /v
    The type of the file system is NTFS.
    Cannot lock current drive.

    Chkdsk cannot run because the volume is in use by another
    process. Would you like to schedule this volume to be
    checked the next time the system restarts? (Y/N)

    Type: Y
    reboot


    18) Use the information in this link to find the chkdsk report in the event viewer.
    Copy and paste into notepad > save to desktop > post into the thread using one drive or drop box share link:
    Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials
    Read Chkdsk Log in Event Viewer in Windows 10


    19) These steps can be performed overnight:
    a) HD Tune full error scan
    b) Sea Tools for Windows long generic test
    c) Chkdsk /r /v
    Attached Thumbnails Attached Thumbnails Intermitent Boot Up Failure-image.png  
      My Computer


  9. Posts : 32,373
    windows 10 professional version 1607 build 14393.969 64 bit
       #9

    First scannow:
    Code:
    Windows Resource Protection found corrupt files and successfully repaired them.

    Second scannow:
    Code:
    Windows Resource Protection did not find any integrity violations.



    F15a 6.39 MB 2019/11/28
    Download
    Workaround beta BIOS to improve Kingston DDR4-2666 stability concern on some specific memory chip suppliers.
    Add NTFS format support for Q-Flash™
    Z370 AORUS Gaming 5 (rev. 1.0) | Motherboard - GIGABYTE U.S.A.
      My Computer


  10. Posts : 28
    Windows 10
    Thread Starter
       #10

    zbook said:
    First scannow:
    Code:
    Windows Resource Protection found corrupt files and successfully repaired them.

    Second scannow:
    Code:
    Windows Resource Protection did not find any integrity violations.



    F15a 6.39 MB 2019/11/28
    Download
    Workaround beta BIOS to improve Kingston DDR4-2666 stability concern on some specific memory chip suppliers.
    Add NTFS format support for Q-Flash™
    Z370 AORUS Gaming 5 (rev. 1.0) | Motherboard - GIGABYTE U.S.A.
    I see that now. Some times I think I might be going blind! I did see that SFC and WMIC found and corrected errors.

    Here are the HD Tune screen shots:
    Intermitent Boot Up Failure-image.png
    Intermitent Boot Up Failure-image.png
    Intermitent Boot Up Failure-image.png
    I grabbed the pro trial version and started with that then realized and grabbed the free version and completed with that one.

    Check Disk and BIOS down grade F14 to go now.
      My Computer


 

Related Threads
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 14:40.
Find Us




Windows 10 Forums