NdisReadNetworkAddress = Fatal System Error

Hi,

I am porting a WinNT4 driver to Win2k, and at the same time splitting it
into a miniport and intermediate driver. In the intermediate driver’s
MiniportInitialize function, I attempt to retrieve the MAC address of
the network card I’m talking to. In order to do this, I call
NdisOpenConfiguration to get a config handle. I then attempt to call
NdisReadNetworkAddress. During this call, I get this error in WinDbg:

*** Fatal System Error: 0x0000000a
(0xE10088AC,0x00000002,0x00000000,0x8049A95C)

Break instruction exception - code 80000003 (first chance)

A fatal system error has occurred.
Debugger entered on first try; Bugcheck callbacks have not been invoked.

A fatal system error has occurred.

************************************************************************
*******
*
*
* Bugcheck Analysis
*
*
*
************************************************************************
*******
Bugcheck code 0000000A
Arguments e10088ac 00000002 00000000 8049a95c

Any idea why this might be failing?

Thanks,

John


You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

John,

Did you take the 0x0000000A bug check code and look at it in the Help for
winDbg? that shows it to be IRQL_NOT_LESS_OR_EQUAL. One good reason for this
failure is that 8049a95c is at DISPATCH_LEVEL and tried to read e10088ac
which is probably in page-able memory.

Gary G. Little
Sr. Staff Engineer
Broadband Storage, LLC
xxxxx@broadstor.com
xxxxx@delphieng.com

-----Original Message-----
From: John Hirschi [mailto:xxxxx@SonicWALL.com]
Sent: Thursday, February 15, 2001 3:31 PM
To: NT Developers Interest List
Subject: [ntdev] NdisReadNetworkAddress = Fatal System Error

Hi,

I am porting a WinNT4 driver to Win2k, and at the same time splitting it
into a miniport and intermediate driver. In the intermediate driver’s
MiniportInitialize function, I attempt to retrieve the MAC address of
the network card I’m talking to. In order to do this, I call
NdisOpenConfiguration to get a config handle. I then attempt to call
NdisReadNetworkAddress. During this call, I get this error in WinDbg:

*** Fatal System Error: 0x0000000a
(0xE10088AC,0x00000002,0x00000000,0x8049A95C)

Break instruction exception - code 80000003 (first chance)

A fatal system error has occurred.
Debugger entered on first try; Bugcheck callbacks have not been invoked.

A fatal system error has occurred.

************************************************************************
*******
*
*
* Bugcheck Analysis
*
*
*
************************************************************************
*******
Bugcheck code 0000000A
Arguments e10088ac 00000002 00000000 8049a95c

Any idea why this might be failing?

Thanks,

John


You are currently subscribed to ntdev as: xxxxx@delphieng.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com


You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

Thanks Gary, I appreciate your response.

I am fairly new at this stuff, so please forgive this question: Why
would anything be at dispatch level? The problem occurs in the Miniport
initialize function, which should be passive level. Surely opening and
reading the registry should be a passive level operation, right?

Thanks,
John

-----Original Message-----
From: Gary Little [mailto:xxxxx@Broadstor.com]
Sent: Thursday, February 15, 2001 5:49 PM
To: NT Developers Interest List
Subject: [ntdev] RE: NdisReadNetworkAddress = Fatal System Error

John,

Did you take the 0x0000000A bug check code and look at it in the Help
for
winDbg? that shows it to be IRQL_NOT_LESS_OR_EQUAL. One good reason for
this
failure is that 8049a95c is at DISPATCH_LEVEL and tried to read
e10088ac
which is probably in page-able memory.

Gary G. Little
Sr. Staff Engineer
Broadband Storage, LLC
xxxxx@broadstor.com
xxxxx@delphieng.com

-----Original Message-----
From: John Hirschi [mailto:xxxxx@SonicWALL.com]
Sent: Thursday, February 15, 2001 3:31 PM
To: NT Developers Interest List
Subject: [ntdev] NdisReadNetworkAddress = Fatal System Error

Hi,

I am porting a WinNT4 driver to Win2k, and at the same time splitting it
into a miniport and intermediate driver. In the intermediate driver’s
MiniportInitialize function, I attempt to retrieve the MAC address of
the network card I’m talking to. In order to do this, I call
NdisOpenConfiguration to get a config handle. I then attempt to call
NdisReadNetworkAddress. During this call, I get this error in WinDbg:

*** Fatal System Error: 0x0000000a
(0xE10088AC,0x00000002,0x00000000,0x8049A95C)

Break instruction exception - code 80000003 (first chance)

A fatal system error has occurred.
Debugger entered on first try; Bugcheck callbacks have not been invoked.

A fatal system error has occurred.

************************************************************************
*******
*
*
* Bugcheck Analysis
*
*
*
************************************************************************
*******
Bugcheck code 0000000A
Arguments e10088ac 00000002 00000000 8049a95c

Any idea why this might be failing?

Thanks,

John


You are currently subscribed to ntdev as: xxxxx@delphieng.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com


You are currently subscribed to ntdev as: xxxxx@sonicwall.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com


You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com