Tuesday, October 12, 2010

Blue Screen ndis.sys w22n51.sys Intel PRO/Wireless 2200BG

For those who spent hours to solve this Blue Screen of death..

Yesterday I spent like 8 hours or more to find out why my sick old laptop crash when I turn on the wireless radio switch..

The problem is: w22n51.sys

Even tough at first it said ndis.sys, but when I turned all services off the BSOD still happens and said w22n51.sys instead.

Many people couldnt solve this because everywhere on the internet they share the old buggy driver, even on the laptop manufacturer website (mine is acer)..

Intel have fixed this bug on 2009, and post the driver on their website.. So if you have same problem with mine, just go to intel websites and search for new driver for this Intel PRO/Wireless 2200BG and try it..

http://downloadcenter.intel.com/SearchResult.aspx?lang=eng&keyword=%22w22n51%22

For me it solved my problem, no more bsod when I turned on the wireless device..

NOTE:
- many ndis.sys BSOD is simply solved by switching hardware slots (mostly memory)
- many ndis.sys BSOD is actually a different driver problem, so try turn off all windows services and see if the BSOD still happens and caused by other thing.
- turned off all services is done from msconfig (start->run->msconfig), on services tab click disable all services

good luck
.zoc

17 comments:

Bart said...

Hero, thanks.
I actually bought another 2nd hand 2200BG as drivers from Acer couldn't help me either.

Only after trying yet another driver I noticed the w22n51.sys message. Any reboots and BSOD beyond that didn't display W22n51.

Googling that got me here and solved it for me also. Another $15 and 20 hrs down the drain for the wifi-card...

Make free money online said...

While googling i came across your blog, and i think you have done a good job to list this blog.

Browse free phone said...

This has help me solve my laptop problem.
Thanks.

UpdateYoOldCompsGeez said...

Hey I have this same wifi adapter with the smae drivers from a 6 year old laptop for a user, it is an Compaq nc6000 with Wifi Intel 2200BG drivers from 2004. I noticed as well the computer would blue screen on wifi turn "on-age" so I googled a bit and came to this post. I did indeed use the w22n51.sys driver but now it uses:

w29n51.sys
Netw2c32.dll
Netw2r32.dll

With a driver fileversion of 9.0.4.39 andI have been able to turn it on no problem.

Just thought I would update for anyone else having problems

Anonymous said...

Hello to all,
I was stuck with this bsod problem too which ends up rebooting my vintage Sony notebook (2004)non-stop to the point it was killing the old lady. I spent hours online searching until I came across the solution on this website which SOLVED the problem, even as of this day in October 2012! Yes, for my 32-bit computer, I went to the Intel download site and got the file ICS_Dx32.exe version 9.0.4.39, ran the downloaded exe file and restarted. I was almost in tears and I can't be more grateful.

DiegoAGP said...

Thanks you man! I was fighting hours with this BSOD in a Acer TM 291 with 2200BG wifi adapter.. replace ndis.sys, trying old drivers, new drivers from Acer support site, and nothing! so, thanks you for the solution. Great post!

DiegoON said...

Thanks you man! I was fighting hours with this BSOD in a Acer TM 291 with 2200BG wifi adapter.. replace ndis.sys, trying old drivers, new drivers from Acer support site, and nothing! so, thanks you for the solution. Great post!

DiegoAGP said...

Thanks you man! I was fighting hours with this BSOD in a Acer TM 291 with 2200BG wifi adapter.. replace ndis.sys, trying old drivers, new drivers from Acer support site, and nothing! so, thanks you for the solution. Great post!

DiegoON said...

Thanks you man! I was fighting hours with this BSOD in a Acer TM 291 with 2200BG wifi adapter.. replace ndis.sys, trying old drivers, new drivers from Acer support site, and nothing! so, thanks you for the solution. Great post!

PS: the captcha is impossible!

Anonymous said...

I have had the same problem for the last two months. It works now :) Thanks.

Denzil Wraight said...

It works! I had BSODs in 2009 in my ACER Travelmate 4000 but my computer shop never recognised the WLAN as the source of the trouble. A friend thought it could be a hardware problem with the WLAN card (Intel ProWireless 2200BG)so I uninstalled the WLAN card and had no more trouble. I used a USB WLAN stick, until that expired. Last week I found that the internal WLAN which previously worked intermittently wouldn't even load, with a code 10 error in the Device Manager. The new driver (w29n51.sys) fixed the problem. Thank you very much!

AbominĂ¡vel said...
This comment has been removed by the author.
jimmyjones said...

dude, was working on a reinstallation for my girlfriend - it would have been a big issue if i couldnt get it working... you not only saved me from sweating but also from the weeks of evil eye contact and probably my balls from being, well reused... much appreciated, if you are ever in germany i'll buy you a drink

Anonymous said...

Thx very much, this helped me to fix my BSoD Problem.

Unknown said...

Had the same problem - thinking it was ndis.sys. Had a look at the drivers - and couldn't get them updated. Googled the driver name "w22n51.sys" and found this! Thanks alot!

Anonymous said...

Thanks it's solved my problem

Don Ramsey said...

I was having BSODs every time I reset the laptop but it cleared the screen too quickly for me to be able to read anything. I finally thought of using my cell phone camera in the video mode instead of the picture mode and took a mini movie of the screen. When I played it back on my phone I was able to freeze the video at the BSOD. I pinch zoomed on the name of the driver, Googled it and found your wonderful page. I found the updated driver at the Intel site, downloaded the zip file and installed the newest driver that they had by clicking on the installation exe file. After the install I rebooted the computer just fine. Thanks so much. I am leaving this note for anyone else who is having the problem of not being able to see the BSOD because the computer reboots too quickly.
-- Don