Log Dejargonizer

Windows System Log · Event 6062

Event 6062: 'Lso was triggered' from your network adapter

Your wireless or wired adapter driver logged that a network offload feature was used. It is a debugging message that Intel left switched on in shipping drivers. Nothing is wrong, nothing needs fixing, and it is one of the most searched-for harmless warnings in Event Viewer.

Also written as Event ID 6062Lso was triggeredLSO was triggered on adapter6062 netwtw08 warning

What it means for you

On a personal computer

This one is genuinely nothing. LSO stands for Large Send Offload — a normal feature where your network card breaks big chunks of data into packets so the processor does not have to. The driver logs a note every time it does it. Windows shows it as a Warning, which makes it look like a problem it is not.

For an analyst

Netwtw08, Netwtw10, Netwtw12 and Netwtw14 are Intel wireless drivers and are the usual sources; some Killer and Realtek drivers log the same way. It is diagnostic chatter, not an error path. The one operational note worth keeping is that LSO and its cousin large receive offload do occasionally interact badly with virtualisation and VPN software, so the feature is sometimes disabled deliberately — but do that because you have a real symptom, never because of this event.

The fields that decide it

Everything else in the log line is context.

Source or provider
The driver that logged it. Netwtw## names an Intel wireless adapter; the number is the driver generation, not a severity.
Adapter name
Which network interface. On a laptop with both Wi-Fi and Ethernet it tells you which one is chattering, which is otherwise the only thing distinguishing these entries.
Frequency
Not a field, but the only thing worth measuring. Hundreds a day is normal for this message and does not indicate escalating trouble.
Actual symptoms
Whether the network is dropping, slow, or fine. The event carries no information about that, so it has to come from elsewhere.

Common questions

Is Event 6062 'Lso was triggered' a problem?

No. Large Send Offload is a standard network card feature that hands packet segmentation to the adapter instead of the CPU. The driver writes a log entry when it uses it. Intel shipped drivers with this diagnostic message enabled, so ordinary machines fill their System log with warnings about a feature working correctly.

How do I stop Event 6062 from filling my event log?

Updating the network driver is the only clean fix, and it works when the newer driver has the message removed — check your laptop manufacturer's support page as well as Intel's, since OEM drivers lag. Disabling Large Send Offload in the adapter's advanced properties also stops it, but you would be turning off a performance feature to silence a log entry, which is a poor trade unless you have another reason.

Could Event 6062 be causing my Wi-Fi to drop?

It is not the cause, though the two can appear together simply because both involve the same adapter. If your connection genuinely drops, look for adapter reset or disconnect events, check for a newer driver, and test with power management for the adapter disabled. Chasing 6062 will not lead anywhere, because it is logged just as often on machines with perfect connectivity.

Why is a normal event logged as a Warning?

Because the severity is chosen by the driver author, not by Windows. Driver developers commonly leave diagnostic messages at Warning level so they show up during testing, and shipping that way is an oversight rather than a statement about seriousness. Event Viewer has no way to know the difference, which is why the log is full of alarming entries that mean nothing.

Read next

Vendor documentation

Last reviewed 6 September 2026