Fix Windows Stop Code 0x00000035: NO_MORE_IRP_STACK_LOCATIONS

Quick Answer

NO_MORE_IRP_STACK_LOCATIONS (0x00000035) is a Windows stop code. It means a driver tried to pass an I/O request to another driver, but the request had no stack location left for that driver. If the crash repeats, check what changed recently, especially drivers, device software, and hardware. Roll back or update a suspected driver, then use a crash dump to investigate if the cause remains unclear. The stop code alone does not identify a specific driver. Microsoft Learn

What the Error Means

Windows drivers pass input/output (I/O) requests through I/O request packets, or IRPs. Each driver that handles a request needs a location in the packet for its parameters. Bug check 0x35 occurs when an upper-level driver calls a lower-level driver and no location remains. Microsoft notes that the resulting write can also corrupt other memory. The first bug-check parameter is the address of the IRP; the remaining three parameters are reserved. Microsoft Learn

A recent driver or device change is a useful clue, but it is not proof of the cause. Investigate the timing and, when crashes recur, the crash dump before attributing the error to a particular product.

Before You Begin

• Save your work and back up important files before changing drivers or recovery settings.
• Note when the crash happens and any driver, security software, device, or Windows update installed shortly beforehand.
• Use an administrator account for driver rollback or removal.
• If Windows cannot start normally, use Safe Mode to perform the checks below. Microsoft recommends Safe Mode when repeated stop errors prevent a normal startup. Microsoft Support

Recommended Troubleshooting

1. Restart and observe. If the error happened once and does not return, record the code and continue using the PC. If it repeats, proceed with the steps below.
2. Disconnect recently added hardware. Shut down first, disconnect the new device, and restart. If the crashes stop, check the device and its compatible driver before reconnecting it.
3. Check Device Manager. Right-click Start and select Device Manager. Look for devices marked with an exclamation point and consider any device whose driver changed just before the crashes.
4. Roll back a recently updated driver when applicable. Right-click the device, select Properties > Driver > Roll Back Driver, give a reason, and restart if prompted. If the button is unavailable, there may be no previous driver available to restore.
5. Update a suspected driver if rollback is unsuitable or ineffective. Check Windows Update or obtain the driver that matches your Windows version from the device manufacturer’s official site. Restart when required.
6. Install available Windows updates and check whether the same stop code returns. Microsoft Support

If a driver change makes the device unusable, return to Device Manager and reinstall the appropriate driver from the manufacturer. If the problem began recently and other steps fail, consider a Windows restore point created before the crashes. Microsoft Support

If Windows Will Not Start Normally

From the Windows Recovery Environment, choose Troubleshoot > Advanced options > Startup Settings > Restart, then select Safe Mode. Use it to investigate or reverse a recent change. If this is a managed work device, coordinate driver or security software removal with your IT administrator. support.microsoft.com

Advanced Troubleshooting: Examine the Crash Dump

When the error recurs, a dump can provide more evidence than the stop code alone. Small memory dumps, when configured and successfully created, are stored in %SystemRoot%\Minidump. Other dump configurations commonly write %SystemRoot%\MEMORY.DMP. A small dump contains limited information, so its analysis may not establish the root cause. Microsoft Learn

An IT professional can open the relevant dump in WinDbg and run:

!analyze -v

Review the bug-check details, involved drivers, and call stack alongside the machine’s recent changes. A driver named in the output is a lead to investigate, not automatic proof that its file caused the fault. If the dump is inconclusive, retain it and seek help from the device or driver vendor. Microsoft Learn

Do not enable Driver Verifier as a routine first step on a production PC. Microsoft says it can deliberately cause crashes and should be used on computers intended for testing and debugging. Microsoft Learn

How to Verify the Fix

Restart after the driver or software change. Use the PC through the activity that previously triggered the crash and check whether 0x00000035 returns. If it does, reverse the ineffective change where appropriate, record the crash time, and examine the newest dump. Several crashes may need comparison before a cause becomes clear.

Frequently Asked Questions

Does 0x00000035 identify the faulty driver?

No. It describes how the I/O request failed. A crash dump and the history of recent changes can help identify what to investigate. Microsoft Learn

Is this the same as running out of RAM?

No. “Stack locations” here refers to positions in an I/O request packet used by drivers. The stop-code name does not mean the computer has exhausted its physical RAM. Microsoft Learn

Why is there no file in the Minidump folder?

Windows may not have been configured to create a small dump, or a dump may not have been written for that crash. Check the system’s dump configuration before relying on that folder for evidence. Microsoft Learn

Should I remove every recently installed driver?

No. Change one suspected component at a time and test the result. This helps you identify which change matters and makes recovery easier.

What if the crash continues after updating drivers?

Preserve the newest dump and investigate the driver stack with WinDbg or the relevant vendor’s support team. Avoid treating a generic update or repair command as a confirmed fix for this specific bug check.

Conclusion

For a repeated 0x00000035 crash, start with recent device and driver changes. Roll back or update a plausible suspect, verify the result, and inspect a crash dump if the error persists. The code identifies the failure condition; the affected driver still requires investigation.

Sources

• Microsoft Learn, Bug Check 0x35: NO_MORE_IRP_STACK_LOCATIONS. Microsoft Learn
• Microsoft Support, Troubleshooting Windows unexpected restarts and stop code errors. Microsoft Support
• Microsoft Support, Update drivers through Device Manager in Windows. Microsoft Support
• Microsoft Learn, Stop code error or bug check troubleshooting. Microsoft Learn
• Microsoft Learn, Small Memory Dump and Open a dump file with WinDbg. Microsoft Learn
• Microsoft Learn, How to Use Driver Verifier for Driver Testing. Microsoft Learn