0x00000060: What It Means and How to Fix the Crash

Stop code 0x00000060 is the PROCESS_INITIALIZATION_FAILED bug check. Use the crash timing, update history, and Windows kernel crash dump analysis to narrow the next step instead of making several changes at once. For this bug check, Microsoft provides WinDbg !analyze as a way to inspect the crash and help determine the root cause.

What does stop code 0x00000060 mean?

It is Bug Check 0x60, named PROCESS_INITIALIZATION_FAILED. The bug check value is 0x00000060, and Microsoft says the !analyze debug extension can display information about the bug check and help determine the root cause.

If the machine reaches the sign-in screen and then crashes, note that timing and the last system change are important clues. If it fails earlier during startup, collect the same evidence before trying more fixes.

Why rarity changes the first move

Because this stop code is uncommon, start with the most recent change that lines up with the crash rather than trying several repairs at once. Test one change, reboot, and confirm whether the same stop code returns.

According to Bug Check 0x60: PROCESS_INITIALIZATION_FAILED — The bug check value for PROCESS_INITIALIZATION_FAILED is 0x00000060. (source)

What causes 0x00000060 most often?

The facts provided here support only two grounded leads: the bug check itself, and using WinDbg !analyze to inspect the crash. Treat the last recent change that matches the crash timing as the most practical starting point, then confirm the result in the dump.

Likely causes, ranked by clue quality

• Recent driver or software change: worth checking when the crash begins after a package, device, or service change.
• Recent Windows update: worth checking when the crash begins soon after an update install.
• Firmware or hardware change: worth checking when the crash began after a BIOS, firmware, or hardware change.
• No recent change: the dump becomes the best source for narrowing the faulting component.

Use this triage matrix before changing anything

This table separates the main response paths by timing. Collect evidence first, then choose one action that matches the most recent change.

How do I troubleshoot bug check 0x60 in Windows?

Start with Event Viewer, update history, and the last change before the crash. If the machine will not boot normally, use Safe Mode or recovery to get back to a point where you can collect evidence and undo the most likely recent change.

1. Open Event Viewer and check Windows Logs > System for the crash time and any driver, disk, or update events before it.
2. Open Settings > Windows Update > Update history and note the last successful boot after a cumulative update or driver package.
3. Boot into Safe Mode from Settings > System > Recovery in Windows 11, or Settings > Update & Security > Recovery in Windows 10.
4. If the crash started after a change, use Device Manager to roll back or uninstall that driver, or remove the recent Windows update.
5. Test one change at a time, then reboot and watch whether the same stop code returns.

Fix the driver path first if the crash followed a change

If the crash started after a driver, filter, or service update, test that path first. Use the vendor’s package or Device Manager to roll back, uninstall, or update the changed driver, then reboot and check whether the stop code returns.

1. Open Device Manager, find the device that changed, and check Properties > Driver for the version and date.
2. Use the vendor’s driver package, not only Windows Update, to install the newest supported release.
3. If no update exists, use Device Manager > Properties > Driver > Roll Back Driver or Uninstall device and reboot.
4. If the crash is tied to a non-device service, use msconfig for a clean boot, then disable the related service and test again.

Should you check Windows updates, BIOS, or firmware next?

Check whether the crash started after a Windows update, BIOS change, or firmware change. If the most recent change matches the crash start time, remove that change and retest before moving to other areas.

1. Go to Settings > Windows Update and review the latest updates offered for the device.
2. Open Update history and note the last patch before the first crash.
3. Check the system vendor’s BIOS and firmware versions, then compare them with the OEM’s support page and update if they lag the supported release line.
4. If a recent update matches the crash start time, remove that update and retest before making deeper changes.

Where can I find the crash dump for a 0x00000060 BSOD?

Check %SystemRoot%\MEMORY.DMP for the main dump and %SystemRoot%\Minidump for small dumps. For recurring boot failures, use a dump setting that preserves enough state to inspect the faulting path in WinDbg.

1. Open System Properties > Advanced > Startup and Recovery.
2. Set Write debugging information to Automatic memory dump for most recurring cases.
3. Use Kernel memory dump when the machine has enough space and the crash repeats during boot.
4. Use Complete memory dump only when full RAM state is needed and the disk can hold it.
5. Use Small memory dump (256 KB) for quick triage or one-off failures. (salivity.github.io)

What does Microsoft recommend for analyzing bug check 0x60?

Open the dump in WinDbg and run !analyze to identify the faulting component and narrow the cause class. Microsoft says this debug extension can display information about the bug check and help determine the root cause.

1. Install WinDbg on a technician system.
2. Open %SystemRoot%\MEMORY.DMP or the newest file in %SystemRoot%\Minidump.
3. Run !analyze -v and note the faulting module, stack, and bug check context.
4. Use the result to confirm whether the next move is a driver rollback, a recent-update removal, or a hardware check.
5. If the output is unclear, hand the dump, update history, and device list to the OEM or driver vendor.

Still not working?

Run hardware and memory tests next, then try a clean boot or remove recently added hardware. If the machine still crashes at the same point, stop swapping parts and escalate with the dump file, Event Viewer export, firmware version, and update history.

1. Run Windows Memory Diagnostic or memtest86 to check RAM. (howtogeek.com)
2. Run chkdsk on the system volume if storage activity appears in the logs.
3. Use msconfig for a clean boot and retest with non-Microsoft services off.
4. Remove newly added hardware and test again.
5. Escalate to Microsoft, the OEM, or the driver vendor with the dump and the exact crash timing.

What should I check first after a PROCESS_INITIALIZATION_FAILED crash?

Check whether Safe Mode starts, then inspect Event Viewer and the last change before the crash. If Safe Mode works, a driver or service is a better lead. If it fails before that, move to firmware and hardware evidence first, because startup code is not getting far enough to blame a user session. (Microsoft Learn)

Is 0x00000060 a driver problem or a hardware problem?

Either is possible. A crash that starts right after a driver or service change points toward that change, while a crash that happens before login with no recent software change points more toward firmware or hardware. The dump and update history are the tie-breakers.

How do I collect a memory dump for this blue screen error?

Open System Properties > Advanced > Startup and Recovery, then choose the dump type that matches your debugging need. After the next crash, look in %SystemRoot%\MEMORY.DMP and %SystemRoot%\Minidump.

Can Windows updates, BIOS, or firmware fixes stop 0x00000060 crashes?

They can help if the crash began right after one of those changes. Check update history, BIOS version, and firmware version, then remove or roll back the most recent matching change and retest.

0x00000060 Lenovo: what should be checked on that hardware?

Check the vendor update history, BIOS level, and storage and chipset drivers before replacing parts. If the crash starts after a platform utility, driver package, or firmware change, undo that last change and retest.

Why does 0x00000060 keep happening or get stuck?

Repeated crashes usually mean the same boot-time change is still present. Undo the most recent matching change, boot Safe Mode if possible, collect the dump, and use WinDbg !analyze to confirm the next step.