topic Re: Wireless driver spamming Windows Event Log in Wireless

Wireless driver spamming Windows Event Log

GLuci — Wed, 14 Mar 2018 17:27:20 GMT

This is for a Intel Dual Band Wireless-AC 8260 chip on a Lenovo P50. The driver for the wireless chip keeps posting this to the Application Event Log every 9-11 seconds:

Source: Netwtw06

Event ID: 7023

Level: Information

Content: 7077 - Intel proprietary

It's cluttering my event log and making it difficult to find anything useful.

I have the latest version of the driver (20.30.1).

Is there any way to turn off this event logging? Or can it be removed in the next version?

Re: Wireless driver spamming Windows Event Log

idata — Thu, 15 Mar 2018 16:25:57 GMT

Hello gabe_luci,

Thanks for being part of our community. We understand that Netwtw06 is showing in several events at Event Viewer. Other than the multiple entries, are there any other issues regarding wireless connectivity?

In order to better assist you, we would like to gather some more information. Please download and run the https://downloadcenter.intel.com/download/25293/Intel-System-Support-Utility-for-Windows- Intel® System Support Utility and share the resulting report with us.

Best regards,

Eugenio F.

Re: Wireless driver spamming Windows Event Log

GLuci — Thu, 15 Mar 2018 17:37:30 GMT

I've attached the output from the utility.

But no, I have no problems with connectivity. Everything is working fine, except the flood of entries in my event log. I have attached a screenshot.

And I was wrong about which event log: They're going in the System event log, not Application.

Re: Wireless driver spamming Windows Event Log

idata — Thu, 15 Mar 2018 19:36:24 GMT

Hello gabe_luci,

Thanks for your reply and for providing the files. Your adapter settings are https://www.intel.com/content/www/us/en/support/articles/000005544/network-and-i-o/wireless-networking.html configured as recommended.

To provide you with a direct answer to your question, we can't prevent a driver from triggering events. This is managed by the operating system and cannot be disabled.

As long as your system is working properly, you may ignore the information events and most error and warning entries in the Event Viewer. In case you ever need to troubleshoot, we recommend to clear the logs in order to capture the specific error information.

Here's an interesting and informative reading regarding Windows* Event Viewer functionality:

- https://www.howtogeek.com/123646/htg-explains-what-the-windows-event-viewer-is-and-how-you-can-use-it/ What Is the Windows Event Viewer, and How Can I Use It? How-To Geek*

NOTE: Links to third party sites are being offered for your convenience and should not be viewed as an endorsement by Intel of the content, products, or services offered there.

Please let us know if there's anything else we can do for you.

Best regards,

Eugenio F.

Re: Wireless driver spamming Windows Event Log

GLuci — Thu, 15 Mar 2018 19:40:30 GMT

That's fair enough that I cannot stop the events. But your development team can. Would you suggest to your development team that they remove these events in a future version? The events don't seem to serve any useful purpose.

Re: Wireless driver spamming Windows Event Log

idata — Thu, 15 Mar 2018 19:49:17 GMT

Hello gabe_luci,

I can't confirm if these events are part of the driver design. However, I'll share your feedback with our business unit for consideration.

Best regards,

Eugenio F.

Re: Wireless driver spamming Windows Event Log

GLuci — Thu, 15 Mar 2018 19:50:42 GMT

Thank you

Re: Wireless driver spamming Windows Event Log

LSaue — Mon, 26 Mar 2018 19:21:58 GMT

I noticed the same problem and this prompted me to google for it, find this post, register to the forum, and post this comment. So yes - this is considered spam in the Event logs by at least two users.

I find a staggering 42762 (fortytwothousandsevenhundredsixtytwo) entries in my Event Log.

Re: Wireless driver spamming Windows Event Log

idata — Mon, 26 Mar 2018 20:46:13 GMT

Hello Leobard,

Thanks for your reply. We understand that you're also reviving multiple driver notifications on the Event logs. Please bear in mind that Event Viewer is not an Intel software, and event tracking cannot be disabled from the driver.

gabe_luci Doing further research, we found some information regarding Event Viewer that might interest you. From https://technet.microsoft.com/en-us/library/bb687437.aspx Microsoft* Technet:

To disable logging for a specific event

In the Application Center snap-in, expand the cluster node.
Under the cluster node, right-click the Events node, and then on the pop-up menu, click Properties.
In the Event Properties dialog box, click Exclusions.
In the Event Exclusions dialog box, in the Product box, click the appropriate event source, and then click Add.
Click the appropriate event severity, and then, if required, in the Source box, enter the event source and in the Event ID box, enter the identifier number.

You can disable logging for specific events. This can be useful to hide events that you are aware of and no longer need to see. Events of this type that are already logged are still displayed in the Events view until they are cleaned-up by Application Center after the period of time specified in the Keep logged events for (days) text box or until the log is cleared.

NOTE: Links to third party sites are being offered for your convenience and should not be viewed as an endorsement by Intel of the content, products, or services offered there.

Best regards,

Eugenio F.

Re: Wireless driver spamming Windows Event Log

GLuci — Mon, 26 Mar 2018 22:18:52 GMT

Eugenio,

I think you misunderstand the purpose of the Event Viewer. Event Viewer does not create the events, it only views them. Events only show in the Viewer when an application (or driver) purposefully logs an event. In this case, the Event Source is "Netwtw06", which is the short name for the Intel Wireless driver (the file name of the driver is Netwtw06.sys).

All this means that there is code in the Intel driver that is logging this event. That's why I asked that you forward this feedback to your developers so that they can remove that code, or otherwise provide a way to disable it.

The method you gave to disable logging won't work in Windows 10. As described in this link, the Application Center is no longer supported and was last updated for Windows Server 2003: https://technet.microsoft.com/en-us/library/bb545877.aspx https://technet.microsoft.com/en-us/library/bb545877.aspx

Re: Wireless driver spamming Windows Event Log

idata — Tue, 27 Mar 2018 20:12:58 GMT

Hello gabe_luci,

Thanks for your reply. We'll gladly pass on your feedback along with the new inputs.

Best regards,

Eugenio F.

Re: Wireless driver spamming Windows Event Log

MDjog — Thu, 29 Mar 2018 21:14:19 GMT

Hi,

Same troubleshoot here !

The amount of useless traces this driver is inserting into the event viewer database is just insane.

Can Intel update its driver please?

Regards

Re: Wireless driver spamming Windows Event Log

MDjog — Thu, 29 Mar 2018 21:29:21 GMT

For example: "7021 - Connection telemetry fields and analysis usage" [event id 7021] (24% of the Netwtw06 events). It's usefulness is debatable...

But "7077 - Intel proprietary" [event id 7023] represent 32% of the Netwtw06 events. Does this mean something useful for you?

Re: Wireless driver spamming Windows Event Log

MDjog — Thu, 29 Mar 2018 22:07:31 GMT

Nothing possible in Powershell, no way to deal with this issue removing only the interesting even ids.

https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.management/remove-eventlog?view=powershell-5.1 Remove-EventLog or https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.management/limit-eventlog?view=powershell-5.1 Limit-EventLog doesn't bring any viable solution.

So Intel, the ball's in your court.

Re: Wireless driver spamming Windows Event Log

HJoha4 — Fri, 30 Mar 2018 19:51:04 GMT

You cant write just "7077 - Intel proprietary" in the event log.

We are talking about the driver to "Intel(R) Dual Band Wireless-AC 8260" version 20.30.1.2 dated 10-01-2018 (day, month, year).

Please search the source code for the driver for the text "7077 - Intel proprietary", and solve the problem.

/Henning

Re: Wireless driver spamming Windows Event Log

idata — Tue, 03 Apr 2018 22:04:33 GMT

Hello everyone,

Thanks for your feedback. Please confirm if the same behavior is present if you use the https://www.intel.com/content/www/us/en/support/articles/000005559/network-and-i-o/wireless-networking.html latest wireless driver (version 20.40.0.4 as of today). Please make sure you follow-up the https://www.intel.com/content/www/us/en/support/articles/000022173/network-and-i-o/wireless-networking.html clean installation process.

Best regards,

Eugenio F.

Re: Wireless driver spamming Windows Event Log

MDjog — Wed, 04 Apr 2018 15:10:08 GMT

Hello Eugenio,

Thanks for this swift answer.

I installed the new version for 8265 interface few mins ago. For now, no more events 7023.

But just one observation, the driver 20.40.0.4 has been released the 6th of Feb (see screenshot below). So what's the point making us demonstrate there is something wrong if your dev team already knows it, I don't get it?

Anyway, I will revert if there is something wrong.

Re: Wireless driver spamming Windows Event Log

idata — Wed, 04 Apr 2018 17:54:34 GMT

Hello M@tt3.0,

Thanks for taking the time to install the latest driver update. We just wanted to confirm if you get the same results we got in our labs.

Please let us know if there's anything else we can do for you.

Best regards,

Eugenio F.

Re: Wireless driver spamming Windows Event Log

MDjog — Wed, 04 Apr 2018 18:08:42 GMT

So far so good, no more useless events and the system is stable, connexion too.

Thank your for your assistance.

Regards

Matt

Re: Wireless driver spamming Windows Event Log

GLuci — Wed, 04 Apr 2018 18:33:40 GMT

Looks good here too. I installed it about 15 minutes ago and haven't had any more events showing up. So it looks good!

Thank you Eugenio.