Problem during loading of the NDIS 5.0 driver

NTDEV
1

Hi All,

   Any body can tell me i’ve got the problem while installing the NDIS miniport driver on the 98 as:

“Trap 14 (0EH) - Page fault 0004, Not Present, Read Access, Supervisor”

Any pointer will be appriciated, This driver is made by me for an ethernet adapter. This crash comes after the DriverEntry called successfully. And the debugee stops working.

Thanks in advance…

Visit Malaysia. Win a free trip! Have an exotic holiday

2

Have you tried adding debug prints before every major step to see what call
it’s actually failing on? I’m not sure what suggestions to offer other than
that. It seems like you are trying to read memory from an invalid address.
You might make sure all of your pointers are properly initialized. You
should at least be able to narrow it down. What things are you using that
require NDIS 5, just out of curiosity?

Matt
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of yatindra vaishnav
Sent: Friday, April 11, 2003 7:34 AM
To: NT Developers Interest List
Subject: [ntdev] Problem during loading of the NDIS 5.0 driver

Hi All,

Any body can tell me i’ve got the problem while installing the NDIS
miniport driver on the 98 as:

“Trap 14 (0EH) - Page fault 0004, Not Present, Read Access, Supervisor”

Any pointer will be appriciated, This driver is made by me for an ethernet
adapter. This crash comes after the DriverEntry called successfully. And the
debugee stops working.

Thanks in advance…



----------------------------------------------------------------------------
–
Visit Malaysia. Win a free trip! Have an exotic holiday —
You are currently subscribed to ntdev as: xxxxx@positivenetworks.net
To unsubscribe send a blank email to xxxxx@lists.osr.com

3

Hi Matt,

               As i already written that the DriverEntry Routine is getting completed, but the MiniportInitilize is not getting called. and the 98 Kernel get stuck with the error i mentioned. Hey! it is rt that this error shud come if ur pointer is mismatching, but after successfull completion of the DriverEntry and the calling to the MiniportInitialize,there is some thing happening which is affecting the Kernel and it is raising the trap 14.



Vrroooom…… Fasten your seatbelts. Get set for F1 2003

4

It sounds to me like you may be filling out your ndis characteristics
structure with invalid or incomplete function pointers. Does the call to
NdisMRegisterMiniport succeed? I’m guessing it does. It’s a shame that
your debugger is freezing when things crash. If you could figure out how to
fix that, you could look at EIP to see if it’s pointing to an address that
is invalid. This would be the case if NDIS attempted to call into one of
the functions that you specified in NDIS characteristics that happened to be
invalid. It would also explain why you are getting a page fault.

One other thought, do you zero out your characteristics structure?

Matt
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of yatindra vaishnav
Sent: Friday, April 11, 2003 10:40 AM
To: NT Developers Interest List
Subject: [ntdev] RE: Problem during loading of the NDIS 5.0 driver

Hi Matt,

As i already written that the DriverEntry Routine is
getting completed, but the MiniportInitilize is not getting called. and the
98 Kernel get stuck with the error i mentioned. Hey! it is rt that this
error shud come if ur pointer is mismatching, but after successfull
completion of the DriverEntry and the calling to the
MiniportInitialize,there is some thing happening which is affecting the
Kernel and it is raising the trap 14.



----------------------------------------------------------------------------
–
Vrroooom?? Fasten your seatbelts. Get set for F1 2003 —
You are currently subscribed to ntdev as: xxxxx@positivenetworks.net
To unsubscribe send a blank email to xxxxx@lists.osr.com

5

Hi Matt,

See inlines.

 

It sounds to me like you may be filling out your ndis characteristics structure with invalid or incomplete function pointers.

If assigning the Pointer to the function by function name is the invalid way then i’m doin that only.

 

Does the call to NdisMRegisterMiniport succeed?

Yes it is getting succeed.

 

I’m guessing it does.

yes ur rt.

 

It’s a shame that your debugger is freezing when things crash.

It’snt debugger freezing but as the kernel is getting stuck-up, the debugger is showing that only.

 

If you could figure out how to fix that, you could look at EIP to see if it’s pointing to an address that is invalid. This would be the case if NDIS attempted to call into one of the functions that you specified in NDIS characteristics that happened to be invalid. It would also explain why you are getting a page fault.

After completion of the DriverEntry first interface called is “MiniportInitialize” rt?

 

 

One other thought, do you zero out your characteristics structure?

Yes, i’m zeroing the structure.

 

Matt

Visit Malaysia. Win a free trip! Have an exotic holiday

6

Yogi,

Yes, MiniportInitialize should be the first function to be called.
Which debugger are you using for 98? wdeb386, wdeb98, or softice? It sounds
like to me you are doing all the things you need to do. Is this miniport
for a virtual or physical NIC? I’m wondering if perhaps there is not an INF
problem. It seems unlikely, but possible I suppose.

Matt
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of yatindra vaishnav
Sent: Friday, April 11, 2003 11:18 AM
To: NT Developers Interest List
Subject: [ntdev] RE: Problem during loading of the NDIS 5.0 driver

Hi Matt,
See inlines.


It sounds to me like you may be filling out your ndis characteristics
structure with invalid or incomplete function pointers.
If assigning the Pointer to the function by function name is the
invalid way then i’m doin that only.

Does the call to NdisMRegisterMiniport succeed?
Yes it is getting succeed.

I’m guessing it does.
yes ur rt.

It’s a shame that your debugger is freezing when things crash.
It’snt debugger freezing but as the kernel is getting stuck-up, the
debugger is showing that only.

If you could figure out how to fix that, you could look at EIP to see if
it’s pointing to an address that is invalid. This would be the case if NDIS
attempted to call into one of the functions that you specified in NDIS
characteristics that happened to be invalid. It would also explain why you
are getting a page fault.
After completion of the DriverEntry first interface called is
“MiniportInitialize” rt?

One other thought, do you zero out your characteristics structure?
Yes, i’m zeroing the structure.

Matt

----------------------------------------------------------------------------
–
Visit Malaysia. Win a free trip! Have an exotic holiday —
You are currently subscribed to ntdev as: xxxxx@positivenetworks.net
To unsubscribe send a blank email to xxxxx@lists.osr.com

7

Yogi,

Try turning on full debug spew from NDIS just before you call NdisMRegisterMiniport. When in the debugger, do:

wa ndis (to load the symbols, if they’re not already)
e ndisdebugsystems ff ff ff ff
e ndisdebuglevel 00 00 00 00
g

This may produce something that will give more insight.

Bryan S. Burgin
xxxxx@microsoft.com

This posting is provided “AS IS” with no warranties, and confers no rights.

-----Original Message-----
From: Matt Miller [mailto:xxxxx@positivenetworks.net]
Sent: Friday, April 11, 2003 9:33 AM
To: NT Developers Interest List
Subject: [ntdev] RE: Problem during loading of the NDIS 5.0 driver

Yogi,
?
??? Yes, MiniportInitialize should be the first function to be called.? Which debugger are you using for 98? wdeb386, wdeb98, or softice?? It sounds like to me you are doing all the things you need to do.? Is this miniport for a virtual or physical NIC?? I’m wondering if perhaps there is not an INF problem.? It seems unlikely, but possible I suppose.
?
Matt
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com]On Behalf Of yatindra vaishnav
Sent: Friday, April 11, 2003 11:18 AM
To: NT Developers Interest List
Subject: [ntdev] RE: Problem during loading of the NDIS 5.0 driver
Hi Matt,
??? See inlines.

?
It sounds to me like you may be filling out your ndis characteristics structure with invalid or incomplete function pointers.
If assigning the Pointer to the function by function name is the invalid way then i’m doin that only.
?
Does the call to NdisMRegisterMiniport succeed??
Yes it is getting succeed.
?
I’m guessing it does.
yes ur rt.
?
It’s a shame that your debugger is freezing when things crash.?
It’snt debugger freezing but as the kernel is getting?stuck-up, the debugger?is?showing that only.
?
If you could figure out how to fix that, you could look at EIP to see if it’s pointing to an address that is invalid.? This would be the case if NDIS attempted to call into one of the functions that you specified in NDIS characteristics that happened to be invalid.? It would also explain why you are getting a page fault.
After completion of the DriverEntry?first?interface called is?“MiniportInitialize” rt?
?
?
One other thought, do you zero out your characteristics structure?
Yes, i’m zeroing the structure.
?
Matt

Visit Malaysia. Win a free trip! Have an exotic holiday —
You are currently subscribed to ntdev as: xxxxx@positivenetworks.net
To unsubscribe send a blank email to xxxxx@lists.osr.com
—
You are currently subscribed to ntdev as: xxxxx@microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

8

Hi Bryan,

                I want to tell u one more thing it is working perfectly on the Windows 2000. Now the question is arised of the portability and binary compatibiliy across the windows platform as the NDIS Specification says. Then only it is giving problem.

 

Thanx for quick reply



Catch the Oscar fever. See winners & losers. Right here