now all I get are BSOD's  

Page 6 of 18 FirstFirst ... 4567816 ... LastLast

  1. Posts : 7,603
    Windows 10 Home 20H2
       #51

    Please right-click on the Start button --> Windows PowerShell.
    Run the following command and post the output.

    Get-PhysicalDisk

    I wonder why the command does not work on some Windows.
      My Computer


  2. Posts : 115
    Windows 10 Pro Version 21H2 OS build 19044.1466
    Thread Starter
       #52

    I've just found these files dated 21-02-2021... I think these may help...

    bcdinfo.txt

    disklayout.txt

    SrtTrail.log

    SrtTrail.txt

    - - - Updated - - -
    @Matthew Wai I'm booting off a USB (WinPE) please read the post...
    now all I get are BSOD's Attached Files
      My Computer


  3. Posts : 7,603
    Windows 10 Home 20H2
       #53

    b1gt1m said:
    I'm booting off a USB (WinPE)
    @zbook, should I write a different version that works on WinPE?
      My Computer


  4. Posts : 5,879
    Windows 7 HP - Windows 10 Pro - Lubuntu
       #54

    topgundcp said:
    Based on what you post in #38
    Attachment 319995
    Your disk 0 is an MBR disk, Your disk 1 29GB USB is a GPT disk.
    Did you use the 29GB USB to fix the boot problem ??? If so, it will not work. You'd need to build the Macrium boot disk format as FAT32 and set to active then boot from it to fix the boot problem.
    In one of your BSOD screen, it looks for winload.efi which only for GPT disk, not MBR.

    To manually rebuild the BCD:

    Attachment 319996
    Your C drive is set to Active, meaning the BCD is stored there.
    To manually create a new BCD, just use bcdboot command.
    Boot up the WinPE then open the command prompt, type:
    bcdboot C:\windows /s C: /f BIOS

    The above command should fix the boot problem. If not then there's a problem during the upgrade with Windows system file.
    You'd need to boot up the Windows 10 installtion disk, select upgrade to install Windows which will preserve your programs/data etc...
    Almost everyone is running in circles.
    b1gt1m must has made some modifications to the partitions. How do you have a Fat32 partition on a Legacy-MBR drive?
    The first thing is to see the disk partitions with Disk Manager (C:\Windows\System32\diskmgmt.msc). If the Win PE doesn't have it, go to the C: drive and launch it.

    Only topgundcp has seen the problem and gave the solution, that wasn't implemented by b1gt1m
      My Computers


  5. Posts : 41,009
    windows 10 professional version 1607 build 14393.969 64 bit
       #55

    The BIOS displayed:
    UEFI
    IDE

    Diskpart displayed MBR drive with a FAT32 partition.


    These are trial and error steps:

    Post images of the command with results.

    1) Attempt to boot BIOS Legacy
    2) Attempt to boot BIOS UEFI with CSM
    3) Run: bcdboot C:\windows /s C: /f All
    a) repeat steps 1 and 2
      My Computer


  6. Posts : 41,009
    windows 10 professional version 1607 build 14393.969 64 bit
       #56

    Matthew Wai said:
    @zbook, should I write a different version that works on WinPE?
    Yes.
    What options are there in WinRE?
      My Computer


  7. Posts : 7,603
    Windows 10 Home 20H2
       #57

    zbook said:
    What options are there in WinRE?
    I ran the following commands in a Chinese version of Windows PE last month.

    Code:
    Microsoft Windows [版本 10.0.18362.30]
    (c) 2019 Microsoft Corporation. 著作權所有,並保留一切權利。
    
    X:\Users\Default>C:\Windows\System32\Reagentc /info /Target C:\Windows
    Windows Recovery Environment (Windows RE) and system reset configuration
    Information:
    
        Windows RE status:         Disabled
        Windows RE location:
        Boot Configuration Data (BCD) identifier: 00000000-0000-0000-0000-000000000000
        Recovery image location:
        Recovery image index:      0
        Custom image location:
        Custom image index:        0
    
    REAGENTC.EXE: Operation Successful.
    
    
    X:\Users\Default>C:\Windows\System32\Reagentc /SetREImage /path R:\Recovery /Target C:\Windows
    Directory set to: \\?\GLOBALROOT\device\harddisk0\partition4\Recovery
    
    REAGENTC.EXE: Operation Successful.
    
    
    X:\Users\Default>C:\Windows\System32\Reagentc /enable /Target C:\Windows
    Enables the local copy of the Windows Recovery Environment (Windows RE).
    
    This command can be used from the running operating system without additional
    parameters, or from the Windows Preinstallation Environment (Windows PE) using
    the optional /osguid parameter.
    
    REAGENTC.EXE /enable [/osguid <bcd_guid>] [/logpath <file_path>]
    
      /osguid <bcd_guid>    - Specifies the Boot Configuration Data (BCD) identifier of the
                              target Windows installation. The identifier can be determined
                              by running "bcdedit -enum -v".
    
      /logpath <file_path>  - Specifies the path of log file. If this argument is
                              not specified, the default path is Windows\Logs\
                              Reagent\Reagent.log.
    
      Example:
        REAGENTC.EXE /enable /logpath C:\Temp\Reagent.log
        REAGENTC.EXE /enable /osguid {00000000-0000-0000-0000-000000000000}
    
    
    
    X:\Users\Default>bcdedit -enum -v
    
    Windows 開機管理程式
    --------------------
    identifier              {9dea862c-5cdd-4e70-acc1-f32b344d4795}
    device                  partition=\Device\HarddiskVolume1
    path                    \EFI\Microsoft\Boot\bootmgfw.efi
    description             Windows Boot Manager
    locale                  en-US
    inherit                 {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
    default                 {562f507d-413a-11eb-bfdb-e0d55ecc65a3}
    resumeobject            {562f507c-413a-11eb-bfdb-e0d55ecc65a3}
    displayorder            {562f507d-413a-11eb-bfdb-e0d55ecc65a3}
    toolsdisplayorder       {b2721d73-1db4-4c62-bf78-c548a880142d}
    timeout                 0
    
    Windows 開機載入器
    -------------------
    identifier              {562f507d-413a-11eb-bfdb-e0d55ecc65a3}
    device                  partition=C:
    path                    \Windows\system32\winload.efi
    description             Windows 10
    locale                  en-US
    inherit                 {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
    recoverysequence        {562f507e-413a-11eb-bfdb-e0d55ecc65a3}
    displaymessageoverride  Recovery
    recoveryenabled         Yes
    isolatedcontext         Yes
    allowedinmemorysettings 0x15000075
    osdevice                partition=C:
    systemroot              \Windows
    resumeobject            {562f507c-413a-11eb-bfdb-e0d55ecc65a3}
    nx                      OptIn
    bootmenupolicy          Standard
    
    X:\Users\Default>C:\Windows\System32\Reagentc /enable /osguid {562f507d-413a-11eb-bfdb-e0d55ecc65a3}
    REAGENTC.EXE: Operation Successful.
    
    
    X:\Users\Default>C:\Windows\System32\Reagentc /info /Target C:\Windows
    Windows Recovery Environment (Windows RE) and system reset configuration
    Information:
    
        Windows RE status:         Enabled
        Windows RE location:       \\?\GLOBALROOT\device\harddisk0\partition4\Recovery\WindowsRE
        Boot Configuration Data (BCD) identifier: 1017b9fa-5a6c-11eb-9481-e0d55ecc65a3
        Recovery image location:
        Recovery image index:      0
        Custom image location:
        Custom image index:        0
    
    REAGENTC.EXE: Operation Successful.
    
    
    X:\Users\Default>
      My Computer


  8. Posts : 2,798
    Linux Mint 20.1 Win10Prox64
       #58

    Megahertz said:
    Almost everyone is running in circles.
    b1gt1m must has made some modifications to the partitions. How do you have a Fat32 partition on a Legacy-MBR drive?
    The first thing is to see the disk partitions with Disk Manager (C:\Windows\System32\diskmgmt.msc). If the Win PE doesn't have it, go to the C: drive and launch it.
    Yes I noticed the 451 MB Fat32 partition. However, it is irelevant to the problem, it is just a regular FAT32 partition with partition type id=OCnow all I get are BSOD's-2021-02-23_113027.jpg
    A typical UEFI Windows EFI System FAT32 partition would have partition type ID shown in the screenshot below
    now all I get are BSOD's-2021-02-23_112123.jpg
    @b1gt1m
    Your Windows disk is an MBR disk and on the BIOS screen you have UEFI enabled. Disable it then try to boot again.
      My Computer


  9. Posts : 115
    Windows 10 Pro Version 21H2 OS build 19044.1466
    Thread Starter
       #59

    Allo guys, sorry for the late reply, life got in the way - well I work at a hospital, I'm not gonna go into it, I was F***** Busy!! So, anyway, I had a brain storming session while dealing with other problems, jobs, etc... I decided that one of the easiest ways to help you guys, help me is to make a Bootable USB from off this site - (Win10XPE - Build Your Own Rescue Media ), which I have done and am now using! I'll try your last advice again and post the appropriate results. You guys are angels and no end of help!!!

    - - - Updated - - -

    OK so, I followed zbook's instructions ...

    1) Attempt to boot BIOS Legacy
    2) Attempt to boot BIOS UEFI with CSM
    3) Run: bcdboot C:\windows /s C: /f All
    a) repeat steps 1 and 2

    please see the posted results below. A note though, when I set the BIOS to AHCI and UEFI, it tried to boot when I selected the F8 key for Startup settings!? I selected a few different options, and for a second on each one, I saw the blue windows logo then back to BSOD... this must be a file error no?

    now all I get are BSOD's-152955999_902617817156115_2348957699634849726_n.jpg
    now all I get are BSOD's-153620642_478788069801430_7015164414744599807_n.jpg

    - - - Updated - - -

    HEY! I made no mods to my partitions by the way, except for what you guys told me to do...

    - - - Updated - - -

    I just ran DiskMgmt, I can now off this great USB! Results below...

    now all I get are BSOD's-diskmgmt.jpg
      My Computer


  10. Posts : 41,009
    windows 10 professional version 1607 build 14393.969 64 bit
       #60

    Please update the progress with post#44: Bootable Windows 10 iso 20H2



    Code:
    Root cause found: 
    ---------------------------
    Boot configuration is corrupt.
    
    Repair action: Partition table repair
    Result: Failed. Error code =  0x20
    Time taken = 1203 ms



    Code:
    The operating system couldn't be loaded because the NLS data is missing or contains errors.
    Error code:  0xc0000225
    
    
    The Boot Configuration Data file doesn't contain valid information for an operating system.
    Error code:  0xc0000098
      My Computer


 

  Related Discussions
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 03:37.
Find Us




Windows 10 Forums