BSOD once a week with bug check code, 0x00000124

rob909e · 11 Oct 2015

I'm at my wits end with this computer. I get BSOD 0x124 about once a week, some times twice a week, since the life of the computer, which I've had for about 3 years. I've changed out the mobo from a GA-Z77X-UD3H to my current mobo a Z77 Extreme6 I've run memtest on each dim, had to RMA two of them due to the hammer test, and even with the fresh new ram, I still get BSOD almost daily.

While running the dm_log_collector to get the info to upload to this forum, I had another BSOD 124 while the program was collecting my PC's info. Luckily I was able to re run it after I booted to my computer.

No Im not OCing ANYTHING. This happens when the bios defaults are loaded. Happens when I turn off intel turbo boost and/or C states, and shared memory. XMP profile for my MEM on or off makes no difference. I also have a kernal memory dump, if anyone wants to look.

Please! Could someone take me on as a side project, because I can't find a case were a BSOD code 124 ever gets solved. I know that a 124 is usually hardware related but not all the time.

__________________
Windows 10
Asrock Z77 Extreme 6
Intel i7 3770K 35GHz Not OCed
G.SKILL Ripjaws X Series (4 x 4GB) F3-12800CL9D
His IceQ X2 AMD 7950 3GB
Samsung 850 Series SATA3 SSD 500GB
Western Digital 1TB HD
Asetek 510lc 120mm Closed Loop WaterCooler
Presonus Firestudio 2626
Logitech G700s
Ducky Shine Keyboard
Corsair CMPSU 850TX V2

axe0 · 12 Oct 2015

Hi rob909e,

Welcome to the 10forums.

The errors are 0x124 WHEA_UNCORRECTABLE_ERROR (Windows Hardware Error Architecture)
This means that there are problems with your hardware, but this error is also caused by overclocking or faulty drivers

STOP 0x124 Troubleshooting

Read carefully before proceeding.

Warning

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

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

Run Prime95 to stress test your CPU. Prime95 - Stress Test Your CPU - Windows 10 Forums

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

Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 10 Forums

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

Run SeaTools to check the integrity of your HDD. http://www.sevenforums.com/tutorials...s-how-use.html

Note

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

Run chkdsk http://www.sevenforums.com/tutorials...isk-check.html

FOUR

GPU TEST

Run Furmark to stress test your GPU. FurMark - GPU Stress Test - Windows 10 Forums

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.

The problem
There is a data read error with the cache in core 6 of the CPU.

Code:

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


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


Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Cache error
Operation     : Data Read
Flags         : 0x00
Level         : 2
CPU Version   : 0x00000000000306a9
Processor ID  : 0x0000000000000001


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


Local APIC Id : 0x0000000000000001
CPU Id        : a9 06 03 00 00 08 10 01 - bf e3 9a 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  @ ffffe00184374240


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


Error         : DCACHEL2_DRD_ERR (Proc 1 Bank 6)
  Status      : 0xbe20000000021136
  Address     : 0x000000008f2cec00
  Misc.       : 0x000000b041004086

rob909e · 12 Oct 2015

There is a data read error with the cache in core 6 of the CPU....

What causes this? Is this a bad CPU? What can I do, test wise, to help figure out how to correct this.

axe0 · 12 Oct 2015

It is hard to say what causes this as this is a read error.
This could mean the CPU is damaged, or another component is passing corrupted data, or driver problems.

Please run the stress tests above in my previous post.

rob909e · 19 Oct 2015

I have around 10 different dumps that point to a stop error 124. When I ran the dm_log_collector.exe tool, did it save all those dumps or just the latest one? The reason I'm asking, I would like to know if all the dumps are reporting the same data read error with the cache in core 6 of the CPU. When you inspected the file that I uploaded, do you know if all or just the latest dumps were included?

Also, I replaced the motherboard, changed out both the HDD and the SSD with new ones, and I also replaced the RAM and ran a memtest86 with no ERRORS. I still crash with the same 124 code even after replacing those components. I still need to run the CPU test and GPU test.

Also worth noting, throughout the computers life, I have NEVER been able to run with BIOS settings at optimized defaults due to Intel turbo boost crashing my system within minutes, instead of days now. Same 124 error. So I have to turn that setting to OFF in order to have a more stable system. I've never OCed my CPU before because I still haven't managed a stable system at default clocks.

axe0 · 19 Oct 2015

I have only analysed the most recent ones, there is not often a reason to check dumps more then a month old.
The zip you have uploaded contains dumps spread over 2 months.

If you'd like an update of your drivers, which are old or could cause problems, just let me know by uploading a new zip created with te dm log collector tool. Please keep in mind that this could take some time which is not always presented.

Note

Rarely is specific software also causing this crash and it doesn't always have to be known software!

rob909e · 19 Oct 2015

I uploaded the new zip file from the dm log collector tool. So far I have been BSOD 124 free for 12 days.... However, if my computer follows the same time pattern for BSOD, a BSOD should present itself any time now.

In the meantime, I'm going to run Prime95 and Furmark. When running Prime95, If the temperature starts rising too much, at what temps should I stop the test? Also, is there a report and/or analysis that I should upload? When I run Furmark is there anything that I should upload after the test completes?

axe0 · 19 Oct 2015

If the temperature reaches 85C, abort the test, clean the heatsink, replace the thermal paste (properly!) and try it again.
If Prime95 detects a problem, it'll show them in the logs.
For furmark, it is a little different but you can read it in the tutorial.

So far I know there is nothing to upload with these 2 tests.

rob909e · 19 Oct 2015

Specs before and while running running Prime 95.

rob909e · 19 Oct 2015

Ran Furmark without any issues. temperature maxed out at 71C with no errors or artifacts.