WiFi just got turned off in a Lenovo ThinkPad X61s laptop with Intel Advanced-N 6205 WiFi card running Windows 8.1 x64 that I look after. Event Viewer has Event ID 5092 in NETwNe64 logged at exactly that moment (which cannot be decoded for some reason):
Searching on 5092 here yields these:
/message/208540# 208540 https://communities.intel.com/message/208540
/message/279451# 279451 https://communities.intel.com/message/279451
I'm already on Intel 188.8.131.52 driver dated 22.08.2013 though, the most recent one for this HW/SW platform to the best of my knowledge... or not? What is this error really about and how do I fix it for good? It's critical for networking to be 100% available on this laptop as the end user is incapable of fixing anything like that on their own and it's very far away from me.
I have the .evtx with further details of this error at hand just in case it's of any help.
Many thanks in anticipation!
Event viewer isn't always helpful. In some cases, it may be used to identify behaviors (see what happens before an error). It's not uncommon to receive event IDs that lead nowhere as these are generated by the OS and not our driver.
The latest driver for the Intel® Centrino® Advanced-N 6205 in Windows* 8.1 is version http://www.intel.com/content/www/us/en/support/network-and-i-o/wireless-networking/000006024.html 184.108.40.206. Please download our latest driver's package and let us know if the issue gets resolved.
- https://downloadcenter.intel.com/download/26783/Wireless-Intel-PROSet-Wireless-Software-and-Drivers-... Intel® PROSet/Wireless Software and Drivers for Windows 8.1* Version: 19.60.0.
If the issue persists, please provide us the following:
- Your system event logs. The ones you've already saved will work, but it would be ideal if you could clear your system event logs, reproduce the issue, and then export a new file.
- Please download and run our https://downloadcenter.intel.com/download/25293/Intel-System-Support-Utility System Support Utility. This will allow you to save a report with your settings and hardware configuration.
We look forward to hearing back from you.
Hi Carlos - thank you,
I'm now installing the latest driver as you suggested and will be testing it once done. Will keep you updated.
Meanwhile may I ask what exactly this error with Event ID 5092 is about? I've just found lots of those on another laptop I look after - IBM ThinkPad X60s with Intel Advanced-N 6235, also with "The description for Event ID 5092 from source NETwNe64 cannot be found." statement in Event Viewer and so would like to have its description if possible.
We look forward to finding out how your tests turn out.
As for the event ID, we're not able to provide a definitive answer. Events are not generated by our driver, but rather by the OS in reaction to actions or errors resulting from our hardware, drivers, among many other possible things. Because of this, we don't have an event ID decoder, and Microsoft* doesn't publish one for consumer operating systems either.
The closest we were able to find is for Windows Server 2012*, which is the server equivalent to 8.1:
- https://technet.microsoft.com/en-us/library/cc735173(v=ws.10).aspx Event ID 5092 — IIS WAS Availability
NOTE: Any links provided for third party tools or sites are offered for your convenience and should not be viewed as an endorsement by Intel® of the content, products, or services offered there. We do not offer support for any third party tool mentioned here.
Their suggested troubleshooting is to restart the WAS and W3SVC services. However, this troubleshoots the symptom, not the issue. It's always important to analyze event viewer logs as a small part of the big picture only. They show what happened, and it's up to us to figure out why so that it may be resolved.
We hope this helps.
Hi Carlos - thanks for your reply,
Just to let you know that I haven't seen the error on either laptop since 3rd June, when the driver was upgraded to http://www.intel.com/content/www/us/en/support/network-and-i-o/wireless-networking/000006024.html 220.127.116.11 as you suggested earlier, so it's looking promising. I'll need to monitor both laptops for another few weeks though, as the error wasn't there always, e.g. it occured on 5th May and then only on 25th May again. Meanwhile we can mark it "assumed answered" for now.