Solved: DEVICE REFERENCE COUNT NOT ZERO (0X00000036) BSOD Crash on Windows 10/11

by

How to Fix the DEVICE REFERENCE COUNT NOT ZERO (0X00000036) BSOD Error on Windows 10/11

Understanding the DEVICE_REFERENCE_COUNT_NOT_ZERO (0x00000036) BSOD Error

The **DEVICE_REFERENCE_COUNT_NOT_ZERO (0x00000036)** Blue Screen of Death (BSOD) is a critical system error that occurs when Windows encounters an issue with how it manages references to hardware devices. This error typically appears during startup, file operations, or while using certain applications, often leading to unexpected crashes. The error suggests that the operating system failed to properly release resources associated with a device, which can happen due to driver conflicts, corrupted system files, or hardware issues.

Common Causes of the Error

The DEVICE_REFERENCE_COUNT_NOT_ZERO BSOD can be triggered by several factors, including:

  • **Corrupted system files**: Damaged Windows system files or registry entries.
  • **Faulty or outdated drivers**, particularly those related to storage devices (e.g., hard drives, SSDs) or network adapters.
  • **Hardware issues**, such as failing RAM, overheating components, or faulty connections.
  • **Malware or virus infections** that interfere with system processes.
  • **Improper shutdowns or sudden power loss**, which can leave the system in an unstable state.

Step-by-Step Fixes for DEVICE_REFERENCE_COUNT_NOT_ZERO (0x00000036)

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

Corrupted system files are a common cause of this error. Use the built-in tools **System File Checker (SFC)** and **Deployment Image Servicing and Management (DISM)** to repair them.

1. Open **Command Prompt as Administrator**:

  • Press `Win + X` and select **Terminal (Admin)** or **Command Prompt (Admin)**.
  • If prompted by UAC, click **Yes**.

2. Run the following commands one by one:

DISM /Online /Cleanup-Image /RestoreHealth

This may take several minutes to complete.

3. After DISM finishes, run SFC:

sfc /scannow

4. Restart your PC and check if the issue persists.

# Method 2: Check for Hardware Issues with CHKDSK

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

1. Open **Command Prompt as Administrator**.

2. Run:

chkdsk C: /f /r

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

3. If prompted, press **Y** to confirm and restart your PC.

4. The scan will run on the next bootwait for it to complete before logging in.

# Method 3: Update or Reinstall Problematic Drivers

Outdated or conflicting drivers can trigger this BSOD. Heres how to update them:

1. Press `Win + X` and select **Device Manager**.

2. Expand categories like **Disk drives**, **Network adapters**, or **Storage controllers**.

3. Right-click any device with a yellow exclamation mark (if present) and select **Update driver**.

4. Choose **Search automatically for drivers** and follow the prompts.

5. If updating doesnt work, try rolling back or reinstalling the driver:

  • Right-click the device **Properties** **Driver** tab **Roll Back Driver** (if available).
  • Alternatively, uninstall the driver, then restart your PC to let Windows reinstall it automatically.

# Method 4: Test for RAM Issues

Faulty RAM can cause this error. Use Windows built-in tool:

1. Open **Task Manager** (`Ctrl + Shift + Esc`).

2. Go to the **Performance** tab **Memory** section.

3. Click **Open Resource Monitor**.

4. Check for errors under the **Physical Memory** section.

If issues are detected, run a memory test using third-party tools like [MemTest86](https://www.memtest86.com/).

# Method 5: Scan for Malware

Malware can corrupt system files and trigger BSODs. Run Windows Defender:

1. Open **Windows Security** (search in the Start menu).

2. Go to **Virus & threat protection** **Quick scan**.

3. Let it complete, then restart your PC.

# Method 6: Check for Overheating or Hardware Failures

Overheating can cause system instability:

  • Use tools like **HWMonitor** ([Download here](https://www.cpuid.com/softwares/hwmonitor.html)) to monitor temperatures.
  • Clean dust from fans and ensure proper airflow.

# Method 7: Perform a Clean Boot (Advanced)

If the error occurs with specific apps or services, perform a clean boot:

1. Press `Win + R`, type `msconfig`, and hit **Enter**.

2. Go to the **Services** tab Check **Hide all Microsoft services** Click **Disable all**.

3. Go to the **Startup** tab Open **Task Manager** Disable all startup items.

4. Restart your PC in a clean state. If the error doesnt appear, re-enable services/apps one by one to identify the culprit.

FAQ: Common Questions About DEVICE_REFERENCE_COUNT_NOT_ZERO

# Q: Will this error delete my files?

A: No, BSODs like this do not permanently damage your data. However, if the issue is due to a failing hard drive, back up important files immediately.

# Q: Should I replace my RAM or SSD if I see this error?

A: Not necessarily. Start with software fixes (like SFC/DISM) before assuming hardware failure. If the problem persists after testing RAM and drivers, consider hardware diagnostics.

# Q: Can third-party antivirus cause this BSOD?

A: Yes. Try disabling your antivirus temporarily to check if its the culprit. Use Windows Defender as a temporary replacement.

# Q: How often should I run SFC or DISM?

A: Run these tools monthly for maintenance, especially after major updates or system instability.

Final Notes

If none of the above methods work, consider:

  • **Restoring from a system restore point** (if available).
  • **Reinstalling Windows** as a last resort if corruption is severe.
  • **Contacting Microsoft Support** or visiting a repair shop for hardware diagnostics.

Last Updated: December 13, 2025

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

Leave a Comment