sodcalculator

10 Tech How-To

View Windows NDIS Traces or Logs: A Step-by-Step Guide

Guide 10-52166 · Updated · Step by step

This guide explains how to enable and view Windows NDIS (Network Driver Interface Specification) traces and logs. These logs record network driver activity and are essential for diagnosing network connectivity issues, driver failures, or performance problems. You’ll learn how to use built-in Windows tools like netsh and the Event Viewer to capture and read these traces without third-party software.

What You’ll Need

  • A Windows PC (Windows 10 or Windows 11 recommended, but the steps work on most modern versions).
  • Administrator account access to run commands and view logs.
  • Basic familiarity with the Command Prompt or PowerShell.

Step-by-Step

  1. Open an elevated Command Prompt or PowerShell. Click the Start button, type cmd or PowerShell, right-click the result, and select Run as administrator. Click Yes if prompted by User Account Control.
  2. Check if NDIS logging is enabled. Type the following command and press Enter:
    netsh trace show providers
    This lists all available trace providers. Look for Microsoft-Windows-NDIS in the list. If it’s present, NDIS tracing is supported on your system.
  3. Start an NDIS trace session. Run this command to begin capturing NDIS events:
    netsh trace start capture=yes provider=Microsoft-Windows-NDIS level=5
    The level=5 sets the trace verbosity to “verbose,” capturing the most detail. You can use level=4 (informational) for less noise.
  4. Reproduce the network problem. With tracing active, perform the action that causes the issue—for example, browse a website, connect to a VPN, or run a network diagnostic. This ensures the relevant events are captured.
  5. Stop the trace. Once you’ve reproduced the issue, stop the capture with:
    netsh trace stop
    Windows will process the trace and save the output. Note the file paths shown in the output—typically an .etl file and a .cab file in C:\Windows\Logs\netsh\.
  6. View the trace in Event Viewer. Press Win + R, type eventvwr.msc, and press Enter. In the left pane, expand Windows Logs and select System. Click Filter Current Log in the Actions pane. Under Event sources, check NDIS and NDIS.sys (if available), then click OK. This shows NDIS-related events that Windows has already logged.
  7. View the .etl file in Event Viewer. To open the captured trace file, in Event Viewer click Action → Open Saved Log. Navigate to the .etl file from Step 5 and open it. You’ll see the raw NDIS events with timestamps, levels, and details.
  8. Use the Message Analyzer (optional but powerful). Microsoft Message Analyzer (now archived but still downloadable) can open .etl files directly and parse NDIS events into readable tables. If you have it installed, open the .etl file from Step 5 and filter by provider name Microsoft-Windows-NDIS.
  9. Convert the trace to text (if needed). In the Command Prompt, run:
    netsh trace convert input=C:\Windows\Logs\netsh\YourTrace.etl
    This creates a .txt file with the same name, which you can open in Notepad. The text file contains the same events but in a plainer format.

Common Mistakes

  • Forgetting to run as administrator. The netsh trace commands fail with “Access denied” if you’re not elevated. Always use an admin command prompt.
  • Using the wrong provider name. The provider is Microsoft-Windows-NDIS, not NDIS alone. Typing it wrong yields “Provider not found.”
  • Stopping the trace too early. If you stop before reproducing the issue, the log won’t contain the relevant events. Keep it running until the problem occurs.
  • Ignoring the .cab file. The .cab file contains system information and the trace in a compressed format. It’s useful for support teams, but the .etl is what you want for local viewing.
  • Expecting human-readable text by default. The .etl file is binary. You must convert it or open it in a tool like Event Viewer or Message Analyzer to read it.

Tips

  • Use level=4 for routine checks. Verbose (level 5) generates a huge amount of data, which can slow your system. Use it only when you need deep detail.
  • Filter by event ID. In Event Viewer, common NDIS event IDs include 10400 (miniport initialization) and 10401 (miniport halt). Filtering by these IDs helps you find driver load/unload issues quickly.
  • Capture to a different location. Use trace start capture=yes provider=Microsoft-Windows-NDIS level=5 tracefile=C:\temp\ndis.etl to save the file where you can find it easily.
  • Pair with network monitor. If you need packet-level detail, combine NDIS traces with a network packet capture (like Wireshark). NDIS logs tell you what the driver did; packet captures show what actually went on the wire.
  • Check the System event log first. Often, the answer is already there. Look for NDIS warnings or errors before starting a new trace.

Troubleshooting

  • “The parameter is incorrect” when starting the trace. This usually means the provider name is misspelled or the level value is out of range (0-5). Double-check the command syntax.
  • No events appear in Event Viewer after opening the .etl. The trace file may be empty if you didn’t reproduce the issue or if the provider didn’t fire. Re-run the trace and perform the network action again.
  • Event Viewer shows “File is corrupt” for the .etl. The trace may have been interrupted (e.g., system crash). Try stopping the trace cleanly with netsh trace stop before viewing. If it’s still corrupt, re-capture.
  • Trace file is enormous (hundreds of MB). This is normal at level=5. Reduce the level to 4 or 3 for a shorter capture. You can also use netsh trace start ... maxsize=100 to limit the file to 100 MB (it will stop when full).
  • Cannot find the .etl file. The default path is C:\Windows\Logs\netsh\, but if you specified a different path in the tracefile parameter, look there. The netsh trace stop output also shows the exact location.
  • NDIS provider doesn’t appear in the provider list. This is rare but can happen on very old Windows versions. Ensure your network drivers are up to date, then try again. If it’s still missing, use the System event log instead—it captures NDIS events without the extra provider.

Frequently Asked Questions

Q: What is an NDIS trace used for?
A: It records low-level interactions between Windows and your network adapter driver. It’s used to diagnose driver crashes, adapter resets, connectivity drops, and performance issues that aren’t visible in normal network tools.

Q: Can I view NDIS logs without the command prompt?
A: Yes. The Event Viewer’s System log already contains many NDIS events (source: NDIS). For detailed traces, you need the command prompt to start a capture, but you can view the resulting file in Event Viewer.

Q: How long can I run an NDIS trace?
A: As long as you want, but the log file grows quickly at verbose levels. Use the maxsize parameter to cap the size, or keep the trace short (a few minutes) to capture the problem event.

Q: Is there a way to see NDIS logs in real time?
A: Yes. In Event Viewer, right-click System log and select Enable Log (it’s usually on by default). Then, while reproducing the issue, watch the log refresh. You can also use netsh trace start and then open the .etl file after stopping—it’s not live, but it’s immediate.

Q: Do I need to install anything to use netsh trace?
A: No. netsh is built into Windows. The only optional tool is Microsoft Message Analyzer for easier .etl viewing, but it’s not required.

Q: What’s the difference between an NDIS trace and a packet capture?
A: An NDIS trace logs what the network driver is doing (initialization, resets, power events, errors). A packet capture (e.g., Wireshark) shows the actual network packets. They answer different questions: NDIS tells you about driver health; packet capture tells you about network traffic.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →