Windows errors

Blue screen: IRQL_NOT_LESS_OR_EQUAL stop code

Windows crashes with IRQL_NOT_LESS_OR_EQUAL, which typically means a driver tried to access memory in an improper way. It's one of the most common driver-related blue screens.

Difficulty
Intermediate
Time
1–2 hours
DIY cost
$0
Pro cost
$80–$150

Symptoms

  • Blue screen specifically names IRQL_NOT_LESS_OR_EQUAL
  • Often mentions a specific driver file (like a .sys file) in the details
  • May happen during specific activities like gaming, sleep/wake, or using a particular device
  • PC restarts after the crash

Likely causes

  • CommonOutdated or corrupted device driverThis error is very frequently traced to a specific driver misbehaving, often network, graphics, or storage related.
  • CommonNewly installed hardware or driverA recent addition is a prime suspect if the crashes started right after installing something.
  • PossibleFaulty RAMMemory errors can trigger this stop code similarly to MEMORY_MANAGEMENT.
  • PossibleAntivirus or security software conflictSome security software drivers are known to cause this specific error.
  • Less commonCorrupted system filesLess common, but damaged core files can occasionally produce this error.

What to do

  1. Check the blue screen details or the crash dump for a specific driver file name (ending in .sys); this points directly to the responsible software.
  2. Open Device Manager and update the driver for the hardware category matching the named file (graphics, network, storage, etc.) from the manufacturer's website.
  3. If the crash started after installing new hardware or software, uninstall or roll back that specific item first.
  4. Temporarily disable or uninstall third-party antivirus software to test whether it's the cause, since certain security suites are known culprits for this error.
  5. Run Windows Memory Diagnostic to rule out faulty RAM as a contributing factor.
  6. Run 'sfc /scannow' in an administrator Command Prompt to check for corrupted system files.
  7. If crashes continue despite updated drivers, try a clean boot (search 'msconfig,' Services tab, hide Microsoft services, disable the rest) to isolate a conflicting background program.

Tools and parts

  • None beyond what's built into Windows

When to call a pro

If the crash dump names a driver you can't safely update or remove yourself, or crashes persist after these steps, a technician can analyze the dump file in more depth.

Safety

Generally low risk

Generally low risk for a careful person. Stop if anything looks different from what this guide describes.

Related guides

Operator provides AI-generated troubleshooting information. It can be wrong. For safety-critical, electrical, gas, structural, medical, automotive safety, or other high-risk problems, consult a qualified professional.