Windows Stop Code 0x00000060: PROCESS_INITIALIZATION_FAILED

Quick Answer

The Windows stop code 0x00000060 (PROCESS_INITIALIZATION_FAILED) indicates that Windows encountered a failure during process initialization and could not continue normal system operation. It is a documented but very uncommon bug check.

Start by recording the exact stop code, disconnecting unnecessary external devices, and checking whether the failure began after a Windows update, driver installation, software change, or unexpected shutdown. If Windows cannot start, use Windows Recovery Environment (WinRE) to try Startup Repair or System Restore, where available. If the error persists, investigate crash dumps and system diagnostics rather than assuming that one particular file or hardware component is responsible.

What Does PROCESS_INITIALIZATION_FAILED Mean?

A Windows bug check, commonly called a blue screen of death (BSOD), occurs when Windows detects a critical problem and stops operation.

The value 0x00000060 identifies the PROCESS_INITIALIZATION_FAILED bug check. Microsoft documents this code as occurring very infrequently. Its reference page is primarily intended for developers and debugging professionals, so it does not prescribe a universal end-user repair.

Do not confuse this code with 0x0000006B, which is a separate bug check named PROCESS1_INITIALIZATION_FAILED. The two codes have different diagnostic documentation and should not automatically be treated as the same problem.

Symptoms

A computer affected by this stop code may exhibit one or more of the following symptoms:

• A blue screen displaying PROCESS_INITIALIZATION_FAILED or stop code 0x00000060.
• The computer restarts automatically after displaying the error.
• Windows repeatedly fails to start.
• The error appears after a recent system, driver, or configuration change.
• The computer reaches recovery options instead of the normal sign-in screen.

These symptoms can accompany a startup-related system failure, but they do not establish a specific root cause.

Common Causes and Diagnostic Considerations

The stop code alone is insufficient to establish the underlying cause. Investigate the circumstances surrounding the failure instead of replacing system files or changing boot settings without evidence.

• Windows system or configuration problems: Damaged or inconsistent operating-system components may warrant investigation, particularly when other startup errors occur.
• Recent updates or driver changes: A failure that begins immediately after an update or driver installation makes that change a useful diagnostic lead, although timing alone does not prove causation.
• Third-party system software: Recently installed utilities, security products, storage software, or other software that interacts with Windows may be relevant.
• Storage or hardware problems: Drive errors, unstable hardware, or memory problems can complicate startup. Investigate these possibilities when symptoms or diagnostic results support them.
• Unresolved initialization failure: Additional debugging information may be needed to identify the component or operation that failed.

None of these possibilities should be treated as the confirmed cause without supporting evidence.

Before You Begin

• Record the complete blue-screen message, including any additional stop codes or parameter values.
• Determine whether the failure occurs on every boot or only after a recent change.
• Disconnect unnecessary USB storage devices, docks, and recently attached peripherals.
• If Windows starts occasionally, back up important files before attempting repairs.
• If BitLocker or device encryption is enabled, make sure you can access the recovery key before using recovery tools.

How to Fix PROCESS_INITIALIZATION_FAILED (0x00000060)

1. Disconnect External Devices and Restart

Start with the simplest checks. Shut down the computer, disconnect nonessential external devices, and turn it on again. Keep essential equipment connected.

If Windows starts normally, reconnect the devices one at a time and restart as necessary to determine whether a particular device or its driver is associated with the failure.

Verification: Check whether Windows starts repeatedly without displaying the same stop code. A single successful boot does not prove that the problem is resolved.

2. Enter Windows Recovery Environment

If Windows repeatedly fails to start, Windows Recovery Environment (WinRE) provides access to supported repair options.

1. Turn on the computer and wait for Windows to begin loading.
2. If normal startup fails repeatedly, Windows may enter recovery automatically.
3. If recovery does not appear, use compatible Windows installation media created on a working computer and select the repair option rather than installing Windows.
4. In WinRE, select Troubleshoot > Advanced options.

Menu labels may vary slightly by Windows version and recovery method. Do not repeatedly interrupt startup while the computer is performing an update, firmware operation, or recovery process.

See Microsoft's Windows Recovery Environment documentation.

3. Run Startup Repair

Startup Repair checks for certain problems that prevent Windows from starting, including some damaged system files and boot configuration problems. It may not resolve this particular bug check if the underlying failure is unrelated to a problem it can repair.

1. Enter WinRE and open Troubleshoot > Advanced options.
2. Select Startup Repair.
3. Select the Windows installation and provide authentication details if requested.
4. Allow the repair process to finish without powering off the computer.
5. Restart and check whether Windows starts normally.

If Startup Repair cannot repair the computer, record the result and investigate other recovery options rather than repeating the same procedure indefinitely.

Official instructions: Microsoft Startup Repair.

4. Use System Restore if the Problem Began Recently

If the stop code appeared after a driver installation, software change, or Windows update, System Restore may return system files, registry settings, drivers, and installed programs to an earlier restore point.

1. Open WinRE and select Troubleshoot > Advanced options > System Restore, if available.
2. Select an appropriate restore point dated before the failure began.
3. Review affected programs and changes when the option is offered.
4. Confirm the restore and allow it to finish.
5. Restart the computer and test Windows startup.

System Restore is not a substitute for a personal-file backup. Restore points may not exist, and recovery tools may request the BitLocker recovery key.

Read Microsoft's backup, restore, and recovery guidance.

5. Try Safe Mode

Safe Mode starts Windows with a limited set of drivers and services. If Windows runs in Safe Mode but fails during normal startup, this can help narrow the investigation to drivers, services, or other components that load differently during normal startup.

1. Enter WinRE.
2. Select Troubleshoot > Advanced options > Startup Settings > Restart.
3. After the restart, select Safe Mode or the corresponding option displayed on screen.
4. If Windows starts, review recently installed drivers, applications, and system changes.
5. Undo only changes that are relevant to the failure, using the appropriate vendor-supported procedure.

If Safe Mode also fails, return to WinRE and continue with other recovery options. Do not disable driver-signature enforcement or antimalware protections as a routine fix.

Reference: Microsoft Windows Startup Settings.

Advanced Troubleshooting

Use the following procedures when basic checks and recovery tools have not resolved the problem. These steps are most appropriate for IT support technicians and system administrators who can identify the Windows installation and recover the system if a repair fails.

6. Check Windows System Files

If Windows can boot sufficiently to open an elevated terminal, Microsoft's Deployment Image Servicing and Management (DISM) and System File Checker (SFC) tools can check and repair supported Windows image and system-file problems.

1. Open Start and search for Terminal or Command Prompt.
2. Select the option to run it as administrator.
3. Run the DISM command below and wait for it to finish.
4. Run SFC and review the final message.
5. Restart Windows and check whether the problem recurs.

Run these commands in an elevated Windows Command Prompt or compatible elevated terminal while the installed Windows system is running.

DISM.exe /Online /Cleanup-Image /RestoreHealth

sfc /scannow

DISM attempts to repair the online Windows image using available repair sources. SFC checks protected system files and attempts to repair integrity problems. DISM may require access to Windows Update or a suitable repair source, depending on the environment and image condition.

Important: The /Online option refers to the currently running operating system. Do not run these commands unchanged in WinRE and assume they will repair the offline Windows installation. Offline servicing requires identifying the correct Windows volume and using the appropriate offline options.

For more information, consult Microsoft's Windows image repair documentation.

7. Inspect Crash Dumps and Diagnostic Evidence

For a persistent 0x60 bug check, debugging evidence may be more useful than repeating generic repairs. Windows may have created a crash dump, depending on its configuration and whether the dump could be written successfully.

• Look for crash dumps in C:\Windows\Minidump and, if configured, C:\Windows\MEMORY.DMP.
• Review the System event log for relevant errors immediately before the crash, if the logs are accessible.
• Record recent system changes and any other stop codes observed.
• For technical analysis, use Microsoft's Windows debugging tools and examine the dump with the WinDbg !analyze -v command when applicable.

The dump location may differ, and a dump may be absent or incomplete. The !analyze -v command is intended for use inside WinDbg, not directly in an ordinary Command Prompt.

Microsoft's reference for this specific stop code recommends using the !analyze debugger extension to help determine the root cause: Bug Check 0x60: PROCESS_INITIALIZATION_FAILED.

8. Investigate Storage or Memory Problems

If the computer has storage-related errors, unusually slow disk access, unexpected drive disconnections, or memory-related failures, investigate the relevant hardware before attempting repeated operating-system repairs.

• Check the manufacturer's storage diagnostic utility or built-in hardware diagnostics where available.
• Run the computer manufacturer's memory diagnostic or another trusted memory test when memory errors are suspected.
• Check drive health using a supported diagnostic method appropriate to the storage device.
• Review relevant firmware, hardware, and system logs before replacing components.

If a drive is making unusual mechanical noises, disappearing intermittently, or reporting serious hardware errors, prioritize data recovery. Repair utilities and extended tests can put additional load on a failing device.

Do not update BIOS/UEFI firmware, change storage-controller modes, remove hardware, or replace system components solely because error 0x60 appeared. Such actions should be based on a specific diagnosis and the manufacturer's instructions.

What to Do If the Repairs Do Not Work

If Startup Repair and other appropriate recovery options fail, preserve the available evidence and choose the next step according to the condition of the Windows installation.

• Windows starts intermittently: Back up important data, collect relevant crash dumps, and inspect system and hardware diagnostics.
• Windows cannot start but WinRE works: Consider System Restore, supported offline diagnostics, or a repair using compatible Windows installation media.
• Hardware failure is suspected: Address the storage or memory issue before reinstalling Windows onto potentially faulty hardware.
• Recovery options are unavailable: Use compatible Windows installation or recovery media and select the repair options where available.

Resetting or reinstalling Windows should be a later option, not the first response to this stop code. Depending on the selected procedure, applications, settings, and personal data may be removed. Verify backups and encryption recovery access before proceeding.

For additional options, consult Microsoft's Windows recovery options.

How to Verify That the Problem Is Resolved

After performing a repair, verify the outcome rather than assuming that the absence of an immediate blue screen proves success.

1. Restart the computer and confirm that Windows reaches the sign-in screen.
2. Perform additional normal restarts to check for recurrence.
3. Check whether the original stop code appears again.
4. Review available event logs and crash dumps for new failures.
5. If a driver, application, or hardware component was changed, confirm that the system remains stable with that change in place.

If the same stop code returns, record the new crash details and investigate the underlying cause instead of repeatedly applying the same repair.

Frequently Asked Questions

Is PROCESS_INITIALIZATION_FAILED (0x60) a serious error?

Yes. It is a critical Windows bug check that prevents normal operation at the time of the failure. It does not, by itself, establish that the hardware is damaged or that Windows must be reinstalled.

Does error 0x00000060 always mean Windows system files are corrupted?

No. System-file integrity is one area that may warrant investigation, but the stop code alone does not confirm file corruption. Crash-dump analysis and other diagnostic evidence may be needed.

What is the difference between 0x60 and 0x6B?

0x00000060 is PROCESS_INITIALIZATION_FAILED. 0x0000006B is PROCESS1_INITIALIZATION_FAILED. They are distinct bug checks with separate Microsoft documentation, so troubleshooting should be based on the exact code displayed.

Can I fix this error without reinstalling Windows?

Potentially. Startup Repair, System Restore, removal of a confirmed problematic change, or a targeted system repair may resolve the underlying problem. The appropriate method depends on the cause, and no single procedure is guaranteed to work for every system.

Can I run SFC and DISM from the recovery Command Prompt?

Offline repair is possible in supported circumstances, but commands intended for the currently running Windows installation should not be copied unchanged into WinRE. The correct Windows volume and servicing options must first be identified.

Should I replace the hard drive or RAM?

Not based on this stop code alone. Replace hardware only when manufacturer diagnostics, system logs, physical symptoms, or other reliable evidence indicates a hardware fault.

Conclusion

The Windows stop code 0x00000060 PROCESS_INITIALIZATION_FAILED identifies an uncommon critical initialization failure, but it does not provide a complete diagnosis by itself. Start with basic checks, use WinRE and Startup Repair when Windows cannot boot, and consider System Restore if the problem followed a recent change. If the failure persists, prioritize crash-dump analysis and targeted system or hardware diagnostics before attempting destructive recovery procedures.

Sources

• Microsoft Learn: Bug Check 0x60 — PROCESS_INITIALIZATION_FAILED
• Microsoft Learn: Bug Check Code Reference
• Microsoft Support: Windows Recovery Environment
• Microsoft Support: Startup Repair
• Microsoft Support: Windows Startup Settings
• Microsoft Support: Backup, Restore, and Recovery in Windows
• Microsoft Learn: Repair a Windows Image