Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Windows NT Stop error with Intel Pro 100+ card

78 views
Skip to first unread message

Chris Apfelbeck

unread,
Jan 5, 1999, 3:00:00 AM1/5/99
to
Has anyone encountered the following Stop Error with the Intel Pro 100+ network card?

Stop: 0x0000000A (0xC9BDS509, 0X00000002, 0X0000000, 0XF8FA1AA7)
IRQL_NOT_LESS_OR_EQUAL ***Address f8fa1aa7 has base at f8fa0000 - e100bnt.sys

CPUID: Genuine Intel 5.4.3 irql: 1f DFC SYSVER 0xf0000565

It occurs sporadically, a user can log on and do some work and may not have a Stop Error for a day or two and then have three or four in the same day.

I have downloaded and installed the latest drivers but they didn't solve the problem.

Thank you.

Chris Apfelbeck
WI Dept of Veterans Affairs
capf...@mail.state.wi.us

Colin Kissack

unread,
Jan 6, 1999, 3:00:00 AM1/6/99
to
Hi Chris

Me too, many people seem to be having a problem with the Pro 100's.

We have an NT Server with the Dual port and have the same message but different
address. The Stop Blue screen is still associated with the e100bnt.sys driver.

Hope we all get a resolution soon.

Cheers.

Colin.

Sam Shipp

unread,
Jan 7, 1999, 3:00:00 AM1/7/99
to
Chris and Colin,

I am also recieving the very same infrequent stop errors on various NT workstations, and am attempting to resolve it. Is it fair to say from the info posted here, that the problem is in the driver loading for that adapter on the NT OS platform, and that until it is addressed in a new one, there isn't a workaround? Input from any and all is welcomed.

Thanks,

Sam Shipp
Network Analyst
PVA-EPVA, INC


Phil L.

unread,
Jan 7, 1999, 3:00:00 AM1/7/99
to
--
Thank you for your post.

Try this.

Extract E100B.SYS (the NDIS 3 driver) from the /NT directory of the
installation diskette, and rename it to E100BNT.SYS. Then replace the
NDIS 4 driver (E100BNT.SYS) in the system32\drivers directory. Let me
know if this helps.

--
Phil L.
Intel Internet Customer Support

*Third-party marks and brands are the property of their respective
owners.

Colin Kissack

unread,
Jan 8, 1999, 3:00:00 AM1/8/99
to
Phil

I have tried this and the stability appears to be better.

There seems to be a performance issue that I cant put my finger on at present,
things arent as they were with the NDIS 4 driver.

Whats the difference ?

Many thanks.

Colin.

Phil L.

unread,
Jan 8, 1999, 3:00:00 AM1/8/99
to
--
Thank you for your post.

I am not sure what you are looking for when you ask, "What is the
difference between NDIS 3 and NDIS 4?" For detailed technical
information about the NDIS wrapper, you should check Microsoft's support
site.

Colin Kissack

unread,
Jan 11, 1999, 3:00:00 AM1/11/99
to
Phil

I wasnt looking for a detailed tech explanation, just basically why does the
NDIS3 version work better and is more stable than the NDIS4 version.

Will there be a new driver out soon ?

Colin.


Phil L.

unread,
Jan 13, 1999, 3:00:00 AM1/13/99
to
--
Thank you for your post.

It has something to do with the pointers from the NDIS wrapper. They
are different in the later version of NDIS. By the way, we just posted
a new version of the driver for your adapter today.

Aiysha Bellamy

unread,
Jan 14, 1999, 3:00:00 AM1/14/99
to
I was having similar intermittent drop outs. Once I updated to SP3,
these errors stopped. HOpe this helps

Michael Loeckle

unread,
Jan 19, 1999, 3:00:00 AM1/19/99
to
We are experiencing this same error exactly as described below
which is another message from this news group. We will try the
proposed solution from the 2.57 diskette and see what happens.
It seems to have started when we began installing drivers from
the 2.5 version and above. I would go back to 2.0 but I cannot
find our disk. If there is a better way to fix this please let
me know.

Michael Loeckle
MicroSage, Inc.
mloe...@microsage.com

Chris Apfelbeck wrote:
>
> Has anyone encountered the following Stop Error with the Intel Pro 100+
network card?
>
> Stop: 0x0000000A (0xC9BDS509, 0X00000002, 0X0000000, 0XF8FA1AA7)
> IRQL_NOT_LESS_OR_EQUAL ***Address f8fa1aa7 has base at f8fa0000 - e100bnt.sys
>
> CPUID: Genuine Intel 5.4.3 irql: 1f DFC SYSVER 0xf0000565
>
> It occurs sporadically, a user can log on and do some work and may not have a
Stop Error for a day or two and then have three or four in the same day.
>
> I have downloaded and installed the latest drivers but they didn't solve the
problem.
>
> Thank you.
>
> Chris Apfelbeck
> WI Dept of Veterans Affairs
> capf...@mail.state.wi.us

--
Thank you for your post.

Try this.

Extract E100B.SYS (the NDIS 3 driver) from the /NT directory of the
installation diskette, and rename it to E100BNT.SYS. Then replace the
NDIS 4 driver (E100BNT.SYS) in the system32\drivers directory. Let me
know if this helps.

--

Patrick

unread,
Feb 3, 1999, 3:00:00 AM2/3/99
to
HELP!! I am having these blue screens also, I've updated the NIC's with the latest drivers for the pro 100+ and still cpu stops-any sugguestions???? Any help would be very much appreciated.
Thank-you,
Patrick Doring

Phil L.

unread,
Feb 3, 1999, 3:00:00 AM2/3/99
to
--
Thank you for your post.

Have you tried the solution that I posted in this thread? What is the
tezt of you stop screen? Let me know.

0 new messages