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]

Hi All,

I too have been having a similiar issue with a Dell 1645. I have recently change 2 things regarding the wireless setup and things have been ok for 1 day.

The thing which i think potentially resolved the issue was setting the power management options under the driver(currently i'm running the 13.5.0.6 driver) . The option i turned off was the" Allow the computer to turn off this device to save power". I have since tested this while on mains power and also on battery(sleep and hibernate). I did also remove a client\service network driver called applian(but don't think it was what solved the issue). Finger crossed I'll see how I go over the next few days and provide an update.

Michael

[idata]

I also get the BSOD. After I turned off the wirelees N feature (802.11 N Mode: Disabled), no more BSOD. Driver only works on wireless G.

[idata]

@Jeb Many Thanks ! I also tried disabling wireless N mode and now now more BSOD

[idata]

I have also tried disabling Wireless N, but I would still get the BSOD. On Windows 7 x64 and Windows XP x86.

Note that as per our network team, the Aruba Networks AP-125 routers are not "N enabled".

[idata]

Hi All,

Aftering turning off the option " Allow the computer to turn off this device to save power" on the wireless card I haven't had a BSOD for 2 weeks. I have tested to sleep and hibernate and I don't get BSOD. The option for wireless N is still active and working.

[idata]

One of our older models (Dell Latitude D830) started blue screening as well (Intel PRO/Wireless 3945ABG wireless card, driver version 12.1.2.1) when connected to an Aruba Networks AP-125.

After seeing this last post about disabling "Allow the computer to turn off this device to save power", I rapidly disabled it, but NO LUCK, the computer eventually had 2-3 blue screens during the day.

Resolutions anyone?

[idata]

Hey cotjoey.

Have you updated the driver to 13.5.0.6? Also have your tried to disable Wireless N as other have mentioned?

[idata]

Michael M,

Please see posts /message/128830# 128830 102, /message/131679# 131679 108 and /message/133101# 133101 110 for everything that I have tried.

[idata]

It might be due to the fact your are running Intel Centrino Advanced-N 6205 or Intel Centrino Ultimate-N 6300 AGN while I'm running Intel 5300 AGN.

It's frustrating Intel is not doing anything to resolves these issues.

[idata]

Microsoft had released some hotfixes.

http://support.microsoft.com/kb/2482122/en-us http://support.microsoft.com/kb/2482122/en-us

http://support.microsoft.com/kb/2459268/en-us http://support.microsoft.com/kb/2459268/en-us

Maybe it will help you to solve the problems with these bluescreens.

[idata]

Do you know if there are similar hotfixes for Windows XP SP3? I would like to try it.

Again, this is the minidump analysis of the bluescreens that I'm still having on Windows XP SP3:

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)

BugCheck 100000D1, {2c, 2, 1, b6b5a799}

*** WARNING: Unable to verify timestamp for mssmbios.sys

*** WARNING: Unable to verify timestamp for NDIS.sysProbably caused by : NETwNx32.sys ( NETwNx32+1a6799 )

This is the minidump analysis of the bluescreens that I'm still having on Windows 7 (64 bit):

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)

BugCheck D1, {2c, 2, 1, fffff88004ef9c7e}

Probably caused by : NETwNs64.sys ( NETwNs64+21ac7e )

Thanks,

Joey

[idata]

I found a Windows 7 Enterprise system that is having this issue and installed the two hotfixes suggested by janeinjanein in post /message/134615# 134615 114.

Result: Failed

The minidump crash analysis still reports driver NETwNs64.sys as being the problem (Stop error 0x000000d1)

[idata]

That's a hotfix which ONLY catches a special problem with your wifi-card and the power state functions of windows. So it depends on the case. It might help someone who has similar blue screens that are described in the knowledge base articles. For instance I've got a Thinkpad T500 with Windows7 x64 & intel-wifi 5100 which caused randomly blue screens but since I installed the patches, I neither had a F9 nor a D1 crash again.

[idata]

A bug has been found by Intel.

When we turned off ARM (Adaptive Radio Management) on our wireless controller configuration, our clients stopped blue screening.

Intel is working actively on having a new revision of their driver (currently, only the old version 14.00.2000, A02 is available on the Dell website for the Dell Latitude E6420 and Dell Latitude E6520).

[OLiet]

The problem also still happens for me, latest drivers installed 14.2.0.10

any news?

[idata]

Are you sure the bluescreen is related to your wireless network drivers? You can paste the minidump analysis of the .dmp file created when your computer blue screened.

If you have ARM enabled on your company's wireless controller, did you try disabling it?

[OLiet]

Yes, it is sure the NETwNs64 is the problem. Several dumps show it.

See below.

Updated to 14.3.0.6 driver from the Intel site does not help. Still issues with standby.

Please advise how to switch off ARM - did not find this setting.

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64Copyright (c) Microsoft Corporation. All rights reserved.Loading Dump File [C:\Windows\Minidump\022812-85285-01.dmp]Mini Kernel Dump File: Only registers and stack trace are available

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?00000000`00000000?

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00b9c500?Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols http://msdl.microsoft.com/download/symbolsExecutable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506Machine Name:Kernel base = 0xfffff800`03412000 PsLoadedModuleList = 0xfffff800`03657670Debug session time: Tue Feb 28 11:25:41.120 2012 (GMT+1)System Uptime: 1 days 3:25:31.242Loading Kernel Symbols.....................................................................................................................................................................................................Loading User SymbolsLoading unloaded module list......................................******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa80049d4060, fffff80000b9c518, fffffa8005e91af0}

*** 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

Followup: MachineOwner

---------

0: kd> !analyze -v

******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)

A driver is causing an inconsistent power state.Arguments:Arg1: 0000000000000003, A device object has been blocking an Irp for too long a timeArg2: fffffa80049d4060, Physical Device Object of the stackArg3: fffff80000b9c518, Functional Device Object of the stackArg4: fffffa8005e91af0, The blocked IRP

Debugging Details:

------------------DRVPOWERSTATE_SUBCODE: 3

IRP_ADDRESS: fffffa8005e91af0

DEVICE_OBJECT: fffffa8003f3a050

DRIVER_OBJECT: fffffa8007ec3740

IMAGE_NAME: NETwNs64.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4eaf27e7

MODULE_NAME: NETwNs64

FAULTING_MODULE: fffff880058eb000 NETwNs64

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from fffff800034fccd2 to fffff8000348ec40

STACK_TEXT:

fffff800`00b9c4c8 fffff800`034fccd2 : 00000000`0000009f 00000000`00000003 fffffa80`049d4060 fffff800`00b9c518 : nt!KeBugCheckExfffff800`00b9c4d0 fffff800`0349a5fc : fffff800`00b9c600 fffff800`00b9c600 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x34a90fffff800`00b9c570 fffff800`0349a496 : fffff800`03639f00 00000000`00609235 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6cfffff800`00b9c5e0 fffff800`0349a37e : 000000e5`e067fc3a fffff800`00b9cc58 00000000`00609235 fffff800`03607928 : nt!KiProcessExpiredTimerList+0xc6fffff800`00b9cc30 fffff800`0349a167 : 0000003b`b6e509c1 0000003b`00609235 0000003b`b6e5092e 00000000`00000035 : nt!KiTimerExpiration+0x1befffff800`00b9ccd0 fffff800`0348696a : fffff800`03604e80 fffff800`03612cc0 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5aSTACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: X64_0x9F_IMAGE_NETwNs64.sys

BUCKET_ID: X64_0x9F_IMAGE_NETwNs64.sys

Followup: MachineOwner

---------

0: kd> !irp

Free build - use !irpfind to scan memory for any active IRPs0: kd> !irp fffffa8005e91af0Irp is active with 4 stacks 2 is current (= 0xfffffa8005e91c08) No Mdl: No System Buffer: Thread 00000000: Irp stack trace. cmd flg cl Device File Completion-Context [ 0, 0] 0 0 00000000 00000000 00000000-00000000

Args: 00000000 00000000 00000000 00000000

>[ 16, 2] 0 0 fffffa8003f3a050 00000000 00000000-00000000 \Driver\NETwNs64 Args: 00014400 00000000 00000004 00000002 [ 16, 2] 0 e1 fffffa8006e97890 00000000 fffff800036d61b0-fffffa8003bee520 Success Error Cancel pending \Driver\vwifibus nt!PopSystemIrpCompletion Args: 00014400 00000000 00000004 00000002 [ 0, 0] 0 0 00000000 00000000 00000000-fffffa8003bee520

Args: 00000000 00000000 00000000 00000000

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64Copyright (c) Microsoft Corporation. All rights reserved.Loading Dump File [C:\Windows\MEMORY1.DMP]Kernel Sum...

[idata]

You are getting a "DRIVER_POWER_STATE_FAILURE"

I was getting a "DRIVER_IRQL_NOT_LESS_OR_EQUAL"

If you are not using your computer in a business environment, I doubt that you would have ARM enabled on your router. If you are having that problem at work, I suggest you communicate the concern to your network support team.

Those are the things I woudl try on your system:

- Try to replicate the issue in SAFE MODE;

- Try to replicate the issue in SAFE MODE with networking;

- Check if you computer is set to hibernate or to go to sleep;

This looks like a WiFi driver. If the updated driver doesn't fix it, check this hotfix:

"0x0000009F" Stop error when you restart a Windows 7-based or Windows Server 2008 R2-based computer that has certain Wi-Fi drivers installed

http://support.microsoft.com/kb/2482122 http://support.microsoft.com/kb/2482122

[OLiet]

The problem seems to be happening less often with the latest drivers, but still does.

The problem does not happen when the Wireless adapter is deactivated in Windows,

so it makes no difference in starting the safe mode.

I tried to switch off some driver settings (power down, n mode, etc.) without success.

The MS patch did not help either.

Any idea?

below is the windbg log.

- Oliver

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64Copyright (c) Microsoft Corporation. All rights reserved.Loading Dump File [C:\Windows\Minidump\031312-21543-01.dmp]Mini Kernel Dump File: Only registers and stack trace are available

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?00000000`00000000?

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00b9c500?Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols http://msdl.microsoft.com/download/symbolsExecutable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506Machine Name:Kernel base = 0xfffff800`03459000 PsLoadedModuleList = 0xfffff800`0369e670Debug session time: Tue Mar 13 18:58:41.002 2012 (GMT+1)System Uptime: 0 days 6:39:24.470Loading Kernel Symbols.................................................................................................................................................................................................Loading User SymbolsLoading unloaded module list..........******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa80049b8060, fffff80000b9c518, fffffa8007df5010}

*** 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

Followup: MachineOwner

---------

0: kd> !analyze -v

******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)

A driver is causing an inconsistent power state.Arguments:Arg1: 0000000000000003, A device object has been blocking an Irp for too long a timeArg2: fffffa80049b8060, Physical Device Object of the stackArg3: fffff80000b9c518, Functional Device Object of the stackArg4: fffffa8007df5010, The blocked IRP

Debugging Details:

------------------DRVPOWERSTATE_SUBCODE: 3

IRP_ADDRESS: fffffa8007df5010

DEVICE_OBJECT: fffffa80054f8050

DRIVER_OBJECT: fffffa80053e7060

IMAGE_NAME: NETwNs64.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4eaf27e7

MODULE_NAME: NETwNs64

FAULTING_MODULE: fffff88005824000 NETwNs64

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from fffff80003543cd2 to fffff800034d5c40

STACK_TEXT:

fffff800`00b9c4c8 fffff800`03543cd2 : 00000000`0000009f 00000000`00000003 fffffa80`049b8060 fffff800`00b9c518 : nt!KeBugCheckExfffff800`00b9c4d0 fffff800`034e15fc : fffff800`00b9c600 fffff800`00b9c600 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x34a90fffff800`00b9c570 fffff800`034e1496 : fffff800`03680f00 00000000`001770ae 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6cfffff800`00b9c5e0 fffff800`034e137e : 00000037`cbeff03d fffff800`00b9cc58 00000000`001770ae fffff800`0364f848 : nt!KiProcessExpiredTimerList+0xc6fffff800`00b9cc30 fffff800`034e1167 : 0000000e`7e8932c1 0000000e`001770ae 0000000e`7e8932fb 00000000`000000ae : nt!KiTimerExpiration+0x1befffff800`00b9ccd0 fffff800`034cd96a : fffff800`0364be80 fffff800`03659cc0 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5aSTACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: X64_0x9F_IMAGE_NETwNs64.sys

BUCKET_ID: X64_0x9F_IMAGE_NETwNs64.sys

Followup: MachineOwner

---------

0: kd> !devobj fffffa80054f8050 f

fffff80003680f90: Unable to get value of ObpRootDirectoryObjectDevice object (fffffa80054f8050) is for: InfoMask field not found for _OBJECT_HEADER at fffffa80054f8020 \Driver\NETwNs64 DriverObject fffffa80053e7060Current Irp 00000000 RefCount 0 Type 00000017 Flags 00002050DevExt fffffa80054f81a0 DevObjExt fffffa80054f98c0 ExtensionFlags (0x00000800) Unknown flags 0x00000800AttachedDevice (Upper) fffffa80053f3040 \Driver\vwifibusAttachedTo (Lower) fffffa80049b8060 \Driver\pciDevice queue is not busy.0: kd> !drvobj fffffa80053e7060 ffffff80003680f90: Unable to get value of ObpRootDirectoryObjectfffff80003680f90: Unable to get value of ObpRootDirectoryObjectDriver object (fffffa80053e7060) is for: \Driver\NETwNs64Driver Extension List: (id , addr)

Device Object list:...

[idata]

Hello Oliver,

Do you live somewhere where there could be a lot of wireless interference? (close to a business, big apartment building, etc)

I am asking this because it could be the neighbour's ARM (Active Radio Management) - enabled on their wireless infrastructure - that's causing that to your wireless adapter.

I suggest you connect your laptop to wireless in a spot where you know there could be minor interference (i.e. isolated corner in the university library, public library, wireless Internet at your cottage, cafe, etc).

Try that and let me know. I guess you must leave it connected for a good while to prove that your neighbour's ARM could be the problem.

Thanks,

Joey

[OLiet]

Hello Joey,

thanks for your quick response. I had the issue in my home network with only very few private networks around, and in office, with some more traffic.

I did not find any ARM setting in any router yet, and I assume private and small business installations would not have it activated (?)

Difficult to isolate this. Anyway what would it help? Seems quite strange that a router network setting would lead to a BSOD on my laptop.

Furthermore I need to work in my common environments. I would be able to send more info about my log and debug session etc.but would prefer not sending it in this public forum. Might be useless for other readers as well.

Regards, Oliver