Wireless adapter causing system error

Operating under Windows XP Home, my laptop connects perfectly at home, but
comes up with a serious system error at my office which produce a stop. At
home there are two unsecure networks recognized, mine and a neighbor's. At
the office there are several, nearly all of which are secure. The computer
has recently had most of its components replaced, including a new hard disk,
and Windows has been reinstalled, including SP2. If I disable the wireless
adapter, there is no error.

Any ideas?

Lon Sarnoff

Lon Sarnoff wrote:
> Operating under Windows XP Home, my laptop connects perfectly at home, but
> comes up with a serious system error at my office which produce a stop. At
> home there are two unsecure networks recognized, mine and a neighbor's. At
> the office there are several, nearly all of which are secure. The computer
> has recently had most of its components replaced, including a new hard disk,
> and Windows has been reinstalled, including SP2. If I disable the wireless
> adapter, there is no error.
>
> Any ideas?
>
> Lon Sarnoff
>

Providing the details of the "serious system error," including the stop
code, might help. Another interesting tidbit would be to tell us if you
have "connected perfectly at home" *after* you made all of those changes.

--
Lem -- MS-MVP - Networking

To the moon and back with 2K words of RAM and 36K words of ROM.
http://en.wikipedia.org/wiki/Apollo_Guidance_Computer
http://history.nasa.gov/afj/compessay.htm

Hi
How do you expect to connect in the office, do you have the security code,
or and the logon credentials or you are just trying and erroring to connect
to protected, or special netwroks.
Jack (MVP-Networking).

"Lem" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Lon Sarnoff wrote:
>> Operating under Windows XP Home, my laptop connects perfectly at home,
>> but comes up with a serious system error at my office which produce a
>> stop. At home there are two unsecure networks recognized, mine and a
>> neighbor's. At the office there are several, nearly all of which are
>> secure. The computer has recently had most of its components replaced,
>> including a new hard disk, and Windows has been reinstalled, including
>> SP2. If I disable the wireless adapter, there is no error.
>>
>> Any ideas?
>>
>> Lon Sarnoff
>>
>
> Providing the details of the "serious system error," including the stop
> code, might help. Another interesting tidbit would be to tell us if you
> have "connected perfectly at home" *after* you made all of those changes.
>
> --
> Lem -- MS-MVP - Networking
>
> To the moon and back with 2K words of RAM and 36K words of ROM.
> http://en.wikipedia.org/wiki/Apollo_Guidance_Computer
> http://history.nasa.gov/afj/compessay.htm

The stop code was 0x0000000A
parameter 1 = 0xFF111072
parameter 2 = 0x00000002
parameter 3 = 0x00000000
paramtere 4 = 0x80406B8C

I was attempting, and indeed had successfully connected at the office
through a secured connection using a WEP.

Since posting I have had an idea. At home, the router's name is the
default, unchanged name, linksys. I now realize that there is a connection
in my office building also called linksys, a network different from the
linksys at home. I suspect that my laptop has been trying to connect to the
linksys at the office using configuration information related to the linksys
at home. Do you think that might be possible, and might be causing the
problem?

"Lon Sarnoff" wrote:

> Operating under Windows XP Home, my laptop connects perfectly at home, but
> comes up with a serious system error at my office which produce a stop. At
> home there are two unsecure networks recognized, mine and a neighbor's. At
> the office there are several, nearly all of which are secure. The computer
> has recently had most of its components replaced, including a new hard disk,
> and Windows has been reinstalled, including SP2. If I disable the wireless
> adapter, there is no error.
>
> Any ideas?
>
> Lon Sarnoff
>

Lon Sarnoff wrote:
> The stop code was 0x0000000A
> parameter 1 = 0xFF111072
> parameter 2 = 0x00000002
> parameter 3 = 0x00000000
> paramtere 4 = 0x80406B8C
>
> I was attempting, and indeed had successfully connected at the office
> through a secured connection using a WEP.
>
> Since posting I have had an idea. At home, the router's name is the
> default, unchanged name, linksys. I now realize that there is a connection
> in my office building also called linksys, a network different from the
> linksys at home. I suspect that my laptop has been trying to connect to the
> linksys at the office using configuration information related to the linksys
> at home. Do you think that might be possible, and might be causing the
> problem?
>
> "Lon Sarnoff" wrote:
>
>> Operating under Windows XP Home, my laptop connects perfectly at home, but
>> comes up with a serious system error at my office which produce a stop. At
>> home there are two unsecure networks recognized, mine and a neighbor's. At
>> the office there are several, nearly all of which are secure. The computer
>> has recently had most of its components replaced, including a new hard disk,
>> and Windows has been reinstalled, including SP2. If I disable the wireless
>> adapter, there is no error.
>>
>> Any ideas?
>>
>> Lon Sarnoff
>>

If you received "0x0000000A: IRQL_NOT_LESS_OR_EQUAL" see
http://www.aumha.org/a/stop.php#0x0a

Because you said that you had changed many hardware components and also
reinstalled WinXP, and also because you said that the problem doesn't
happen if you disable the wireless adapter, my guess is that you didn't
install the proper driver for your wireless adapter when you reinstalled
WinXP.

You didn't say whether you had successfully connected anywhere (home or
office) since you reinstalled.

Completely apart from the 0xA stop code, your concern about connecting
to the wrong wireless network is well-founded. If there are two
wireless networks with the same name, one with encryption and the other
without, you will have problems connecting to one or the other. Do the
following, assuming that you are using Windows to configure the wireless
adapter in your computer:

1. From "View Available Wireless Networks" ("Choose a wireless
network") screen, under "Network Tasks," click on "Change the order of
preferred networks."

2. You will see a list of "Preferred networks." I suggest that you
delete *all* of these.

3. Access your router's configuration utility using a computer
connected to it by Ethernet cable. This can be a temporary connection.
Change the SSID of the router to something unique and recognizable
other than your name or address. While you're at it, set your router to
use WPA2 or WPA encryption (you want the "personal," PSK, or "pre-shared
key" flavor of WPA/WPA2). WEP encryption is so outdated (it didn't take
very long) that it can be cracked in a few minutes using utilities
easily available on the Internet. If the wireless adapter in your
laptop is reasonably new, and has an up-to-date driver, it should
support WPA2. Make sure that you have installed the Windows Update from
http://support.microsoft.com/kb/917021

You'll now be able to connect to your home network (and recognize it by
its unique SSID) by entering the WPA/WPA2 password you configured in
your router. If you also want to connect to the "linksys" network at
work, you can do that too, by entering the appropriate passkey for that
network. By using separate names, you won't confuse the Windows
wireless configuration utility.


--
Lem -- MS-MVP - Networking

To the moon and back with 2K words of RAM and 36K words of ROM.
http://en.wikipedia.org/wiki/Apollo_Guidance_Computer
http://history.nasa.gov/afj/compessay.htm

In addition to everything else that has been stated, it is
considered bad practice to NOT change the name of the SSID from
whatever was supplied by the manufacturer. You might suggest to the
person that runs your office network that they change the SSID name
from Linksys to something else.

On Sun, 16 Dec 2007 20:24:01 -0800, Lon Sarnoff
<(E-Mail Removed)> wrote:

>I suspect that my laptop has been trying to connect to the
>linksys at the office using configuration information related to the linksys
>at home. Do you think that might be possible, and might be causing the
>problem?
--

Barb Bowman
MS Windows-MVP
http://www.microsoft.com/windowsxp/e...ts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/

I eliminated the ambiguity between the two "linksys" routers by renaming the
one at home. Connection at home continues to be perfect. As soon as windows
attempts the connection at the office (to a secured network), it crashes. If
I disable the network adapter, there is no problem in the bootup. Very
bizarre! Any further suggestions?

"Lon Sarnoff" wrote:

> The stop code was 0x0000000A
> parameter 1 = 0xFF111072
> parameter 2 = 0x00000002
> parameter 3 = 0x00000000
> paramtere 4 = 0x80406B8C
>
> I was attempting, and indeed had successfully connected at the office
> through a secured connection using a WEP.
>
> Since posting I have had an idea. At home, the router's name is the
> default, unchanged name, linksys. I now realize that there is a connection
> in my office building also called linksys, a network different from the
> linksys at home. I suspect that my laptop has been trying to connect to the
> linksys at the office using configuration information related to the linksys
> at home. Do you think that might be possible, and might be causing the
> problem?
>
> "Lon Sarnoff" wrote:
>
> > Operating under Windows XP Home, my laptop connects perfectly at home, but
> > comes up with a serious system error at my office which produce a stop. At
> > home there are two unsecure networks recognized, mine and a neighbor's. At
> > the office there are several, nearly all of which are secure. The computer
> > has recently had most of its components replaced, including a new hard disk,
> > and Windows has been reinstalled, including SP2. If I disable the wireless
> > adapter, there is no error.
> >
> > Any ideas?
> >
> > Lon Sarnoff
> >

delete any connections named Linksys in the list of preferred
wireless networks on the computer. restart. what happens? and tell
the folks at work who run the network that they should change the
SSID name and that WEP is not secure.

On Fri, 21 Dec 2007 16:34:01 -0800, Lon Sarnoff
<(E-Mail Removed)> wrote:

>I eliminated the ambiguity between the two "linksys" routers by renaming the
>one at home. Connection at home continues to be perfect. As soon as windows
>attempts the connection at the office (to a secured network), it crashes. If
>I disable the network adapter, there is no problem in the bootup. Very
>bizarre! Any further suggestions?
>
>"Lon Sarnoff" wrote:
>
>> The stop code was 0x0000000A
>> parameter 1 = 0xFF111072
>> parameter 2 = 0x00000002
>> parameter 3 = 0x00000000
>> paramtere 4 = 0x80406B8C
>>
>> I was attempting, and indeed had successfully connected at the office
>> through a secured connection using a WEP.
>>
>> Since posting I have had an idea. At home, the router's name is the
>> default, unchanged name, linksys. I now realize that there is a connection
>> in my office building also called linksys, a network different from the
>> linksys at home. I suspect that my laptop has been trying to connect to the
>> linksys at the office using configuration information related to the linksys
>> at home. Do you think that might be possible, and might be causing the
>> problem?
>>
>> "Lon Sarnoff" wrote:
>>
>> > Operating under Windows XP Home, my laptop connects perfectly at home, but
>> > comes up with a serious system error at my office which produce a stop. At
>> > home there are two unsecure networks recognized, mine and a neighbor's. At
>> > the office there are several, nearly all of which are secure. The computer
>> > has recently had most of its components replaced, including a new hard disk,
>> > and Windows has been reinstalled, including SP2. If I disable the wireless
>> > adapter, there is no error.
>> >
>> > Any ideas?
>> >
>> > Lon Sarnoff
>> >
--

Barb Bowman
MS Windows-MVP
http://www.microsoft.com/windowsxp/e...ts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/

It turns out that the connection names was not the problem, for the system
error continued even after deleting the "linksys" names for the profiles list.

Further research disclosed that Intel has a more recent driver version. I
have downloaded Intel's generic version of the driver, and the problem
appears to have disappeared.

What is annoying is that the fresh reinstall of the XP system, followed by
Windows Update, did not cause an update of the driver. (I guess that drivers
are beyond the purview of the Automatic Update.)

Anyway, thanks for your suggestions. I hope this information might help
others who encounter the same problem.


"Barb Bowman" wrote:

> delete any connections named Linksys in the list of preferred
> wireless networks on the computer. restart. what happens? and tell
> the folks at work who run the network that they should change the
> SSID name and that WEP is not secure.
>
> On Fri, 21 Dec 2007 16:34:01 -0800, Lon Sarnoff
> <(E-Mail Removed)> wrote:
>
> >I eliminated the ambiguity between the two "linksys" routers by renaming the
> >one at home. Connection at home continues to be perfect. As soon as windows
> >attempts the connection at the office (to a secured network), it crashes. If
> >I disable the network adapter, there is no problem in the bootup. Very
> >bizarre! Any further suggestions?
> >
> >"Lon Sarnoff" wrote:
> >
> >> The stop code was 0x0000000A
> >> parameter 1 = 0xFF111072
> >> parameter 2 = 0x00000002
> >> parameter 3 = 0x00000000
> >> paramtere 4 = 0x80406B8C
> >>
> >> I was attempting, and indeed had successfully connected at the office
> >> through a secured connection using a WEP.
> >>
> >> Since posting I have had an idea. At home, the router's name is the
> >> default, unchanged name, linksys. I now realize that there is a connection
> >> in my office building also called linksys, a network different from the
> >> linksys at home. I suspect that my laptop has been trying to connect to the
> >> linksys at the office using configuration information related to the linksys
> >> at home. Do you think that might be possible, and might be causing the
> >> problem?
> >>
> >> "Lon Sarnoff" wrote:
> >>
> >> > Operating under Windows XP Home, my laptop connects perfectly at home, but
> >> > comes up with a serious system error at my office which produce a stop. At
> >> > home there are two unsecure networks recognized, mine and a neighbor's. At
> >> > the office there are several, nearly all of which are secure. The computer
> >> > has recently had most of its components replaced, including a new hard disk,
> >> > and Windows has been reinstalled, including SP2. If I disable the wireless
> >> > adapter, there is no error.
> >> >
> >> > Any ideas?
> >> >
> >> > Lon Sarnoff
> >> >
> --
>
> Barb Bowman
> MS Windows-MVP
> http://www.microsoft.com/windowsxp/e...ts/bowman.mspx
> http://blogs.digitalmediaphile.com/barb/
>

thanks for the update. can you please post the version and link of
the driver that resolved the issue for you?

On Sat, 22 Dec 2007 15:51:00 -0800, Lon Sarnoff
<(E-Mail Removed)> wrote:

>It turns out that the connection names was not the problem, for the system
>error continued even after deleting the "linksys" names for the profiles list.
>
>Further research disclosed that Intel has a more recent driver version. I
>have downloaded Intel's generic version of the driver, and the problem
>appears to have disappeared.
>
>What is annoying is that the fresh reinstall of the XP system, followed by
>Windows Update, did not cause an update of the driver. (I guess that drivers
>are beyond the purview of the Automatic Update.)
>
>Anyway, thanks for your suggestions. I hope this information might help
>others who encounter the same problem.
>
>
>"Barb Bowman" wrote:
>
>> delete any connections named Linksys in the list of preferred
>> wireless networks on the computer. restart. what happens? and tell
>> the folks at work who run the network that they should change the
>> SSID name and that WEP is not secure.
>>
>> On Fri, 21 Dec 2007 16:34:01 -0800, Lon Sarnoff
>> <(E-Mail Removed)> wrote:
>>
>> >I eliminated the ambiguity between the two "linksys" routers by renaming the
>> >one at home. Connection at home continues to be perfect. As soon as windows
>> >attempts the connection at the office (to a secured network), it crashes. If
>> >I disable the network adapter, there is no problem in the bootup. Very
>> >bizarre! Any further suggestions?
>> >
>> >"Lon Sarnoff" wrote:
>> >
>> >> The stop code was 0x0000000A
>> >> parameter 1 = 0xFF111072
>> >> parameter 2 = 0x00000002
>> >> parameter 3 = 0x00000000
>> >> paramtere 4 = 0x80406B8C
>> >>
>> >> I was attempting, and indeed had successfully connected at the office
>> >> through a secured connection using a WEP.
>> >>
>> >> Since posting I have had an idea. At home, the router's name is the
>> >> default, unchanged name, linksys. I now realize that there is a connection
>> >> in my office building also called linksys, a network different from the
>> >> linksys at home. I suspect that my laptop has been trying to connect to the
>> >> linksys at the office using configuration information related to the linksys
>> >> at home. Do you think that might be possible, and might be causing the
>> >> problem?
>> >>
>> >> "Lon Sarnoff" wrote:
>> >>
>> >> > Operating under Windows XP Home, my laptop connects perfectly at home, but
>> >> > comes up with a serious system error at my office which produce a stop. At
>> >> > home there are two unsecure networks recognized, mine and a neighbor's. At
>> >> > the office there are several, nearly all of which are secure. The computer
>> >> > has recently had most of its components replaced, including a new hard disk,
>> >> > and Windows has been reinstalled, including SP2. If I disable the wireless
>> >> > adapter, there is no error.
>> >> >
>> >> > Any ideas?
>> >> >
>> >> > Lon Sarnoff
>> >> >
>> --
>>
>> Barb Bowman
>> MS Windows-MVP
>> http://www.microsoft.com/windowsxp/e...ts/bowman.mspx
>> http://blogs.digitalmediaphile.com/barb/
>>
--

Barb Bowman
MS Windows-MVP
http://www.microsoft.com/windowsxp/e...ts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/