How to fix bootup issues from nt!_memset_spec_ermsb+66 & nt!KiFatalExceptionHandler+22?

Hi Simone,

Thanks for posting your question here. Those symbols are simply the kernel’s final stop when Windows encounters an unrecoverable error, while nt!_memset_spec_ermsb is a CPU‑optimized memory routine that typically crashes due to invalid or unstable memory access, not corrupted system files.

Because the system freezes before the Windows loading dots appear often showing a black screen or a stuck logo and only booting after a forced shutdown. Here what I recommend trying:

1. Update the BIOS to the latest version from Dell Ryzen systems are extremely sensitive to BIOS/AGESA changes, and many early‑boot freezes are resolved this way.
2. Disable Fast Startup
   • Control Panel → Power Options
   • Choose what the power buttons do
   • Disable Turn on fast startup Fast Startup can preserve unstable memory states between boots.
3. Run MemTest86 (not the Windows memory test)
   • Let it complete at least 4 passes
   • Even a single error indicates unstable or failing RAM
4. Update AMD chipset drivers directly from AMD’s website (not just Windows Update)
5. If BIOS allows it, disable any performance / overclocking options and keep memory settings at default.

Please refer to this links: Advanced troubleshooting for Windows startup issues / Troubleshooting Windows unexpected restarts and stop code errors

Let me know if you have questions, I'm here to help

Thanks,

Jobelle C.

The minidump symbols (nt!_memset_spec_ermsb and nt!KiFatalExceptionHandler) only indicate that Windows crashed in kernel mode, not the real root cause. For intermittent black screen / stuck logo at boot on Windows 11, the supported approach is to treat this as a stop‑code/boot issue and systematically troubleshoot drivers, system files, and startup.

Follow an end‑to‑end path like this:

1. Capture the actual stop code
   • When the system does reach a blue/black screen with text, note the stop code at the bottom (for example, PAGE_FAULT_IN_NONPAGED_AREA, MEMORY_MANAGEMENT, etc.).
   • That code is what identifies whether this is more likely a driver, disk, memory, or other hardware problem.
2. Use Windows Recovery Environment (WinRE) When the device fails to boot or hangs at the logo, force entry into WinRE:
   1. Power on the laptop.
   2. As soon as the Windows or OEM logo appears and it hangs, press and hold the power button until it shuts off.
   3. Repeat this power‑on/forced‑off cycle about three times. On the next boot, Windows should show Automatic Repair and then Advanced options.
   4. Select Advanced options.
3. Run startup/boot repair actions In WinRE, use the built‑in tools for boot issues:
   • Go to Troubleshoot > Advanced options.
   • First try Startup Repair. Let it complete and reboot.
   • If Startup Repair does not resolve it and the problem persists, return to Advanced options and use System Restore if any restore point exists (this rolls back system files and drivers but keeps personal data). Steps for System Restore are described for similar crash scenarios in the CrowdStrike KB and general stop‑code guidance.
4. Check for driver or system file corruption If the stop code or dump analysis points to a driver or system file:
   • Boot again into WinRE.
   • Open Command Prompt from Advanced options.
   • Run System File Checker in offline mode against the Windows installation, for example:

          SFC /Scannow /OffBootDir=C:\ /OffWinDir=C:\Windows
     

     (Adjust drive letters if Windows is on a different volume.)
   • If the dump later shows a specific third‑party boot driver (for example, a storage, antivirus, or GPU driver) as missing or corrupted, follow the documented pattern: identify what the driver does, and if it is non‑essential and has no dependencies, disable or remove it from offline registry or by uninstalling the associated software once Windows boots normally.
5. If the stop error occurs late in startup or persists
   • Configure the system to generate a kernel or complete memory dump (once it is bootable) so that the next crash can be analyzed more precisely. The referenced guidance explains that a good dump is key to finding the root cause when crashes continue late in startup.
6. Consider hardware causes The general stop‑code guidance notes that unexpected restarts and stop errors are often caused by:
   • Hardware devices
   • Their drivers
   • Other software If the stop code you eventually see is memory‑related (for example, MEMORY_MANAGEMENT), run the built‑in memory diagnostic from WinRE or from Windows when it is bootable. If it is storage‑related, check the disk from WinRE Command Prompt using chkdsk.

If none of the above resolves the intermittent boot hangs and crashes, collect the stop code and a fresh memory dump and then escalate through support channels with that data, since the kernel‑level symbols alone (nt!_memset_spec_ermsb, nt!KiFatalExceptionHandler) are not sufficient to identify a specific fix.

References:

• Troubleshooting Windows unexpected restarts and stop code errors
• Advanced troubleshooting for Windows startup issues