Interesting

cormie

Following on from this thread, I have come across a strange occurance regarding the so called blue screen of death.

It was diagnosed to be a hardware (wireless lan) error with the following info:

Stop: 0x000000D1 (0x82400000,0x00000002,0x00000000,0xf808aa98)

w22N51.sys address f808aa98 base at f8017000

Date Stamp 3ff54d71




Every so often it would happen again, just out of the blue it would go to the blue screen of death and I would have to restart the laptop. It could happen at any given time.


However, today I was backing up an audio cd with Exact Audio Copy and when I hit Alt+G to get the DB info the bsod appeared. I tried it again to make sure it wasn't just another irregular occurance and it happened again.

So for some reason it goes to the bsod when I hit Alt+G in Exact Audio Copy and also irregularly on different occasions just out of the blue.

Any help would be appreciated.
Thanks

cormie

any feedback is appreciated:)

Random

Blue screens are notoriously difficult to track down. The error messages are often beyond misleading and send you in the opposite direction.

Strip your system down to the bare essentials and work your way up until you begin to get the blue screens.

Gosh

Found this @ http://www.project-insomnia.com/2004_08_01_archive.shtml

Specific to BSoD (1/4 way down page)

My Dell Inspiron 600m notebook came with the Intel 2200BG wireless NIC. Since activating WPA (Wireless Protected Access) on my new Linksys WAP54G AP, I've gotten a BSoD referencing the 2200BG driver (w22n51.sys) whenever I try to telnet to an SMTP server. A quick Google on 'w22n51.sys bsod' turned up this thread (see below) from HP's Business Support Forums. Apparently Intel knows about the problem and has addressed it in a beta driver, but they are not actually shipping the beta driver even to people reporting the problem. Luckily someone on that thread has made the driver available.
If you are experiencing this problem (if you have the Intel 2200BG wireless NIC and are using WPA on your wireless network), you should install the beta driver from the link on that thread. I did and have seen zero ill effects, and the BSoD problem is fixed.
One caveat: Installing the new driver will clear any WEP or WPA keys you may have saved. You'll just need to re-enter the keys to connect to your encrypted networks.

http://forums1.itrc.hp.com/service/forums/bizsupport/questionanswer.do?admit=716493758+1109617891079+28353475&threadId=631777

cormie

Thanks but it's a laptop

Gosh

cormie wrote:

Thanks but it's a laptop

For notebook - read laptop

What version of w22n51.sys do you have?
Do you have the Intel 2200BG wireless NIC in your laptop?

cormie

Hi,
Thanks allot for that Gosh,
my "thanks, but it's a laptop" post was for Ciaranfo's suggestion of stripping it apart.

I will try the driver update!!! hope it works, thanks again!

Gosh

If it is the Intel 2200BG wireless NIC here's the latest driver download

http://downloadfinder.intel.com/scripts-df/detail_desc.asp?strState=LIVE&ProductID=1637&DwnldID=7822

cormie

Hi again,
yes, it's the 2200BG. Unfortunately, the link that was posted in the above thread didn't work but it was posted Aug 2004 so do you reckon the update you provided above should work? I bought the laptop in December so hopefully it will be an update of the one I currently have, I'll give it a shot and see!
Thanks again!

cormie

:mad: Every time I try to install the above driver an error occurs at the same place every time and wont continue.

ok hang on.... I just right clicked the file and chose extract to desktop, it extracted but gave a message saying there were loads of broken files, but I ran autorun anyway. Now I have a new icon in taskbar showing signal which is excellent and I am posting this...

Furthermore I opened EAC, clicked ALT+G and hey presto, it got the CDDB info without the BSOD!! I think I'm ok so:)

Seems a bit dodgy but let's hope it runs error free from now on!!! Thanks for help!

Capt'n Midnight

You want a BSOD from the keyboard ?
http://support.microsoft.com/kb/244139/EN-US/

Windows includes a feature that you can use to cause the system to stop responding
...
1. Start Registry Editor (Regedt32.exe).
2. Locate the following key in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\i8042prt\Parameters
3. On the Edit menu, click Add Value, and then add the following registry value:
Value Name: CrashOnCtrlScroll
Data Type: REG_DWORD
Value: 1
...
holding down the right CTRL key and pressing the SCROLL LOCK key twice.

cormie

Capt'n Midnight wrote:

You want a BSOD from the keyboard ?
http://support.microsoft.com/kb/244139/EN-US/

Hi,
I don't really understand what that is or why I would do it Please elaborate

Mutant_Fruit

Basically, go to the intel site, and download the INTEL drivers for the 2200bg chipset. I had to do that myself last week because i was getting that exact error. So far, i havn't had a problem.

cormie

Mutant_Fruit wrote:

Basically, go to the intel site, and download the INTEL drivers for the 2200bg chipset. I had to do that myself last week because i was getting that exact error. So far, i havn't had a problem.

Hi, I got the drivers and new software and it doesn't have the same problem:) However it has lost connection a few times since last night which wasn't a regular occurance with the last software

cormie

My connection is still a bit dodgy with the new software. I tried to reinstall it and first it gives an excellent connection, then it just gets worse and sometimes disconnects asking me for the password key. But I dont even have to put in the key, it just re-connects after a few seconds.

What's the difference with WPA-2, enterprise, personal etc does anyone know?

It gets REALLY slow sometimes (allot of the time) and another wireless laptop hasn't got the same speed problems, seems to just be since I installed the new software Is it either speed problems or the BSOD? Can I fix this?
Thanks