Unsolved

This post is more than 5 years old

Closed

23 Posts

30600

June 29th, 2005 22:00

BSOD/Stop error: DRIVER_IRQL_NOT_LESS_OR_EQUAL: w22n51.sys

It says:

DRIVER_IRQL_NOT_LESS_OR_EQUAL

w22n51.sys - Address F6BBCB98 base at F6B49000, DateStamp 40054b01

What I did was I tried to run a scan using software which finds game servers for you called All Seeing Eye. This software has not caused problems on my desktop.

There must be something wrong with my networking on this laptop, because I also get a similar error when I use Telnet to access an email account. I can open up Telnet and connect to a server but as soon as I send the USER command it crashes to the same kind of BSOD.

It is an Inspiron 8600 with the following network card:

K3444 CARD (CIRCUIT), NETWORK, MINI PCI CARD, INTEL2200, NOT APPLICABLE

or in other words, an Intel Pro 2200 BG Wireless card

and I use the Intel PRO Set software to manage my network.

Please help me solve this problem

51 Posts

June 30th, 2005 03:00

Well, the BSOD certainly looks like a driver problem.  I am not familiar with "All Seeing Eye" but my 6000D has the same wireless card.

In the Networking forum, there is a thread discussing a new generic driver for the Pro 2200 available from the Intel website.  I would suggest trying  this driver and see if it solves your problem.

Good Luck!

 

 

2 Intern

 • 

14.4K Posts

June 30th, 2005 09:00

A link to the latest Intel 2200 wireless ver 9.0.2.0 B/G Card drivers can be found on http://www.notebookforums.com/showthread.php?t=85185&page=4&pp=15

354 Posts

June 30th, 2005 11:00

And on a supporting note to the ones below:  some thinkpad folks are having problems with their Intel 2200 Pro wireless cards.  It would appear in most cases that if you just load up the driver (forget the control applet) and use the Windows Wireless Zero configuration tool, then the card works just fine. 

23 Posts

June 30th, 2005 13:00

Hey, thanks for all your replies!

I decided to first try and disable Intel's PRO Set software and see how Windows manages the network. IT worked! I fired up telenet, connected to my email server and punched in my username bracing for the BSOD... and it didn't happen! Checked my mail everything went OK. Then I launched All Seeing Eye and clicked the search button which produced a BSOD last time (it pings all active servers and gets some information about them) and that went fine as well.

Conclusion: Intel makes lousy drivers.

2 Intern

 • 

14.4K Posts

June 30th, 2005 13:00

hehe, well although you're now using windows to manage your wireless connection, you are still using the intel drivers for the wireless card unless you've totally uninstalled the intel software.

23 Posts

June 30th, 2005 14:00

Yeah you know, I thought about that... there's only one set of drivers- and I didn't touch them or update them. I just changed what software is using them. So it would be more accurate to say Intel's software is poor, because apparantly Intel's wireless software does not know how to use it's own drivers- making some kind of illegal/invalid call resulting in the BSOD I used to get, right?

2 Intern

 • 

14.4K Posts

June 30th, 2005 18:00

Don't mind me, I was just being pedantic.

354 Posts

July 1st, 2005 16:00

I think that you can install the network card driver and leave the network manager software inactive (of course, I could be wrong :) )

2 Intern

 • 

14.4K Posts

July 1st, 2005 17:00

Yes, you are correct in your assumption!
No Events found!

Top