So right now i'm having symbol issues with WinDBG, i can't read dumps at all because it says i don't have the right symbols. Ever since i installed Windows 10 i've been having some issues with WinDBG. Can anyone please help?
are you seeing something like this in the middle of the analysis:
because that is happening to me like 8/10 times on my debugger.Code:************************************************************************* *** *** *** *** *** 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!_WHEA_ERROR_RECORD_HEADER *** *** *** *************************************************************************
No i see something like you don't have the equipped symbols to analyze this blahblahblah.
Have you seen this Laith?
WinDBG - Install & Configure - Windows 10 Forums
Remember we have a sister forum Ten Forums
I remember them having issues with earlier builds. Might as in the BSOD section there. A Guy
Still no success, i changed the path and deleted the old symbol folder and still same issue.
Have you tried setting up WinDBG with the Windows 10 SDK?
No i haven't, but i think it's working now. I'll test with the dumps i can't analyze.
*sigh* I'll try your idea, John.Code:************************************************************************* *** *** *** *** *** 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!_MMPTE *** *** *** *************************************************************************
Quote