Module load completed but symbols could not be loaded

1、 http://forum.sysinternals.com/windbg-symbols-could-not-be-loaded_topic13838.html

ask:  I am debugging a driver in the primitive state using windbg with 2systems.  Initially, Ihad some problems getting symbols loaded and breakpoints set, but itseemed to resolveitself somehow.  The error I am now consistently getting is below:Symbol search path is:C:\WINDDK\2600.1106\src\network\ndis\softair\51\objchk_wxp_x86\i386;c:\symbols*** ERROR: Module load completed but symbols could not be loaded forsoftair.sysI have softair.sys and softair.pdb in the c:\symbols directory asevidenced by:C:\WINDDK\2600~1.110\src\network\ndis\softair>dir c:\symbols Volume in drive C has no label. Volume Serial Number is 8401-7D77

answer: 

It could be that the symbols don't match what is running on the system.

Do:

!sym noisy

.reload

And you'll get more info about why the symbol load is failing.I'm sure you are doing this already, but it is always worth reminding tomake sure you are using the latest version of the debugger.  See http://www.microsoft.com/ddk/debugging

2、

This isn't really a Visual C++ related problem AFAICT. The microsoft.public.windbg newsgroup might be a better place to get information.

 Anyhow, you probably do not have the matching ntdll.pdb you need. The dump would usually contain the CV record of the module (only very old dumps did not, you need to download the binary first). This uniquely identifies the particular build of ntdll.

 You would usually use our public symbol server to get these symbols. See .sympath, .symfix and !sym noisy.

 You can also use your local file path followed by a srv* path like

 .sympath c:\mypdbs;srv*c:\msftpdbs*http://msdl.microsoft.com/download/symbols