Solved Bad Symbol package

[ugabuga]

I'm getting an error when trying to run MS debugger, it says the following:

Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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.

I am using SRV*c:\Symbols\*http://msdl.microsoft.com/download/symbols
I have never had an issue with this in the past, but it is no longer working for some reason. I tried running the debugger on the minidump and on the memory.dmp file in c:\windows. I get the same error either way. Could it just be an issue with this blue screen or is it my debugger and symbols? Let me know if any information is needed and any help is greatly appreciated.

 

[derekimo]

It's happening to everybody,

http://www.sevenforums.com/chillout-room/378542-windbg-symbols.html

It started around the middle of August.

 

[ugabuga]

lol, well that makes it a lot more difficult to determine exactly what is going on. Thanks for the information!

 

[derekimo]

You're welcome!

That's an understatement, I hope they get it sorted out soon.