NETw5s64.sys keeps on giving me bluescreens

[idata]

My new Clevo M570TU Montevina laptop has a Intel WiFi Link 5300 AGN with the latest driver running on Windows 7 x64 (13.0.0.107). I get bluescreens several times a day. If I leave the laptop on when I go to sleep, I often will find that it has automatically restarted because of a BSoD sometime during the night. The stop error is 0x000000d1 and I believe the BSoD says DRIVER_IRQL_NOT_LESS_OR_EQUAL refering to NETw5s64.sys.

It seems the BSoD occurs a lot when utilizing the my WLAN connection a bit more than just surfing. That is running 3-4 torrents, streaming Internet radio and surfing at the same time. I use the newest uTorrent client which again uses the latest Java RE (1.8.5 and 6u17). I am at the moment not using any anti virus software.

In addition to the bluescreens, I often lose my WLAN connection. WLAN is however fine on my other laptops. In these cases I get the event ID 5010 referring to NETw5s64 in my in my Event Log. I resolve this issue by disabling and reenabling the WLAN card, but this is very annoying.

I'm starting to think that the driver is faulty, WLAN on Windows 7 x64 is unstable at the moment, or that maybe my WLAN adapter is faulty.

I ran MemTest on my laptop the whole last night without any errors. I am considering trying another torrent client.

Anybody else having these problems? Any tips is highly appreciated as I'm getting fed up.

Update: I've disabled 11n and power saving on the adapter, but it keeps on giving me bluescreens. A Google search shows that this is a common problem with these Intel adapters. It would really be nice if Intel would acknowledge and address these issues.

[idata]

There is a July update of this driver on 7/2/2010 (or 2/7/2010 if you're reading from outside USA): 13.2.1.5

http://downloadcenter.intel.com/SearchResult.aspx?lang=eng&ProductFamily=Wireless+Networking&ProductLine=Intel%C2%AE+WiFi+Products&ProductProduct=Intel%C2%AE+Centrino%C2%AE+Ultimate-N+6300+and+Intel%C2%AE+Centrino%C2%AE+Advanced-N+6200+products&ProdId=3200&LineId=1784&FamilyId=1783 Download link

[idata]

I would like to clarify something important here. Using WPA encryption instead of WPA2 will limit your wireless connection to 54Mpbs (legacy connection). In other words, if your AP is 11n capable, then using WPA will prevent you from utilizing the high throughput capability in the AP and the adapter. Once Intel provides a fix for the blue screen issue, you all need to make sure that you go back and use WPA2 instead of WPA.

[idata]

I tried the latest driver updates and no luck - if anything, my crashes became more frequent (up to a dozen a day).

However, I'm glad to report that I've had 0 random shutdowns for over a week. The solution turned out to be very simple:

I did a complete uninstall (using the special Zone Alarm Uninstall utility - it's very difficult to find, but you can Google it) of Zone Alarm Pro.

I never thought about this solution because I didn't think it was possible for it to literally cause what seemed like a 'hardware failure'. Alas, it was the culprit. I haven't installed Zone Alarm again to see if installing it AFTER the driver updates makes a difference ie. it acknowledges the updates because they already exist. I'm currently running Windows Firewall and so far happy with it.

So my advice to you all is try removing your firewall software and see if it makes a difference.

[idata]

Hi,

finally I fixed it. Although I did no longterm testing I think I could fix it.

Here is how I did it. I restored my notebook to the factory default, to verify it works with that default setup. Then I checkend all Intel WiFi related driver files and copied them to an external drive.

Go to device manager , right click you wifi device, click properties, click the driver tab and then the driver details button, here you can see every file related to that devie.

C:\windows\system32\DRIVERS\NETw5s64.sys

Version 13.0.0.107

C:\windows\system32\drivers\vwifibus.sys

Version 6.1.7600.16385 --> it's a ms file and should be something similar to the windows 7 build number, but this file is not the root of the problem,

C:\windows\system32\netw5c64.dll

Version: 13.0.0.7

C:\windows\system32\netw5r64.dll

Version: 13.0.0.7

The solution was: using the version 13.0.0.107 of C:\windows\system32\DRIVERS\NETw5s64.sys since all other files allready where on 13.0.0.7.

The device manager still claims a wrong version number, but I do not care because everything works fine.

At least that is waht worked for me. If you do not have the driver try this one http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=18212&ProdId=3200&lang=deu http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=18212&ProdId=3200&lang=deu and double check the version of your netw5s64.sys

HTH

Manuel

[idata]

Hi @ all

I'm experiencing the same problem...

I'm now trying the vista x64 driver to see if the problem still occurs...

[idata]

Still no success with vista x64 driver. Now i get the bluescreen with netw5v64.sys instead of netw5s64.sys...

[idata]

What is your adapter model and what driver version are you using?

[idata]

I'm having these issues - but only under a specific situation - I am using the Intel Centrino 6200N card, with the latest drivers from Intel (reinstalled fresh today, after uninstalling and rebooting) -

When I attempt to connect my Android phone using My Wifi or Connectify software using my laptop as a wireless access point, and using the LAN connection as the share, I'm getting this BSOD:

******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************Use !analyze -v to get detailed debugging information.BugCheck D1, {28, 2, 0, fffff88005d16f4b}Unable to load image \SystemRoot\system32\DRIVERS\NETwNs64.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for NETwNs64.sys*** ERROR: Module load completed but symbols could not be loaded for NETwNs64.sysProbably caused by : NETwNs64.sys ( NETwNs64+e1f4b )Followup: MachineOwner---------0: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)An attempt was made to access a pageable (or completely invalid) address at aninterrupt request level (IRQL) that is too high. This is usuallycaused by drivers using improper addresses.If kernel debugger is available get stack backtrace.Arguments:Arg1: 0000000000000028, memory referencedArg2: 0000000000000002, IRQLArg3: 0000000000000000, value 0 = read operation, 1 = write operationArg4: fffff88005d16f4b, address which referenced memoryDebugging Details:------------------READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030fd0e80000000000000028CURRENT_IRQL: 2FAULTING_IP:NETwNs64+e1f4bfffff880`05d16f4b 488b4828 mov rcx,qword ptr [rax+28h]CUSTOMER_CRASH_COUNT: 1DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULTBUGCHECK_STR: 0xD1PROCESS_NAME: SystemTRAP_FRAME: fffff80000b9c4c0 -- (.trap 0xfffff80000b9c4c0)NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=0000000000000000 rbx=0000000000000000 rcx=fffffa8004a13f58rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000rip=fffff88005d16f4b rsp=fffff80000b9c650 rbp=fffffa8007902eb0r8=0000000000000000 r9=0000000000000000 r10=006e006500430020r11=0000000000000002 r12=0000000000000000 r13=0000000000000000r14=0000000000000000 r15=0000000000000000iopl=0 nv up ei pl nz na po ncNETwNs64+0xe1f4b:fffff880`05d16f4b 488b4828 mov rcx,qword ptr [rax+28h] ds:7a3b:00000000`00000028=????????????????Resetting default scopeLAST_CONTROL_TRANSFER: from fffff80002ecbbe9 to fffff80002ecc640STACK_TEXT:fffff800`00b9c378 fffff800`02ecbbe9 : 00000000`0000000a 00000000`00000028 00000000`00000002 00000000`00000000 : nt!KeBugCheckExfffff800`00b9c380 fffff800`02eca860 : fffff800`0303ee80 00000000`00000001 fffff800`030538c0 fffffa80`07902eb0 : nt!KiBugCheckDispatch+0x69fffff800`00b9c4c0 fffff880`05d16f4b : fffffa80`07902eb0 fffffa80`07902eb0 fffffa80`00000002 00000000`00000018 : nt!KiPageFault+0x260fffff800`00b9c650 fffffa80`07902eb0 : fffffa80`07902eb0 fffffa80`00000002 00000000`00000018 fffffa80`000000cc : NETwNs64+0xe1f4bfffff800`00b9c658 fffffa80`07902eb0 : fffffa80`00000002 00000000`00000018 fffffa80`000000cc fffff880`05c381ef : 0xfffffa80`07902eb0fffff800`00b9c660 fffffa80`00000002 : 00000000`00000018 fffffa80`000000cc fffff880`05c381ef fffffa80`07902508 : 0xfffffa80`07902eb0fffff800`00b9c668 00000000`00000018 : fffffa80`000000cc fffff880`05c381ef fffffa80`07902508 fffffa80`0420c000 : 0xfffffa80`00000002fffff800`00b9c670 fffffa80`000000cc : fffff880`05c381ef fffffa80`07902508 fffffa80`0420c000 fffffa80`07902508 : 0x18fffff800`00b9c678 fffff880`05c381ef : fffffa80`07902508 fffffa80`0420c000 fffffa80`07902508 fffffa80`07902eb0 : 0xfffffa80`000000ccfffff800`00b9c680 fffffa80`07902508 : fffffa80`0420c000 fffffa80`07902508 fffffa80`07902eb0 fffffa80`06f868a0 : NETwNs64+0x31effffff800`00b9c688 fffffa80`0420c000 : fffffa80`07902508 fffffa80`07902eb0 fffffa80`06f868a0 fffffa80`07b5a178 : 0xfffffa80`07902508fffff800`00b9c690 fffffa80`07902508 : fffffa80`07902eb0 fffffa80`06f868a0 fffffa80`07b5a178 00000000`00000001 : 0xfffffa80`0420c000fffff800`00b9c698 fffffa80`07902eb0 : fffffa80`06f868a0 fffffa80`07b5a178 00000000`00000001 fffff800`00b9c820 : 0xfffffa80`07902508fffff800`00b9c6a0 fffffa80`06f868a0 : fffffa80`07b5a178 00000000`00000001 fffff800`00b9c820 00000000`00000000 : 0xfffffa80`07902eb0fffff800`00b9c6a8 fffffa80`07b5a178 : 00000000`00000001 fffff800`00b9c820 00000000`00000000 00000000`00000000 : 0xfffffa80`06f868a0fffff800`00b9c6b0 00000000`00000001 : fffff800`00b9c820 00000000`00000000 00000000`00000000 fffffa80`07b54000 : 0xfffffa80`07b5a178fffff800`00b9c6b8 fffff800`00b9c820 : 00000000`00000000 00000000`00000000 fffffa80`07b54000 fffff880`05d17488 : 0x1ffff...

[idata]

1) Can you please specify the driver version?

2) Is the machine running on battery or connected to AC supply when the issue occur?

[idata]

Thanks for a reply, and I apologize for the delay - I have had zero luck in getting any help with this issue.

I'm running Windows 7 64bit btw...

1.) Latest drivers, I actually updated again today to 13.5.0

2.) It doesn't really seem to matter, it does it on battery or AC power

The latest drivers did nothing to solve this issue, as soon as I connect my phone via My Wifi, or Connectify, boom - BSOD.

[idata]

I can add that I just started getting this BSOD the same day I changed my home network from WEP to WPA2. I never got this before, but now have gotten it about 5 times in 2 days since.

My computer has 64-bit Windows 7. The problem seems to happen after the computer awakes from Sleep mode, or after rebooting from the BSOD. I have noticed that before it happens, the computer seems to have trouble identifying the network. Rebooting the router seems to allow the network to be identified.

I have just updated to version 13.2.1.5 (I had a version number starting with 12) and I am crossing my fingers.

[idata]

Just so you guys don't feel picked on: I have the identical problems given in this thread using Win XP64 Professional and Intel Ultimate 6300N adaptor with the 0X000000D1 BSOD showing NETwNx64.sys as the culprit.

I used all drivers in the 13.X series and found a 14.X dated 11/9/2010 that still BSODs

[idata]

Can you please specify the scenario of making this BSOD occure?

[idata]

I have this same problem. I have some files that Microsoft generated from the incident today. I have tried twice to paste the system diagnostic report to this reply without success. If you think that they will help, please contact me and I will email them since there is no place for attachments.

[idata]

I also have a brand new Dell L502X laptop with Centrino Advanced-N 6230 and have been having a lot of BSOD while connecting to Wi Fi.

The BSOD shows DRIVER_IRQL_NOT_LESS_OR_EQUAL and that the bug is related to NETwNs64.sys. Has anyone had any luck solving this issue?

Any ideas or suggestions will be really appreciated.

[idata]

Ah!

A whole slew of BSOD here - I'm joining in:

Windows 7

Dell Inspiron Laptop

Intel 4965AGN Wireless Card Driver version 13.4.0.139

BSOD at random times, WiFi connection breaking on occasion.

Can trigger BSOD everytime using Intel Driver Update utility (from husdawg llc, also cannot remove part deinstalled version!)

WinDbg:

FOLLOWUP_IP:

NETwLv32+8f998916bb998 8b4014 mov eax,dword ptr [eax+14h]

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: NETwLv32+8f998

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: NETwLv32

IMAGE_NAME: NETwLv32.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4cadb8da

FAILURE_BUCKET_ID: 0xD1_NETwLv32+8f998

BUCKET_ID: 0xD1_NETwLv32+8f998

Followup: MachineOwner

---------

1: kd> lmvm NETwLv32

start end module name9162c000 91c8b000 NETwLv32 (no symbols) Loaded symbol image file: NETwLv32.sys Image path: \SystemRoot\system32\DRIVERS\NETwLv32.sys Image name: NETwLv32.sys Timestamp: Thu Oct 07 13:11:06 2010 (4CADB8DA) CheckSum: 0065677A ImageSize: 0065F000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

"Intel, you have a problem!"

[idata]

I keep getting bluescreen and crash check software is telling me it is the above plugin.

Is there an update. Can I uninstall and reinstall. Do you have a site where I can download

this. I need to get it fixed because it is slowly destroying my hard drive.

thanks,

[idata]

Same problem here. Happens regularly with wifi transfer speeds > 500 kb/s (usually when seeing some you tube video or utorrent) on wireless.

I'm on a Dell Studio 1558, details:

http://intel-drv-ws.systemrequirementslab.com/iduu/iduu.aspx?app=multi&lang=eng# Intel Chipset Software Installation Utility (Chipset INF) Product Detectedhttp://www.intel.com/p/en_US/support/highlights/chpsts/inf Intel® 6, 5, 4, 3, 900 Series ChipsetsCurrent Version Installed9.1.1.1020http://intel-drv-ws.systemrequirementslab.com/iduu/iduu.aspx?app=multi&lang=eng# Wireless Networking (WiFi) Product Detectedhttp://www.intel.com/p/en_US/support/highlights/wireless/6300-6200 Intel® Centrino® Advanced-N 6200Current Driver Installed13.0.0.0This device is unknown or unsupported. Please contact the manufactu

The details I get from http://www.nirsoft.net/utils/blue_screen_view.html http://www.nirsoft.net/utils/blue_screen_view.html is:

Crash ListCreated by using http://www.nirsoft.net/ BlueScreenViewDump File Crash Time Bug Check String Bug Check Code Parameter 1 Parameter 2 Parameter 3 Parameter 4 Caused By Driver Caused By Address File Description Product Name Company File Version Processor Computer Name Full Path Processors Count Major Version Minor Version Dump File Size 051411-7456-01.dmp14/05/2011 13:51:41DRIVER_IRQL_NOT_LESS_OR_EQUAL0x000000d1fffff880`033d0d8000000000`0000000200000000`00000000fffff880`0567ce75NETw5s64.sysNETw5s64.sys+30e75 x64 C:\Windows\Minidump\051411-7456-01.dmp4157601280.976

[idata]

I am using Dell latitude E6510 and seeing exactly same issue.

Strange this is that for many days I didnt have thos issue then had for few days then worked ok, and now just unable to work at all.

I having installed Connectify on my laptop and trying to make wifi hotspot for sharing wired internet with mobile devices.

As soon as I try to connect my phones with wifi hotspot created by connectify , I get blue screen of death.

[idata]

I have a Service Request opened with Dell on this issue. We all our laptops on hold until we find a fix, but no one seems to collaborate (Aruba, Intel or Dell). I think Intel needs to have their driver revisoned, since their most recent one (14.1.1.3) is still causing the bluescreens. Read below for all the configurations and tests that were tried:

It happened on all the following models of laptops:

- Dell Latitude E6420

- Dell Latitude E6520

- HP ProBook E6560b

And they all have this Wireless Card in common:

- Intel Centrino Advanced-N 6205 /or

- Intel Centrino Ultimate-N 6300 AGN (we tried this card after testing intensively with the other one (6205), but with no luck)

We tried all the following versions of drivers:

- Dell version 14.0.2.2 (Most recent from Dell)

- Dell version 14.0.0

- Intel version 14.1.1.3 (Most recent from Intel)

Intel ignored my request because they said this was not a problem big enough because their call center wasn't swamped with calls. From this forum entry, I can see it is affecting many people.

We have found out that it was only happening (bluescreening) when I was connected to an Aruba Networks AP-125 Wireless Access Point. I believe you have different access points, so I'm guessing this problem is wider than just affecting the AP-125s.

This issue was reproduced on the following OS (with all the drivers listed above):

- Windows XP SP3 32-bit (minidump error on NETwNx32.sys) /and

- Windows 7 64-bit (minidump error on NETwNs64.sys).

To my opinion, Dell & Aruba will have to work in collaboration with Intel to fix this issue in the driver.

Can anyone reading this forum entry put some pressure on Intel to have this issue escalated?

Thanks,

[idata]

"11. Feb 19, 2010 3:30 PM /message/80409# 80409 in response to: /message/80409# 80409 tomvanallen /message/84480# 84480 Re: NETw5s64.sys keeps on giving me bluescreens

Intel is aware of this problem and is actively working to resolve the issue. We will update this thread as new information is available.

Thank you,

IleneK"

its been over a year now and i am having this very issue seems intel is slow with a fix, i am going to use a differnt brand of wireless card for my lappy since this is really costing me money with down time. i just updated my computer and this starts, i have rolled the driver back, but it still keeps giving me Bsod with the bad pool caller dump file and shows this very driver to be the cause. anybody have a decent fix on their own?