Trying to Attach .dmp for Analysis

[Thuggish]

I would like to attach a .dmp file for someone to analyze, since Windows can't just make it a .txt file or something, God only knows why.

But it says access denied when I try.

Anyone know what's going on?

 

[writhziden]

You need to copy and paste it into a folder in your Documents folder. You can't move it because you do not have the permissions to do so, and you do not want to change the permissions to do so. Just copy it and paste it in your Documents folder. You can also follow the http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html to provide us with your .dmp files.

 

[Thuggish]

Okay, analyze please?

 

[writhziden]

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Thuggish\Dump On Me\010412-91931-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e0d000 PsLoadedModuleList = 0xfffff800`03052670
Debug session time: Wed Jan  4 18:53:02.427 2012 (UTC - 7:00)
System Uptime: 8 days 8:23:18.756
Loading Kernel Symbols
...............................................................
................................................................
................................................................
........
Loading User Symbols
Loading unloaded module list
......................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800799f028, b6004000, 68000135}

Probably caused by : hardware

Followup: MachineOwner
---------

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa800799f028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b6004000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000068000135, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`031ddb08 fffff800`03408a3b : 00000000`00000124 00000000`00000000 fffffa80`0799f028 00000000`b6004000 : nt!KeBugCheckEx
fffff880`031ddb10 fffff800`02f9a513 : 00000000`00000001 fffffa80`0778aa10 00000000`00000000 fffffa80`0778aa60 : hal!HalBugCheckSystem+0x1e3
fffff880`031ddb50 fffff800`03408700 : 00000000`00000728 fffffa80`0778aa10 fffff880`031ddeb0 00000000`56970800 : nt!WheaReportHwError+0x263
fffff880`031ddbb0 fffff800`03408052 : fffffa80`0778aa10 fffff880`031ddeb0 fffffa80`0778aa10 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`031ddd00 fffff800`033fbe8f : 00000000`00000000 00000000`00000001 fffff880`031ddf30 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`031ddd40 fffff800`02e8852c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x47
fffff880`031ddd70 fffff800`02e88393 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`031ddeb0 00000000`51a09130 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`03d2f170 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x51a09130


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE

BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE

Followup: MachineOwner
---------

See http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html for troubleshooting steps to your blue screen crash.

 

[writhziden]

Any luck finding the culprit in your hardware related crashes?