Please tell me what I am doing wrong? FindSourceFileAndToken Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\050812-20077-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\050812-20077-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: *** Invalid *** **************************************************************************** * Symbol loading may be unreliable without a symbol search path. * * Use .symfix to have the debugger choose a symbol path. * * After setting your symbol path, use .reload to refresh symbol locations. * **************************************************************************** Executable search path is: ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* TIA, Gerry

I no longer have the software installed on my system, but somewhere in the documentation is information about the Symbol Path. It may be in the Help. But, in any case it is a Microsoft website URL that needs to be in the specified file related to the Debugger. Try the Help, or try reading the documentation. Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

It can be a web site or to a folder / file on the computer being used to debug.Hope this helps, Gerry

It can be a web site or to a folder / file on the computer being used to debug.Hope this helps, Gerry

When I was using the Debugger, the symbols for Windows came directly from a URL on the Microsoft website. Apparently it is a rather large repository of information.Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

When I was using the Debugger, the symbols for Windows came directly from a URL on the Microsoft website. Apparently it is a rather large repository of information.Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi, How to read the small memory dump files that Windows creates for debugging http://support.microsoft.com/kb/315263 You may upload *.dump file on SkyDrive and let us analyze for you. The log file will be %systemroot%\Minidump which is normally C:\windows\Minidump Ivan-Liu TechNet Community Support

Ivan Thanks for your interest. I am pretty sure I have read the Article before but another look cannot but help. You may *.dump file on SkyDrive and let us analyze for you. The system failures on my computer are few and far between. For some years I have been studying error reports including dumpfiles but I have never been able to get satisfactory results from the Windows Debugger. I am determined to master the techniques involved. In this situation my interest is not in having someone else interpret a dumpfile but in being able to do it myself. Are you able to comment from the partial report what is wrong. I have downloaded the symbols for a Windows 7 SP1 64 bit computer and from BlueScreen View I know the dumpfile is from that type of computer. I am trying to debug using my Windows 7 SP1 64 bit computer but the dumpfile is one I downloaded from the internet and I can look at it using BlueScreen View. However, the report is saying: * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* How do I ensure the symbol path is initialised using the Windows interface as the suggestions, unless I am mistaken, are for using a command prompt approach? I can use a command line approach but do not wish to do so because my skills in that area are not extensive. TIA, Gerry

You can set the symbol path in the windbg menu somewhere as: srv*c:\symbols*http://msdl.microsoft.com/download/symbols Or set _NT_SYMBOL_PATH to the same thing in the system control panel, environment variables. Mark Russinovich has a talk about crash files on youtube somewhere, or just click '!analyze -v'.

I decided to uninstall the Windows Debugging Tools and reinstall. Having uninstalled and looking again at the options available I realised I was uncertain which alternative I needed. I downloaded the Standalone Component but now think that was a mistake. What I want to do is simple debug BSOD dumpfiles. Which is the right one to choose? http://msdn.microsoft.com/en-us/windows/hardware/gg463009 In this Article it says that Net Framework 4 must be installed before the Windows SDK. I did not do this before my first download in 2011. Was this my mistake or one of them? http://msdn.microsoft.com/en-us/library/ms717422.aspx TIA, Gerry

From the article you provide, there is one method to install Debugging Tools for Windows without installing .NET Framework. You'd better update Windows to the latest, and then install the debug tools. Pay attendtion that the first article describes the Windebug tool as part of Windows SDK, the second is Windows SDK Overview.Ivan-Liu TechNet Community Support

From the article you provide, there is one method to install Debugging Tools for Windows without installing .NET Framework. You'd better update Windows to the latest, and then install the debug tools. Pay attendtion that the first article describes the Windebug tool as part of Windows SDK, the second is Windows SDK Overview.Ivan-Liu TechNet Community Support