Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Configuring the "Debugging Tools"


25 Apr 2013   #61
rovopio

windows 7 home premium 64bit
 
 

okay trying the analyze! v command as we speak,

will post the result of reading my own dmp files on my own BSOD thread,

cheers for the help

KP!


My System SpecsSystem Spec
31 Jul 2013   #62
doveman007

Windows 7 Ultimate x64
 
 

It was a bit confusing installing this. I already had the Windows Performance Toolkit installed so maybe that makes the installer not work properly.

Anyway, I downloaded sdksetup.exe from the second link here Download and Install Debugging Tools for Windows which goes to Windows Software Development Kit (SDK) for Windows 8

Running that once download, WPT was already checked (as was .NET Framework 4.0) so I ticked Debugging Tools and when it had finished downloading, I ran the new sdksetup.exe in the StandaloneSDK folder but it told me that everything was already installed. Re-running the original sdksetup.exe still only shows WPT (and .NET) checked.

After doing this a few times, it's installed and I have the shortcuts in the Start Menu under Windows Kits (next to the WPT ones I already had) but at no time did the installer offer me a choice of x86/x64 or location to install to, in fact it didn't give me any indication that it was going to install anything, nor that it had.
My System SpecsSystem Spec
31 Jul 2013   #63
Vir Gnarus

Microsoft Community Contributor Award Recipient

Windows 7 64-bit
 
 

It would've had a progress bar during installation and then when complete it would've populated the Start Menu programs menu with a Debugging Tools for Windows entry. To find the x64/x86 versions of the debugger, you'll navigate to the appropriate Program Files (x86) folder (most likely Windows Kits), and then go to the Debuggers subfolder where it'll have a separate directory for each version. There's even a redistributable for when you just want to install the tool itself to a system.

Understand that since 2009 (time this article was posted), the Windows dev kits - including their installer - has been altered considerably. That may explain the discrepancies in this tutorial.
My System SpecsSystem Spec
31 Jul 2013   #64
doveman007

Windows 7 Ultimate x64
 
 

Sure, I understand the tutorial was written a while ago. Just wanted to point out that it might be an idea to update it, as it's a bit confusing now with the current installer.
My System SpecsSystem Spec
01 Aug 2013   #65
caruncles

Windows 7 Professional 64 bit 6.1.7600 build 7600
 
 
can I copy the dump to another computer

Will the setup for the debugger work if I copied the .dmp file to another computer. In other words, if I config the debugger on my computer, can I debug a file I copied from another computer?
My System SpecsSystem Spec
01 Aug 2013   #66
Vir Gnarus

Microsoft Community Contributor Award Recipient

Windows 7 64-bit
 
 

You mean taking a dump file from one PC and running it through the debugger on your debugging machine? Of course! How else are we tech support reading the dump files from all of you guys?
My System SpecsSystem Spec
02 Aug 2013   #67
caruncles

Windows 7 Professional 64 bit 6.1.7600 build 7600
 
 

can you tell me what all this means?

Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [W:\Exception.exe(1).6844.dmp]
User Mini Dump File: Only registers, stack and portions of memory are available
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: SingleUserTS
Machine Name:
Debug session time: Thu Aug 1 08:20:20.000 2013 (UTC - 4:00)
System Uptime: not available
Process Uptime: 0 days 0:03:45.000
................................................................
....................
Loading unloaded module list
....
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(1abc.10d0): Access violation - code c0000005 (first/second chance not available)
*** ERROR: Symbol file could not be found. Defaulted to export symbols for msvbvm60.dll -
eax=002b1024 ebx=021a6fa4 ecx=00ffffff edx=0219f360 esi=01666234 edi=00000000
eip=72949e85 esp=0012fd3c ebp=0012fd58 iopl=0 nv up ei pl nz na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00010202
msvbvm60!EbLoadRunTime+0xfa3:
72949e85 ff5104 call dword ptr [ecx+4] ds:0023:01000003=????????
My System SpecsSystem Spec
02 Aug 2013   #68
Vir Gnarus

Microsoft Community Contributor Award Recipient

Windows 7 64-bit
 
 

It starts off with basic info about the dump file, symbols, and the system state at time of the crash (e.g. "Debug session time" is time of crash).

The second half tells you that it has an exception context stored in it of an exception that occurred during the dump file - primarily the exception that triggered the crash. It tells you the type of exception (c0000005 - memory could not be read/written/executed). It then alerts you that symbols for a particular module that's related (msvbvm60.dll) could not be found, and then dumps the CPU register contents during the exception and the instruction that caused it (msvbvm60!EbLoadRunTime+0xfa3).

To set to the context of Windbg to the point of the exception, follow what it says (type .ecxr command). Best step after that would be to dump the callstack with the kv command.

Your other option is to type !analyze -v. This will have a basic analysis engine sift through the data and display to you a general synopsis of what it thinks was the problem. You can use this as a starting point for your own manual analysis.
My System SpecsSystem Spec
17 Nov 2013   #69
MrHintz

Windows 7 Ultimate x64
 
 
Access denied

It wont let me access my dump files. I keep getting something that says:

Could not find the
C:\Windows\Minidump\111713-24359-01.dmp Dup File, Win32
error 0n5

Access is Denied

I believe I need to turn on administrator priviliges but I could be wrong, any advice on what to do here?
My System SpecsSystem Spec
17 Nov 2013   #70
x BlueRobot

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium x86 Service Pack 1 - Linux Mint Mate 14 x64
 
 

Quote   Quote: Originally Posted by MrHintz View Post
It wont let me access my dump files. I keep getting something that says:

Could not find the
C:\Windows\Minidump\111713-24359-01.dmp Dup File, Win32
error 0n5

Access is Denied

I believe I need to turn on administrator priviliges but I could be wrong, any advice on what to do here?
Read my blog post here - BSODTutorials: Access Denied Message with WinDbg and Dump Files - ProcMon
My System SpecsSystem Spec
Reply

 Configuring the "Debugging Tools"




Thread Tools



Similar help and support threads for2: Configuring the "Debugging Tools"
Thread Forum
Solved Error Message "Failure configuring Windows update" Windows Updates & Activation
Solved Google "More" and "Search Tools" buttons no longer working... Browsers & Mail
Windows 7 hangs at "configuring updates" at launch BSOD Help and Support
"Failure configuring updates" message - advice please! Windows Updates & Activation
What is "windows 7 debugging symbols"? General Discussion
Which Setting for "Write Debugging Information" BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 04:37 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App