Debugger Can't Find dmp File from Blue Screen

[cyberbiker]

I had another blue screen on 2Jul11 at 9:35pm on my Asus 10005PE with the following Microsoft transmittal info on restart.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 48
BCP1: FFFFFA80049BF010
BCP2: 0000000003826000
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\070211-21886-01.dmp
C:\Users\Cyberbiker\AppData\Local\Temp\WER-78094-0.sysdata.xml
_____________________________

I installed the Windows Debugger software at http://www.microsoft.com/whdc/devtools/debugging/default.mspx. The software was placed in C:\Program Files\Debugging Tools for Windows (x64)\ I then opened the command prompt, changed directories and entered the address of the dmp file exactly as instructed at http://support.microsoft.com/kb/315263. The following is the command window text.
---------------------
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Cyberbiker>cd c:\program files\debugging tools for windows (x64)

c:\Program Files\Debugging Tools for Windows (x64)>windbg -z c:\Windows\Minidump\070211-21866-01.dmp

c:\Program Files\Debugging Tools for Windows (x64)>
----------------------
However, the dumpchk.exe application presented the error windows below. For some reason it could not find the dmp file even though the directory address in my command entry was exactly what appeared in the transmittal report.

What could be wrong?

 

[zigzag3143]

I had another blue screen on 2Jul11 at 9:35pm on my Asus 10005PE with the following Microsoft transmittal info on restart.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 48
BCP1: FFFFFA80049BF010
BCP2: 0000000003826000
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\070211-21886-01.dmp
C:\Users\Cyberbiker\AppData\Local\Temp\WER-78094-0.sysdata.xml
_____________________________

I installed the Windows Debugger software at Download and Install Debugging Tools for Windows. The software was placed in C:\Program Files\Debugging Tools for Windows (x64)\ I then opened the command prompt, changed directories and entered the address of the dmp file exactly as instructed at How to read the small memory dump files that Windows creates for debugging. The following is the command window text.
---------------------
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Cyberbiker>cd c:\program files\debugging tools for windows (x64)

c:\Program Files\Debugging Tools for Windows (x64)>windbg -z c:\Windows\Minidump\070211-21866-01.dmp

c:\Program Files\Debugging Tools for Windows (x64)>
----------------------
However, the dumpchk.exe application presented the error windows below. For some reason it could not find the dmp file even though the directory address in my command entry was exactly what appeared in the transmittal report.

What could be wrong?

Why the "-z" switch? perhaps either debug, or dmp dir isnt in path. Also the instructions are for XP SP-3 the directory structure is different in win7.

 

[cyberbiker]

zigzag3143, "windbg -z DumpFilePath" was in the instructions at How to read the small memory dump files that Windows creates for debugging.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.

To ensure minidumps are enabled:

Go to Start, in the Search Box type: sysdm.cpl, press Enter.
Under the Advanced tab, click on the Startup and Recovery Settings... button.
Ensure that Automatically restart is unchecked.
Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (thy.e 256kb varies).
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
OK your way out.
Reboot if changes have been made.

Attached is the zip archive containing my Minidump folde, which you requested in http://www.sevenforums.com/crashes-...-related-gupdate-conflict-display-driver.html. As you can see there have been many blue screens lately.

Thanks for sharing your knowledge.