Error 0x00000048 is the Windows stop code CANCEL_STATE_IN_COMPLETED_IRP. It means a device driver completed an I/O request packet (IRP), then the request was canceled afterward. The usual fix is to identify the driver or hardware change involved, roll it back or update it, and use a crash dump if the cause is not obvious. Start with the manual steps below; replacing hardware or editing the registry is not a reliable first response.
What error 0x00000048 means
Microsoft defines 0x00000048 as CANCEL_STATE_IN_COMPLETED_IRP. An I/O request packet is a kernel data structure that carries a request between Windows and a device driver. A driver is expected to complete that request once, with the cancel path coordinated correctly. This stop error occurs when a driver completes an IRP and later calls its cancel routine, or when two drivers access the same IRP improperly.
As an Amazon Associate I earn from qualifying purchases.
The blue screen may show four bug-check parameters and a What failed filename. Those details are more useful than the hexadecimal code by itself. Microsoft notes that the cancel-routine parameter can help identify the driver or driver stack responsible. A graphics, storage, network, audio, USB, printer, security, or other third-party driver can be involved, but the stop code alone does not identify a particular device.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Why the crash can repeat
Once a faulty driver is loaded, the same request and cancel sequence can recur whenever Windows performs the affected operation. For a gaming PC, that might coincide with starting a game, changing display modes, connecting a controller, loading an anti-cheat component, or resuming from sleep, but timing does not prove which component is at fault. A recent update, newly attached device, firmware change, or service installation is stronger evidence than the application that happened to be open.
#1 Best Overall
- STREAMLIMED AND INTUITIVE UI | Intelligent desktop | Personalize your experience for simpler efficiency | Powerful security built-in and enabled.
- JOIN YOUR BUSINESS OR SCHOOL DOMAIN for easy access to network files, servers, and printers.
- OEM IS TO BE INSTALLED ON A NEW PC WITH NO PRIOR VERSION of Windows installed and cannot be transferred to another machine.
- OEM DOES NOT PROVIDE PRODUCT SUPPORT | To acquire product with Microsoft support, obtain the full packaged “Retail” version.
Record the stop screen before changing anything
If Windows restarts quickly, use your phone to photograph the entire blue screen. Write down:
0x00000048and the textCANCEL_STATE_IN_COMPLETED_IRP.- Every filename shown after What failed, including its extension.
- All four bug-check parameters, in order, if they are displayed.
- The time of the crash, what the computer was doing, and anything installed or connected immediately beforehand.
Keep this record. A driver name can be truncated on the screen, and the parameters may disappear after a reboot. If you can boot normally, open Event Viewer and note entries at the same time before attempting repairs.
Undo the most recent change
Microsoft’s stop-error guidance starts with changes made just before the failures. Reversing a recent change is usually safer and more informative than replacing components at random.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Disconnect new hardware
- Shut down the PC completely.
- Remove a newly installed USB device, expansion card, docking station, external drive, printer, or other peripheral.
- Reconnect only the keyboard, mouse, display, and other equipment required to start Windows.
- Start the computer and repeat the activity that normally triggers the crash.
If the stop error disappears, reconnect devices one at a time and test between additions. The device that brings the crash back, or its driver, becomes the primary suspect. Do not open a powered desktop or remove an internal component unless you are comfortable with the manufacturer’s safety procedures and warranty conditions.
Roll back or remove a recent driver or service
In Device Manager, open the suspected device, choose Properties, and inspect the Driver tab. If Roll Back Driver is available, use it to return to the previous package. Otherwise choose Uninstall Device, select the option to remove the driver package only when you are certain you can reinstall it, and restart. For software that installed a kernel service, use Settings > Apps (Windows 11) or Apps & features (Windows 10) to uninstall the recently added application. Record the version before removal.
Do not delete random files from C:WindowsSystem32drivers. A filename on the blue screen can be a component shared by several products, and deleting it can make Windows unbootable.
Start in Safe Mode when normal startup is unstable
Safe Mode loads a limited set of drivers and services, which can let you remove a recently installed package or collect evidence without triggering the normal driver stack.
Rank #2
- Less chaos, more calm. The refreshed design of Windows 11 enables you to do what you want effortlessly.
- Biometric logins. Encrypted authentication. And, of course, advanced antivirus defenses. Everything you need, plus more, to protect you against the latest cyberthreats.
- Make the most of your screen space with snap layouts, desktops, and seamless redocking.
- Widgets makes staying up-to-date with the content you love and the news you care about, simple.
- Stay in touch with friends and family with Microsoft Teams, which can be seamlessly integrated into your taskbar. (1)
- Hold Shift while selecting Power > Restart from the sign-in screen or Start menu.
- Choose Troubleshoot > Advanced options > Startup Settings > Restart.
- Press 4 or F4 for Safe Mode. Choose 5 or F5 only when you need networking to download a known driver.
- Use Device Manager or Apps to roll back or uninstall the recent change, then restart normally.
If Windows fails before the recovery menu appears, interrupt startup twice by holding the power button as Windows begins to load. On the next start, Windows should enter the recovery environment. Avoid repeatedly forcing power-offs once recovery is available; use its troubleshooting options instead.
Update Windows, vendor drivers, BIOS, and firmware
An outdated or mismatched driver can remain unstable after a Windows update, while a newer Windows build can expose a defect in an older driver. Update the complete software stack after recording the current versions.
Install Windows updates
Open Settings > Windows Update and install all applicable quality, cumulative, and optional driver updates. Restart when prompted and check again until Windows reports that it is current. On Windows 10, the labels and layout differ slightly, but the Windows Update page is still under Settings.
Use the PC or component manufacturer’s drivers
For a laptop or branded desktop, obtain drivers from the manufacturer’s support page for the exact model and Windows edition. For a separately purchased graphics, storage, network, audio, or motherboard component, use the component vendor’s official package. Compare the installed version in Device Manager with the recommended version before installing. If the blue screen names a module, start with the device category that owns that file rather than installing a broad collection of unrelated driver tools.
Update BIOS and firmware carefully
Microsoft’s stop-error checklist includes current BIOS and firmware. Read the manufacturer’s instructions, connect AC power on a laptop, and do not interrupt an update. Confirm the model and revision first; firmware intended for a different board or system can prevent startup. If the crashes began immediately after a firmware update, check whether the manufacturer documents a rollback path instead of applying another unverified image.
Check Device Manager and Event Viewer
Device Manager
Press Windows key + X and select Device Manager. Expand categories related to the suspected hardware and look for a yellow warning icon, an unknown device, or a device that appears and disappears. Open Properties > General for a status message, then Driver for provider, date, and version. The Events tab can show when Windows installed, configured, or failed to start the device.
A clean Device Manager does not prove that every driver is healthy. Some kernel drivers do not appear as a normal device entry, and a driver can be defective without displaying a warning icon. Use the information here to correlate a module name and installation time, not as a standalone certification.
Rank #3
- Instantly productive. Simpler, more intuitive UI and effortless navigation. New features like snap layouts help you manage multiple tasks with ease.
- Smarter collaboration. Have effective online meetings. Share content and mute/unmute right from the taskbar (1) Stay focused with intelligent noise cancelling and background blur.(2)
- Reassuringly consistent. Have confidence that your applications will work. Familiar deployment and update tools. Accelerate adoption with expanded deployment policies.
- Powerful security. Safeguard data and access anywhere with hardware-based isolation, encryption, and malware protection built in.
Event Viewer
- Press Windows key + X and open Event Viewer.
- Go to Windows Logs > System.
- Choose Filter Current Log and review Critical, Error, and Warning events around the crash time.
- Open entries from the affected device, driver service, storage stack, or Windows Error Reporting and save the event details.
Look for a sequence rather than one isolated warning: a device reset, driver-service failure, and unexpected restart immediately before the stop error is more useful than an unrelated event from hours earlier.
Recommended Free Tools
Run memory, hardware, malware, and file checks
Test system memory
Search for Windows Memory Diagnostic, choose Restart now and check for problems, and let the test complete. The result appears after Windows starts; it can also be reviewed in Event Viewer by searching the System log for the memory-diagnostics source. If the test reports errors, shut down and test the memory modules and slots according to the PC or motherboard manufacturer’s procedure. Do not assume a driver is guilty when physical memory is returning corrupted data.
Use manufacturer diagnostics
Run the hardware diagnostics supplied for the PC or component, especially for memory, storage, and the motherboard. Record the test name, date, and result. A passing test reduces suspicion but cannot rule out an intermittent fault that appears only under heat or load. If diagnostics report a failure, follow the manufacturer’s replacement or support process before continuing with software experiments.
Check for malware and Windows corruption
Run a complete scan with your installed security software, then use Windows’ built-in options for checking file-system errors and corrupted system files. Microsoft includes malware, file-system, and Windows-file checks in its stop-error troubleshooting list because corruption can destabilize driver loading. Allow repairs to finish, restart, and test again. Keep the scan results with your crash notes; a clean scan does not identify the driver, while a detected threat or repaired system file changes the investigation.
Configure and analyze a crash dump
A memory dump preserves information from the failure, including the stack and bug-check parameters. It is the most useful next step when rollback and updates do not identify a cause.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteEnable a dump
- Press Windows key + R, enter
sysdm.cpl, and press Enter. - Open the Advanced tab and select Settings under Startup and Recovery.
- Under System failure, leave Write an event to the system log enabled and clear Automatically restart if you need time to read the next stop screen.
- Choose a kernel or complete memory dump type appropriate to the available disk space, confirm the dump path, and apply the settings.
Windows must be able to write to the system drive. Keep enough free space for the selected dump, and do not use a cleanup utility that removes dump files before analysis.
Open the dump in WinDbg
Install WinDbg from Microsoft’s supported source, open it with administrator rights, and use File > Open dump file to load the newest file from the configured path. In the command window, run !analyze. Review the bug-check code, the four parameters, the probable module, and the call stack. The module named in the summary is a lead, not automatic proof: Microsoft-supplied modules often appear because a third-party driver passed them invalid data.
Rank #4
- Video Link to instructions and Free support VIA Amazon
- 24/7 Tech Support!
- key code included
Interpret the 0x48 parameters
Compare the dump’s parameters with the values photographed from the blue screen. Pay particular attention to the cancel-routine parameter, because Microsoft documents it as a way to determine which driver or stack caused the bug check. Note every third-party module on the stack, its file path, company, and version. Then match that module to a device or application installed on the PC and obtain an official update or rollback for that exact product.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Use Driver Verifier only as a targeted advanced test
Driver Verifier can stress selected drivers and expose illegal IRP handling, but Microsoft warns that it can consume substantial CPU, slow the computer, and cause additional crashes. It should not be the first step or enabled indiscriminately.
- Back up important files and make sure you know how to reach Safe Mode.
- Open Driver Verifier Manager by searching for
verifier. - Create standard settings and choose only suspicious, recently changed, unsigned, or clearly third-party drivers. Test a small group rather than every driver.
- Restart and reproduce the problem while collecting the resulting dump.
- When testing is complete, open Driver Verifier Manager and choose Delete existing settings, then restart. If Windows cannot boot, enter Safe Mode and disable Verifier there.
Verifier is an isolation tool, not a repair utility. If enabling it causes immediate crashes, disable it before drawing conclusions about the driver named in the new dump.
Choose the troubleshooting route that fits the situation
| Route | Risk | Evidence gained | Skill level | Reversibility | Best use |
|---|---|---|---|---|---|
| Safe Mode rollback or uninstall | Low | Whether a recent driver or service is required for the crash | Basic | High; reinstall or restore the previous package | Crashes began after a known change |
| Device Manager and Event Viewer | Low | Device status, installation events, and system-log timing | Basic | High | You need to correlate a device with the failure |
| Windows and hardware diagnostics | Low to moderate | Memory, storage, firmware, malware, or file-corruption signals | Basic to intermediate | Usually high; firmware changes require extra care | The crash persists without a clear software change |
| WinDbg dump analysis | Low to the running system | Bug-check parameters, stack, and candidate modules | Intermediate to advanced | High; it reads evidence rather than changing drivers | The stop screen does not identify a reliable cause |
| Driver Verifier | High; extra crashes and heavy system load are possible | Stress evidence for selected drivers | Advanced | Moderate; disable from Safe Mode if necessary | Only after ordinary rollback, updates, and dumps are inconclusive |
What broad stop-error statistics do and do not tell you
Microsoft has published a broad analysis in which approximately 70% of stop errors were attributed to third-party driver code, 10% to hardware issues, 5% to Microsoft code, and 15% to unknown causes where memory corruption prevented analysis. These figures are general stop-error categories, not a 0x00000048-specific epidemiological study. They justify checking third-party drivers first, but they do not prove that a particular vendor or component caused your crash.
When to escalate
Contact the hardware or software vendor, your organization’s administrator, or a qualified technician when the crash continues after the rollback-and-update cycle, when a dump implicates a signed vendor driver that has no newer release, or when diagnostics report hardware errors. Supply an evidence bundle:
- The photographed stop screen, exact parameters, and crash timestamps.
- The newest dump file and the output from
!analyze. - Event Viewer entries from the minutes surrounding the crash.
- Device Manager driver provider, date, and version information.
- Recent hardware, driver, BIOS, firmware, and application changes.
- Memory and manufacturer-diagnostic results.
Tell support what you already rolled back, uninstalled, updated, or tested. Reporting only “Windows shows 0x00000048” leaves the person helping you without the information needed to isolate an IRP sequencing fault.
Quick Recap
Prevent another 0x00000048 crash
- Create a restore point or other recovery backup before installing a kernel-level driver or firmware update.
- Keep a record of driver versions and installation dates, especially for graphics, storage, network, audio, USB, and motherboard components.
- Prefer the exact package supplied for your PC or component model over unofficial driver repositories.
- Install one major driver or firmware change at a time so a new crash has a clear comparison point.
- Keep crash dumps until the issue is resolved; do not let routine cleanup remove the evidence.
- Disable Driver Verifier after testing rather than leaving it enabled during normal use.
As an optional shortcut after the manual checks, Outbyte Driver Updater can scan more than 100 devices for outdated, corrupted, or missing drivers, install official drivers, show current and recommended versions, and provide driver backup, restore, and scheduled scans. It runs on Windows 11, 10, 8, and 7. A 2-day free trial requires no credit card, followed by a subscription; results vary and no tool repairs every crash.
