Dump Data collection tool and instructions

JoeHobart · 2004/07/30

Last Update: December 2, 2010

To collect data from a USER.DMP or a MEMORY.DMP file:

Click here to download the current debugging tools: Download Microsoft Windows SDK for Windows 7 and .NET Framework 4 from Official Microsoft Download Center

Please note that on Windows XP you’ll need to have .NET framework 2.0 installed

Once you downloaded the installer (winsdk_web.exe), double click to run it.

Click OK on the "Windows SDK Setup warning" (Where it says "some components cannot be installed ") - You don't need .NET 4

On the "Windows SDK Setup Wizard ", click Next

Select I agree and click Next

Leave the default Install locations and click Next

On the Installation Options screen, de-select everything except "Debugging Tools for Windows ", click Next and click Next again to start installation

Download debugwiz.zip from the link at the bottom of this page, extract the EXE from the ZIP file and run the tool (debugwiz.exe). (Note: When running on Windows Vista / Windows 7, right-click the debugwiz.exe, and choose Run as administrator from the menu)

Select the Advanced check-box and click the Browse button next to "Location of the debugging tools… "

Locate and select cdb.exe (by default in C:\Program Files\Debugging Tools for Windows (x86)\ )

If you are running a 64-bit OS, you can find cdb.exe in C:\Program Files\Debugging Tools for Windows (x64)\ )

Click the Browse button next to "Dump file to be analyzed" and browse to your dump file

Click Generate Log (Note: You should be connected to the Internet while debugging.)

Wait for the command window to close and then find your log file here: C:\debuglog.txt

Open the file c:\debuglog.txt in notepad

Cut and paste the data to your thread, if you are starting a new thread, please include DUMP DATA in your title.

Your program crash dump is probably located in C:\Documents and Settings\All Users\Application Data\Microsoft\Dr Watson\user.dmp

Blue Screens:
The dump file will be c:\MEMORY.DMP or (for Mini-dumps) in C:\WINDOWS\Minidump\

If you do not have a dump, ensure that your machine is configured to write out a dump by following the directions from Microsoft

If you are unable to find a dump file at any of the locations given above search your drive for *.dmp files.

Download debugwiz.zip (Please note that the EXE file has been digitally signed by WinShareSoft)

Admin. · 2011/09/06

Running Driver Verifier

You may also want to run Driver Verifier. Please read these instructions BEFORE using it as it can cause a BSOD loop that won't let you into Windows:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using Windows Repair feature - See How to recover from a corrupted registry that prevents Windows XP from starting).

Windows 7 & Vista users can follow the XP procedure to restore their system.

Then, here's the procedure:

In your Start Search box type Verifier and press ENTER (In XP go to Start > Run and type verifierin the Open box, press OK)

Select Create custom settings (for code developers) and click Next

Select Select individual settings from a full list and click Next

Select everything EXCEPT FOR Low Resource Simulation and click Next

Select Automatically select unsigned drivers and click Next

If no drivers show up, then select Select driver names from a list and click Next

Then select all drivers NOT provided by Microsoft and click Next

Select Finish on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.

Reboot into Windows, turn off Driver Verifier by going back in and selecting Delete existing settings on the first page, then locate and post the memory dump file with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.

If you can't get into Safe Mode, try using System Restore as indicated above to set the system back to the previous restore point that you created.
Click to expand...

More information on Drive Verifier here: Using Driver Verifier to identify issues with Windows drivers for advanced users

Log in or Sign up

Dump Data collection tool and instructions

JoeHobart Inactive Alumni Thread Starter

Admin. Administrator Administrator Staff

Share This Page

Log in or Sign up

Dump Data collection tool and instructions

JoeHobart Inactive Alumni Thread Starter

Admin. Administrator Administrator Staff

Share This Page

Useful Searches