Windows BSOD Error 0x00000036 — What It Means & How to Fix It

What Does This Error Mean?

BSOD 0x00000036 (DEVICE_REFERENCE_COUNT_NOT_ZERO) means Windows tried to delete a device object, but the device still had active references — meaning some driver or component was still holding onto it and had not let go. This is a driver programming error. It almost always points to a buggy or incompatible device driver that is not releasing resources properly.

Affected Models

Windows 10
Windows 11
Windows 8.1
Windows 7

Common Causes

A device driver has a bug where it fails to release its reference to a device object before Windows removes it
A third-party filter driver (antivirus, backup software, virtual drive software) is holding onto a device that Windows is trying to unload
A USB or Bluetooth device was removed while a driver was still actively communicating with it
An outdated driver is not compatible with the Windows version's device management rules
Conflicting drivers — two programs managing the same device simultaneously — prevent proper cleanup

How to Fix It

Identify which driver caused the crash using WhoCrashed (free from resplendence.com). Install it and run it — it reads your BSOD minidump files from C:\Windows\Minidump and tells you the name of the driver file responsible. This tells you exactly where to look.

The driver name will end in .sys. Search for it online to find out which device or program installed it. That is your primary fix target.
Update the identified driver. If it is a hardware driver, visit the manufacturer's website and download the latest version. If it is part of a software package (antivirus, backup tool, virtual drive software), update that software through its own update mechanism.

Driver bugs that cause reference count errors are usually fixed in newer releases. Always download drivers from the manufacturer's official website, not from third-party driver update utilities.
Uninstall virtual drive or disk emulation software. Programs like Daemon Tools, Virtual CloneDrive, or alcohol software install virtual device drivers that are common causes of this error. Open Control Panel > Programs > Programs and Features and uninstall them.

Virtual drive software installs filter drivers that intercept device removal events. If the virtual drive software is not updated to work with your Windows version, it can fail to release device references properly.
Safely eject USB and external devices before unplugging them. Always use the 'Safely Remove Hardware' icon in the system tray (bottom-right corner) before disconnecting USB drives, external hard drives, or other devices. This tells Windows to release all driver references first.

Yanking a USB device while it is being actively accessed is a common trigger for this BSOD. Making safe ejection a habit can prevent it entirely.
Roll back any recently updated drivers. Open Device Manager (right-click Start > Device Manager). Find the device associated with the identified driver. Right-click it > Properties > Driver tab > Roll Back Driver. This restores the previous working driver version.

This error sometimes appears after automatic driver updates pushed by Windows Update. Rolling back restores the stable version you had before.

When to Call a Professional

If you cannot identify the driver from crash dumps and the error persists after driver updates, consult a technician. They can use advanced kernel debugger tools to pinpoint exactly which driver is failing to release the device reference.

Frequently Asked Questions

When does this BSOD most commonly happen?

This crash most often happens during shutdown, restart, or when unplugging a device. That is because Windows tries to unload device objects during those events. If a driver is holding onto a device reference at that moment, the crash occurs. If your BSOD only happens when shutting down, that is a strong confirmation that this error is the cause.

Could my antivirus software cause this?

Yes — antivirus programs install kernel-level filter drivers that monitor device activity. These drivers sometimes hold device references longer than Windows expects. To test if antivirus is the cause, boot into Safe Mode (which disables third-party drivers) and see if the crash still happens. If it does not crash in Safe Mode, your antivirus or another third-party program's driver is the likely culprit.

Is it safe to keep using my PC with this error?

Only for short periods while you fix the issue. The BSOD itself is a hard crash — any unsaved work is lost each time it happens. If the crash occurs during shutdown only, it may not interrupt your daily work, but it can corrupt files that were still being written at the time. Fix the driver issue as soon as possible to avoid potential data loss.