Solved Occasional BSOD "NETwNs64.sys" and Ver_irql_not_less_or_equal

[Huck5]

Occasional BSOD "NETwNs64.sys" and Ver_irql_not_less_or_equal

Hi there,

I have been experiencing occasional BSOD. I'm not certain what the cause is, as it is fairly infrequent. Possibly once a week, if less. This is still enough to cause concern, though, as it often happens in the middle of working on a project.

I get the message VER_IRQL_NOT_LESS_OR_EQUAL, and it mentions NETwNs64.sys.

Since the BSOD is fairly infrequent, it's really hard to pinpoint any trend in what I'm doing that might have caused it.

I'm running Windows 7 Home Premium 64bit, on a Lenovo laptop (V570).

Though it's not extremely urgent, I would really like to be able to resolve this problem, and prevent this BSOD occurring in the future.

Your help is much appreciated, so thank you for your time.

 

[koolkat77]

Welcome to the forum.

Please update this driver: Intel(R) Wireless WiFi Link 5000 Series Adapter Driver for Windows 7

• Driver Reference Table - NETwNs64.sys

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

Use !analyze -v to get detailed debugging information.

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

*** WARNING: Unable to verify timestamp for NETwNs64.sys
*** ERROR: Module load completed but symbols could not be loaded for NETwNs64.sys
Probably caused by : NETwNs64.sys ( NETwNs64+21a4ce )

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 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: 000000000000002c, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff88008a614ce, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff8000370f100
GetUlongFromAddress: unable to read from fffff8000370f1c0
 000000000000002c Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
NETwNs64+21a4ce
fffff880`08a614ce 89732c          mov     dword ptr [rbx+2Ch],esi

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TAG_NOT_DEFINED_c000000f:  FFFFF80000BA2FB0

TRAP_FRAME:  fffff80000b9c2a0 -- (.trap 0xfffff80000b9c2a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88001ed2110 rbx=0000000000000000 rcx=fffff88001ed5ec0
rdx=fffff800036dc8d0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88008a614ce rsp=fffff80000b9c430 rbp=fffffa800905da48
 r8=0000000000000000  r9=0000000000000000 r10=002900520028006c
r11=fffffa800c3056a8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
NETwNs64+0x21a4ce:
fffff880`08a614ce 89732c          mov     dword ptr [rbx+2Ch],esi ds:00000000`0000002c=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800034d71a9 to fffff800034d7c00

STACK_TEXT:  
fffff800`00b9c158 fffff800`034d71a9 : 00000000`0000000a 00000000`0000002c 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff800`00b9c160 fffff800`034d5e20 : fffffa80`054fdc58 fffff880`0886605e fffffa80`08a55470 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`00b9c2a0 fffff880`08a614ce : 00000000`00000000 fffffa80`0905da48 fffffa80`00000002 00000000`000000c0 : nt!KiPageFault+0x260
fffff800`00b9c430 00000000`00000000 : fffffa80`0905da48 fffffa80`00000002 00000000`000000c0 00000000`000004ba : NETwNs64+0x21a4ce


STACK_COMMAND:  kb

FOLLOWUP_IP: 
NETwNs64+21a4ce
fffff880`08a614ce 89732c          mov     dword ptr [rbx+2Ch],esi

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  NETwNs64+21a4ce

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: NETwNs64

IMAGE_NAME:  NETwNs64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4cd92d8f

FAILURE_BUCKET_ID:  X64_0xD1_NETwNs64+21a4ce

BUCKET_ID:  X64_0xD1_NETwNs64+21a4ce

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

0: kd> lmvm NETwNs64
start             end                 module name
fffff880`08847000 fffff880`090b2000   NETwNs64 T (no symbols)           
    Loaded symbol image file: NETwNs64.sys
    Image path: \SystemRoot\system32\DRIVERS\NETwNs64.sys
    Image name: NETwNs64.sys
    Timestamp:        Tue Nov 09 17:16:31 2010 (4CD92D8F)
    CheckSum:         0082008A
    ImageSize:        0086B000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

To perform a clean install of a driver, follow this tutorial:

• How to Clean Left Over Driver Files with Driver Sweeper

Reduce items at start-up. Nothing except anti-virus is required:

• http://www.sevenforums.com/tutorials/1401-startup-programs-change.html
• http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html

http://www.eset.com/us/online-scanner/
Perform a System File Check:

• Click on the rb:
• Type CMD on Search
• Left click and Run as Administrator
• Type SFC /scannow

Full tutorial here:

• http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Make scans with the following:

Kaspersky TDSSKiller

• Anti-rootkit utility TDSSKiller

ESET online scanner

• Free Online Virus Scanner | ESET

Disk Check on your hard disk for file system errors and bad sectors on it:

• http://www.sevenforums.com/tutorials/433-disk-check.html

Check for heating issues using Speccy or HWmonitor

• HWMonitor
• Speccy

Upload a screen shot: http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

 

[Huck5]

Thanks very much for the quick response, it is much appreciated.

I will try this fix as soon as possible. Right now I am working on assignments for school, and I don't want to cause any possible additional problems by updating drivers, as I need it to be functioning (and don't want to spend few hours fixing it).

I will edit this reply with the information you requested, and any additional information I might be able to provide, once I have attempted the suggested fix.

Again, thank you. I do appreciate your time.

 

[Huck5]

I apologize in advance,

I can't immediately find the 'edit' button, so I'm writing a new post.

I've got to the Disk Check step. I am curious if this is where you wanted the screenshot(s) taken? I feel like it might be difficult to time my proximity with the computer with the completion of the Disk Check. Is there a way to capture the data in a log/txt file somewhere, for easier access?

ESET found a number of problems (I believe n > 6). I'm sure that had something to do with it.

Also, I did not use Driver Sweeper in my installation of the Intel Wireless driver, because it appeared the application only removed traces of NVIDIA/(etc) graphics drivers. I downloaded an alternate driver-sweeper, which I also ended up not using (as it wanted to remove an Intel driver, which was not the network driver I uninstalled). I resorted to simply uninstalling the driver via Add/Remove. Restart. Re-Installing new driver. I have not encountered any issues yet, so it seems it worked fine.

I have downloaded HWM to monitor core temperatures.

Again, I would like to thank you for the your time in assisting me with my problem.

Cheers,

 

[koolkat77]

OKay thanks for the update, observe for further issues & keep us posted.

 

[Huck5]

All steps completed.

OK! I've completed all the steps recommended above (excluding steps mentioned in previous post).

Here is a screenshot of HWM. This is after my computer has been running for a couple of hours, at a minimum/regular stress-level (Running Eclipse, bunch of Firefox tabs, Dropbox in background, MSWord, and calculator).

View attachment 295269

To me these seem pretty high. In attempt to lower them, I'll try to figure out a means to keep my laptop more elevated while operating, to increase airflow to vents.

The only other option I can think of to increase airflow, is to dismantle the PC Shell and remove excess dust that may be clogging vents or fan. Though this is something I would like to avoid, I have not yet cleaned the inside of the computer in the year or more that I've had it. Prior to doing this I would ensure that any warranty I have on the computer has expired, so as not to void.

If you have any other suggestions to decrease core temps, please advise.

Again, thank you for your assistance.

Due to the infrequent nature of the BSOD, it is hard to say for sure whether the problem has indeed been remedied, but I am confident that updating the Intel Wifi driver (and removing adware,etc through free online scan) has solved the issue.

Thanks team!

Cheers,

 

[essenbe]

Without dismantling your laptop, I can only suggest blowing out all vents with a can of compressed air, try to keep it on a flat level surface so no vents are blocked and look into a laptop cooler. If any or all of these have been suggested already, I apologize. But, I do think those temps are way too high. They need to be reduced however you decide to do it. Dismantling a laptop is not a small matter. Normally the case has to be removed as well as the screen and keyboard. You Tube is full of videos on how it's done. Usually an authorized service center for your laptop can do it without voiding the warranty, but that can be expensive.

EDIT: If you also still have trouble with BSODs I would try memtest86+. http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html it takes quite a few hours to run a complete 8 passes, so it's best to run it overnight. Also, there is a difference in memtest86 and memtest86+. I would recommend memtest86+ as it appears to be the most reliable.

 

[Huck5]

Thank you, I appreciate your advice.

I blew compressed air into my previous laptop, and this actually caused dust to clog the fan so that it could not spin. This, obviously, caused my computer to overheat (especially since I thought things were fine for some time, until I realized my fan wasn't just running quietly). In the end that laptop's MOBO-embedded graphics card fried...

So I don't want to use compressed air.

I have, due to that incident, had some experience taking laptops apart (as I had to free up the fan somehow).

I will look into memtest86+ when I have some free time (which may not be for a week or so).

Again, I appreciate all of your assistance!

Thanks,

 

[essenbe]

Just let us know if we can be of any assistance to you. From what little I know of your problems, I am sure you are aware, those temps have to come down. I would consider if you go as far as the dismantling of the laptop, new thermal paste on the CPU if you can.

 

[Huck5]

Yeah, the temps aren't normally that high. Right now they are steady ~55*. Pack highest at 60*.

Laptop was refurbished (by manufacturer) when purchased, so it's likely the thermal paste was not replaced. I've swapped thermal paste on my PS3 before; I imagine the process is quite similar.

Again, thanks for all your help!

I'll mark this as solved now since, to the best of my knowledge, the BSOD has been cured.

Cheers, team!

EDIT: After a bit of experimentation I believe I've discovered the route of my overly high core temperatures. It appears that my USB-Powered external-soundcard/midi-controller takes a pretty big toll on my CPU. High temperatures seem to coincide with using it to play music from iTunes through my stereo. (If anyone interested).

 

[essenbe]

Thanks, I hope things work out well for you. If you need anything further, we'll be right here. Good luck.