Bug check code 1E(80000003) with Ndistest.sys

[Neeraj]

Hi ,

Is the .pdb file for ndistest.sys(driver version 4.03.87 for ia64)
available in Microsoft website ?

Actually, I'm running WHQL test for my 64bit 802.11 WLAN Miniport
driver(OS Windows XP-64 bit). The test 2c_performanceBlast always
result in BSOD with
Error code 1e (ffffffff80000003, fffff8000104b330, 0000000000000000,
0000000000000000)

The stack trace indicates that a break point was hit from ndistest.sys.
Any idea why the
breakpoint/Assert was hit?

Below is the o/p of the debugger for the memory dump.

0: kd> !analyze -v
*******************************************************************************

*
*


* Bugcheck Analysis
*

*
*

*******************************************************************************



KMODE_EXCEPTION_NOT_HANDLED (1e)

This is a very common bugcheck. Usually the exception address
pinpoints

the driver/function that caused the problem. Always note this address

as well as the link date of the driver/image that contains this
address.

Arguments:

Arg1: ffffffff80000003, The exception code that was not handled

Arg2: fffff8000104b330, The address that the exception occurred at

Arg3: 0000000000000000, Parameter 0 of the exception

Arg4: 0000000000000000, Parameter 1 of the exception



Debugging Details:

------------------



***** Kernel symbols are WRONG. Please fix symbols to do analysis.



*************************************************************************

***
***

***
***

*** Your debugger is not using the correct symbols
***

***
***

*** In order for this command to work properly, your symbol path
***

*** must point to .pdb files that have full type information.
***

***
***

*** Certain .pdb files (such as the public OS symbols) do not
***

*** contain the required information. Contact the group that
***

*** provided you with these symbols if you need this command to
***

*** work.
***

***
***

*** Type referenced: nt!_KPRCB
***

***
***

*************************************************************************

*************************************************************************

***
***

***
***

*** Your debugger is not using the correct symbols
***

***
***

*** In order for this command to work properly, your symbol path
***

*** must point to .pdb files that have full type information.
***

***
***

*** Certain .pdb files (such as the public OS symbols) do not
***

*** contain the required information. Contact the group that
***

*** provided you with these symbols if you need this command to
***

*** work.
***

***
***

*** Type referenced: nt!_KPRCB
***

***
***

*************************************************************************



FAULTING_MODULE: fffff80001000000 nt



DEBUG_FLR_IMAGE_TIMESTAMP: 4207e015



EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more
arguments are invalid



FAULTING_IP:

nt!DbgBreakPoint+0

fffff800`0104b330 cc int 3



EXCEPTION_PARAMETER1: 0000000000000000



EXCEPTION_PARAMETER2: 0000000000000000



DEFAULT_BUCKET_ID: DRIVER_FAULT



BUGCHECK_STR: 0x1E



LAST_CONTROL_TRANSFER: from fffff800010860dd to fffff800010501d0



STACK_TEXT:

fffff800`003c71d8 fffff800`010860dd : 00000000`0000001e
ffffffff`80000003 fffff800`0104b330 00000000`00000000 : nt!KeBugCheckEx

fffff800`003c71e0 fffff800`0104ffef : fffff800`003c78d0
fffff800`01057750 fffff800`003c7960 ffffffff`ffffffff :
nt!PoRegisterSystemState+0x1491d

fffff800`003c77e0 fffff800`0104e3b7 : fffffadf`f35f5be0
fffffadf`ffe68cc0 00000000`00000177 fffff800`0106144e :
nt!ZwUnloadKey+0x239f

fffff800`003c7960 fffff800`0104b331 : fffffadf`efa19a01
00000000`00000000 fffff800`01053930 0000fadf`efa2cbe5 :
nt!ZwUnloadKey+0x767

fffff800`003c7af8 fffffadf`efa19a01 : 00000000`00000000
fffff800`01053930 0000fadf`efa2cbe5 00000000`00000002 :
nt!DbgBreakPoint+0x1

fffff800`003c7b00 fffffadf`efa0f500 : fffffadf`efa1faf0
00000000`ffff0002 00000000`ffffffff 00000000`00000000 :
ndistest+0x19a01

fffff800`003c7b30 fffff800`0102c649 : 00000000`0000002d
fffffadf`ffbfbc38 fffff800`0083f480 00000001`01e941d2 : ndistest+0xf500

fffff800`003c7ba0 fffff800`010554ff : 00000000`00000010
00000000`00000206 fffff800`00000001 00000000`00000018 :
nt!KeTerminateThread+0x2e9

fffff800`003c7d40 fffff800`01071950 : fffff800`01189180
fffff800`01189180 00000000`0005ffd4 fffff800`0118d500 :
nt!KeDelayExecutionThread+0xcaf

fffff800`003c7dd0 fffff800`013fc1d1 : 00000000`00000000
00000000`00000000 00000000`00000000 00000000`00000000 :
nt!PoRegisterSystemState+0x190

fffff800`003c7e00 00000000`fffff800 : 00000000`00000000
00000000`00000000 00000000`00000000 00000000`00000000 :
nt!NlsMbOemCodePageTag+0x7111

fffff800`003c10b0 00000000`00000000 : 00000000`00000000
00000000`00000000 00000000`00000000 00680000`00000000 : 0xfffff800

fffff800`003c10b8 00000000`00000000 : 00000000`00000000
00000000`00000000 00680000`00000000 00000000`00000000 : 0x0

fffff800`003c10c0 00000000`00000000 : 00000000`00000000
00680000`00000000 00000000`00000000 00000000`00000000 : 0x0

fffff800`003c10c8 00000000`00000000 : 00680000`00000000
00000000`00000000 00000000`00000000 00000000`00000000 : 0x0

fffff800`003c10d0 00680000`00000000 : 00000000`00000000
00000000`00000000 00000000`00000000 00000000`00000000 : 0x0

fffff800`003c10d8 00000000`00000000 : 00000000`00000000
00000000`00000000 00000000`00000000 00000000`00000000 :
0x680000`00000000

fffff800`003c10e0 00000000`00000000 : 00000000`00000000
00000000`00000000 00000000`00000000 00000000`00000000 : 0x0

fffff800`003c10e8 00000000`00000000 : 00000000`00000000
00000000`00000000 00000000`00000000 00000000`00000000 : 0x0

fffff800`003c10f0 00000000`00000000 : 00000000`00000000
00000000`00000000 00000000`00000000 00000000`00000000 : 0x0



FOLLOWUP_IP:

ndistest+19a01

fffffadf`efa19a01 b001 mov al,0x1



SYMBOL_STACK_INDEX: 5



FOLLOWUP_NAME: MachineOwner



SYMBOL_NAME: ndistest+19a01



MODULE_NAME: ndistest



IMAGE_NAME: ndistest.sys



STACK_COMMAND: kb



BUCKET_ID: WRONG_SYMBOLS



Followup: MachineOwner