Minidump ntoskrnl.exe crashes w/ idle computer or at 35-40 min w/ use

Hoping someone can help.

Please excuse me if I use incorrect terms or don't quickly understand as I am a Mac person who uses PCs at work.

I have a MacPro Early 2009 running Windows 7 Pro 64bit via BootCamp.

Things were going fine until my work changed software in office. While creating a partition on the SSD and installing the image on to the partition, I now have constant crashes either when computer goes idle after the screen shuts off per power savings settings or if using the computer occurs between 35-40 minutes after the computer restarts. In fact it occurred writing this post.

I have never been able to see the BSOD, but either the screen does not wake with the keyboard, or if I do not allow the computer monitor to go off, clicking on the cursor either does not work or the cursor is not visible. Only a power button restart recovers.

Recently I have now begun getting error dialog boxes saying different things. One more repeated message is "Desktop Window Manager has stopped working and was closed" but when I look it is running. I have also begun receiving messages like "javaw.exe - Bad Image" from Explorer.exe or some other program - Bad Image.

I have tried a fresh install of Windows 7 Pro 64bit on a reformatted drive but the crash still occurs.

Any insight would be appreciated.

Thanks.

Code:

*******************************************************************************
*                                                                             *
*                        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: fffffa8015759038, 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_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

STACK_TEXT:  
fffff880`035f56f0 fffff800`044c2cb9 : fffffa80`15759010 fffffa80`13bbcb50 00000000`00000000 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`035f5c10 fffff800`043a3ea7 : fffffa80`15759010 fffff800`0441d2d8 fffffa80`13bbcb50 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`035f5c40 fffff800`0430b275 : fffff800`0447ed00 00000000`00000001 00000000`00000000 fffffa80`13bbcb50 : nt!WheapProcessWorkQueueItem+0x57
fffff880`035f5c80 fffff800`04281261 : fffff800`046d2100 fffff800`0430b250 fffffa80`13bbcb00 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`035f5cb0 fffff800`0451373a : 00000000`00000000 fffffa80`13bbcb50 00000000`00000080 fffffa80`13ba1130 : nt!ExpWorkerThread+0x111
fffff880`035f5d40 fffff800`042688e6 : fffff880`03500180 fffffa80`13bbcb50 fffff880`0350b2c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`035f5d80 00000000`00000000 : fffff880`035f6000 fffff880`035f0000 fffff880`035f52d0 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP:  0

IMAGE_VERSION:  

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_MEMORY__UNKNOWN_PRV

BUCKET_ID:  X64_0x124_GenuineIntel_MEMORY__UNKNOWN_PRV

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x124_genuineintel_memory__unknown_prv

FAILURE_ID_HASH:  {8b317a10-b18e-5d7a-b289-672e1356fa8f}

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

If you are overclocking, please stop and reset everything to defaults. 0x124 is indicative of a HW issue.