BSOD always while playing FSX sim

It is something to do with Microsoft® Flight Simulator X prima facie. May be it is the source of the issue itself. But it is always tough to say about a stop 0x124.

Do the basic and fundamental troubleshooting of stop 0x124 as guided in Stop 0x124 - what it means and what to try .... if it finds anything as problematic, let us knoe for the required action. Otherwise contract with Microsoft about Flight Simulator X, ask them for a fix that may be applicable in your system.
_______________________________________

Code:

...........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa80140d3028, bf800000, 124}

Probably caused by : GenuineIntel

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

2: 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: fffffa80140d3028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000bf800000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000124, 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:  fsx.exe

CURRENT_IRQL:  f

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

STACK_TEXT:  
fffff880`0336db58 fffff800`03a13a3b : 00000000`00000124 00000000`00000000 fffffa80`140d3028 00000000`bf800000 : nt!KeBugCheckEx
fffff880`0336db60 fffff800`035a6713 : 00000000`00000001 fffffa80`139ae9a0 00000000`00000000 fffffa80`139ae9f0 : hal!HalBugCheckSystem+0x1e3
fffff880`0336dba0 fffff800`03a13700 : 00000000`00000728 fffffa80`139ae9a0 fffff880`0336df30 fffff880`0336df00 : nt!WheaReportHwError+0x263
fffff880`0336dc00 fffff800`03a13052 : fffffa80`139ae9a0 fffff880`0336df30 fffffa80`139ae9a0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`0336dd50 fffff800`03a12f0d : 00000000`00000008 00000000`00000001 fffff880`0336dfb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`0336dd90 fffff800`03a06e88 : 00000000`00000000 00000000`02f56f18 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`0336ddc0 fffff800`0348d7ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`0336ddf0 fffff800`0348d613 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`0336df30 00000000`200f5b6d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`03e7ff2c 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x200f5b6d


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_PROCESSOR_CACHE

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x124_genuineintel_processor_cache

FAILURE_ID_HASH:  {270f58cb-a20a-a72d-6d81-eb8c82f01f7a}

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

Go through Stop 0x124 - what it means and what to try ... it will guide you to all the necessary steps that isneeded to troubleshoot the issue.

First of all, make it sure that the computer is not overclocked. As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings. Also set the BIOS to default, too.

How To Clear CMOS (Reset BIOS)

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: Speccy - Publish Snapshot of your System Specs .

Test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+

Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Stress test the Graphics Card using Furmark.

Video Card - Stress Test with Furmark

Take a screenshot of the furmark window before closing it. Upload the screenshot for us. Also let us know if you have experienced any crash/BSOD and/or artifacts during the test.

Stress test the CPU.

Hardware - Stress Test With Prime95

It saves the result as a .txt file in the prime95's folder. Upload the file for us.

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.

eXtreme Power Supply Calculator - The only power supply calculator trusted by PSU manufacturers and computer enthusiasts

Also let us know the wattage of the PSU.

Let us see upto this point. In nothing came up, we will check the next set of things.