Windows Bug Check 0x000000BC: NETWORK_BOOT_DUPLICATE_ADDRESS – Causes and Troubleshooting

Quick Answer

NETWORK_BOOT_DUPLICATE_ADDRESS (Bug Check 0x000000BC) is a Windows stop error that occurs when a computer attempts to boot from a network and detects that another device is already responding to the same IP address assigned to it.

Windows detects the conflict when the TCP/IP networking component sends an Address Resolution Protocol (ARP) request to verify its IP address and receives a response indicating that another machine is using that address. Because duplicate IP addressing prevents reliable network communication during network boot, Windows treats this condition as a fatal error.

The primary troubleshooting approach is to identify the conflicting IP address, determine which device is responding to it, inspect DHCP assignments and static IP configurations, and correct the addressing conflict before attempting another network boot.

What Is NETWORK_BOOT_DUPLICATE_ADDRESS (0x000000BC)?

NETWORK_BOOT_DUPLICATE_ADDRESS is a Windows bug check, also known as a Stop error or Blue Screen of Death (BSOD), with the hexadecimal value 0x000000BC.

This error is specifically associated with Windows network boot operations. Network booting allows a computer to start its operating system or deployment environment using resources supplied over a network rather than relying entirely on a locally installed operating system.

During this process, Windows initializes its networking components and verifies that the assigned IP address is not already in use. If another device responds to the address verification request, Windows identifies a duplicate IP address condition and generates the 0x000000BC bug check.

Microsoft documents this bug check in its Windows driver documentation:

Microsoft Learn: Bug Check 0xBC – NETWORK_BOOT_DUPLICATE_ADDRESS

Where Does This Error Occur?

The error is associated with Windows starting through a network-based boot process. Common environments where network booting is used include:

• PXE boot: Preboot Execution Environment allows a computer to start using boot files and operating system deployment resources provided by a network server.
• Windows Deployment Services (WDS): Network-based Windows deployment infrastructure used to install or deploy Windows operating systems.
• Enterprise imaging environments: Organizations may use network booting to deploy standardized operating system images across multiple computers.
• Network-based recovery environments: Certain recovery and maintenance environments use network resources to start or restore computers.
• Diskless workstation environments: Computers without a conventional local operating system installation may rely on network-based startup.

The presence of this bug check does not establish that the DHCP server, PXE server, network adapter or a particular driver is defective. The documented condition is an IP address conflict detected during network boot.

Understanding the Technical Cause

How the duplicate IP address is detected

Every device communicating over an IPv4 network requires an IP address. Within the same network segment, an IP address must identify the intended device rather than multiple independently operating devices.

Windows uses Address Resolution Protocol (ARP) to associate IPv4 addresses with hardware addresses, such as Ethernet MAC addresses.

During network boot, the relevant sequence is:

1. The computer starts its network boot process.
2. The network infrastructure provides an IP address to the computer, commonly through DHCP.
3. Windows initializes TCP/IP networking.
4. TCP/IP sends an ARP request to check whether another device is responding for the assigned IP address.
5. Another device responds, indicating that the address is already associated with a different machine.
6. Windows detects the duplicate IP address condition.
7. The network boot operation encounters a fatal error and generates bug check 0x000000BC.

What is ARP?

Address Resolution Protocol (ARP) is an IPv4 networking protocol that helps devices determine the hardware address associated with an IPv4 address on a local network segment.

For example, if a computer needs to communicate with another device at 192.168.1.50, it can use ARP to discover the MAC address associated with that IP address.

If a different device responds for an IP address that the computer is attempting to use, the response can indicate an addressing conflict.

ARP is defined in RFC 826 – An Ethernet Address Resolution Protocol.

Common Causes of Error 0x000000BC

The bug check identifies a duplicate IP address condition, but the underlying reason for the conflict must be investigated in the network environment.

1. Duplicate static IP address

Two computers or network devices may have been manually configured with the same static IPv4 address.

For example, a workstation may be configured with 192.168.1.100, while another computer or server already uses that address.

2. DHCP scope configuration problems

A DHCP server dynamically assigns IP addresses to network clients. Incorrect scope configuration, overlapping address ranges or conflicting reservations can contribute to duplicate address assignments.

3. Static IP addresses overlapping the DHCP pool

A common network administration mistake is assigning static IP addresses from the same range that the DHCP server uses for automatic allocation.

If the DHCP server is unaware that an address is already configured manually on another device, it may assign that address to a different client.

4. Incorrect DHCP reservations

A DHCP reservation associates a specific IP address with a device's hardware address or client identifier. Incorrect reservations, duplicate reservation entries or outdated device information can contribute to address conflicts.

5. Multiple DHCP servers

Two unauthorized or incorrectly configured DHCP servers on the same network segment may distribute overlapping address ranges or inconsistent network settings.

6. Stale or incorrect network configuration

Changes to network infrastructure, device replacements, cloned workstation configurations or incorrectly restored system images may leave conflicting IP address settings in place.

7. Network segmentation or VLAN configuration problems

Incorrect VLAN assignments, overlapping subnet configurations or unintended Layer 2 connectivity between network segments may expose devices to unexpected address conflicts.

These are possible contributing conditions, not individually confirmed causes of every 0x000000BC occurrence.

Understanding Bug Check Parameters

The 0x000000BC bug check provides four parameters that can help administrators and technical support personnel investigate the duplicate IP address.

Parameter	Description
Parameter 1	The IP address represented as a DWORD value.
Parameter 2	Part of the hardware address of the other machine responding to the duplicate address check.
Parameter 3	Additional hardware address information for the other machine.
Parameter 4	Additional hardware address information. For an Ethernet connection, this parameter is zero.

Parameter 1 – Conflicting IP address

Parameter 1 contains the IP address as a DWORD (32-bit value).

Microsoft specifies that an IP address in the format aa.bb.cc.dd appears as 0xDDCCBBAA.

For example, consider the IPv4 address:

192.168.1.50

Its DWORD representation, following the byte ordering documented by Microsoft, is:

0x3201A8C0

This value corresponds to the IP address whose bytes are C0 A8 01 32 in hexadecimal.

Parameters 2, 3 and 4 – Hardware address

These parameters provide information about the hardware address of the other device responding to the duplicate IP address check.

For an Ethernet connection, Parameter 4 is zero. In this case, the MAC address is stored across Parameters 2 and 3.

Microsoft provides the following representation rule:

• Parameter 2 contains the first four MAC address bytes.
• Parameter 3 contains the remaining two MAC address bytes in the documented representation.
• Parameter 4 equals zero for Ethernet.

For example, an Ethernet MAC address in the format:

AA-BB-CC-DD-EE-FF

Is represented as:

Parameter 2: 0xAABBCCDD
Parameter 3: 0xEEFF0000
Parameter 4: 0x00000000

These values can assist an administrator in identifying the device responsible for responding to the conflicting IP address.

How to Troubleshoot and Fix NETWORK_BOOT_DUPLICATE_ADDRESS

The most effective solution is to resolve the IP address conflict at the network level. Start with non-disruptive diagnostic checks before changing DHCP scopes, reservations or device configurations.

Step 1: Record the bug check information

Before making network changes, record the following information from the blue screen or crash dump:

• Bug check code: 0x000000BC.
• Bug check name: NETWORK_BOOT_DUPLICATE_ADDRESS.
• All four bug check parameters.
• The affected computer's MAC address, if available.
• The network segment or VLAN where the computer is attempting to boot.
• The approximate time of the failure.

Parameter 1 is particularly useful because it identifies the conflicting IP address.

Step 2: Identify the conflicting IP address

Convert Parameter 1 into the IPv4 address using the byte ordering documented by Microsoft.

For example:

Parameter 1: 0x3201A8C0
IP address: 192.168.1.50

Use the actual parameter value from the affected computer rather than assuming that the example address is involved.

Step 3: Check the ARP table from another computer

Use a working computer connected to the same network segment to investigate which MAC address currently responds for the conflicting IP address.

Open Command Prompt and run:

arp -a

To inspect a specific address, use:

arp -a 192.168.1.50

Replace the example IP address with the address identified from Parameter 1.

The ARP table may display an associated physical address and interface. However, an entry is not guaranteed to be available or current.

For a more targeted investigation, clear the relevant ARP cache entry if supported by the operating system and permissions, then generate traffic to the target address and inspect the newly learned entry. Be aware that ARP cache changes can temporarily affect network communication.

Important: An ARP table entry alone does not prove that the responding device caused the original boot failure. ARP entries can be stale, and the network may have changed since the crash occurred.

Step 4: Check DHCP leases and reservations

If the network uses Windows DHCP Server, an administrator should inspect the relevant DHCP scope.

Open the DHCP management console and navigate to:

DHCP
  > IPv4
    > Relevant Scope
      > Address Leases

Check for:

• The conflicting IP address.
• The device name associated with the lease.
• The client's hardware address or client identifier.
• Duplicate or unexpected reservations.
• Address conflict or bad-address entries, where available.
• Unexpected leases from devices that are no longer connected.

For PowerShell-based inspection, an administrator with the DHCP Server PowerShell tools installed can use:

Get-DhcpServerv4Lease -ComputerName DHCP01 -ScopeId 192.168.1.0

To inspect the lease information for the relevant scope, replace DHCP01 with the actual DHCP server name and 192.168.1.0 with the correct scope ID.

Where the installed DHCP module and server version expose the relevant lease state, an administrator can also inspect address conflict information:

Get-DhcpServerv4Lease -ComputerName DHCP01 -ScopeId 192.168.1.0 |
    Format-Table IPAddress, HostName, ClientId, AddressState

The availability of individual properties can depend on the Windows Server and DHCP PowerShell module version.

Step 5: Check for unauthorized DHCP servers

If the network has multiple DHCP servers, verify that each one is authorized and configured with the correct scopes.

On an appropriately administered Windows DHCP server, the following command can display authorized DHCP servers in Active Directory:

Get-DhcpServerInDC

This command requires the appropriate DHCP PowerShell tools and permissions. It does not independently identify every possible unauthorized DHCP service on a network.

If an unauthorized router, access point or other device is distributing DHCP addresses, investigate its configuration and correct the network design.

Step 6: Check devices configured with static IP addresses

Identify servers, printers, network appliances, workstations and other devices that may be manually configured with the conflicting IP address.

Where a device is using an IP address that overlaps the DHCP allocation range, review the addressing plan.

Possible corrective actions include:

• Changing the static IP address to an unused address within the correct subnet.
• Creating an appropriate DHCP reservation.
• Excluding statically assigned addresses from the DHCP dynamic pool.
• Removing duplicate or outdated address reservations.

Do not change an address until its ownership and dependencies have been verified.

Step 7: Correct the DHCP scope configuration

If the conflict is caused by an overlapping DHCP range, correct the scope configuration.

For example, if an organization uses a DHCP pool that overlaps with addresses reserved for manually configured servers, adjust the dynamic range or create appropriate exclusions.

Before changing the scope:

1. Document the current scope configuration.
2. Identify all static IP addresses and reservations.
3. Check existing leases and active devices.
4. Determine a valid address range for dynamic allocation.
5. Apply the smallest necessary configuration change.
6. Monitor DHCP leases and network connectivity after the change.

Changing a DHCP scope can affect multiple clients. Perform the change under the organization's normal network change-management procedure.

Step 8: Review PXE and network boot configuration

After correcting the addressing conflict, review the network boot environment.

Check the following:

• The DHCP server is providing the correct network configuration.
• The affected client receives an appropriate IP address.
• The PXE or deployment server is reachable from the client network.
• The correct VLAN and subnet are assigned to the computer's switch port.
• Network boot services are functioning normally.
• No other device is responding for the newly assigned address.

Do not modify PXE server configuration or DHCP boot options without evidence that they are contributing to the problem. The documented 0x000000BC condition is a duplicate IP address detected during network boot.

Step 9: Retry network boot and verify the result

Once the IP address conflict has been corrected:

1. Ensure that the conflicting address is no longer being used by another device.
2. Verify the DHCP scope and reservation configuration.
3. Restart the affected computer.
4. Initiate the network boot process again.
5. Confirm that the computer receives the intended IP address.
6. Verify that Windows or the deployment environment starts successfully.

If the same bug check occurs again, collect the new bug check parameters and investigate whether another device or network segment is causing the conflict.

Using Windows Debugging Tools to Analyze the Crash

In enterprise troubleshooting environments, a Windows crash dump can provide additional information about the failure.

Microsoft WinDbg can be used to inspect Windows crash dump files. After opening the relevant dump file, run:

!analyze -v

This command displays detailed bug check information and available debugging analysis.

Review the reported bug check code and parameters, and compare them with the official 0xBC documentation.

For this specific bug check, the four parameters are important because they contain the conflicting IP address and information about the other machine's hardware address.

Official documentation:

Microsoft Learn – Bug Check 0xBC

How to Prevent Duplicate IP Address Conflicts

Organizations that use network booting, PXE deployment or centrally managed DHCP infrastructure should maintain a consistent IP address management process.

1. Maintain a centralized IP address plan

Document the IP addresses used by servers, printers, switches, access points, workstations and other network devices.

2. Avoid overlapping static and dynamic address ranges

Reserve appropriate address ranges for manually configured devices and ensure that DHCP dynamic allocation does not overlap with those addresses.

3. Use DHCP reservations where appropriate

For devices requiring predictable IP addresses, DHCP reservations can help centralize address assignment and reduce manual configuration errors.

4. Monitor DHCP address conflicts

Periodically review DHCP leases, scope utilization, reservations and address conflict records. Investigate repeated conflicts rather than simply removing the visible warning.

5. Control DHCP server deployment

Prevent unauthorized DHCP servers from operating on production network segments. Ensure that routers, wireless access points and other network devices have the intended DHCP configuration.

6. Review network segmentation

Maintain correct VLAN, subnet and DHCP relay configurations. Unintended connectivity between network segments can introduce addressing problems and make troubleshooting more difficult.

7. Validate deployment images and network boot workflows

For organizations deploying large numbers of computers, verify that cloned systems and deployment configurations do not introduce duplicate network settings.

When Should You Contact Network Support?

Escalate the issue to a network administrator or infrastructure support team when:

• The duplicate IP address continues to appear after DHCP configuration has been reviewed.
• The responding MAC address cannot be identified.
• Multiple computers experience network boot failures.
• Several DHCP servers or VLANs are involved.
• The issue affects production servers or business-critical systems.
• The conflict appears intermittently or changes between devices.
• Network boot continues to fail despite correcting the known address conflict.

Provide the bug check parameters, affected IP address, client MAC address, network segment, DHCP lease information and relevant crash dump details to help the support team investigate efficiently.

Frequently Asked Questions (FAQs)

1. What does Windows error 0x000000BC mean?

Error 0x000000BC, named NETWORK_BOOT_DUPLICATE_ADDRESS, means Windows detected that another machine was responding for the IP address assigned to the computer during network boot.

2. Is NETWORK_BOOT_DUPLICATE_ADDRESS a hardware failure?

Not necessarily. Microsoft documents this bug check as a duplicate IP address condition detected through ARP. The underlying cause is generally investigated through network addressing, DHCP and device configuration rather than assuming a hardware failure.

3. Can a DHCP server cause error 0x000000BC?

DHCP configuration can contribute to duplicate IP address assignments, particularly when dynamic allocation overlaps with static addresses or incorrect reservations. However, the bug check alone does not prove that the DHCP server is responsible.

4. What is the difference between an IP address conflict and error 0x000000BC?

An IP address conflict is a general networking condition in which multiple devices use or respond for the same IP address. Error 0x000000BC is a specific Windows bug check associated with detecting that condition during network boot.

5. What does Parameter 1 indicate in bug check 0xBC?

Parameter 1 contains the conflicting IP address in DWORD format. Microsoft documents that an address written as aa.bb.cc.dd appears as 0xDDCCBBAA.

6. What do Parameters 2 and 3 indicate?

Parameters 2 and 3 contain hardware address information for the other machine responding to the duplicate address check. For Ethernet, the MAC address is represented across these two parameters, while Parameter 4 is zero.

7. Can changing the IP address fix NETWORK_BOOT_DUPLICATE_ADDRESS?

Changing the conflicting IP address can resolve the issue if the actual cause is a duplicate static assignment or incorrect address allocation. However, the change must be made on the correct device and coordinated with the DHCP configuration to prevent the conflict from recurring.

8. Does this error mean the PXE server is faulty?

No. The error specifically identifies a duplicate IP address detected during network boot. The PXE server may be functioning correctly even when the client cannot complete its startup because of an addressing conflict.

9. Can a duplicate IP address cause a blue screen during network boot?

Yes. Microsoft explicitly documents that this condition is fatal when Windows is booting from a network, resulting in bug check 0x000000BC.

10. Will updating the network adapter driver fix error 0x000000BC?

A driver update should not be treated as the primary solution without evidence of a driver-related problem. First investigate the duplicate IP address and the device responding to the ARP request. Consider driver troubleshooting only if additional evidence points to a network adapter or driver issue.

Key Takeaways

• 0x000000BC is the Windows bug check code for NETWORK_BOOT_DUPLICATE_ADDRESS.
• It occurs when Windows detects another machine responding for its assigned IP address during network boot.
• Microsoft identifies ARP-based duplicate address detection as the underlying condition.
• Parameter 1 identifies the conflicting IP address in DWORD format.
• Parameters 2 and 3 contain hardware address information for the other responding machine; Parameter 4 is zero for Ethernet.
• DHCP scope conflicts, overlapping static addresses and incorrect reservations are possible contributing conditions that should be investigated.
• The appropriate resolution is to identify the conflicting device and correct the network addressing configuration.

Official References

1. Microsoft Learn – Bug Check 0xBC: NETWORK_BOOT_DUPLICATE_ADDRESS
2. Microsoft Learn – Bug Check Code Reference
3. RFC 826 – An Ethernet Address Resolution Protocol
4. Microsoft Learn – Get-DhcpServerv4Lease PowerShell Reference
5. Microsoft Learn – Get-DhcpServerInDC PowerShell Reference