Windbg не берет символы для дампов

[__sa__nya]

Доброе время суток. Решил заняться методикой изучения дампов памяти для анализа причин BSOD'ов. Взял файлы минидампов с системы Win 7 Prof SP1 x64 (версия 6.1, сборка 7601:Service Pack 1), коробочная версия. Установил отсюда (http://msdn.microsoft.com/en-us/windows/hardware/gg463028.aspx) файлы символов:
1. Windows 7 Service Pack 1 x64 retail symbols, all languages
2. Windows 7 Service Pack 1 x64 checked symbols, all languages
3. Windows 7 RTM x86 checked symbols, all languages
В Windbg в "Symbol File Path" прописал пути к папкам в которые установил символы:
D:\windbg_symbols\Win_7_SP1_x64_checked_symbols_all_languages;D:\windbg_symbols\Win_7_SP1_x64_retail _sym_all_languages;D:\windbg_symbols\Win_7 RTM_x64_checked_symbols_all_languages

Но при открытии дампа windbg все равно пишет что не может подгрузить символы:
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** 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: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: nt!_KPRCB ***
*** ***
*************************************************************************

- Что я делаю не так?

[Petya V4sechkin]

__sa__nya, после установки обновлений ОС версии системных файлов меняются, очевидно.
Лучше позволить WinDbg скачивать недостающие символы из интернета.
В Windbg в "Symbol File Path" прописал пути к папкам
Например:
srv*D:\Symbols*http://msdl.microsoft.com/download/symbols

[Nik User]

Добрый день, картина один в один. У меня тоже перестал брать символы Windbg сразу как обновил свю win 10 1607 (14393.3..) до 1607 (14393.447), пишет - Символы ядра являются неправильными. Исправьте символы, чтобы сделать анализ.
Хотя источник указан SRV*С:\Symbols*http://msdl.microsoft.com/download/symbols.
Но если рассматривать более ранние дампы, которые были созданы еще до этого обновления, то символы загружаются.
Это там у них на сервере не загрузили новые символы или проблема моя?