BSOD Stop Code 0x0124 - But Stress Test Passed?

I've been getting a BSOD on this machine pretty sporadically for about two years and trying to get to the bottom of it. It always seemed to be when I was working on Photoshop or some other resource intensive application, and fairly rarely. But today I got the BSOD three times.

I'm thinking it may be related to inadequate power, but not entirely sure.

The stop code is: 0x00000124.

I've ran the following tests:
Memtest86
Furmark
Prime95
Chkdsk /r on the 4 drives
mdsched
RealTemp looks good

I've checked to make sure all drivers are updated, and looks good there. Only thing left I can think of is that it's not getting enough power, but not sure how to test for that.

I attached the memory.dmp, but unable to interpret the report from Windbg (pasted below). Any thoughts on how I can fix this once and for all?

Appreciate the help in advance.

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is 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.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`03205000 PsLoadedModuleList = 0xfffff800`03448890
Debug session time: Wed Jan  7 14:21:19.127 2015 (UTC - 6:00)
System Uptime: 0 days 1:05:21.609
Loading Kernel Symbols
...............................................................
................................................................
..............................................
Loading User Symbols

Loading unloaded module list
................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800ab82028, f2000000, 20008f}

Probably caused by : hardware

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