Step-by-Step Guide to Fix Windows Stop Code 0x00000087

0x00000087 Error: Invalid Handle BSOD in Windows

Try it yourself, or Reach Out!

If you still need a hand, we’re just a plan away

What is the 0x00000087 Error?


The Windows Stop Code 0x00000087, known as INVALID_HANDLE, occurs when a kernel-mode driver or system process references an invalid or improperly closed handle. Handles are essential for accessing system objects like files, registry keys, or device interfaces. When a driver or application tries to use a handle that has been closed or corrupted, Windows halts to prevent system instability or data corruption. This BSOD often appears during driver initialization, software installation, or hardware access when a poorly coded driver attempts to reference invalid handles in kernel space.

Causes

  • Faulty or Incompatible Kernel Drivers: Drivers incorrectly managing object handles or using freed handles.
  • Corrupted System Files: Damaged kernel or system-level files causing invalid handle mapping.
  • Third-Party Filter Drivers: Antivirus, backup, or encryption filters mishandling kernel objects.
  • Improper Resource Deallocation: Drivers not releasing handles properly during shutdown or sleep transitions.
  • Memory Corruption: Faulty RAM or pagefile inconsistencies leading to handle mismanagement.
  • Registry or File System Corruption: Invalid entries affecting handle references.
  • Outdated BIOS or Chipset Drivers: Inconsistent communication with hardware resources.

Resolution Steps




1. Boot into Windows Recovery Environment (WinRE)

  • Interrupt boot 3 times to enter WinRE.
  • Go to Troubleshoot β†’ Advanced Options β†’ Command Prompt.

2. Run System File Checker and DISM

  • Repair corrupted kernel modules and handle-related files by running:

sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows  

DISM /Image:C:\ /Cleanup-Image /RestoreHealth

  • Restart after scan completion.

3. Run CHKDSK to Fix File System Errors

  • In Command Prompt, type:

chkdsk C: /f /r /x

  • Restart the system after scanning to correct any file system or registry handle errors.

4. Boot into Safe Mode and Isolate Drivers

  • Start Windows in Safe Mode.
  • Open Device Manager β†’ View β†’ Show hidden devices.
  • Identify recently installed or updated drivers.
  • Right-click β†’ Uninstall device or Roll Back driver.
  • If a third-party driver caused the issue, uninstall the associated software completely.

5. Remove or Disable Third-Party Filter Drivers

  • Filter drivers used by antivirus, backup, or encryption tools can cause handle corruption.
  • Temporarily disable or uninstall these tools in Safe Mode.
  • Restart and verify if BSOD persists.

6. Repair Registry and Handle Mappings

  • Use Command Prompt (Admin) to repair and reset handle mappings:

sfc /verifyonly  

regedit

  • Inspect HKLM\SYSTEM\CurrentControlSet\Services for invalid driver entries.
  • Remove obsolete driver subkeys cautiously (only if verified).

7. Check and Test Memory Stability

  • Run Windows Memory Diagnostic or MemTest86 to identify RAM corruption.
  • If memory errors occur, replace the faulty RAM module.

8. Update BIOS and Chipset Drivers

  • An outdated chipset or BIOS firmware may mismanage hardware handle allocation.
  • Update to the latest BIOS version and install updated chipset drivers from your motherboard manufacturer.

9. Perform a Clean Boot

Perform a Clean Boot to disable all third-party services and startup programs:

  • Open System Configuration (msconfig).
  • Disable all non-Microsoft services.
  • Restart and check if BSOD reappears.
  • Gradually re-enable services to identify the problematic driver or application.

10. Perform System Restore or Reinstallation

If all else fails:

  • Use System Restore in WinRE to revert to a point before the BSOD began.
  • If corruption persists, back up important files and perform a Clean Windows Installation for a complete system reset.

The 0x00000087 (INVALID_HANDLE) BSOD signifies kernel-level handle corruption or mismanagement caused by faulty drivers or system file inconsistencies.

To fix the issue:

  • Repair system and file integrity with SFC/DISM and CHKDSK.
  • Roll back or uninstall defective drivers.
  • Check RAM stability and update BIOS or chipset drivers.
  • Remove conflicting filter drivers and perform a clean boot.

If unresolved:

  • Reinstall Windows to rebuild a clean handle mapping environment.
  • Replace faulty RAM or storage devices if hardware instability persists.

Timely diagnosis and driver correction help prevent recurring INVALID_HANDLE errors and restore long-term Windows stability.



We’re Here for You!


Follow our step-by-step instructions to troubleshoot the issue. Still need help?
Contact us and choose a plan, and our experts will take care of it for you.

Transparent Pricing

Simple, upfront pricing with no hidden fees or surprises

Endpoints

  • Desktops$49
  • Laptops$49
  • Mobile Devices (MDM)$19
  • Workstations$69
  • POS/Kiosks$49
  • Network Printers$29
  • Purchase Now

Network

  • Routes$29
  • Switches$15
  • Firewalls$29
  • Access Points$9
  • VPN Gateways$19
  • Load Balancers$49
  • Purchase Now

Server

  • On-Prem Servers$99
  • Virtual Servers$69
  • Cloud Servers$99
  • Storage Systems (NAS/SAN)$49
  • Backup Appliances$99
  •   
  • Purchase Now

Security

  • Endpoint Protection (EDR)$9
  • AV/Antimalware$9
  • Patch Management$9
  • Web Filtering$9
  • MFA$5
  •   
  • Purchase Now

BDR

  • Local Backup$49
  • Cloud Backup$49
  • DR Infrastructure$199
  •   
  •   
  •   
  • Purchase Now

Compliance

  • Policy Mgmt & Audits$149/month
  • DLP$5/user
  • IT Governance Tools$199/month
  •   
  •   
  •   
  • Purchase Now

NOC

  • 24/7 Monitoring$10/device
  • RMM Tools$3/device
  • MDR Service$25/device
  •   
  •   
  •   
  • Purchase Now

SOC & SIEM

  • Threat Intelligence$199/month
  • Cloud SIEM (Sentinel, etc.)$200–$1000+
  •   
  •   
  •   
  •   
  • Purchase Now

Helpdesk

Open a Ticket / Contact Us

Need help now or want to explore partnership options?

Subscribe our newsletter to stay updated!