How to Fix Windows Bug Check 0x00000092 (UP_DRIVER_ON_MP_SYSTEM)

Quick Answer

The Windows stop code 0x00000092 (UP_DRIVER_ON_MP_SYSTEM) indicates that a driver compiled to work only on a uniprocessor system has been loaded while Windows is running with multiple active processors. Microsoft identifies this as a driver compatibility problem. The first step is to identify the driver involved by examining the crash dump with WinDbg and the !analyze -v command.

To troubleshoot the error, review recently installed or updated drivers and software, install compatible drivers from the computer or hardware manufacturer's official website, and remove or roll back a problematic driver when the evidence supports doing so. The stop code identifies the type of problem, but additional diagnostic evidence is needed to determine the responsible driver.

What Is UP_DRIVER_ON_MP_SYSTEM?

UP_DRIVER_ON_MP_SYSTEM is a Windows bug check, also known as a blue screen of death (BSOD) error. Its hexadecimal value is 0x00000092.

A uniprocessor (UP) system has one active processor, whereas a multiprocessor (MP) system has more than one active processor. The error occurs when Windows detects that a driver intended for a uniprocessor environment has been loaded on a multiprocessor system.

This is a kernel-level driver compatibility issue. It does not, by itself, establish that the processor, RAM, motherboard, or another physical component is defective.

Microsoft documents the bug check and its parameters in the Bug Check 0x92: UP_DRIVER_ON_MP_SYSTEM reference.

Common Causes

The documented cause is the loading of a uniprocessor-only driver on a system with multiple active processors. The following situations are worth investigating when diagnosing how that driver came to be installed or loaded.

• Legacy driver software: An old driver package may not support the current processor configuration or Windows environment.
• Incompatible driver installation: A driver intended for a different operating-system version or hardware configuration may have been installed.
• Recent driver changes: The problem may have appeared after installing, updating, or rolling back a driver.
• Third-party kernel software: Older hardware utilities, security products, virtualization components, or other software that installs kernel-mode drivers may warrant investigation if the crash evidence points to them.
• Incorrect or incomplete vendor package: The installed driver may not match the device or supported platform.

These are investigation leads, not individually confirmed causes of every 0x00000092 crash. Use crash-dump evidence and installation history to narrow the possibilities.

Symptoms

Depending on when the incompatible driver is loaded, the error may appear during startup, after installing a driver, or while Windows is initializing or using a device.

• Windows displays a blue screen with the stop code UP_DRIVER_ON_MP_SYSTEM.
• The computer restarts unexpectedly after the crash.
• The same stop code appears repeatedly during startup or normal operation.
• The crash begins after a driver or hardware-related software change.
• A crash dump records bug check code 0x92.

These symptoms are useful clues, but none identifies the responsible driver without further investigation.

How to Fix UP_DRIVER_ON_MP_SYSTEM (0x00000092)

1. Restart Windows and Check for Recent Changes

If the error occurred once and Windows now starts normally, save your work and monitor the system. If the blue screen recurs, investigate before making extensive changes.

1. Disconnect newly added external hardware that is not required for startup, then check whether the error recurs.
2. Review any driver, hardware utility, security software, or system component installed immediately before the first crash.
3. Record the exact stop code and any driver filename displayed on the blue screen or in the crash report.
4. If Windows cannot start normally, use Windows Recovery Environment (WinRE) to access Startup Settings and attempt Safe Mode.

Microsoft provides additional guidance in its guide to troubleshooting unexpected restarts and stop code errors.

2. Analyze the Crash Dump to Identify the Driver

Crash-dump analysis is the most useful next step when the cause is unclear. A dump file contains diagnostic information captured when Windows crashed. WinDbg can display the bug check details and relevant driver information.

Check whether a dump file exists in one of these standard locations:

• C:\Windows\Minidump\ — commonly used for small memory dump files.
• C:\Windows\MEMORY.DMP — the default location commonly used for a kernel or complete memory dump, depending on the configured dump type.

These are standard locations, not a guarantee that a dump was created or saved there. Dump generation may be disabled, and the configured path can differ.

Analyze the Dump with WinDbg

1. Obtain WinDbg from Microsoft's official debugging tools resources.
2. Open WinDbg and load the available crash dump file.
3. Allow symbol loading to complete. Symbols help the debugger interpret Windows and driver code.
4. Enter the following command in the debugger command window:

!analyze -v

The !analyze -v command displays a verbose analysis of the bug check, including diagnostic information that may help identify the relevant driver.

Review the bug check code, its parameters, the stack trace, and any driver or module information. Do not assume that a module named in the report is necessarily the original cause; it may be involved in the failure without being the underlying source of the incompatibility.

Microsoft documents this command in !analyze (WinDbg) and provides a procedure for analyzing a kernel-mode dump file with WinDbg.

3. Update or Replace the Identified Driver

If the dump analysis or other reliable evidence identifies a particular driver, obtain a compatible version from the computer manufacturer or the device manufacturer's official support website.

1. Identify the device, its hardware model, and the installed driver version.
2. Check the manufacturer's compatibility information for your Windows version and hardware platform.
3. Install the appropriate supported driver package using the manufacturer's instructions.
4. Restart Windows if required by the installer.
5. Check whether the same bug check occurs again.

For an older device, check whether the manufacturer provides a supported replacement driver. If no compatible driver exists, the device or its associated software may need to be removed or replaced with a supported alternative.

Do not download replacement driver files from unverified driver-download websites. Do not manually replace a Windows system driver simply because its filename appears in a crash report.

4. Roll Back a Recently Updated Driver

If the error began immediately after a driver update and the previous version was compatible with the system, rolling back the driver may help determine whether the update introduced the problem.

1. Right-click Start and open Device Manager.
2. Locate the relevant device category and expand it.
3. Right-click the identified device and select Properties.
4. Open the Driver tab.
5. If the option is available, select Roll Back Driver and follow the prompts.
6. Restart the computer if necessary and check for recurring crashes.

The Roll Back Driver option may be unavailable if Windows has no previous driver package to restore. In that case, obtain the correct supported version from the device manufacturer instead.

If Windows cannot start normally, use Safe Mode or an appropriate WinRE recovery option when available. Avoid removing drivers indiscriminately, especially storage or boot-critical drivers, because doing so can make Windows unbootable.

5. Remove or Update the Software That Installed the Driver

Some applications install kernel-mode drivers as part of their functionality. Examples include certain device utilities, virtualization products, and security software. Investigate these applications only when their drivers or installation history are relevant to the crash.

1. Review recently installed applications and their release or compatibility notes.
2. Check the software manufacturer's official documentation for a compatible update.
3. Use the application's supported uninstaller if removal is necessary.
4. Restart Windows and verify whether the error returns.

Do not disable antivirus protection, firewalls, or other security controls as a routine fix. If a security product is implicated, follow its vendor's supported update or removal procedure and maintain appropriate protection.

6. Use Safe Mode if Windows Keeps Crashing

Safe Mode starts Windows with a limited set of drivers and services. It can help determine whether the system can start in a reduced environment and allow troubleshooting of a recent driver or software change.

1. Enter Windows Recovery Environment. If Windows repeatedly fails to start, its recovery screen may appear automatically. You can also use official Windows installation or recovery media when necessary.
2. Navigate to Troubleshoot, Advanced options, Startup Settings, and Restart, where these options are available.
3. After the restart, select the Safe Mode option shown on the screen.
4. Review the suspected driver or application and perform only the relevant supported rollback, update, or removal procedure.
5. Restart normally and check whether Windows starts without the stop code.

The available menus can vary by Windows version and device configuration. Follow Microsoft's Windows stop-code troubleshooting guidance for the supported recovery options applicable to your system.

Advanced Troubleshooting for IT Professionals

Review the Bug Check Parameters

Microsoft documents the following parameters for bug check 0x00000092:

Use the dump and debugger output to investigate the driver associated with the base address. Do not treat the address as a driver filename or attempt to identify a driver by guessing from the address alone.

Check Driver Compatibility and Installation History

For managed systems, compare the crash timeline with driver deployment records, hardware changes, operating-system updates, and software installations. Confirm the driver package's intended platform and supported Windows versions with the vendor.

Where multiple drivers are involved in a device stack, examine the surrounding debugger output rather than focusing only on one module name. If the evidence is inconclusive, preserve the dump and relevant system details for further analysis.

Use Driver Verifier Only in a Controlled Test Environment

Driver Verifier is a Windows diagnostic tool that monitors selected kernel-mode drivers for improper behavior. Microsoft warns that it can cause the computer to crash and recommends using it on test or debugging systems.

It is not the first-line fix for bug check 0x00000092. Use it only when a qualified technician has a specific driver-testing objective, understands the recovery procedure, and can access the system if it fails to boot.

For official instructions and limitations, see How to Use Driver Verifier for Driver Testing.

If Driver Verifier has already been enabled and you need to clear its settings, open an elevated Command Prompt and run:

verifier /reset

This command clears Driver Verifier settings so drivers will no longer be verified after the next restart. Restart Windows to apply the reset. If the computer cannot boot normally, use an appropriate recovery method and obtain technical assistance if needed.

How to Verify That the Error Is Resolved

After updating, rolling back, or removing the suspected driver, verify the result using the following checks:

1. Restart Windows normally.
2. Use the device or application associated with the suspected driver under ordinary operating conditions.
3. Check whether the same 0x00000092 stop code recurs.
4. If another crash occurs, retain the new dump and compare its bug check information with the earlier report.
5. Confirm that the installed driver matches the manufacturer's supported package for the hardware and Windows version.

A successful restart alone does not prove the root cause has been corrected. Confidence increases when the system remains stable and subsequent diagnostic evidence no longer indicates the same driver incompatibility.

When to Seek Technical Assistance

Consult the hardware manufacturer, software vendor, or a qualified Windows debugging specialist when:

• The computer repeatedly crashes before you can sign in.
• No compatible driver is available from the manufacturer.
• The dump does not provide enough information to identify the driver.
• The crash involves a boot-critical or security-sensitive driver.
• The system remains unstable after the suspected driver has been addressed.

Provide the Windows version, device model, recent changes, stop code, and relevant debugger output. Share crash dumps only through an appropriate trusted support channel.

Frequently Asked Questions

What does stop code 0x00000092 mean?

It means Windows detected a uniprocessor-only driver loaded on a system with multiple active processors. The error is documented as UP_DRIVER_ON_MP_SYSTEM.

Is UP_DRIVER_ON_MP_SYSTEM a hardware failure?

Not necessarily. Microsoft identifies the bug check as a driver compatibility problem. The code alone does not establish a defective CPU, motherboard, or memory module.

Can updating a driver fix error 0x00000092?

Yes, if the responsible driver has a compatible replacement version. Identify the driver using available diagnostic evidence and obtain the replacement from the relevant hardware or software manufacturer.

How do I identify the driver responsible for the crash?

Analyze an available crash dump with WinDbg and run !analyze -v. Review the bug check parameters, stack trace, and module information. Additional investigation may be required to establish the underlying cause.

Should I run Driver Verifier to fix this error?

Not as an initial troubleshooting step. Driver Verifier is a diagnostic testing tool that can trigger additional crashes. Use it only in a controlled test environment with a clear recovery plan.

What if Windows cannot start after the blue screen?

Use Windows Recovery Environment to attempt Safe Mode and investigate recent driver changes. Avoid indiscriminate driver removal, particularly for storage and boot-critical components. Seek professional assistance if the system cannot be recovered safely.

Sources

• Microsoft Learn: Bug Check 0x92 — UP_DRIVER_ON_MP_SYSTEM
• Microsoft Learn: !analyze (WinDbg)
• Microsoft Learn: Analyze a Kernel-Mode Dump File by Using WinDbg
• Microsoft Support: Troubleshooting Windows Unexpected Restarts and Stop Code Errors
• Microsoft Learn: How to Use Driver Verifier for Driver Testing