How to Fix NO MORE IRP STACK LOCATIONS (0X00000035) BSOD on Windows 10 & 11

by

How to Fix NO MORE IRP STACK LOCATIONS (0X00000035) BSOD on Windows 10 & 11

The NO MORE IRP STACK LOCATIONS (0x00000035) Blue Screen of Death (BSOD) is a frustrating error that can occur in Windows 10 and 11, often leading to system crashes. This error typically happens when the system runs out of stack locations for processing Input/Output Request Packets (IRPs), which are used by the operating system to communicate with hardware devices. If you’re experiencing this issue, don’t worrythere are several troubleshooting steps you can take to resolve it.

What Causes the NO MORE IRP STACK LOCATIONS (0x00000035) Error?

The error usually occurs due to:

  • Corrupt system files or drivers: Damaged or outdated drivers, especially those related to storage or hardware devices, can trigger this BSOD.
  • Hardware issues

    Faulty RAM, hard drives, or other hardware components may cause instability in the system.

  • Malware or virus infections: Some malicious software can interfere with system processes and corrupt critical files.
  • Overloaded system resources: Running too many applications or background processes can exhaust IRP stack locations.
  • Windows updates or driver conflicts: Recent updates or incompatible drivers may introduce instability.

How to Fix NO MORE IRP STACK LOCATIONS (0x00000035) BSOD

### **Method 1: Run System File Checker (SFC) and DISM**

A corrupted system file can trigger this error. Use the following commands to repair missing or damaged files:

  • Press Win + X and select Terminal (Admin) or open Command Prompt as Administrator.
  • Run the following command to check for system file corruption: 
    sfc /scannow
  • Wait for the scan to complete, then restart your PC.
  • If issues persist, run DISM (Deployment Image Servicing and Management) with: 
    DISM /Online /Cleanup-Image /RestoreHealth
  • Restart your computer after the process finishes.

### **Method 2: Run CHKDSK to Check for Disk Errors**

If the error is related to disk corruption, use CHKDSK to scan and repair bad sectors:

  • Open Command Prompt as Administrator.
  • Run: 
    chkdsk C: /f /r

    (Replace C: with your system drive letter if needed.)

  • If prompted, press Y to confirm and restart your PC.
  • The scan will run on the next bootwait for it to complete before proceeding.

### **Method 3: Update or Reinstall Problematic Drivers**

Outdated or faulty drivers (especially storage or chipset drivers) can cause this error. Heres how to update them:

  • Press Win + X and select Device Manager.
  • Expand Disk drives, Storage controllers, or other relevant categories.
  • Right-click each device, select Update driver, then choose Search automatically for drivers.
  • If updating doesnt work, try rolling back the driver (right-click Properties Driver Roll Back Driver).
  • Alternatively, download the latest driver from the manufacturers website.

### **Method 4: Check for Malware and Run a Full Scan**

Malware can corrupt system files. Use Windows Defender or a trusted antivirus to scan your system:

  • Open Windows Security (search in the Start menu).
  • Go to Virus & threat protection Quick scan and run a full scan.
  • Follow any additional cleanup steps if threats are detected.

### **Method 5: Disable Overloaded Services or Startup Programs**

Too many background processes can exhaust IRP stack locations. Optimize startup:

  • Press Ctrl + Shift + Esc to open Task Manager.
  • Go to the Startup tab and disable unnecessary programs.
  • Check for resource-heavy applications in the Processes tab and close them if needed.

### **Method 6: Test Hardware for Issues**

Faulty RAM or a failing hard drive can cause this error. Run these tests:

  • RAM Test: Use Windows Memory Diagnostic: 
    mdsched.exe
  • Hard Drive Health Check: Open File Explorer, right-click your drive Properties Tools Error checking. Run the scan.
  • If hardware issues are detected, replace faulty components if necessary.

### **Method 7: Perform a Clean Boot to Identify Conflicts**

A clean boot helps determine if third-party software is causing the issue:

  • Press Win + R, type msconfig, and press Enter.
  • Go to the Services tab, check Hide all Microsoft services, then click Disable all.
  • Go to the Startup tab, click Open Task Manager, and disable all startup items.
  • Restart your PC. If the error doesnt occur, re-enable services/apps one by one to identify the culprit.

### **Method 8: Restore Windows to a Previous State (System Restore)**

If the issue started after recent updates or changes, restore your system:

  • Search for Create a restore point in the Start menu and click System Protection System Restore.
  • Follow the prompts to choose a restore point before the error occurred.
  • Confirm and complete the processyour PC will reboot.

### **Method 9: Check for Windows Updates**

Ensure your system is up to date:

  • Go to Settings Update & Security Windows Update.
  • Click Check for updates and install any pending updates.
  • Restart your PC after installation.

### **Method 10: Reinstall or Replace Problematic Hardware**

If the error persists, a failing hardware component (like a hard drive or RAM) may be the cause. Consider:

FAQ About NO MORE IRP STACK LOCATIONS (0x00000035)

  • Is this error dangerous?

    No, the BSOD itself doesnt damage your data, but it indicates a serious issue that should be fixed to prevent further crashes.

  • Can I recover lost data after this error?

    Yes, if the crash was sudden, your files are usually safe. However, frequent BSODs may risk corruptionback up important data regularly.

  • Why does this happen randomly?

    Random occurrences often point to hardware instability (e.g., overheating, failing RAM) or driver conflicts. Run diagnostics to pinpoint the cause.

  • Should I reinstall Windows if nothing works?

    Reinstalling is a last resort. Try the steps above firstmost issues can be resolved without a clean install.

Final Thoughts

The NO MORE IRP STACK LOCATIONS (0x00000035) BSOD is usually fixable with the right troubleshooting. Start with SFC and DISM, then move to driver updates, malware scans, and hardware checks. If the problem persists, consider professional diagnostics or hardware replacement. By following these steps, you should be able to stabilize your system and prevent future crashes.

If youve tried all methods and still face issues, share details in the commentswere here to help!

Last Updated: December 13, 2025

Tested on: Windows 10 (22H2) & Windows 11 (23H2)

Leave a Comment