by admin

Livekd Could Not Resolve Symbols For Ntoskrnl.Exe

Livekd Could Not Resolve Symbols For Ntoskrnl.Exe Average ratng: 9,1/10 5252 votes

I downloaded the symbols from http://www.microsoft.com/whdc/devtools/debugging/symbolpkg.mspxthe package (Windows 7 RTM x86 retail symbols, all languages) but it still gives me the same error!

  1. Resolve Symbols

Done .sympath but still not working

Jan 26, 2016 - >livekd.exe -hv name -p -o c: memory.dmp. If you get any errors about kdversionblock or cannot resolve symbols for ntoskrnl, make sure your.

.sympath C:inetpubwwwrootProductsServicebinProductsEntityModel.pdb;srvc:Symbolshttp://msdl.microsoft.com/download/symbols

Am I missing something? Any help will be much appreciated. Thanks

Symbols
Pinchy
PinchyPinchy

1 Answer

I would have the sympath like this

You could probably have mismatched symbols. Here is a command which will help in diagnosing the symbol load problems !sym noisy

NaveenNaveen

Not the answer you're looking for? Browse other questions tagged debuggingwindbgsymbolsw3wp or ask your own question.

I installed retail symbols in D:Symbols and given the path to my windbg.exe but it can't be loaded why?

Mojtaba KarimdokhtMojtaba Karimdokht

2 Answers

The Debug Symbols that Microsoft provides are only usable for the RTM or Sp1 Version of Windows 7. When you install an Update, the PDBs no longer match.

Here you must point to the Symbol Server to download the new PDBs:

Resolve Symbols

magicandre1981magicandre1981

It's easier if you have an internet connection to let windbg find and download the correct ones for you, whereby it will be cached locally:

.symfix;.reload

Will go and fetch the correct symbols from the MS symbol server at http://msdl.microsoft.com/download/symbols

if you download them yourself then you have to download the correct version matching your specific build and this is just too much of a headache to maintain so IMO it's just simpler to just let windbg handle this for you.

EdChumEdChum

Not the answer you're looking for? Browse other questions tagged windbgdebug-symbols or ask your own question.