I somewhat doubt your problem has anything to do with any memory leak
since there is no known leak in ndis.vxd. The only known memory leak
being in ndiswan.vxd which is very specific to certain hardware and very
rarely encountered. As a result Microsoft have not released an updated
version of ndis.vxd since this has not been found to be necessary.
There are a number of KB articles that might help you including KB279356 -
"How To NDIS Debugging Tips for Windows ME"
(http://support.microsoft.com/?kbid=279356) but probably only of help if
you are going to write your own driver, and KB261766 - "Hang at Startup or
Shutdown with Ndis.vxd Enabled"
(http://support.microsoft.com?kbid=261766).

Signature
Mike Maltby MS-MVP
mike.maltby@gmail.com
> While runing a program I get a blue screen message that
> says exception 0E in Vxd Ndis. After looking at some other
[quoted text clipped - 6 lines]
> Is there any thing else that needs to be upgraded because
> of my dsl drivers and modem interacting with Win ME?
El Blamange - 24 Dec 2004 15:59 GMT
> I somewhat doubt your problem has anything to do
> with any memory leak
The main problem is that I get this 0E exception
from the ndis vxd and I can't use the internet unless I restart. People keep
telling me that in order to fix the problem I need to upgrade my drivers.
This is difficult for me considering I have a 100/10m ethernet pci network
interface card attached to a toshiba pcx 2500
dsl modem. I went to the toshiba site and found no drivers
at all for any of their modems. The next option I have in order to fix this
error is to upgrade ndis, After looking in the registry I noticed that I have
Ndis 3 unfortunately I can't find an ndis 5 upgrade for win me.
I'm just following the steps the knowledge base article
says to in order to fix this 0E exception error.
Mike M - 24 Dec 2004 16:23 GMT
At the risk of repeating myself I very much doubt that your problem has
anything whatsoever to do with ndis.vxd. No upgrade is required. Instead
undo the changes that you made to your PC prior to this problem starting.

Signature
Mike Maltby MS-MVP
mike.maltby@gmail.com
>> I somewhat doubt your problem has anything to do
>> with any memory leak
[quoted text clipped - 13 lines]
> I'm just following the steps the knowledge base article
> says to in order to fix this 0E exception error.