Crash when working with picture files; minidump created

Code:

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


Loading Dump File [C:\Users\Usra\Downloads\ssmross\SF_24-02-2014\022414-34734-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`02e54000 PsLoadedModuleList = 0xfffff800`030976d0
Debug session time: Tue Feb 25 08:13:33.125 2014 (UTC + 6:00)
System Uptime: 0 days 0:00:15.750
Loading Kernel Symbols
.................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800560d8f8, 0, 0}

Probably caused by : AuthenticAMD

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

1: 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: fffffa800560d8f8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`031c46f0 fffff800`03114ca9 : fffffa80`0560d8d0 fffffa80`039f9b50 fffff8a0`0000000b 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`031c4c10 fffff800`02ff5ea7 : fffffa80`0560d8d0 fffff800`0306f2d8 fffffa80`039f9b50 00000000`00000282 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`031c4c40 fffff800`02f5d275 : fffff800`030d0b40 00000000`00000001 fffffa80`0554dfa0 fffffa80`039f9b50 : nt!WheapProcessWorkQueueItem+0x57
fffff880`031c4c80 fffff800`02ed3261 : fffff880`01052e00 fffff800`02f5d250 fffffa80`039f9b00 fffffa80`0000055a : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`031c4cb0 fffff800`031662ea : 00000000`00000000 fffffa80`039f9b50 00000000`00000080 fffffa80`03973990 : nt!ExpWorkerThread+0x111
fffff880`031c4d40 fffff800`02eba8e6 : fffff880`02f63180 fffffa80`039f9b50 fffff880`02f6dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031c4d80 00000000`00000000 : fffff880`031c5000 fffff880`031bf000 fffff880`031c3d90 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: AuthenticAMD

IMAGE_NAME:  AuthenticAMD

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

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

A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint. Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress. You can read more on this error and what to try here... Stop 0x124 - what it means and what to try: Stop 124 - What it means and what to try