Microsoft Kernel Debug Network Adapter Driver

-->

Debugging is a popular tool used to get to the root cause of a bug. A bug can maninfest itself in many different ways. It can cause a system crash (blue screen/BSOD), it can cause an application crash, it can cause your system to freeze to name a few issues. The root cause can be in the OS, a device driver or even a hardware issue.

To do kernel debugging over an Ethernet network cable, the target computer must have a supported network interface card (NIC).

During kernel debugging, the computer that runs the debugger is called the host computer, and the computer being debugged is called the target computer. For more information, see Setting Up KDNET Network Kernel Debugging Automatically.

For general information on supported network adapters see Supported Ethernet NICs for Network Kernel Debugging in Windows 10.

Version Information

The list of supported adapters is for the following versions of Windows

  • Windows 10, version 1903 (19H1) Build 18362

Related topics

-->

To do kernel debugging over an Ethernet network cable, the target computer must have a supported network interface card (NIC).

During kernel debugging, the computer that runs the debugger is called the host computer, and the computer being debugged is called the target computer. For more information, see Setting Up KDNET Network Kernel Debugging Automatically.

Microsoft Kernel Debug Network Adapter Driver

To do kernel debugging over a network cable, the target computer must have a supported network adapter. When the target computer is running Windows, the network adapters listed here are supported for kernel debugging.

Version Information

This topic lists the supported adapters for the following versions of Windows

  • Windows 10, version 2004 (20H1) Build 19041
  • Windows Server 2019

Adapter Support for Previous Releases of Windows 10

See these topics for information on supported versions of NICs in previous versions of Windows 10.

Microsoft kernel debug network adapter driver

Microsoft Kernel Debug Network Adapter Driver Windows 7 Free Download

Determining NIC support using VerifiedNicList.xml

To determine which set of NICs is supported for any particular release of Windows, examine the VerifiedNicList.xml file that is in the debuggers directory installed by the WDK that shipped with that particular release of Windows. For 64 bit Windows, by default, it will be installed in this directory:

Microsoft Kernel Debug Network Adapter Driver

C:Program Files (x86)Windows Kits10Debuggersx64VerifiedNicList.xml

Checking the VerifiedNicList.xml that ships in the WDK for a particular release, is required because additional hardware support is added to new releases of Windows that is not present in previous releases. So you must check the VerifiedNicLIst.xml file for that particular release.

Finding the vendor ID and device ID

To find the vendor ID and device ID of the network adapter on your target computer.

Descargar Microsoft Kernel Debug Network Adapter Driver Windows 10

  • On the target computer, open Device Manager (enter devmgmt in a Command Prompt window).
  • In Device Manager, locate the network adapter that you want to use for debugging.
  • Select and hold (or right-click) the network adapter node, and choose Properties.
  • In the Details tab, under Property, select Hardware Ids.

The vendor and device IDs are shown as VEN_VendorID and DEV_DeviceID. For example, if you see PCIVEN_8086&DEV_104B, the vendor ID is 8086, and the device ID is 104B.

Vendor ID 8086, Intel Corporation

For vendor ID 8086, these device IDs are supported:

00010008000C000D0438043A043C0440047010001001100410081009100C100D100E100F1010101110121013101410151016101710181019101A101D101E1026102710281049104A104B104C104D105E105F1060107110751076107710781079107A107B107C107D107E107F108A108B108C109610981099109A10A410A510A710A910B510B910BA10BB10BC10BD10BF10C010C210C310C410C510C610C710C810C910CB10CC10CD10CE10D310D510D610D910DA10DB10DD10DE10DF10E110E510E610E710E810EA10EB10EC10EF10F010F110F410F510F610F710F810F910FB10FC11A91501150215031507150A150B150C150D150E150F151015111514151615171518151C152115221523152415251526152715281529152A1533153415351536153715381539153A153B1546154A154D155715581559155A15601563156F1570157B157C15A015A115A215A315AA15AB15AC15AD15AE15B715B815B915BB15BC15BD15BE15D615D715D815DF15E015E115E215E317D01F401F411F451F631F72211B2159294C8976

Vendor ID 10EC, Realtek Semiconductor Corp.

For vendor ID 10EC, these device IDs are supported:

250226003000812581368137816181668167816881698225

Vendor ID 14E4, Broadcom

For vendor ID 14E4, these device IDs are supported:

1600160116141639163A163B163C163D163E16411642164316441645164616471648164A164C164D164E164F1650165316541655165616571659165A165B165C165D165E165F16621663166516681669166A166B166D166E1672167316741676167716781679167A167B167C167D167F168A168D168E1680168116821683168416861687168816901691169216931694169616981699169A169B169D16A016A116A216A416A516A616A716A816AA16AC16AE16B016B116B216B316B416B516B616B716C616C716C916CA16CE16CF16D016D116D216D516D616D716D816D916DD16DF16E016E216E316E416E916F016F116F716FD16FE16FF170D170E170FD802

Vendor ID 1969, Atheros Communications

For vendor ID 1969, these device IDs are supported:

10621063107310831090109110A010A110B010B110C010C110D010D110E010E110F010F120602062E091E0A1E0B1E0C1E0D1E0E1E0F1

Vendor ID 19A2, ServerEngines (Emulex)

For vendor ID 19A2, these device IDs are supported:

02110215022107000710

Vendor ID 10DF, Emulex Corporation

For vendor ID 10DF, these device IDs are supported:

0720E220

Vendor ID 15B3, Mellanox Technology

For vendor ID 15B3, these device IDs are supported:

1000100110021003100410051006100710081009100A100B100C100D100E100F10101013101510171019101B101D101F10211023102510271029102B102F63406341634A634B635463686369637267326733673C673D674667506751675A67646765676E6778

Vendor ID 1137, Cisco Systems Inc

For vendor ID 1137, these device IDs are supported:

0043

XML Supported NIC List

This is the same information shown above in the XML format.

Related topics