Seeing the blue Automatic Repair screen on Windows can be stressful—especially when it won’t boot into Safe Mode and resetting the PC fails. One of the most common stop codes users see is “Stop Code: MEMORY_MANAGEMENT” or “Stop Code: PAGE_FAULT_IN_NONPAGED_AREA”, but the one you’re facing, “Stop Code: NOT LESS OR EQUAL,” usually points to RAM problems, corrupted system files, or faulty drivers.
Before you panic or take it to a repair shop, here are the most effective steps you can try at home to fix the issue.
1. What the “NOT LESS OR EQUAL” Stop Code Really Means
This error usually appears when Windows tries to access memory it shouldn’t.
The most common causes include:
- Faulty or failing RAM
- Corrupted system files (from shutdown crash, update failure, etc.)
- Bad drivers
- Disk errors
- Hardware conflicts
If the issue is RAM-related, Windows often fails to load Safe Mode or perform Reset—exactly what you’re experiencing.
2. Start With the Easiest Fix: Power Cycle the PC
Sometimes a simple full power drain fixes memory issues.
Steps:
- Shut down the PC.
- Unplug the power cable.
- Hold the power button for 15 seconds.
- Plug it back in and try booting again.
This clears stuck memory and helps in many “Automatic Repair Loop” cases.
3. Reseat or Swap Your RAM (If You Can Open the PC)
If you’re comfortable opening your desktop/laptop:
- Power off the PC.
- Remove the RAM sticks.
- Clean the gold contacts gently with a dry microfiber cloth.
- Reinsert them firmly.
- If you have two sticks, try booting with one stick at a time.
Why this works:
- RAM may have dust interference.
- A single faulty stick can cause this error.
- Reseating resets memory communication.
If the PC boots successfully with only one stick, you found the faulty one.
4. Run Memory Diagnostics from the Recovery Screen
If Windows won’t boot but the Recovery menu loads:
- Go to Troubleshoot
- Advanced Options
- Command Prompt
- Enter:
mdsched.exe
Restart and let it run.
If it reports memory errors → RAM is the problem.
5. Run System File Repair Commands
You mentioned using Command Prompt, but make sure you run all three critical repair commands in this order:
Step 1 — Check Disk
chkdsk c: /r /f
Step 2 — Restore system health
dism /online /cleanup-image /restorehealth
Step 3 — Repair corrupted system files
sfc /scannow
These can fix Automatic Repair Loop issues caused by:
- Corrupted Windows files
- Damaged boot configurations
- Disk errors
6. Rebuild the Boot Loader (If Windows Boot Files Are Damaged)
At Command Prompt:
bootrec /fixmbr
bootrec /fixboot
bootrec /scanos
bootrec /rebuildbcd
Restart the system after this.
This helps when Windows can’t locate essential boot files.
7. Check the SSD/HDD Health
If your drive is failing, Windows often enters Automatic Repair and throws memory-related stop codes.
Run:
wmic diskdrive get status
If you see “Pred Fail” or anything other than “OK,” the disk may be dying.
8. If Nothing Works, It Might Be a Hardware Failure
Based on your symptoms:
✔ Automatic Repair Loop
✔ Reset PC fails
✔ Safe Mode won’t load
✔ “Not Less or Equal” stop code
✔ RAM suspected
There’s a strong chance this is a hardware issue (RAM or motherboard).
You likely need a repair shop if:
- Memory diagnostics show errors
- PC does not boot with multiple RAM sticks tested individually
- You get frequent BSOD loops even after repairs
- The motherboard fails to detect RAM properly
Final Advice: What You Should Do Next
Try all the software fixes first, especially DISM/SFC and boot repair.
If those don’t fix the issue and RAM testing shows problems, replacing the RAM is usually cheaper than a repair shop visit.
But if you’re unable to open the device or tests show consistent failures, taking it to a repair professional is the safest option.