Intermittent hardware failure

I have a mid 2013 M17x which has been giving me intermittent problems since delivery. No idea what is causing the problem; I don't think it has ever crashed under use, only when idling. Like, I'll come home and open the lid to find it's rebooted and can't find one of the hard drives (possible SATA controller failure?) or had a BSOD. Occasionally, when I start using it, everything looks normal, until I try to do something - can't launch anything or do anything, can still move mouse, but system just seems to have stalled, and doesn't recover until a hard power cycle.

Here's an analysis from my last (and only) minidump:

Code:

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18717.amd64fre.win7sp1_gdr.150113-1808
Machine Name:
Kernel base = 0xfffff800`0345d000 PsLoadedModuleList = 0xfffff800`036a1890
Debug session time: Fri Feb 27 02:27:38.002 2015 (UTC - 5:00)
System Uptime: 0 days 0:00:09.860
*******************************************************************************
*                                                                             *
*                        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: fffffa80108e08f8, 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:
------------------

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

BUGCHECK_STR:  0x124_GenuineIntel

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:
fffff880`037d35b0 fffff800`0371ecb9 : fffffa80`108e08d0 fffffa80`0d3fb040 00000000`00000016 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`037d3ad0 fffff800`035ff157 : fffffa80`108e08d0 fffff800`036792d8 fffffa80`0d3fb040 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`037d3b00 fffff800`03566505 : fffff800`036dad00 00000000`00000001 fffffa80`10f6b260 fffffa80`0d3fb040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`037d3b40 fffff800`034dba95 : fffff880`013d2e00 fffff800`035664e0 fffffa80`0d3fb000 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`037d3b70 fffff800`03770b8a : 00000000`00000000 fffffa80`0d3fb040 00000000`00000080 fffffa80`0d388ae0 : nt!ExpWorkerThread+0x111
fffff880`037d3c00 fffff800`034c38e6 : fffff880`03589180 fffffa80`0d3fb040 fffff880`035940c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`037d3c40 00000000`00000000 : fffff880`037d4000 fffff880`037ce000 fffff880`045d2770 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE_PRV

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE_PRV

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

 

That's usually a CPU error.

 

How would I go about testing that? CPU stress test?

Considering that aside from the odd BSOD, the system generally doesn't freeze...something makes me think that's not the only problem.