Whea_uncorrectable_error

could someone debug my dump file?

memory tested fine
maybe cpu is overheating. i dont know. the fans look clean and working
the video card was replaced. i got a new 750ti that requires less power then the old graphics card i was using
i replaced the dell power supply a couple years ago with a thermaltake tr2-600w
its a dell bloomfield 435mt
i did in inplace install of windows 7, it seemed to help a lot but i got a stop 124 0x0 today

On Sun 3/29/2015 7:22:03 AM your computer crashed
This was likely caused by the following module: hardware
Bugcheck code: 0x124 (0x0, 0xFFFFFA800E43B028, 0xBE000000, 0x800400)
Error: WHEA_UNCORRECTABLE_ERROR
Dump file: C:\Windows\Minidump\032915-30778-01.dmp

rigorkrad said:

could someone debug my dump file?

Doing only what you asked for, reading the dump file .....

Code:

BugCheck 124, {0, fffffa800e43b028, be000000, 800400}

Probably caused by : GenuineIntel

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

Code:

BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  ffmpeg.exe

CURRENT_IRQL:  f

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

Code:

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_MAE

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x124_genuineintel_processor_mae

FAILURE_ID_HASH:  {addebe90-d04a-b9c9-a39c-2531fe75dd4e}

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

Code:

0: kd> !errrec fffffa800e43b028
===============================================================================
Common Platform Error Record @ fffffa800e43b028
-------------------------------------------------------------------------------
Record Id     : 01d05be6ed607644
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 3/29/2015 7:19:24 (UTC)
Flags         : 0x00000000

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

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Micro-Architectural Error
Flags         : 0x00
CPU Version   : 0x00000000000106a4
Processor ID  : 0x0000000000000000

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

Local APIC Id : 0x0000000000000000
CPU Id        : a4 06 01 00 00 08 10 00 - bd e3 98 00 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  @ fffffa800e43b240

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

Error         : Internal timer (Proc 0 Bank 5)
  Status      : 0xbe00000000800400
  Address     : 0x0000000000de3080
  Misc.       : 0x0000000000000000

Code:

Child-SP          RetAddr           Call Site
fffff800`04a1fa98 fffff800`037ffa3b nt!KeBugCheckEx
fffff800`04a1faa0 fffff800`03392713 hal!HalBugCheckSystem+0x1e3
fffff800`04a1fae0 fffff800`037ff700 nt!WheaReportHwError+0x263
fffff800`04a1fb40 fffff800`037ff052 hal!HalpMcaReportError+0x4c
fffff800`04a1fc90 fffff800`037fef0d hal!HalpMceHandler+0x9e
fffff800`04a1fcd0 fffff800`037f2e88 hal!HalpMceHandlerWithRendezvous+0x55
fffff800`04a1fd00 fffff800`032797ac hal!HalHandleMcheck+0x40
fffff800`04a1fd30 fffff800`03279613 nt!KxMcheckAbort+0x6c
fffff800`04a1fe70 00000000`00e0af0a nt!KiMcheckAbort+0x153
00000000`08d390a8 00000000`00000000 0xe0af0a

If you want to know how to troubleshoot the issue, follow Stop 0x124 - what it means and what to try

If you want any other member to assist you in troubleshooting, upload teh data following the Blue Screen of Death (BSOD) Posting Instructions.

I personally faced some mishaps with ffmpeg, but it usually does not a cause a BSOD, as far as I have noticed.
As you are in DVD decrypting, uninstall ffmpeg and reinstall it afresh. That will take care of any issue about ffmpeg.

The ffmpeg in the codes means, it was the thing running when the BSOD took place; it may not be the cause of it.

For an old branded desktop like this one, stop 0x124 BSODs are possible, and at first you have to pay attention to these following things:

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 installed PSU. It is a must.

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 .

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.

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.

Let us know the results when you can. You can report them one by one if you want.