Windows Stop Code 0x00000094: KERNEL_STACK_LOCKED_AT_EXIT – Causes and Troubleshooting

Quick Answer

The Windows stop code 0x00000094 (KERNEL_STACK_LOCKED_AT_EXIT) indicates that a thread exited while its kernel stack was marked as not swappable. Windows detects this unexpected kernel-level condition and generates a Blue Screen of Death (BSOD) to prevent continued operation in an unstable state.

A kernel-mode driver or another low-level system component may be involved, but Microsoft does not document a universal root cause or a guaranteed fix for this error. Troubleshooting should focus on recent driver and hardware changes, crash dump analysis, and identifying the component associated with the failure.

What Is KERNEL_STACK_LOCKED_AT_EXIT?

KERNEL_STACK_LOCKED_AT_EXIT is a Windows bug check identified by hexadecimal error code 0x00000094. It occurs when a thread terminates while its kernel stack remains marked as not swappable.

A kernel stack is a memory area used by Windows to manage the execution of kernel-mode threads. The operating system must maintain the correct memory-management state while threads are running and terminating.

When Windows detects that a thread has exited without the expected kernel-stack state being restored, it generates a system bug check. This prevents the operating system from continuing with a potentially inconsistent kernel state.

Bug Check Details

Common Causes of KERNEL_STACK_LOCKED_AT_EXIT

The bug check identifies an unexpected kernel-stack condition, but it does not independently establish why that condition occurred. The following areas are reasonable troubleshooting targets rather than confirmed causes.

1. Faulty or Incompatible Device Drivers

Kernel-mode drivers interact directly with Windows kernel resources. A driver programming defect, compatibility problem, or incorrect handling of kernel resources may contribute to system instability.

Recently installed or updated graphics, storage, network, and other hardware drivers deserve attention when their installation coincides with the first crash.

2. Recently Installed Hardware

Newly installed hardware may introduce driver compatibility problems or interactions with existing system components. External peripherals and internal expansion devices should be investigated if the error started after a hardware change.

3. Third-Party System Software

Some antivirus products, backup applications, virtualization platforms, disk utilities, and system-monitoring tools install kernel-mode drivers. An incompatibility or programming defect in one of these components may contribute to a kernel crash.

4. Windows or Driver Updates

A recent Windows update or driver update may introduce compatibility problems with existing hardware or software. The update date and the first occurrence of the blue screen can help establish whether there is a possible connection.

5. System or Hardware Instability

Memory corruption, unstable hardware configurations, and firmware-related problems may also deserve investigation when supported by diagnostic evidence. The 0x00000094 code alone does not prove that RAM, the motherboard, or another hardware component is defective.

Symptoms of Error 0x00000094

A computer experiencing this bug check may show the following symptoms:

• A blue screen displaying KERNEL_STACK_LOCKED_AT_EXIT.
• The hexadecimal stop code 0x00000094.
• Unexpected Windows restarts or shutdowns.
• Crashes during particular applications or hardware operations.
• Repeated system failures after installing or updating a driver.
• Windows instability following a hardware or software change.
• Crash dump files generated after a system failure, depending on Windows dump configuration.

These symptoms are not exclusive to this bug check. Always verify the displayed stop code and examine available crash information before selecting a troubleshooting procedure.

How to Fix KERNEL_STACK_LOCKED_AT_EXIT (0x00000094)

Follow the troubleshooting methods below in order. Start with basic checks and investigate recent system changes before attempting advanced debugging or recovery operations.

1. Restart the Computer and Check for Recurring Errors

If the error appeared only once, restart Windows and observe whether the problem returns.

1. Save your work if Windows is still accessible.
2. Restart the computer normally.
3. Check whether Windows starts successfully.
4. Use the computer normally and observe whether the same blue screen appears again.
5. Record the circumstances surrounding any repeated crash.

A single crash does not necessarily indicate a persistent problem. Repeated occurrences require further investigation.

2. Disconnect Recently Added Hardware

If the problem started after connecting a new peripheral or installing a hardware component, investigate that device first.

1. Shut down the computer.
2. Disconnect recently added external devices that are not necessary for startup.
3. Start Windows and check whether the error returns.
4. Reconnect the devices individually.
5. Observe whether connecting a particular device is associated with another crash.

For internal hardware, follow the manufacturer's service instructions. Disconnect power before opening a computer, and use a qualified technician when internal component removal is necessary.

3. Update or Roll Back Problematic Drivers

Investigate recently installed or updated device drivers, particularly if the error began immediately after a driver change.

1. Right-click the Windows Start button.
2. Select Device Manager.
3. Expand the relevant hardware category.
4. Right-click the suspected device and select Properties.
5. Open the Driver tab and review the driver information.
6. Check the manufacturer's official website for a compatible driver.

If the problem started after an update and the previous driver was working correctly, consider selecting Roll Back Driver if Windows makes that option available.

Download replacement drivers only from Windows Update or the official hardware manufacturer's support website. Avoid installing unrelated driver-update utilities.

4. Review Recently Installed Applications

Investigate applications installed or updated shortly before the blue screen appeared. Give particular attention to applications that install system-level drivers or services.

1. Open Windows Settings.
2. Select Apps and then Installed apps.
3. Review recently installed applications.
4. Identify software that installs security, backup, virtualization, storage, or hardware-management components.
5. If a strong connection exists, use the application's official uninstallation procedure.
6. Restart Windows and check whether the problem returns.

Do not remove essential security, storage, or system components without understanding their purpose and preparing an appropriate recovery method.

5. Install Applicable Windows Updates

Check for available Windows updates that may contain relevant operating-system or compatibility improvements.

1. Open Settings.
2. Select Windows Update.
3. Click Check for updates.
4. Review and install applicable updates.
5. Restart the computer if required.

If the crash started immediately after a particular update, record its KB number and installation date. Investigate that update rather than assuming that installing additional updates will necessarily resolve the problem.

6. Start Windows in Safe Mode

Safe Mode starts Windows with a limited set of drivers and services. It can help investigate whether a problem is associated with software or drivers loaded during normal startup.

1. Open Windows Recovery Environment (Windows RE).
2. Select Troubleshoot.
3. Select Advanced options.
4. Choose Startup Settings.
5. Select Restart.
6. After restarting, select the Safe Mode option.

If Windows operates more reliably in Safe Mode, investigate recently installed drivers and third-party software. This result is a diagnostic clue and does not independently identify the faulty component.

If Windows cannot start normally, Windows RE may be accessed through supported recovery startup procedures or Windows installation or recovery media.

For additional instructions, see Microsoft's Start your PC in Safe Mode documentation.

7. Use System Restore

If the problem began after installing a driver, application, or update, System Restore may help return Windows system configuration to an earlier restore point.

1. Search for Create a restore point in the Windows Start menu.
2. Open the System Protection settings.
3. Select System Restore if available.
4. Choose a restore point created before the problem started.
5. Review the affected programs and follow the on-screen instructions.

System Restore can reverse certain system changes, but it does not guarantee a fix for this particular bug check. Back up important personal files before performing recovery operations.

Advanced Troubleshooting for IT Professionals

If basic troubleshooting does not identify the problem, an experienced Windows technician can investigate the crash using memory dumps and debugging tools.

1. Locate Windows Memory Dump Files

Windows can generate memory dump files when a system bug check occurs. These files preserve diagnostic information that may help identify the execution context and components involved in the crash.

Common dump locations include:

• Small memory dumps: C:\Windows\Minidump
• Kernel or complete memory dump: C:\Windows\MEMORY.DMP

The actual dump location depends on the configured system failure settings. If no dump exists, check whether memory dump generation is enabled, sufficient disk space is available, and the page-file configuration supports the selected dump type.

Memory dumps may contain sensitive information from system memory. Do not upload them to public websites or share them with untrusted parties.

2. Analyze the Crash Dump Using WinDbg

WinDbg is a Microsoft debugging tool used to investigate Windows crash dumps and kernel-level problems.

1. Install WinDbg from Microsoft's official distribution.
2. Open WinDbg.
3. Select File > Open dump file.
4. Select the relevant crash dump.
5. Allow the debugger to load the required symbols.
6. Enter the following command in the debugger command window:

!analyze -v

This command requests a detailed automated analysis of the current crash dump.

The following command can also display the bug check code and available parameters:

.bugcheck

Microsoft does not document parameters for bug check 0x00000094. Therefore, do not assume that additional parameter values will establish the cause of this error.

Review the following information when available:

• Bug check identification and crash context.
• Current thread information.
• Available kernel stack information.
• Loaded kernel modules and driver versions.
• Driver names appearing in the execution path.
• Similarities between multiple crash dumps.

A driver appearing in a stack trace is not conclusive proof that it caused the crash. Examine the execution context and supporting evidence before assigning responsibility.

Refer to Microsoft's documentation for analyzing kernel-mode dump files using WinDbg and the !analyze debugger command.

3. Use Driver Verifier Only When Necessary

Driver Verifier is a Windows diagnostic utility that monitors selected drivers for certain programming errors and improper operations.

It can help experienced developers and IT professionals investigate suspected kernel-mode driver defects. However, its checks can deliberately cause additional system crashes or make Windows temporarily unbootable.

Use it only when a specific driver is suspected and the diagnostic environment is suitable. Follow Microsoft's instructions for selecting drivers, configuring verification, analyzing failures, and recovering from resulting crashes.

Official documentation: Microsoft Driver Verifier documentation.

How to Verify Whether the Error Is Resolved

After making a relevant system change, monitor Windows to determine whether the original failure returns.

• Restart the computer and confirm that Windows starts normally.
• Use the applications and hardware associated with the original crash.
• Check whether the 0x00000094 stop code appears again.
• Review any newly generated memory dump files.
• Compare new crash information with previous dumps if another failure occurs.

A successful restart alone does not prove that the underlying problem has been permanently resolved. Continue monitoring the system if the error was recurring.

What to Do If the Blue Screen Continues

If KERNEL_STACK_LOCKED_AT_EXIT continues to occur, avoid repeatedly changing drivers or removing system components without diagnostic evidence.

1. Preserve the available crash dump files.
2. Record the dates and circumstances of each crash.
3. Document recent Windows updates, driver installations, hardware changes, and system utilities.
4. Have an experienced technician analyze the crash dumps using WinDbg.
5. Investigate suspected drivers and kernel components using official vendor documentation.
6. Run appropriate hardware diagnostics if the available evidence suggests a hardware problem.
7. Consider Windows recovery options only after evaluating less disruptive troubleshooting methods.

For additional assistance, refer to Microsoft's guide to troubleshooting unexpected restarts and stop code errors.

Frequently Asked Questions

1. What does KERNEL_STACK_LOCKED_AT_EXIT (0x00000094) mean?

It means that a Windows thread exited while its kernel stack remained marked as not swappable. Windows generates a bug check after detecting this unexpected kernel-stack state.

2. Is KERNEL_STACK_LOCKED_AT_EXIT caused by a faulty driver?

A faulty or incompatible kernel-mode driver is an important possibility to investigate, but Microsoft does not identify one universal root cause. Crash dump analysis can help narrow down the component involved.

3. Does bug check 0x00000094 have any parameters?

Microsoft's official documentation does not define parameters for KERNEL_STACK_LOCKED_AT_EXIT. Troubleshooting should focus on available crash dump information and the execution context.

4. Can outdated drivers cause this blue screen?

Driver incompatibility or programming defects may contribute to kernel-level problems. Investigate recently changed drivers and check for compatible updates from the hardware manufacturer.

5. Can reinstalling Windows fix error 0x00000094?

Reinstalling Windows is not a documented specific fix for this bug check. Identify the possible driver or system component involved before considering an operating-system reinstall.

6. How can I identify the driver responsible for this error?

Use WinDbg to analyze the crash dump with !analyze -v. Examine the thread context, available stack information, and loaded modules. A driver appearing in the analysis is a clue, not automatic proof of responsibility.

7. Should ordinary users run Driver Verifier?

Driver Verifier is primarily intended for driver testing and advanced troubleshooting. Because it can cause additional crashes, ordinary users should not enable it without suitable technical knowledge and recovery preparations.

Sources

• Microsoft Learn – Bug Check 0x94: KERNEL_STACK_LOCKED_AT_EXIT
• Microsoft Support – Troubleshooting Windows Unexpected Restarts and Stop Code Errors
• Microsoft Learn – Analyzing a Kernel-Mode Dump File with WinDbg
• Microsoft Learn – !analyze (WinDbg)
• Microsoft Learn – Driver Verifier
• Microsoft Support – Start Your PC in Safe Mode