BSOD driver irql not less than or equal to

Hi deathbeckons,

All of your crashes are related to NETIO.SYS

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {28, 2, 0, fffff880018106fd}
Probably caused by : NETIO.SYS ( NETIO!RtlCopyBufferToMdl+1d )

4: 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: 0000000000000028, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880018106fd, address which referenced memory

0: kd> lmvm NETIO
start end module name
fffff880`01a00000 fffff880`01a60000 NETIO (pdb symbols) c:\symbols\netio.pdb\76E292820E9A4B67A41B1C5BDB269DEE2\netio.pdb
Loaded symbol image file: NETIO.SYS
Mapped memory image file: c:\symbols\NETIO.SYS\5034F6A060000\NETIO.SYS
Image path: \SystemRoot\system32\drivers\NETIO.SYS
Image name: NETIO.SYS
Timestamp: Wed Aug 22 16:11:28 2012 (5034F6A0)
CheckSum: 00067D76
ImageSize: 00060000
File version: 6.1.7601.17939
Product version: 6.1.7601.17939
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 3.6 Driver
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: netio.sys
OriginalFilename: netio.sys
ProductVersion: 6.1.7601.17939
FileVersion: 6.1.7601.17939 (win7sp1_gdr.120822-0331)
FileDescription: Network I/O Subsystem
LegalCopyright: © Microsoft Corporation. All rights reserved.

Network I/O Subsystem (maybe available through windows update)

Install all windows updates, look at optional and software updates also.


Please download the latest drivers for your LAN and WLAN devices found here:

http://www.dell.com/support/home/us/en/19?c=us&s=dhs&cs=19&l=en

Install the drivers
Reboot

Post back any progress.

Cheers

Dave

Your network adapter it is.

Code:

Name    [00000007] DW1501 Wireless-N WLAN Half-Mini Card
Driver    c:\windows\system32\drivers\bcmwl664.sys (5.60.48.35, 2.92 MB (3,058,168 bytes), 12/8/2011 12:16 AM)

And it is failing.

Code:

fffff880`03776da8  fffff880`0524ac20Unable to load image \SystemRoot\system32\DRIVERS\bcmwl664.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for bcmwl664.sys
*** ERROR: Module load completed but symbols could not be loaded for bcmwl664.sys
 bcmwl664+0x26c20

Coz it is old.

Code:

fffff880`05224000 fffff880`05513000   bcmwl664 T (no symbols)           
    Loaded symbol image file: bcmwl664.sys
    Image path: \SystemRoot\system32\DRIVERS\bcmwl664.sys
    Image name: bcmwl664.sys
    Timestamp:        Fri Jan 22 09:00:58 2010 (4B591BF2)
    CheckSum:         002F8634
    ImageSize:        002EF000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Search in Dell's site if any possible update is found. Or, if the system is out of warranty, you may change it with a non-problematic card.

Edit: Sorry, Northernsoul55 has already done it

deathbeckons said:

updating using the drivers found at dell seems to have resolved the issue, but i wont be certain until ive let bt run over night. generally the crashes were coming pretty quick after downloading began and its been running for ~5 mins without issue.

arc, do you think it would still be worthwhile to replace my nic? and if so, can you make any recommendations?

Mate, the particular network adapter is very widely troublesome .... but if the driver update solves the issue, keep it.

Recommending an adapter ... better if you need to replace it at one time, ask for a recommendation in Network and sharing section of our forums.

Glad it has helped resolve your issue.

But Arc's advice is sound and maybe you should think of
buying a replacement/back up network adapter in the near future,

See how it goes

Cheers

Dave

Nice to let us know :)
But, as far as the updated drivers are not causing any more crashes, use your existing NIC :)

One request. Please let us know how you have updated the driver elaborately? How have you searched it? How you have found it?

It will help a lot of other people in that case.

Asking the moderators to mark this thread as solved, coz this is a common crash, and this thread may serve other people having similar issue in future.