WindowsAdvanced

0x000000BB NETWORK_BOOT_INITIALIZATION_FAILED – Causes and Troubleshooting Guide

Quick Answer The 0x000000BB NETWORK_BOOT_INITIALIZATION_FAILED error is a Windows Stop error (Blue Screen of Death or BSOD) indicating that Windows failed to...

Bison Technical Team Enterprise IT specialists

Updated 08 Nov 2026 13 min read 10 total views

Structured technical guidanceSafety notes included where requiredSources listed below

Quick Answer

The 0x000000BB NETWORK_BOOT_INITIALIZATION_FAILED error is a Windows Stop error (Blue Screen of Death or BSOD) indicating that Windows failed to complete a critical initialization operation while booting from a network.

According to Microsoft, the error occurs when a critical function fails during I/O initialization as Windows attempts to start from a network source. The failure can involve registry updates, initialization of the Windows network stack, or communication between the network subsystem and TCP/IP.

This error is particularly relevant to systems using network-based boot environments, such as remote boot infrastructure and enterprise deployment environments. It should not automatically be interpreted as a general internet connectivity problem.

The correct troubleshooting approach is to identify the failed initialization stage, examine the bug check parameters, and investigate the network boot infrastructure, relevant drivers and system configuration.

What Is NETWORK_BOOT_INITIALIZATION_FAILED?

NETWORK_BOOT_INITIALIZATION_FAILED is a Windows kernel bug check identified by the following values:

Property	Value
Error name	NETWORK_BOOT_INITIALIZATION_FAILED
Bug Check Code	0x000000BB
Decimal value	187
Error category	Windows Stop Error / Bug Check
Related subsystem	Network boot and Windows network initialization
Primary context	Windows booting from a network

A bug check is a protective mechanism through which Windows stops execution when it encounters a critical kernel-level condition that prevents safe system operation.

Microsoft documents this particular error in its Windows driver debugging reference:

Microsoft Learn – Bug Check 0xBB: NETWORK_BOOT_INITIALIZATION_FAILED.

When Does This Error Occur?

This bug check is associated with network-based Windows startup. During network boot, Windows must initialize the components required to communicate with the network and access the resources needed to continue the boot process.

The initialization process can involve:

Updating registry information required for network initialization.
Starting the Windows network protocol stack.
Initializing network redirector and datagram receiver components.
Communicating with TCP/IP to register the system's IP address through DHCP-related initialization.
Establishing the network communication required for continued startup.

If a critical operation in this process fails, Windows can generate the 0x000000BB bug check.

Understanding the 0x000000BB Bug Check Parameters

The error provides four bug check parameters. These parameters are important when diagnosing the actual failure rather than relying only on the displayed stop code.

Parameter	Description
Parameter 1	Identifies the stage of network initialization that failed.
Parameter 2	Contains the failure status.
Parameter 3	Reserved.
Parameter 4	Reserved.

Parameter 1: Identifying the Failed Initialization Stage

Microsoft documents three possible values for the first parameter:

Parameter 1 Value	Failure Stage	Explanation
1	Registry update	Windows encountered a failure while updating the registry during network initialization.
2	Network stack startup	The network stack failed to initialize successfully. Windows sends I/O control requests (IOCTLs) to the redirector and datagram receiver and waits for the redirector to become ready. The error can occur if it does not become ready within the required period.
3	DHCP initialization	Windows failed while sending the DHCP-related IOCTL to TCP. This operation informs the transport subsystem of the system's IP address.

Parameter 2: Failure Status

The second parameter contains the status associated with the failed operation.

This value is useful for advanced troubleshooting because it can help identify the nature of the underlying failure. Its meaning should be determined using the appropriate Windows debugging and status-code documentation rather than assuming that every value represents the same network problem.

Parameters 3 and 4

These parameters are reserved for this bug check. They do not have documented diagnostic meanings for ordinary troubleshooting of this error.

Possible Causes of NETWORK_BOOT_INITIALIZATION_FAILED

The exact cause depends on the network boot environment and the initialization stage identified by Parameter 1. The following are areas worth investigating, not confirmed causes in every occurrence.

1. Network Stack Initialization Failure

Windows relies on its network stack to initialize network communication. If the redirector, datagram receiver or associated networking components fail to become ready, the system may be unable to continue network-based startup.

Investigate the network initialization failure, relevant system components and the second bug check parameter.

2. DHCP Communication Problems

Dynamic Host Configuration Protocol (DHCP) provides network configuration information, including IP addresses, to network clients.

In a network boot environment, incorrect DHCP configuration, unavailable DHCP services or communication failures can interrupt the boot process.

However, a DHCP problem should not be assumed solely because the error contains the word NETWORK_BOOT. Confirm the failure stage and inspect the relevant network traffic or server logs.

3. Network Adapter Driver Problems

Windows requires an appropriate network adapter driver to communicate with the network hardware.

Incompatible, missing or malfunctioning drivers may interfere with network initialization, particularly in deployment environments where Windows Preinstallation Environment (WinPE) or a network boot image requires additional network adapter support.

Check whether the network adapter is recognized and whether its driver is compatible with the boot environment.

4. Incorrect Network Boot Configuration

Network boot depends on coordinated configuration between the client computer, network infrastructure and boot server.

Potential configuration issues include:

Incorrect PXE or network boot settings.
Incorrect VLAN assignments.
Missing or incorrect DHCP relay or IP helper configuration.
Incorrect boot server configuration.
Firewall rules blocking required network communication.
Incorrect boot image or boot program configuration.

5. Registry Initialization Failure

If Parameter 1 is 1, investigate the registry update operation associated with network initialization.

Possible areas to examine include registry access, system configuration integrity, storage availability and relevant system logs.

Do not modify registry keys or permissions without identifying the affected component and understanding the consequences of the change.

6. Network Boot Infrastructure Problems

In enterprise environments, network boot may depend on several services, including DHCP, Windows Deployment Services (WDS), deployment servers, routers and network switches.

Failure or misconfiguration of these services can interrupt the boot process.

Check the health of the relevant infrastructure components before making changes to the Windows client.

How to Troubleshoot 0x000000BB NETWORK_BOOT_INITIALIZATION_FAILED

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

Step 1: Identify Whether the System Uses Network Boot

First determine how Windows is being started.

Check whether the computer is configured to boot using PXE or another network-based boot method.
Determine whether the computer is part of an enterprise deployment environment.
Check whether the error appears during network boot, Windows installation or a subsequent startup operation.
Identify whether the issue affects one computer or multiple computers.

If the computer normally boots from its internal SSD or hard drive and is not configured for network boot, do not immediately assume that the network infrastructure is responsible. Examine the crash dump and confirm that the reported bug check and parameters are accurate.

Step 2: Check Network Hardware and Physical Connectivity

For systems using network boot, inspect the physical network connection.

Check whether the Ethernet cable is securely connected.
Verify that the network switch port is operational.
Check the network adapter link indicators.
Confirm that the correct network interface is being used for booting.
Where possible, test with a known-working network cable and switch port.

If the computer is configured to boot through a wireless connection, verify whether the specific boot environment supports that method. Standard PXE network boot commonly uses a supported wired network interface.

Step 3: Verify BIOS/UEFI Network Boot Settings

Incorrect firmware settings can prevent a computer from initiating the expected network boot process.

Restart the computer and enter the BIOS/UEFI setup utility.
Locate the Boot Configuration or Boot Priority settings.
Check whether network boot or PXE boot is enabled, if required by the deployment environment.
Verify that the correct network adapter is selected.
Check whether the boot mode is configured for UEFI or Legacy BIOS according to the deployment infrastructure.
Save any necessary changes and restart the computer.

Important: Do not switch between UEFI and Legacy BIOS modes without checking the existing operating system installation and deployment configuration. An incorrect boot-mode change can make an otherwise functional installation unbootable.

Step 4: Check DHCP and PXE Server Availability

If the computer uses PXE boot, verify that the required network services are operational.

Confirm that the DHCP server is running and responding to client requests.
Verify that the PXE-enabled deployment server is operational.
Check whether the client receives a valid IP address during network boot.
Confirm that the deployment server can provide the appropriate network boot program.
Review DHCP and PXE server logs for failed requests or communication errors.
Verify that network security devices are not blocking the required communication.

For Microsoft Configuration Manager environments, the documented PXE troubleshooting process includes checking the following ports where applicable:

Port	Protocol	Purpose
67	UDP	DHCP server communication.
68	UDP	DHCP client communication.
69	UDP	TFTP boot-file transfer.
4011	UDP	PXE Boot Information Negotiation Layer (BINL) communication.

Port requirements can vary according to the deployment architecture. Verify the actual network requirements before modifying firewall rules.

Microsoft provides additional guidance in its Advanced Troubleshooting for PXE Boot Issues.

Step 5: Verify Network Routing and VLAN Configuration

In environments where the client computer and PXE server are on different subnets, DHCP relay or IP helper configuration may be necessary.

Identify the VLAN assigned to the client computer.
Verify that the client subnet can communicate with the DHCP server.
Confirm that the router or Layer 3 switch forwards the required PXE requests to the correct servers.
Verify that the PXE server is reachable from the client network.
Check whether firewall or access control policies are blocking the communication.

Incorrect routing or missing IP helper entries can prevent PXE requests from reaching the appropriate servers.

For additional information, refer to Microsoft's documentation on booting from a PXE server on a different network.

Step 6: Check Network Adapter Drivers

Verify that the network adapter driver is available and compatible with the relevant Windows boot environment.

For systems using Windows Preinstallation Environment (WinPE):

Identify the network adapter manufacturer and model.
Obtain the appropriate driver from the computer or network adapter manufacturer's official support website.
Verify that the driver supports the relevant Windows PE environment and architecture.
Check whether the required network adapter driver is included in the deployment boot image.
If the driver is missing, add the appropriate driver to the boot image using the supported deployment procedure.
Update the boot image on the deployment server and test network boot again.

Only add drivers that are actually required. Unnecessary drivers can complicate deployment image maintenance.

For Microsoft Configuration Manager deployments, the SMSTS.log file can provide useful information about network adapter detection and initialization during task sequence execution.

Step 7: Examine the Bug Check Parameters

If Windows generates a 0x000000BB stop error, examine the four parameters to identify the failed initialization stage.

Pay particular attention to Parameter 1:

Value 1: Investigate the registry update operation.
Value 2: Investigate network stack startup and redirector initialization.
Value 3: Investigate the DHCP-related IOCTL operation and TCP initialization.

Use Parameter 2 to investigate the reported failure status. This information helps narrow down the diagnostic process.

Advanced Troubleshooting Using WinDbg

For recurring crashes or situations where the cause is not apparent, system administrators and technical professionals can analyze the Windows crash dump using WinDbg.

Prerequisites

A Windows computer with access to the crash dump file.
WinDbg installed from Microsoft's official distribution.
Access to the appropriate debugging symbols.
Sufficient permissions to access the dump file.

Step 1: Locate the Crash Dump

Windows may save crash information in one of the following locations, depending on the configured dump type:

C:\Windows\MEMORY.DMP – Kernel or complete memory dump, depending on configuration.
C:\Windows\Minidump\ – Small memory dump files, if configured.

Check the system's startup and recovery settings to determine which dump type is configured.

Step 2: Open the Dump File in WinDbg

Install and launch WinDbg.
Select the option to open a crash dump.
Browse to the relevant .dmp file.
Open the file and allow the debugger to load the necessary information.
Configure the Microsoft public symbol server if required.

The recommended public symbol server path is:

https://msdl.microsoft.com/download/symbols

Step 3: Run the Bug Check Analysis Command

Enter the following command in the WinDbg command window:

!analyze -v

This command displays a detailed analysis of the crash, including the bug check information and other available diagnostic details.

Step 4: Examine the Bug Check Parameters

Locate the bug check analysis section and identify:

The bug check code.
The four bug check parameters.
The failure status.
Relevant driver or module information, if available.
The call stack and associated diagnostic information.

You can also use the following command to display the basic bug check information:

.bugcheck

The command helps verify the bug check code and its parameters.

Important: A module name appearing in a crash analysis is not automatically proof that the corresponding driver caused the failure. Interpret the complete debugging output and supporting evidence before identifying a root cause.

Microsoft's official references:

How to Verify Whether the Problem Is Resolved

After completing the necessary troubleshooting steps, verify that the network boot process works correctly.

Restart the affected computer.
Initiate the configured network boot process.
Confirm that the network adapter is detected.
Verify that the computer receives the expected network configuration.
Confirm that the boot server responds and supplies the appropriate boot files.
Check that Windows or the relevant deployment environment continues starting without generating the same bug check.
Review server and client logs for any remaining network initialization errors.

If the error continues, collect the updated crash dump, bug check parameters, relevant system logs and network infrastructure logs before attempting further modifications.

How to Prevent NETWORK_BOOT_INITIALIZATION_FAILED

The following practices can help reduce network boot failures in enterprise and deployment environments:

Keep network adapter drivers compatible with the deployed Windows and WinPE versions.
Maintain correct DHCP and PXE server configurations.
Verify network routing, VLAN assignments and IP helper settings.
Monitor the availability of DHCP and deployment services.
Ensure that required network communication is permitted by firewall policies.
Test updated boot images before deploying them to production environments.
Maintain backups of working deployment images and network configurations.
Document firmware and network boot settings for supported hardware models.
Regularly review deployment logs and investigate recurring initialization failures.

Frequently Asked Questions (FAQs)

1. What does error 0x000000BB NETWORK_BOOT_INITIALIZATION_FAILED mean?

It means Windows failed to complete a critical initialization operation while booting from a network. Microsoft identifies registry updates, network stack startup and DHCP-related TCP initialization as possible failure stages.

2. Is NETWORK_BOOT_INITIALIZATION_FAILED a network adapter driver error?

Not necessarily. A network adapter driver issue is one area worth investigating, but the error can also involve registry updates, network stack initialization or DHCP-related operations. The bug check parameters and diagnostic evidence should be examined to identify the actual cause.

3. Can DHCP problems cause error 0x000000BB?

DHCP-related initialization is one of the documented failure stages. If Parameter 1 is 3, investigate the DHCP-related IOCTL operation and TCP initialization. However, not every occurrence of this bug check is caused by DHCP.

4. What does Parameter 1 mean in the 0x000000BB error?

Parameter 1 identifies the network initialization stage that failed. The documented values are 1 for registry updating, 2 for network stack startup and 3 for the DHCP-related IOCTL operation to TCP.

5. How can I find the exact cause of this BSOD?

Collect the Windows crash dump and analyze it using WinDbg. Run !analyze -v and examine the bug check parameters, failure status and available call stack information. Also correlate the results with relevant network boot and system logs.

6. Does this error occur during normal Windows startup?

The documented meaning of this bug check specifically concerns Windows failing to boot from a network. If it appears on a computer that normally starts from an internal drive, investigate the crash dump and boot configuration instead of assuming that an ordinary internet connection problem is responsible.

7. Is 0x000000BB the same as a PXE boot error?

No. The 0x000000BB code is a Windows kernel bug check. PXE boot errors are separate failures that can occur during earlier stages of network startup. Both involve network boot environments, but they do not necessarily indicate the same failure or require the same solution.

Key Takeaways

0x000000BB identifies the NETWORK_BOOT_INITIALIZATION_FAILED Windows bug check.
It indicates that Windows could not complete a critical operation while booting from a network.
Parameter 1 identifies the failed initialization stage: registry update, network stack startup or DHCP-related initialization.
Parameter 2 contains the failure status and can assist with advanced diagnosis.
DHCP, PXE infrastructure, network configuration and drivers are relevant areas to investigate according to the actual boot environment.
WinDbg and Windows crash dumps provide additional diagnostic information for recurring failures.
Changes to production deployment infrastructure should be made only after collecting sufficient diagnostic evidence and preserving the existing configuration.

Official References

YOUR FEEDBACK

Was this guide useful?

Your answer helps us keep BISONKB accurate and practical.