BSOD - 0x1e into 0xc0000098

Question

BSOD - 0x1e into 0xc0000098

Luis Lopez Lazaro 0

Dear Support Team,

After shutting down the PC yesterday for a Windows update, PC will not boot and I am stuck in an endless 01xe into 0xc0000098 loop.

Repairing Windows from a USB file is not working either. I have already run sfc /scannow and memory run checks.

I can provide a dmp log to help with the diagnosis for easier assistance.

Could I get some help? Much appreciated.

0 comments

2 answers

Your answer

Answer 1

DaveM121 888.7K Independent Advisor

1

If you are able to access the dump log, please upload that to any cloud service like OneDrive and provide a share link here so I can analyze that for you,

If you are unable to access Windows, how are you able to access the log.

2

Are you able to access the recovery environment using these steps without using the bootable Windows USB?

Start your PC, just as Windows attempts to load (spinning dots), press and hold Power Button for 5 - 10 seconds to perform a Hard Shut Down

Do this twice

On the third start Windows will boot into the Recovery Environment and from there you can access System Repair, Safe Mode, Command Prompt... etc.

Luis Lopez Lazaro 0 Reputation points

2026-06-11T12:02:52.49+00:00

Dear Dave,

Thank you for your promt reply. I am able to boot Windows through Safe Mode (F8 --> F5) after the error screen appears. The Minidump logs can be found here:

https://drive.google.com/drive/folders/16u4r1jPmaKBl2M7fRo6Dyd6u1tXKJWIA?usp=drive_link

I am able to access the Recovery Environment (hence why I can boot in Safe Mode), but I have been unable to Repair Windows from these options.

Is this enough or is additional information required? Thank you!
DaveM121 888.7K Reputation points Independent Advisor

2026-06-11T12:08:29.65+00:00

Hi Luis, your minidump files indicate generic RAM corruption and the Graphics drivers as the cause of the system crashes.

If you are able to access Safe Mode, right click your Start Button and open Device Manager.

Expand the Display Adapters section, then right click and delete the graphics drivers.
Restart your PC to test if Windows will boot up normally.
Luis Lopez Lazaro 0 Reputation points

2026-06-11T13:31:00.1033333+00:00

Hello Dave,

I have tried removing the Graphics drivers but so far the error keeps showing up. I have uploaded the 2 most recent logs to the link provided above.

Hope this helps narrow it down.

Thank you.
DaveM121 888.7K Reputation points Independent Advisor

2026-06-11T13:42:56.1333333+00:00

Those new minidump files just indicate generic errors, nothing specific.

In the Recovery Environment, have you tried uninstalling the latest update and also tried performing a System Restore to a previous date before the problem started.
Luis Lopez Lazaro 0 Reputation points

2026-06-11T16:42:46.5966667+00:00

On the Recovery screen choosing the option to restore while keeping files triggers an error.

The troubleshooter for Windows Update does also not launch, so Restoring does not look like an option.

After many back and forths I decided to perform a clean install from a USB. This, however, was an adventure.
After 100% install, the reboot sent the PC into a BIOS boot loop, failing to start from either the USB, nor from the new, clean Windows install.
Thus, the MoBo settings came into question. Secure Mode could not be truly Disabled, it went back on after each restart. Keys couldn't be truly reset either.

Looked like the Windows update corrupted the BIOS files in some way, thus leading to the cascade of errors.

After downgrading the BIOS to an older version, Windows was able to boot again and finish the install. I am currenly finalizing the installation, which hopefully will resume without issues, thus closing the issue.

The BIOS in question was the F37a for the Z690 GamingX DDR4.
DaveM121 888.7K Reputation points Independent Advisor

2026-06-11T16:50:06.0766667+00:00

Thank you for that information, that was a lot of work, is your system now stable after performing that process?
Luis Lopez Lazaro 0 Reputation points

2026-06-11T17:10:25.75+00:00

Hi Dave,

Yes, that was some work. So far the system seems to run without issues, downloading the expected updates and drivers. The usual at this point. If issues start to arise I will post them.

I do not fully understand, however, why the system was able to run in Safe Mode if the BIOS had corrupted files. Sending it into a meltdown did enable me (i.e. the AI alonside me) to identify a solution.

If you are interested in more information, I will happily provide it.

Thank you for your assistance.
DaveM121 888.7K Reputation points Independent Advisor

2026-06-11T17:28:52.4566667+00:00

That is great news, I am glad your system is now stable, great troubleshooting.

Answer 2

Follow these steps to troubleshoot the boot loop and stop errors:

Run Startup Repair from Advanced Boot Options
1. Power on the PC and repeatedly press F8 before the Windows logo appears.
2. On the Advanced Boot Options screen, select Repair your computer.
3. Choose the keyboard layout and click Next.
4. On System Recovery Options, select Startup Repair and follow the on-screen instructions.
If F8/Repair isn’t available, use Windows installation media
1. Boot from the Windows 11 USB installation media.
2. On the first setup screen, choose language and keyboard, then click Next.
3. Select Repair your computer (do not select Install).
4. Go to Troubleshoot → Advanced options → Startup Repair and let it complete.
If the error is related to a dual‑boot or missing boot entry If the system previously had multiple Windows installations and one no longer appears or the BCD is damaged:
1. Boot to a command prompt from the Windows installation media (Shift+F10 on the setup screen, or Troubleshoot → Advanced options → Command Prompt).
2. Identify the Windows partition using diskpart and list volume.
3. Run bcdboot X:\Windows (replace X: with the correct drive letter) to rebuild/add the boot entry.
4. Reboot and check if Windows now starts.
If the stop error is 0x0000007B (INACCESSIBLE_BOOT_DEVICE)
1. Use the same F8/Advanced Boot Options path as above.
2. Choose Repair your computer → Startup Repair.
3. If needed, repeat Startup Repair more than once, as it may fix different issues on each pass.
If the stop error is 0x0000006B (PROCESS1_INITIALIZATION_FAILED) on Windows 7/Server 2008 R2 (applies if this is an older system or secondary OS):
1. Boot from Windows installation media.
2. Open Repair your computer → Command Prompt.
3. Navigate to %SystemRoot%\System32\CodeIntegrity and delete Bootcat.cache.
4. Reboot and test.
If none of the above resolves the issue
1. Ensure all Windows updates and device drivers (especially storage, chipset, and firmware/BIOS) are current once the system can boot.
2. If the system was recently updated and started failing immediately afterward, consider re‑imaging or restoring from a known good backup if available.

The dump file can then be analyzed with a kernel debugger (WinDBG) to confirm whether the issue is storage/boot configuration, driver, or firmware related.

References:

Share via

BSOD - 0x1e into 0xc0000098

2 answers

Your answer