Hello NTDEV,
I’m trying to enable NDIS tracing using ndiskd.dll, but it would appear that my version of ndis.sys does not facilitate that based on the symbols that the debugger lined up. Here’s the info:
kd> vertarget
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp.050301-1521
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Tue Feb 27 12:39:48.976 2007 (GMT-5)
System Uptime: 0 days 0:13:14.652
kd> lmvm ndis
start end module name
fc361000 fc38da80 NDIS (pdb symbols) c:\symstore\ndis.pdb\42ED3DC0817A4246B157736BBAF668742\ndis.pdb
Loaded symbol image file: NDIS.sys
Image path: NDIS.sys
Image name: NDIS.sys
Timestamp: Wed Aug 04 02:14:27 2004 (41107EC3)
CheckSum: 0003996E
ImageSize: 0002CA80
Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0
kd> .chain
Extension DLL search Path:
C:\Program Files\Debugging Tools for Windows\winext;C:\Program Files\Debugging Tools for Windows\winext\arcade;C:\Program Files\Debugging Tools for Windows\WINXP;C:\Program Files\Debugging Tools for Windows\pri;C:\Program Files\Debugging Tools for Windows;C:\Program Files\Debugging Tools for Windows\winext\arcade;C:\Program Files\Windows Resource Kits\Tools;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\ATI Technologies\ATI Control Panel;C:\Program Files\IBM\Personal Communications;C:\Program Files\IBM\Trace Facility;c:\Program Files\Microsoft SQL Server\90\Tools\binn;C:\Program Files\Common Files\Adaptec Shared\System;C:\Program Files\Microsoft Driver Test Manager\Controller;C:\Program Files\Microsoft Visual Studio\Common\Tools\WinNT;C:\Program Files\Microsoft Visual Studio\Common\MSDev98\Bin;C:\Program Files\Microsoft Visual Studio\Common\Tools;C:\Program Files\Microsoft Visual Studio\VC98\bin;C:\Program Files\IDM Computer Solutions\UltraCompare
Extension DLL chain:
ndiskd: image 6.0.5457.0, API 5.0.6, built Tue Jun 20 20:46:57 2006
[path: C:\Program Files\Debugging Tools for Windows\WINXP\ndiskd.dll]
C:\Program Files\Debugging Tools for Windows\WINXP\ndiskd: image 6.0.5457.0, API 5.0.6, built Tue Jun 20 20:46:57 2006
[path: C:\Program Files\Debugging Tools for Windows\WINXP\ndiskd.dll]
C:\Program Files\Debugging Tools for Windows\WINXP\ndiskd.dll: image 6.0.5457.0, API 5.0.6, built Tue Jun 20 20:46:57 2006
[path: C:\Program Files\Debugging Tools for Windows\WINXP\ndiskd.dll]
C:\Program Files\Debugging Tools for Windows\WINXP\ntsdexts.dll: image 6.0.5457.0, API 1.0.0, built Sat Jul 08 16:29:38 2006
[path: C:\Program Files\Debugging Tools for Windows\WINXP\ntsdexts.dll]
dbghelp: image 6.6.0007.5, API 6.0.6, built Sat Jul 08 16:11:32 2006
[path: C:\Program Files\Debugging Tools for Windows\dbghelp.dll]
ext: image 6.6.0007.5, API 1.0.0, built Sat Jul 08 16:10:52 2006
[path: C:\Program Files\Debugging Tools for Windows\winext\ext.dll]
exts: image 6.6.0007.5, API 1.0.0, built Sat Jul 08 16:10:48 2006
[path: C:\Program Files\Debugging Tools for Windows\WINXP\exts.dll]
kext: image 6.6.0007.5, API 1.0.0, built Sat Jul 08 16:11:01 2006
[path: C:\Program Files\Debugging Tools for Windows\winext\kext.dll]
kdexts: image 6.0.5457.0, API 1.0.0, built Sat Jul 08 16:31:08 2006
[path: C:\Program Files\Debugging Tools for Windows\WINXP\kdexts.dll]
kd> !ndiskd.dbglevel INFO
NDISKD: error - could not access ndis!ndisDebugLevel - check symbols for ndis.sys
Is anyone able to advise?
Thanks,
Ron
You need the checked version of NDIS.sys, if you have MSDN you should be
able to get the checked OS.
–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
Remove StopSpam to reply
wrote in message news:xxxxx@ntdev…
> Hello NTDEV,
>
> I’m trying to enable NDIS tracing using ndiskd.dll, but it would appear
> that my version of ndis.sys does not facilitate that based on the symbols
> that the debugger lined up. Here’s the info:
>
> kd> vertarget
> Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
> Product: WinNt, suite: TerminalServer SingleUserTS
> Built by: 2600.xpsp.050301-1521
> Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
> Debug session time: Tue Feb 27 12:39:48.976 2007 (GMT-5)
> System Uptime: 0 days 0:13:14.652
>
>
> kd> lmvm ndis
> start end module name
> fc361000 fc38da80 NDIS (pdb symbols)
> c:\symstore\ndis.pdb\42ED3DC0817A4246B157736BBAF668742\ndis.pdb
> Loaded symbol image file: NDIS.sys
> Image path: NDIS.sys
> Image name: NDIS.sys
> Timestamp: Wed Aug 04 02:14:27 2004 (41107EC3)
> CheckSum: 0003996E
> ImageSize: 0002CA80
> Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0
>
>
> kd> .chain
> Extension DLL search Path:
> C:\Program Files\Debugging Tools for Windows\winext;C:\Program
> Files\Debugging Tools for Windows\winext\arcade;C:\Program
> Files\Debugging Tools for Windows\WINXP;C:\Program Files\Debugging Tools
> for Windows\pri;C:\Program Files\Debugging Tools for Windows;C:\Program
> Files\Debugging Tools for Windows\winext\arcade;C:\Program Files\Windows
> Resource
> Kits\Tools;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program
> Files\ATI Technologies\ATI Control Panel;C:\Program Files\IBM\Personal
> Communications;C:\Program Files\IBM\Trace Facility;c:\Program
> Files\Microsoft SQL Server\90\Tools\binn;C:\Program Files\Common
> Files\Adaptec Shared\System;C:\Program Files\Microsoft Driver Test
> Manager\Controller;C:\Program Files\Microsoft Visual
> Studio\Common\Tools\WinNT;C:\Program Files\Microsoft Visual
> Studio\Common\MSDev98\Bin;C:\Program Files\Microsoft Visual
> Studio\Common\Tools;C:\Program Files\Microsoft Visual
> Studio\VC98\bin;C:\Program Files\IDM Computer Solutions\UltraCompare
> Extension DLL chain:
> ndiskd: image 6.0.5457.0, API 5.0.6, built Tue Jun 20 20:46:57 2006
> [path: C:\Program Files\Debugging Tools for
> Windows\WINXP\ndiskd.dll]
> C:\Program Files\Debugging Tools for Windows\WINXP\ndiskd: image
> 6.0.5457.0, API 5.0.6, built Tue Jun 20 20:46:57 2006
> [path: C:\Program Files\Debugging Tools for
> Windows\WINXP\ndiskd.dll]
> C:\Program Files\Debugging Tools for Windows\WINXP\ndiskd.dll: image
> 6.0.5457.0, API 5.0.6, built Tue Jun 20 20:46:57 2006
> [path: C:\Program Files\Debugging Tools for
> Windows\WINXP\ndiskd.dll]
> C:\Program Files\Debugging Tools for Windows\WINXP\ntsdexts.dll: image
> 6.0.5457.0, API 1.0.0, built Sat Jul 08 16:29:38 2006
> [path: C:\Program Files\Debugging Tools for
> Windows\WINXP\ntsdexts.dll]
> dbghelp: image 6.6.0007.5, API 6.0.6, built Sat Jul 08 16:11:32 2006
> [path: C:\Program Files\Debugging Tools for Windows\dbghelp.dll]
> ext: image 6.6.0007.5, API 1.0.0, built Sat Jul 08 16:10:52 2006
> [path: C:\Program Files\Debugging Tools for
> Windows\winext\ext.dll]
> exts: image 6.6.0007.5, API 1.0.0, built Sat Jul 08 16:10:48 2006
> [path: C:\Program Files\Debugging Tools for
> Windows\WINXP\exts.dll]
> kext: image 6.6.0007.5, API 1.0.0, built Sat Jul 08 16:11:01 2006
> [path: C:\Program Files\Debugging Tools for
> Windows\winext\kext.dll]
> kdexts: image 6.0.5457.0, API 1.0.0, built Sat Jul 08 16:31:08 2006
> [path: C:\Program Files\Debugging Tools for
> Windows\WINXP\kdexts.dll]
>
>
> kd> !ndiskd.dbglevel INFO
> NDISKD: error - could not access ndis!ndisDebugLevel - check symbols for
> ndis.sys
>
>
> Is anyone able to advise?
>
>
> Thanks,
>
> Ron
>
>
> NDISKD: error - could not access ndis!ndisDebugLevel - check symbols for ndis.sys
Is anyone able to advise?
The best thing to do here is just to download symbols to the machine and point WinDbg to them. I got exactly the same error on quite a few occasions when WinDbg was pointed to MSFT symbol server…
Anton Bassov
> ----------
From: xxxxx@lists.osr.com[SMTP:xxxxx@lists.osr.com] on behalf of xxxxx@hotmail.com[SMTP:xxxxx@hotmail.com]
Reply To: Windows System Software Devs Interest List
Sent: Thursday, March 01, 2007 7:45 AM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] NDIS Tracing & ndis.sys symbols
> NDISKD: error - could not access ndis!ndisDebugLevel - check symbols for ndis.sys
> Is anyone able to advise?
The best thing to do here is just to download symbols to the machine and point WinDbg to them. I got exactly the same error on quite a few occasions when WinDbg was pointed to MSFT symbol server…
This is an overkill. I guess Don is right and checked version of ndis.sys is necessary to make it working.
I saw corrupted symbols downloaded from MS symbol server and WinDbg didn’t detect it. Files weren’t downloaded completely and WinDbg just turned crazy. Manual deletion helped.
Best regards,
Michal Vodicka
UPEK, Inc.
[xxxxx@upek.com, http://www.upek.com]