Blue Screen Error "Driver IRQL Not Less or Equal" for "Netwns64.sys"

[Sad Computerman]

Hi there,
I was hoping someone here could help decipher my issue. A few weeks ago I upgraded my PC from windows 7 home premium 64 bit to windows 10 home premium 64 bit. At the time all was well, and I made sure to update my drivers to their windows 10 versions. Several days after that, however, I began receiving fairly random Blue Screens of Death, stating that "DRIVER_IRQL_NOT_LESS_OR_EQUAL" and having something to do with "Netwns64,sys". Upon researching, this is related to Intel's wireless adapter drivers, however as far as I can tell they are up to date. I have both the minidump file and the memory dump file from the latest crash (Earlier this morning) here:

Minidump: http://www.mediafire.com/download/6m7fcy2fxb02t9u/050316-42093-01.dmp

Memory dump: http://www.mediafire.com/download/8fqaaw4w8cld6yy/MEMORY.DMP

This problem was manageable at first, but now the crashes are becoming more irratating, especially since I was in the middle of a Paper (lucky for saving regularly I guess)

Other Info:
OS: Windows 10 Home Premium 64 bit
RAM: 24GB (x2 8GB Kingston Hyperx 1600Mhz- + x2 4GB HP stock sticks 1600Mhz)
Mo'bo: Biostar TA970
CPU: AMD FX-8350
GPU: EVGA GTX 970 SSC ACX2.0 4GB
HDD: x1 Western Digital Blue 500GB -*Windows is located here* + x1 Segate 3TB Green- Gaming drive
PSU- It's odd; No Listed manufacturer, It was an unmarked spare I had in my garage, 633W
Wireless card: Intel(R) WiFi Link 5300 AGN- It is a Mini-PCIe card on an adapter to PCIe, worked without a hitch in windows 7, but seems to be what's causing problems according to research.

Any help given is greatly appreciated, thanks in advance for having a look!

 

[Colif]

Intel(R) Wireless WiFi Link 5000 Series Adapter Driver for Windows 7 << maybe you have too many wireless drivers installed, have you tried uninstalling them and installing latest?

 

[Sad Computerman]

Intel(R) Wireless WiFi Link 5000 Series Adapter Driver for Windows 7 << maybe you have too many wireless drivers installed, have you tried uninstalling them and installing latest?

Yes, I wasn't exactly clear on that, but I made sure to uninstall the windows 7 drivers before installing those for windows 10.

 

[Colif]

ok, i stop wasting your time and let someone else help. Someone who can read the logs and find true cause.

 

[bratShone]

System File Checker is a handy tool included with Windows that allows you scan for and restore corruptions in Windows system files (including those related to NETwNs64.sys). If System File Checker finds a problem with your SYS or other critical system file, it will attempt to replace the problematic files automatically.
How to run System File Checker (Windows XP, Vista, 7, 8, and 10):
Click the Start button.
Type "command" in the search box... DO NOT hit ENTER yet!
While holding CTRL-Shift on your keyboard, hit ENTER.
You will be prompted with a permission dialog box.
Click Yes.
A black box will open with a blinking cursor.
Type "sfc /scannow" and hit ENTER.
System File Checker will begin scanning for NETwNs64.sys and other system file problems (be patient - the system scan may take a while).
Follow the on-screen commands.

And also try to download ccleaner to clean all garbage and repair registry files.
After that check all ur drivers are they up to date.
If nothing helps i suggest u to perform a clean installation of windows.

cheers

 

[Colif]

Don't do a fresh install without someone reading the logs first, its using a hammer to fix the problem

I have been guilty of suggesting fresh installs to fix minor problems already

I thought SFC just did windows files, not 3rd party drivers as well.

 

[Starcruiser]

I have the Windows Debug tools. Hold on, I'll analyze your dumps.
Oh Mediafire.... Why must you make me wait an hour and a half...

 

[Starcruiser]

From the smaller kernel dump I can see you may be using a Windows 8 driver on your Windows 10 computer. If so, look for a Windows 10 version. If this does not exist, try uninstalling the drivers and installing in compatibility mode. If that still causes issues, as much as it pains me to say, try uninstalling the drivers and letting Windows install some automatically.

I'll have more for you after I analyze the full dump.

 

[Sad Computerman]

From the smaller kernel dump I can see you may be using a Windows 8 driver on your Windows 10 computer. If so, look for a Windows 10 version. If this does not exist, try uninstalling the drivers and installing in compatibility mode. If that still causes issues, as much as it pains me to say, try uninstalling the drivers and letting Windows install some automatically.

I'll have more for you after I analyze the full dump.

Alright, thanks for the update so far. I'll give that a shot

EDIT: Well, shoot! Intel doesn't appear to have drivers for windows 10, and compatibility mode gives no option for windows 10 either. As it's the drivers for my wireless card, my access to the internet, I would have no way of letting windows look for drivers automatically. (The only ethernet line I know of in my house goes into the router, and there's nowhere I could feasibly set up my bulky pc build near it, so that's kind of out of the question) Is it too early to be looking at new wireless cards?

 

[Colif]

You could try the win 8.1 drivers since they the highest version number available: http://www.intel.com/content/www/us/en/support/network-and-i-o/wireless-networking/intel-wifi-link-products/intel-wifi-link-5000-series.html

You might want to consider a new card soon as the one you had has XP to Win 8.1 drivers and good chance Intel will consider that is long enough support. soon.Linksys has done similar with its old cards, they support every os from XP to 8.1 but say Win 10 is a work in progress.

 

[Starcruiser]

Whew, finally got the larger dump done.
So, what I've come up with is this: the ONLY problem I see is from that specific driver, Netwns64.sys. This is both good news and bad. The good news is, besides that driver, your system looks pretty healthy overall. The bad news is now we're basically back to square one.
That said, this driver caused a page fault to be recorded. This points a bit more towards hardware or compatibility issues like I suggested earlier. I say it looks like a Windows 8 driver because of this line: DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
Let me see if I can find a better driver than what you may be using. Where did you get yours?
You can install drivers through compatibility mode by uninstalling the old driver first, telling it to remove all files if possible. Then, right click the installer .exe and click troubleshoot compatibility. Follow the prompts, saying it worked in Windows 8 or 8.1, and install.

If you're curious, this is what I'm working from. It's long, hence spoiler tags.

Spoiler

1: 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 an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000074, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff80065d0a79c, address which referenced memory

Debugging Details:
------------------

Page 1c0 not present in the dump file. Type ".hh dbgerr004" for details
Page 1c0 not present in the dump file. Type ".hh dbgerr004" for details
Page 1c0 not present in the dump file. Type ".hh dbgerr004" for details

DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING: 10586.212.amd64fre.th2_release_sec.160328-1908

SYSTEM_MANUFACTURER: BIOSTAR Group

SYSTEM_PRODUCT_NAME: TA970

SYSTEM_SKU: None

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 4.6.4

BIOS_DATE: 08/07/2014

BASEBOARD_MANUFACTURER: BIOSTAR Group

BASEBOARD_PRODUCT: TA970

DUMP_TYPE: 1

BUGCHECK_P1: 74

BUGCHECK_P2: 2

BUGCHECK_P3: 1

BUGCHECK_P4: fffff80065d0a79c

WRITE_ADDRESS: 0000000000000074

CURRENT_IRQL: 2

FAULTING_IP:
NETwNs64!mmacSchedAckSchedulerHandleSsn+92c
fffff800`65d0a79c ff4074 inc dword ptr [rax+74h]

CPU_COUNT: 8

CPU_MHZ: fa0

CPU_VENDOR: AuthenticAMD

CPU_FAMILY: 15

CPU_MODEL: 2

CPU_STEPPING: 0

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: AV

PROCESS_NAME: System

ANALYSIS_SESSION_HOST: NICK-DESKTOP

ANALYSIS_SESSION_TIME: 05-03-2016 18:02:23.0256

ANALYSIS_VERSION: 10.0.10586.567 amd64fre

TRAP_FRAME: ffffd00024fb91d0 -- (.trap 0xffffd00024fb91d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=ffffe00066d2ffc0
rdx=ffffe00066d2fe20 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80065d0a79c rsp=ffffd00024fb9360 rbp=0000000000000000
r8=ffffd00024fb9428 r9=0000000000000000 r10=fffff8006647b280
r11=ffffe000669a2780 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
NETwNs64!mmacSchedAckSchedulerHandleSsn+0x92c:
fffff800`65d0a79c ff4074 inc dword ptr [rax+74h] ds:00000000`00000074=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff8005696a2e9 to fffff8005695f760

STACK_TEXT:
ffffd000`24fb9088 fffff800`5696a2e9 : 00000000`0000000a 00000000`00000074 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
ffffd000`24fb9090 fffff800`56968ac7 : 00000000`00000000 00000000`00000000 ffffe000`669a2790 ffffe000`66d2fe58 : nt!KiBugCheckDispatch+0x69
ffffd000`24fb91d0 fffff800`65d0a79c : ffffe000`669a2790 ffffe000`66c56fc8 ffffe000`669a2790 ffffe000`69c7cb40 : nt!KiPageFault+0x247
ffffd000`24fb9360 fffff800`65d0b595 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000001 : NETwNs64!mmacSchedAckSchedulerHandleSsn+0x92c
ffffd000`24fb93f0 fffff800`65cb01c8 : ffffe000`69c3fdf0 ffffd000`23eb3004 00000000`00000001 00000000`00000000 : NETwNs64!mmacSchedAckSchedulerSendCompleteCb+0x855
ffffd000`24fb9510 fffff800`65cade0a : ffffd000`00000002 ffffe000`7e2d7000 ffffe000`69c7c800 ffffe000`69c033c8 : NETwNs64!tfdQueueFlush+0x1fe8
ffffd000`24fb9580 fffff800`65cb4078 : ffffe000`69c02e88 fffff800`56ffccc3 ffffe000`68bb98a8 ffffd000`24fb9760 : NETwNs64!tfdQueueSendComplete+0x6a
ffffd000`24fb95b0 fffff800`65cb38dc : ffffe000`69ce2800 00000002`da8ad494 ffffe000`69c7c8e0 ffffe000`6a5589ff : NETwNs64!prvRfdQueueDispatch+0x398
ffffd000`24fb9640 fffff800`65ca8a62 : ffffe000`69ca7e01 ffffe000`69ce2801 ffffd000`24fb9710 ffffe000`690bd101 : NETwNs64!rfdQueueProcessFragments+0x17c
ffffd000`24fb96e0 fffff800`65fd5e12 : 00000000`00000000 ffffe000`69ce2850 fffff800`56ffcc50 00000000`00000000 : NETwNs64!isrHandlerRoutineInta+0x212
ffffd000`24fb9750 fffff800`62277333 : ffff37bc`a5864be9 ffffe000`68bb90e8 ffffe000`68bb81a0 fffff780`00000320 : NETwNs64!oscHandleInterrupt+0x22
ffffd000`24fb9780 fffff800`5688b6a0 : ffffd000`24fb9b20 ffffe000`6a88a010 ffffe000`6a88a320 ffffd000`24f80f44 : ndis!ndisInterruptDpc+0x633
ffffd000`24fb98c0 fffff800`5688adb9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExecuteAllDpcs+0x270
ffffd000`24fb9a10 fffff800`5696251a : ffffffff`00000000 ffffd000`24f8f180 ffffd000`24f9bcc0 ffffe000`75ab5080 : nt!KiRetireDpcList+0xe9
ffffd000`24fb9c60 00000000`00000000 : ffffd000`24fba000 ffffd000`24fb4000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND: kb

THREAD_SHA1_HASH_MOD_FUNC: 2d32a9fd27347986c7f9a6b4a6299f97412b42c3

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: bfd735d3a9dcae71f791ae7af49e333a80070b0c

THREAD_SHA1_HASH_MOD: 20eb5c63f3eb0aea7e2fc382148827f1a4663f46

FOLLOWUP_IP:
NETwNs64!mmacSchedAckSchedulerHandleSsn+92c
fffff800`65d0a79c ff4074 inc dword ptr [rax+74h]

FAULT_INSTR_CODE: 497440ff

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: NETwNs64!mmacSchedAckSchedulerHandleSsn+92c

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: NETwNs64

IMAGE_NAME: NETwNs64.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4e8dbeef

BUCKET_ID_FUNC_OFFSET: 92c

FAILURE_BUCKET_ID: AV_NETwNs64!mmacSchedAckSchedulerHandleSsn

BUCKET_ID: AV_NETwNs64!mmacSchedAckSchedulerHandleSsn

PRIMARY_PROBLEM_CLASS: AV_NETwNs64!mmacSchedAckSchedulerHandleSsn

TARGET_TIME: 2016-05-03T14:23:34.000Z

OSBUILD: 10586

OSSERVICEPACK: 0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 784

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2016-03-28 23:19:02

BUILDDATESTAMP_STR: 160328-1908

BUILDLAB_STR: th2_release_sec

BUILDOSVER_STR: 10.0.10586.212.amd64fre.th2_release_sec.160328-1908

ANALYSIS_SESSION_ELAPSED_TIME: 1443

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:av_netwns64!mmacschedackschedulerhandlessn

FAILURE_ID_HASH: {b9e67c23-754c-f1ad-29e8-0efeb1fcacbe}

Followup: MachineOwner
---------

 

[Starcruiser]

Well, I looked everywhere and I can't seem to find a Windows 10 driver for that card. I even looked through the various vendor databases, such as dell and lenovo. It looks like that card has been around since Windows Vista was relevant. I'd definitely look into getting a replacement that actually supports Windows 10.

 

[Sad Computerman]

Well, I looked everywhere and I can't seem to find a Windows 10 driver for that card. I even looked through the various vendor databases, such as dell and lenovo. It looks like that card has been around since Windows Vista was relevant. I'd definitely look into getting a replacement that actually supports Windows 10.

I figured it was about time. That card served me well while it worked I guess. Luckily it's a wireless card; it's not like a new one is going to totally break the bank!