Symbol Errors

[x BlueRobot]

I forgot to post this, but here's some more information about Symbol Files - DebugInfo.com - Matching debug information

 

[Cube8]

Hi!

I've been getting errors on every dmp lately

*************************************************************************
*** ***
*** ***
*** 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. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************

Anyone have any ideas?

I have the exact same problem.

Is it aW10 dump, Bruce?

We're all having problems with W10 dumps.

I'm trying to analyze several XP dumps and all fail.

I also tried from within WinDbg but the same messages appear.
My search path is SRV*C:\Windows\DbgSymbols*http://msdl.microsoft.com/download/symbols
I also cleared the folder. I don't know what the problem is.

Any ideas for me?

 

[Wrench97]

I think the dmps I had were corrupt, the last several I ran were fine but if I go back to those the issue is present.

 

[Cube8]

Is it possible that all dumps from that particular machine are corrupt?

 

[Wrench97]

Could be, sometimes if memory or disk/controller errors are involved.

 

[Patrick]

Just got an error today. Did anyone find out why it's happening?

Usually we email the team and get a reply.

 

[Cube8]

In my case it seems the problem was an overheating cpu. I cleaned the dust, applied a new thermal paste and it looks ok now.

 

[Patrick]

Unlikely, as that would imply all of our computers are overheating. You'll likely start seeing symbol errors soon again, given that your fix was most likely unrelated.

 

[Cube8]

I think I was misunderstood.
I copied the minidumps to another computer and tried to analyze them. Then I saw those symbol errors and I tried in another computer as well. That's how I assumed that the bsods (and the corrupted minidumps) occurred when the cpu was very overheated and behaved unexpectedly.
I wasn't there when it happened; I was told about it and was asked to help.

 

[Wrench97]

In other words the machine that created the .dmp files was overheating.

 

[Cube8]

Exactly.