• Stop Code 0x1E KMODE_EXCEPTION_NOT_HANDLED and paving your ESP

    From Paul@nospam@needed.invalid to alt.comp.os.windows-11,alt.comp.os.windows-10 on Wed Jun 24 04:07:44 2026
    From Newsgroup: alt.comp.os.windows-11

    I ran into a strange error on a Win10 install (22H2).

    Upon trying to boot it, it stopped, recorded the Stop Code error
    and made a mini-dump file for later.

    I worked on this for a while, with no progress. Every second
    boot would crash.

    I was using the F8 Popup Boot menu, when I noticed there
    were two Windows Boot Manager entries. And then it occurred to me,
    I'll be on the alternate entry, on the boot attempt after the
    crash run, and making mods to the entry that works, won't be
    helping the entry that is damaged.

    An attempt to Repair Install the OS, got all the way down to the
    "restart", and it popped (presumably when it was trying to edit
    a BCD, and the edit failed miserably). I was not going to get
    a fix that way. The C: had also been through a DISM and SFC,
    that didn't help.

    So the vector looked like "a problem with ESP partition". I'd
    tried my hand at editing the BCD, but I was getting strange
    behaviors there as well.

    Time to pave the damn partition (ESP 100MB) and be done with it.

    *******

    Using your installer DVD, you can select Troubleshooting and the
    Command Prompt option there.

    diskpart.exe
    select disk 0
    select partition 1
    assign letter=K # K: is the ESP ["EFI system partition (100MB)"]
    exit # Assigning letter K: helps us manipulate it.

    format K: /fs:fat32 /q # the /q is for Quick format, boot materials... wiped
    # (for dual booters, you would need your YannBuntu Boot Repair DVD next)
    bcdboot c:\Windows /s K: /f uefi # Repopulates K:\EFI\Microsoft\Boot mainly,
    # That's the important function carried out by /f

    After that treatment, and a reboot, the OS came back up and was fine.
    Repeated boots, showed no problems.

    You don't have to give up, if your Repair Install attempt does not work.

    As for the root cause, I have no idea what left it in that state.

    Presumably, Microsoft has some "lever" it uses, to override the BCD
    when doing OS installations, but I've never been able to see any
    visual sign of that in the BCD itself.

    Paul


    --- Synchronet 3.22a-Linux NewsLink 1.2