BSOD when playing FSX only

[Adikool]

Hi guys, I have been getting BSOD whilst playing Microsoft Flight Simulator X.
My custom computer is 6 months old and i have had this BSOD only in FSX. Got know idea, but i have attached the following, thanks in advance
Much appreciated, Adikool

 

[Boozad]

Both of your dumps are 0x124s, these indicate a hardware error most of the time but, as is the case here, they rarely point towards which piece of hardware is failing. In this case please follow the stress and diagnostic tests listed below to try and uncover which piece of hardware is problematic.

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: fffffa800a2f8028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000ff800000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000124, Low order 32-bits of the MCi_STATUS value.
1: kd> !errrec fffffa800a2f8028
===============================================================================
Common Platform Error Record @ fffffa800a2f8028
-------------------------------------------------------------------------------
Record Id     : 01d0cf3809fedc04
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 8/5/2015 8:05:23 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa800a2f80a8
Section       @ fffffa800a2f8180
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Cache error
Operation     : Generic
Flags         : 0x00
Level         : 0
CPU Version   : 0x00000000000306c3
Processor ID  : 0x0000000000000002

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa800a2f80f0
Section       @ fffffa800a2f8240
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000002
CPU Id        : c3 06 03 00 00 08 10 02 - bf fb fa 7f ff fb eb bf
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0  @ fffffa800a2f8240

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa800a2f8138
Section       @ fffffa800a2f82c0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : DCACHEL0_WR_ERR (Proc 1 Bank 1)
  Status      : 0xff80000000000124
  Address     : 0x00000002385a9200
  Misc.       : 0x0000000000000086

STOP 0x124 Troubleshooting

Read carefully before proceeding.

   Warning

:warn: If you're overclocking your system, revert back to stock clocks now. :warn:

   Note

Test the system once the overclock is removed before continuing with the steps outlined below.

Part One: CPU Stress Test
Part Two: MemTest86+ RAM Diagnostic
Part Three: Hard Drive Diagnostics
Part Four: GPU Stress Test

ONE

 CPU TEST

:ar: Run Prime95 to stress test your CPU. http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html

   Warning

Your CPU temperatures will rise quickly while under this stress test. Keep a keen eye on them and abort the test if overheating occurs.

TWO

 RAM TEST

:ar: Run MemTest86+ to analyse your RAM. http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

   Note

MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

THREE

 HDD TEST

:ar: Run SeaTools to check the integrity of your HDD. http://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html

   Note

Do not run SeaTools on an SSD as the results will be invalid.

:ar: Run chkdsk http://www.sevenforums.com/tutorials/433-disk-check.html

FOUR

 GPU TEST

:ar: Run Furmark to stress test your GPU. http://www.sevenforums.com/tutorials/100356-video-card-stress-test-furmark.html

   Note

Run Furmark for around 30 minutes.

   Warning

Your GPU temperatures will rise quickly while Furmark is running. Keep a keen eye on them and abort the test if overheating occurs.

 

[Adikool]

Hi, I did the tests, and nothing abnormal came back! What i did notice, is that when i went into bios and set the processor clock to default, that seemed to have fixed the BSOD so far. I don't know if it's related or not but i will watch the Over Clocking maybe?
Thanks for your help, kind regards Adrian.

 

[Boozad]

You're welcome. Yes it could well have been an unstable overclock, good to hear it's looking good and thanks for letting us know.