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

0x00000064 Error: Object Initialization Failed

Try it yourself, or Reach Out!

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

What is 0x00000064 Error?


The Windows Stop Code 0x00000064, known as OBJECT_INITIALIZATION_FAILED, appears when the system encounters a critical failure during the initialisation of core Windows objects during startup. This error usually occurs during boot or after major updates, indicating issues with system configuration, corrupted registry files, incompatible drivers, or damaged boot sectors. If left unaddressed, it can lead to frequent boot failures, system instability, and even complete OS corruption. Prompt troubleshooting is necessary to restore system reliability and prevent repeated crashes.

Causes

  • Corrupted or Missing System Files: Damaged Windows components needed during initialisation.
  • Faulty or Incompatible Drivers: Outdated or misconfigured drivers interrupt the boot process.
  • Registry Corruption: Invalid registry entries preventing critical services from loading.
  • Disk or Boot Sector Errors: Corruption in the Master Boot Record (MBR) or system partitions.
  • Malware or Rootkits: Malicious code tampering with core system services during startup.
  • Improper Shutdowns: Forced power-offs or abrupt reboots damaging startup configurations.

Resolution Steps




1. Repair System Files and Boot Records

  • Open Command Prompt (Admin) via recovery mode
  • Run the following commands:

sfc /scannow

DISM /Online /Cleanup-Image /RestoreHealth

bootrec /fixmbr

bootrec /fixboot

bootrec /rebuildbcd


These commands repair corrupted system files and rebuild damaged boot records essential for a stable startup.

2. Update or Reinstall Drivers

  • Press Win + X β†’ Device Manager
  • Expand categories such as Disk drives, Display adapters, and Network adapters
  • Right-click and choose Update driver
  • If issues persist, uninstall the driver and reboot to let Windows reinstall it automatically

Ensuring updated drivers prevents startup conflicts and improper memory or device references during boot.

3. Check Disk Health

  • Open Command Prompt (Admin)
  • Run:
  • chkdsk C: /f /r
  • Schedule the scan and restart your computer

This scans for and repairs bad sectors or corrupted partitions that could be triggering initialisation failures.

4. Verify Registry Integrity

  • Back up the registry before changes
  • Use Registry Editor or trusted repair tools to fix invalid entries
  • Corrupted registry settings during boot often prevent critical system processes from initialising properly.

5. Test RAM for Errors

  • Press Win + R, type mdsched.exe, and hit Enter
  • Choose Restart now and check for problems
  • Replace or reseat RAM if errors are detected

Stable memory is essential for the reliable initialisation of Windows objects during the startup process.

6. Scan for Malware

  • Open Windows Security β†’ Virus & threat protection
  • Perform a Full Scan and an Offline Scan
  • Use rootkit removal tools for advanced infections

Malicious code targeting system-level files or boot sectors can prevent proper initialisation and lead to repeated BSOD errors.

7. Perform a System Restore

  • Go to Control Panel β†’ Recovery β†’ Open System Restore
  • Select a restore point before the error
  • Follow prompts to revert recent updates, driver installations, or configuration changes

This restores system stability by undoing faulty changes that may have caused the BSOD.


The 0x00000064 OBJECT_INITIALIZATION_FAILED BSOD indicates critical issues during the Windows startup process, typically caused by corrupted system files, bad registry configurations, or disk errors.

To fix it:

  • Repair system and boot files,
  • Update or reinstall drivers,
  • Check your disk and memory health, and
  • Scan thoroughly for malware.

If the error persists:

  • Disconnect or replace faulty hardware,
  • Use System Restore to roll back system changes, or
  • Consider a clean Windows installation to resolve deep system corruption.

Quickly addressing this error helps maintain data integrity, ensures smoother boot processes, and restores system reliability.

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!