This is more of a Microsoft question but I've had posts in 2 differnet Microsoft forums for almost 2 weeks now and no one has answered me so I'm hoping someone here can help.

I'm trying to nail down the cause of a bad case of the blue screens in one of our images. When open the full memory dump using WinDBG I get something like this:


Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Documents and Settings\jwall\Desktop\dumps\RMS-Lib-06-3600-2009-11-23-NoImDriver-MEMORY.DMP]
Kernel Complete Dump File: Full address space is available

Symbol search path is: SRV*c:\symbols\*Symbol information
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.090206-1234
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0
Debug session time: Mon Nov 23 10:14:29.546 2009 (GMT-6)
System Uptime: 0 days 0:20:59.251
Loading Kernel Symbols
.................................................. .............
.................................................. ..............

Loading User Symbols
.................................................. ..............
...
Loading unloaded module list
................................
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fc07a4d8, 0, bf802247, 0}

************************************************** ***********************
*** ***
*** ***
*** 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: kernel32!pNlsUserInfo ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** 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: kernel32!pNlsUserInfo ***
*** ***
************************************************** ***********************
Probably caused by : win32k.sys ( win32k!StoreQMessage+c )

Followup: MachineOwner
---------



The probable cause in each of the dumps I have is different, but I always get the message about not using the correct symbols. As you can see I've set my symbol search path to SRV*c:\symbols\*Symbol information which should, as I understand it, download the necessary symbols.

Any ideas how to resolve this message, or can I ignore it?

Thanks for the help.