Alex Ruben
How To Resolve 0x135 BSOD Error on Windows 11
Encountering the blue screen with error code 0x135 is kind of annoying, especially since it pops up unexpectedly and messes with your work. It’s often caused by memory problems, driver conflicts, or corrupted system files. The good part? Most of these issues can be tackled without a complete Windows reinstall, and this guide walks through some solid steps to get you back on track. If you’re tired of guessing, these methods can help pinpoint the culprit, fix the problem, and hopefully stop those random crashes from happening again.
How to Fix the 0x135 BSOD Error in Windows 11
Boot into Safe Mode — Because starting minimal often reveals the culprit
This is where most troubleshooting begins — Safe Mode loads only essential drivers, avoiding conflicts that cause the crash. To get there:
- Hold down the Shift key and click Restart from the power menu in Start.
- After the system reboots, pick Troubleshoot > Advanced options > Startup Settings.
- Click Restart. When it comes back up, press 4 or 5 to select regular or minimal Safe Mode (with networking if needed).
This can be a pain, but if you manage to get into Safe Mode, you’re in a good spot for the next fixes. Sometimes, Windows makes this more complicated than it needs to, and on some setups, it refuses to boot into Safe Mode easily — so patience is key here.
Run System File Checker (SFC) — Because corrupt system files could be the sneaky cause
Ever see those mysterious system errors? SFC scans your Windows files and repairs what’s broken. When you’re in Safe Mode:
- Search for cmd, right-click Command Prompt, and choose Run as administrator.
- Type
sfc /scannowand hit Enter. - It might take a while, but it’ll check and fix corrupt system files automatically. On some machines, this might fail initially, especially if the system is really knackered, but don’t give up — try running it again after a reboot.
Use DISM to Repair the Windows Image — Because SFC isn’t always enough
If a lot of files are damaged or missing, SFC can struggle. DISM comes to the rescue by repairing your Windows image from the inside out:
- In the same Command Prompt window, run
dism /online /cleanup-image /restorehealthand wait for it to do its thing — could take some time. - It fetches healthy files *from Windows Update*, which is why a good internet connection helps. Sometimes it pauses, and that’s normal, so don’t stress.
Update or Reinstall Drivers — Because outdated or buggy drivers often cause kernel crashes
Driver conflicts are huge here — especially graphics, network, or storage controllers. Here’s what to do:
- Open Device Manager (right-click the Start menu).
- Check for devices with yellow warning signs, mainly under Display adapters or Network adapters.
- Right-click each suspicious device and pick Update driver > Search automatically for drivers.
- If Windows doesn’t find an update, head over to the device manufacturer’s site and grab the latest driver manually. Sometimes, uninstalling and reinstalling drivers helps if updates don’t work.
Run Windows Memory Diagnostic — Because flaky RAM might be causing instability
Memory issues can be sneaky, especially with BSODs. To test your RAM:
- Type Windows Memory Diagnostic in the Start menu, and open it.
- Select Restart now and check for problems.
- Let the test run — it’ll reboot and scan RAM modules. If errors show up, waste no time testing individual sticks or replacing faulty RAM.
Uninstall Recently Installed Software — Because new apps can sometimes clash with system stability
If the error started after installing certain apps or updates, removing them is worth a shot:
- Head to Settings > Apps > Installed apps.
- Sort by install date, look for anything suspicious or unfamiliar, and uninstall.
- Reboot and see if that helps. Sometimes, newer software conflicts with existing drivers or system files.
Rollback Recent Windows Updates — Because some updates can introduce bugs
Windows updates aren’t perfect; sometimes they cause more problems than they solve. To undo recent updates:
- Go to Settings > Windows Update > Update history.
- Click on Uninstall updates and pick the latest ones, especially if the BSOD popped up right after a patch.
Disable Third-Party Antivirus — Because overzealous security can block legitimate system functions
Antivirus tools sometimes interfere at a kernel level, causing instability. Try disabling yours temporarily:
- Usually, right-click the antivirus icon in the system tray and pick the disable option.
- Reboot and test. If the crashes stop, consider switching to a different solution or adjusting its settings.
Trim Down Startup Items — Because too many programs launching at startup can cause conflicts
Conflicting startup apps can introduce kernel errors. Manage them via Task Manager:
- Press Ctrl + Shift + Esc to open Task Manager.
- Navigate to the Startup tab, disable all unnecessary programs, then reboot.
Check Event Viewer for Clues — Because logs can pin down root causes
Looking through logs might reveal what exactly causes the crash:
- Open Event Viewer (search for it in Start).
- Explore Windows Logs > System, and filter for errors or critical events around the time of the crash.
- Note recurring errors or messages mentioning kernel crashes, driver issues, or memory problems.
Undo Overclocking — Because cranking your CPU or GPU too high can destabilize the system
Overclocked parts can push temperatures or voltages past safe limits:
- Enter your BIOS (usually by hitting Delete or F2 during boot).
- Reset to default settings. Be gradual if you want to overclock later, but for now, default is safest.
Update Your BIOS — Because outdated BIOS might cause compatibility issues with Windows 11
Make sure your motherboard firmware is current — manufacturers often fix bugs with updates:
- Head over to your motherboard or PC manufacturer’s website.
- Follow their instructions carefully; BIOS updates can be risky if not done properly.
- Typically, it involves downloading an update utility or flashing a USB stick with new firmware.
Perform a System Restore — Because a previous stable state might fix lingering issues
If you’ve created restore points before, restoring to an earlier version can undo problematic changes:
- Type Create a restore point and open it.
- Click System Restore and choose a date before the BSOD started happening.
- Follow the prompts and see if it stabilizes things.
Reset This PC — As a last resort, fresh start without losing personal files
If nothing else works, resetting Windows can fix deep-seated issues:
- Go to Settings > System > Recovery.
- Click on Reset this PC, then pick Keep my files. This reinstalls Windows but preserves your documents.
Extra Tips & Troubleshooting
Pro tip: regularly back up your data, especially before trying major fixes. It’s worth creating a restore point before messing with system files or BIOS, just in case. And if these steps seem overwhelming or don’t help, consulting a professional might be better — no shame in that. Sometimes, these crashes are hardware-related or more complex than they look.
Wrap-up
Most of the time, following these steps helps in resolving the 0x135 BSOD error. Each fix targets common causes like driver issues, memory errors, or corrupt system files. Fingers crossed this leads to a stable system. If one method works, that’s a win. Otherwise, keep digging — BSODs can be tricky, but persistence usually pays off. Hope this saves a few hours or at least points you in the right direction.
Summary
- Boot into Safe Mode and run system diagnostics.
- Fix corrupt files with SFC and DISM.
- Update drivers and check RAM stability.
- Remove problematic apps or undo recent updates.
- Adjust system overclocking, BIOS, or restore from previous points.
- If needed, reset Windows — but always backup first.