WindowsAdvanced

0x00000125 NMR_INVALID_STATE – Causes, Meaning and Windows Blue Screen Troubleshooting Guide

Quick Answer The 0x00000125 NMR_INVALID_STATE is a Windows Blue Screen of Death (BSOD) stop code associated with an invalid state detected by the Network Mod...

Bison Technical Team Enterprise IT specialists

Updated 10 Nov 2026 16 min read 0 total views

Structured technical guidanceSafety notes included where requiredSources listed below

Quick Answer

The 0x00000125 NMR_INVALID_STATE is a Windows Blue Screen of Death (BSOD) stop code associated with an invalid state detected by the Network Module Registrar (NMR), a Windows operating system component responsible for managing connections between network-related software modules.

The Network Module Registrar facilitates communication between compatible network modules, including client and provider components used by Windows networking drivers. An invalid state detected in this process can result in a system bug check.

Microsoft's documentation identifies the bug check as NMR_INVALID_STATE. However, its published parameter descriptions contain an apparent inconsistency: the parameter 1 descriptions refer to Windows Hardware Error Architecture (WHEA) error categories, while the main description identifies an NMR-related invalid state. Therefore, the exact underlying failure should be established using the crash dump and debugger analysis rather than assuming a particular hardware or network driver is responsible.

For initial troubleshooting, inspect recent network driver and software changes, install appropriate Windows and manufacturer driver updates, investigate third-party networking components, and analyze the Windows crash dump if the blue screen continues.

What Is 0x00000125 NMR_INVALID_STATE?

The 0x00000125 stop code represents NMR_INVALID_STATE, a bug check documented in the Windows driver debugging reference.

NMR stands for Network Module Registrar. It is a Windows operating system component that manages the registration, attachment and detachment of compatible network modules.

Network modules register themselves with NMR by specifying their characteristics. When compatible client and provider modules register with the same Network Programming Interface (NPI), NMR facilitates their attachment so they can communicate.

If Windows detects an invalid state associated with this bug check, it can stop the operating system to prevent continued execution under an invalid kernel-level condition.

Important technical reference:

Bug Check Code: 0x00000125
Bug Check Name: NMR_INVALID_STATE
Component: Network Module Registrar
Operating System: Windows
Error Type: Kernel-mode bug check / BSOD
Official Documentation: Microsoft Bug Check 0x125: NMR_INVALID_STATE

How Does the Network Module Registrar (NMR) Work?

To understand this error, it is useful to understand the role of NMR in the Windows networking architecture.

NMR provides a mechanism through which compatible software modules can register and establish connections with one another. These modules can include network-related client and provider components implemented by Windows or third-party drivers.

1. Network Module Registration

A client module registers with NMR through the NmrRegisterClient function, while a provider module uses NmrRegisterProvider.

During registration, each module supplies characteristics describing its supported Network Programming Interface (NPI).

2. Module Attachment

When compatible client and provider modules register with the same NPI, NMR initiates the attachment process by invoking the appropriate callback functions.

Once successfully attached, the modules can communicate according to their supported interface.

3. Module Detachment

When a client or provider module deregisters, NMR facilitates the detachment process. The modules must complete the required detachment operations before deregistration and unloading are considered complete.

4. Driver Lifecycle Management

Network drivers must correctly manage registration, attachment, detachment and unloading operations. Incorrect handling of these operations can result in invalid driver states or other kernel-level problems.

Microsoft provides additional technical information in its documentation:

Common Symptoms of 0x00000125 NMR_INVALID_STATE

When this bug check occurs, Windows may display a blue screen and restart automatically. Depending on the circumstances, users may experience the following symptoms:

Windows suddenly displays a Blue Screen of Death.
The system restarts unexpectedly.
The computer crashes during startup or shutdown.
Blue screen errors occur after installing or updating network-related software.
The system becomes unstable when using network adapters or networking applications.
Repeated system crashes occur during normal computer operation.
Windows generates a crash dump file following the system failure.

These symptoms are not exclusive to NMR_INVALID_STATE. The stop code and crash dump should be examined to establish the actual failure.

Possible Causes of NMR_INVALID_STATE

Microsoft identifies this bug check as an NMR-related invalid state but does not publish a definitive list of end-user causes. The following are reasonable investigation areas based on the role of NMR and Windows kernel-mode driver architecture. They should not be treated as confirmed causes without supporting diagnostic evidence.

1. Network Driver Problems

Network adapter drivers provide communication between Windows and network hardware. An outdated, incompatible or defective driver may cause system instability.

Investigate this possibility when crashes begin after installing or updating Ethernet, Wi-Fi or other networking drivers.

2. Third-Party Network Drivers

Some applications install additional network components to provide specialized functionality.

Examples include:

VPN clients.
Network monitoring software.
Third-party firewall products.
Virtual networking applications.
Network filtering and traffic inspection software.
Endpoint security products with network protection components.

If the problem began after installing or updating one of these applications, investigate its associated drivers and components.

3. Incompatible or Corrupted Driver Updates

A driver update may introduce compatibility problems with the installed Windows version or other system components.

Investigate recent changes to network drivers, security software and other kernel-mode components, particularly when the blue screen started immediately after an update.

4. Incorrect Driver Registration or Unloading

NMR-dependent network modules must follow the correct registration and deregistration sequence. Driver developers must ensure that modules are completely detached before their associated resources or memory are released.

Incorrect lifecycle management can create invalid states. This is primarily a driver-development investigation area rather than a normal end-user configuration problem.

5. Windows or Driver Compatibility Problems

Incompatible combinations of Windows updates, third-party drivers and networking software may contribute to kernel-level instability.

Check whether the system recently received a major Windows update, driver replacement or networking software upgrade.

6. Other Underlying System Problems

Not every blue screen involving networking-related activity originates from a network adapter. Other kernel components or underlying hardware problems may contribute to system crashes.

Use the crash dump to distinguish an NMR-related failure from an unrelated or additional system problem.

How to Troubleshoot 0x00000125 NMR_INVALID_STATE

Follow the troubleshooting procedures below in sequence. Start with non-disruptive checks and proceed to advanced diagnostics only when necessary.

Step 1: Record the Blue Screen Error Details

Before making any system changes, record the information displayed on the blue screen.

Check the following details:

Stop code: NMR_INVALID_STATE
Stop code value: 0x00000125
Any driver or file name displayed on the screen.
Whether the crash occurred during startup, shutdown or normal operation.
Recent driver, Windows update or software installation history.

Also determine whether the crash occurs repeatedly or was an isolated incident.

Step 2: Disconnect Recently Added Hardware

If the blue screen started after connecting a new device, temporarily disconnect it and check whether Windows operates normally.

Pay particular attention to newly installed network adapters, USB Ethernet adapters, Wi-Fi adapters and other devices that require third-party drivers.

Shut down the computer properly.
Disconnect the recently added device.
Restart Windows.
Observe whether the system continues to experience the same error.

If removing the device stops the crashes, investigate its driver, firmware and compatibility before reconnecting it.

Step 3: Start Windows in Safe Mode

Safe Mode starts Windows with a limited set of drivers and services. It can help determine whether additional software or drivers are involved in the problem.

If Windows cannot start normally, use Windows Recovery Environment (WinRE).

Enter Windows Recovery Environment.
Select Troubleshoot.
Select Advanced options.
Open Startup Settings.
Select Restart.
After restarting, press 4 or F4 to enable Safe Mode.

If network access is required for a specific diagnostic task, Safe Mode with Networking can be selected using 5 or F5.

Observe whether the blue screen occurs in Safe Mode.

If the problem does not occur in Safe Mode, investigate additional drivers, services and startup applications. However, this result alone does not establish which component is responsible.

Reference: Windows Startup Settings - Microsoft Support.

Step 4: Check Network Adapter Drivers

Inspect the installed network adapter drivers using Device Manager.

Press Windows + X.
Select Device Manager.
Expand Network adapters.
Identify the installed Ethernet, Wi-Fi and virtual network adapters.
Right-click the relevant adapter and select Properties.
Open the Driver tab.
Record the driver provider, version and date.

Check for warning symbols and review whether the driver was recently updated.

When a driver update is appropriate, obtain the compatible driver from Windows Update or the computer or adapter manufacturer's official support website.

Do not install drivers from unverified third-party driver download websites.

Step 5: Roll Back a Recently Updated Network Driver

If the blue screen began immediately after a network driver update, restoring the previous driver may help determine whether the update introduced the problem.

Open Device Manager.
Expand Network adapters.
Right-click the network adapter associated with the recent change.
Select Properties.
Open the Driver tab.
Select Roll Back Driver, if available.
Follow the on-screen instructions.
Restart the computer.

The rollback option may be unavailable if Windows does not have a previous driver package available.

Reference: Update Drivers Through Device Manager.

Step 6: Investigate Recently Installed Networking Software

If the issue started after installing a VPN, firewall, network monitoring application or virtual networking tool, investigate that software.

Open Settings.
Navigate to Apps > Installed apps in Windows 11, or Apps > Apps & features in Windows 10.
Review recently installed networking applications.
Check the software manufacturer's support documentation for known compatibility problems.
If appropriate, temporarily uninstall the suspected application using its supported removal procedure.
Restart Windows and monitor system stability.

Important: Removing VPN, firewall or endpoint security software can affect network connectivity and system protection. Follow organizational security policies and arrange an alternative security solution before removing business-critical protection.

For managed computers, consult the IT administrator before changing security or networking software.

Step 7: Install Available Windows Updates

Windows updates may include operating system fixes, security improvements and compatible driver updates.

Open Settings.
Navigate to Windows Update.
Select Check for updates.
Review available updates.
Install appropriate updates.
Restart the computer if required.

Also check the optional driver updates section when investigating a specific hardware compatibility issue. Do not install unrelated optional drivers without a reason.

Step 8: Check Windows System File Integrity

Windows System File Checker (SFC) checks protected Windows system files and attempts to repair corrupted files using available Windows repair resources.

To run SFC:

Open the Start menu.
Search for Command Prompt.
Right-click Command Prompt.
Select Run as administrator.
Execute the following command:

sfc /scannow

Wait for the scan to complete and review the result.

If Windows reports that some files could not be repaired, run the Deployment Image Servicing and Management (DISM) repair command from an elevated Command Prompt:

DISM /Online /Cleanup-Image /RestoreHealth

After DISM completes, run SFC again:

sfc /scannow

These commands address Windows component and system file integrity. They are general system maintenance procedures and are not a confirmed direct fix for NMR_INVALID_STATE.

Step 9: Review Windows Event Logs

Windows Event Viewer records system events, warnings and errors that may help identify the circumstances surrounding a crash.

Press Windows + R.
Type eventvwr.msc.
Press Enter.
Expand Windows Logs.
Select System.
Review events recorded immediately before and after the blue screen.
Look for relevant driver, device, service and system errors.

Pay attention to recurring events and errors that correspond with the crash time.

Event Viewer may provide useful context, but an event occurring near the crash is not automatically the cause.

Advanced Troubleshooting: Analyze the Windows Crash Dump

If the error continues after basic troubleshooting, analyze the crash dump. This is one of the most useful ways to investigate a kernel-mode bug check.

1. Locate the Minidump Files

Windows may create a small memory dump whenever a system crash occurs.

The default location for small memory dump files is:

C:\Windows\Minidump\

The complete memory dump or automatic memory dump may be located at:

C:\Windows\MEMORY.DMP

The actual dump location depends on the configured Windows startup and recovery settings.

Preserve the dump files before performing major repairs or cleanup operations.

2. Install WinDbg

WinDbg is Microsoft's debugging tool for analyzing Windows crash dumps and investigating kernel-level failures.

Install WinDbg from the official Microsoft source:

Microsoft Windows Debugging Documentation.

3. Open the Crash Dump

Launch WinDbg.
Select the option to open a dump file.
Browse to the relevant .dmp file.
Allow the debugger to load the dump and initialize the debugging environment.
Configure Microsoft Symbol Server access when required.

Correct symbols are important for interpreting Windows kernel structures, functions and stack information.

4. Run the Initial Analysis Command

After opening the dump, execute the following command in the WinDbg command window:

!analyze -v

This command performs an initial analysis of the crash dump and displays detailed information about the bug check.

Review the following information:

Bug check code and parameters.
Failure bucket information.
Faulting thread and process, where available.
Stack trace.
Referenced modules and drivers.
Any additional diagnostic information.

5. Examine the Bug Check Parameters

Microsoft's published documentation describes the parameters for bug check 0x125 as follows:

Parameter	Documented Description
Parameter 1	Subtype of the bug check. The published list includes WHEA-related error categories.
Parameter 2	Pointer to the NMI handle.
Parameter 3	Pointer to the expected type, when available.
Parameter 4	Reserved.

Documentation qualification: Microsoft's parameter 1 descriptions refer to Machine Check Exception, Corrected Machine Check, PCI Express Error and other WHEA-related categories. These descriptions appear inconsistent with the page's NMR_INVALID_STATE title and primary explanation. Do not assume that these WHEA categories establish the cause of an NMR_INVALID_STATE crash. Use the actual parameter values, dump contents and debugger findings when investigating the failure.

6. Investigate Driver and Module Information

If the debugger identifies a particular driver or networking component, investigate it further.

Useful information may include:

Driver filename.
Driver provider and version.
Driver load and unload history, where available.
Module names appearing in the crash stack.
Related network driver callbacks and module interactions.
Whether the identified driver was recently installed or updated.

A driver appearing in the stack does not necessarily mean it is defective. It may simply be part of the execution path when another component encountered a problem.

Driver developers may need to investigate NMR registration, attachment, detachment and deregistration handling using the relevant Windows driver documentation.

Additional Diagnostic Considerations for IT Professionals

Investigate Network Module Registration

For driver developers and kernel debugging specialists, examine the network module lifecycle and associated callbacks.

Relevant Microsoft documentation includes:

Check whether the relevant client and provider modules correctly manage their registration handles, callbacks, memory references and deregistration operations.

Review Driver Verifier Carefully

Driver Verifier is a Windows diagnostic utility designed to detect certain illegal driver behaviors. It is intended primarily for driver developers and experienced troubleshooting professionals.

It can deliberately trigger system crashes when it detects driver violations. Therefore, it should not be enabled casually on a production computer.

Before using Driver Verifier:

Ensure that important data is backed up.
Confirm that a recovery method is available.
Understand how to enter Safe Mode or Windows Recovery Environment.
Identify the specific third-party driver being investigated.
Follow Microsoft's Driver Verifier documentation.

Official reference: Driver Verifier - Microsoft Learn.

How to Prevent NMR_INVALID_STATE and Related Driver Crashes

Although no universal prevention method is documented for this bug check, good driver and system maintenance practices can reduce the likelihood of related compatibility and stability problems.

Keep Windows updated with appropriate security and reliability updates.
Install network drivers from trusted manufacturer sources.
Check driver compatibility before installing new networking software.
Keep VPN, firewall and endpoint security applications updated.
Avoid installing multiple network filtering products without checking compatibility.
Remove unused network adapters and virtual networking components through supported procedures.
Record driver versions before making major system changes.
Investigate recurring system errors instead of repeatedly restarting the computer.
Maintain reliable backups of important business and personal data.
Test significant driver changes before deploying them across business-critical computers.

When Should You Contact Technical Support?

Seek assistance from the computer manufacturer, network adapter manufacturer or a qualified Windows debugging professional when:

The blue screen continues after basic troubleshooting.
Windows repeatedly crashes during startup.
The crash dump identifies a kernel-mode driver that cannot be safely replaced.
Multiple networking components appear involved.
The system contains business-critical applications or enterprise network configurations.
The crash is accompanied by other unexplained hardware or system errors.

When requesting technical support, provide the following information:

Windows edition, version and build number.
Computer manufacturer and model.
Bug check code and all available parameters.
Crash dump files, if available.
Network adapter models and driver versions.
Recently installed software and driver updates.
Event Viewer logs surrounding the crash.
A description of the activities that trigger the failure.

Frequently Asked Questions (FAQs)

1. What does stop code 0x00000125 NMR_INVALID_STATE mean?

It indicates that Windows has detected an invalid state associated with the Network Module Registrar (NMR). NMR manages the registration and attachment of compatible software modules, including network-related components.

2. Is NMR_INVALID_STATE a network adapter hardware failure?

Not necessarily. The bug check is associated with NMR, which is a Windows software component. A network driver or networking software component may be relevant to the investigation, but the stop code alone does not prove that a physical network adapter has failed.

3. Can an outdated Wi-Fi or Ethernet driver cause this error?

An outdated or incompatible network driver is a reasonable investigation target when the crash occurs during networking activity or after a driver change. However, Microsoft does not identify outdated network drivers as a confirmed universal cause of this specific bug check.

4. Can VPN software trigger NMR_INVALID_STATE?

VPN applications can install network-related drivers and filtering components. If the crash begins after installing or updating a VPN, investigate its compatibility and associated drivers. This does not mean every VPN application causes this error.

5. Does NMR_INVALID_STATE mean my motherboard or processor is damaged?

No. The stop code does not independently establish motherboard or processor failure. Hardware diagnostics may be appropriate if additional evidence indicates a hardware problem, but hardware replacement should not be the first troubleshooting step.

6. Can Windows updates fix error 0x00000125?

Installing appropriate Windows updates and compatible driver updates may resolve certain system compatibility problems. However, Microsoft does not document a universal Windows update fix specifically for NMR_INVALID_STATE.

7. Where can I find the crash dump for NMR_INVALID_STATE?

Small memory dump files are normally stored in C:\Windows\Minidump\. Depending on the system configuration, a larger dump may be stored as C:\Windows\MEMORY.DMP.

8. Can I fix NMR_INVALID_STATE by reinstalling Windows?

Reinstalling Windows should not be the first solution. First investigate driver changes, networking software and crash dump information. Reinstallation may be considered only after appropriate diagnosis and data backup if other repair options are unsuccessful.

9. Is NMR_INVALID_STATE related to WHEA_UNCORRECTABLE_ERROR?

The Microsoft documentation for bug check 0x125 contains parameter descriptions referring to WHEA error categories. However, its main description identifies NMR_INVALID_STATE as an NMR-related bug check. These documentation details should not be interpreted as proof that the two bug checks have the same cause. Examine the actual stop code and crash dump independently.

Conclusion

The 0x00000125 NMR_INVALID_STATE blue screen error is documented as an invalid state detected by the Windows Network Module Registrar. Since NMR manages registration and communication between compatible software modules, investigating relevant kernel-mode drivers and networking components is an important part of troubleshooting.

Start by recording the crash details, reviewing recent driver and software changes, checking network adapter drivers and installing appropriate Windows updates. If the problem persists, analyze the crash dump using WinDbg to obtain more specific diagnostic information.

Most importantly, do not assume that the network adapter, processor or motherboard is defective based only on this stop code. Accurate diagnosis should be based on crash dump evidence and the actual behavior of the affected system.

Official References

YOUR FEEDBACK

Was this guide useful?

Your answer helps us keep BISONKB accurate and practical.