Solved BSOD/Restarts 0x00000124

[Dannyx28]

Ok so a little background information. Up until I bought my new hard drive I was getting a lot of BSODs and restarts without BSOD, they happened every 4-5 days and would happen 2-3 times in the same day after happening once. Nearly all of the BSODs showed the 0x00000124 code and would happen irrelevant of what the computer was doing (At least to my knowledge)

After I got a new hard drive (Which was roughly 1 month ago) the problem seemed to have gone but I've had 3 restarts in the past 2 weeks with no obvious cause.

Thanks for reading.

 

[YoYo155]

Hi and welcome to SF .

All three bugchecks are the the exact same consistant error:

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: [COLOR=Blue][U][B]0000000000000000[/B][/U][/COLOR], Machine Check Exception
Arg2: [COLOR=SeaGreen][U][B]fffffa8008757028[/B][/U][/COLOR], Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000fe800000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000020015, Low order 32-bits of the MCi_STATUS value.

!errrec [COLOR=SeaGreen][U][B]fffffa8008757028[/B][/U][/COLOR]

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

Error         : [COLOR=Red][U][B]DTLBL1_ERR (Proc 1 Bank 0)[/B][/U][/COLOR]
  Status      : 0xfe80000000020015
  Address     : 0x0000f880043f1000
  Misc.       : 0x0000000000000000

We can see an error in the TLB cache, which is consistent though out the rest of the dumps.



It appears that your CPU is overclocked:

[CPU Information]
~MHz = REG_DWORD [COLOR=Red][U][B]3616[/B][/U][/COLOR]
Component Information = REG_BINARY 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
Configuration Data = REG_FULL_RESOURCE_DESCRIPTOR ff,ff,ff,ff,ff,ff,ff,ff,0,0,0,0,0,0,0,0
Identifier = REG_SZ AMD64 Family 21 Model 1 Stepping 2
ProcessorNameString = REG_SZ AMD FX(tm)-4100 Quad-Core Processor            
VendorIdentifier = REG_SZ AuthenticAMD

Reset the BIOS back to default in case you're unaware that your CPU is overclocked:

• CLR CMOS

   Note

Write down the current value of the SATA Mode!
Its either AHCI or IDE.
After resetting the CMOS go back and verify the value for SATA Mode is what it was
when the OS was installed.

A newer BIOS version has been released:

BiosVersion = [U][B]1003[/B][/U]   
BiosReleaseDate = 03/26/2012

AMD CPU's are know to be sensitive to BIOS updates and benefit from such.
Please update your BIOS.

   Warning

Flashing the BIOS is a risky procedure. If you are uncomfortable
performing it yourself have a technician perform it.
Regardless, flashingis at your own risk.

• M5A78L-M LX - Motherboards - ASUS

View attachment 286678

A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint. Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress. - H2SO4

The generic nature of the 0x124 (Arg1=0) stop code means we would have to take
the trail & error approach.

Do you have any spear parts (or another PC) to test with, mainly a PSU?
The usual suspect of this kind of BCCode is the CPU but it's often not the the case which is why we need
to test other components to rule them out as the cause.
How old are your components?


What is the make an model of you PSU?
Fill out this form and post back the result:

• Power Supply Calculator

Good practice, open up the case and re-seat all types of connection.

• SATA Cables (HDD/SSD/ODD).
• SATA-Power.
• Motherboard 24-pin.
• Motherboard 4/8-pin (CPU).
• Re-seat the RAM.
• Re-seat the GPU.

Make sure that every slot / cable head is free of dust or other obstruction.
Make sure that every connection is seating properly and firmly in-place.

Also have a look at the motherboard and the GPU, search for any "bad caps", bulky, leaking bloated capacitors.

i.e

• Download Speccy and post a Screenshot of the summary window, one at idle and another while putting load on the PC using Prime95 for the CPU side and Furmark for the GPU.

   Note

If any other component is overclocked reset it back to stock speeds!

Good places to read more:

• Stop 0x124 - what it means and what to try
• Stop 0x124 Troubleshooting - 'New Method'

 

[Dannyx28]

Hello and thanks for your detailed reply

I've never touched anything to do with overclocking so it is weird that my CPU would appear to be overclocked.

I've reset the bios, updated the bios and the sata mode was IDE before and after the reset.

I don't have another PSU or PC however I might be able to borrow a old pc to test with.

My PSU and graphics card are roughly 6-8 months old, my hard drive is about 1 month old, heatsink/fans/case are only a few months old and the motherboard, processor and RAM are about 4 years old.

This is a link to the PSU I have Alpine Alpine II 700Watt PSU White With 120mm Blue Fan PPFC | Falcon Computers

I filled the power supply calculator in as best as i could and the result was Minimum PSU Wattage:321 and Recommended PSU Wattage: 371

I opened up my computer and cleaned everything and made sure all the connections were seated properly and i checked for bad caps but found none.

I took the screenshots for the stress tests:

Idle screenshot:
View attachment 286788

CPU screenshot:
View attachment 286786

GPU Screenshot:
View attachment 286787

Thanks for reading and helping.

 

[YoYo155]

Thanks for the feedback .
The temperatures are looking very good, how long did you allow the stress for?

I wouldn't replace the PSU with an old one as it might just give false positives, keep testing with your current one for the moment being.

Naturally our main focus would be the 4 years old motherboard, RAM and CPU but is not to say
that other newer parts can't hit the dirt prematurely.

Since resetting the CMOS (BIOS), cleaning and re-seating the physical connections
did you have any issues?

 

[Dannyx28]

Hi,

I did the CPU stress test for an hour since after about 20minutes the temperatures didn't really go up. Should i do it again for longer? The GPU was only on for about 10 minutes since the temperatures leveled out after about 6 mins.

Today my PC had an actual BSOD instead of a restart and it was the same code 0x00000124.

I'm not sure if this is relevant but its another issue I'm currently having. So I'd been having a lot of screen flickering for the past month or so and it had got so bad that i was having headaches so since my screen was quite old and i needed a new one anyway i bought a new one, thinking it would fix the problem (This was maybe 2 weeks ago). For the first few days after getting a new one it was fine and there was no problems but then I started to get screen flicker again. Its no where near as bad as it was with my other screen but its still there. Not sure if that has anything to do with the graphics card or if there is something wrong with my settings but either way it might be helpful information.

 

[YoYo155]

What sort of flickering?
Does it look like a low-hertz display (below 59Hz), or are the flickers are very predominant (sudden blackouts)?

Did you update the BIOS?

 

[Dannyx28]

Sort of background waves and lines that are more dominant in games rather than anywhere else. I've messed around with the settings lots and had no luck, currently the res is 1920*1080 with 75hertz refresh rate and its made no difference.

Yeah i updated the bios.

 

[YoYo155]

Could be a faulty GPU / output connector.
Try using a different output source ie. DVI / HDMi..
If that doesn't fix the BSOD's switch to the integrated graphics for testing purposes.

 

[Dannyx28]

Sorry for late reply, had to go buy a cable and test it. I got a DVI-HDMI cable and from what i can tell the screen flicker is gone but I haven't tested it for a long period of time yet.

 

[YoYo155]

Thanks for the update, let us know how things develop due time .

 

[Dannyx28]

Still no screen flicker however my computer restarted again with the same error code. I wasn't doing anything but watching a youtube video and hadn't done anything intensive today either.

 

[YoYo155]

Thanks for the update, please upload a new instance of the file generated by the SFDT .
Seeing how 0x124 is hardware we need to test all aspects of it.

let's start with the RAM.

Testing the RAM:

Test and Diagnose RAM Issues with Memtest86+:

• RAM - Test with Memtest86+

   Tip

• :info: Pay close attention to part 3 of the tutorial "If you have errors"
• :tip: Test the RAM with Memtest86+ for at least 7-10 passes. It may take up to 22 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold.

When done with the testing procedure take a picture and upload it here.


Then;

   Warning

The Following Method Should NOT Be Performed On An SSD!

Testing the HDD:

1. Perform a Disk Check | Disk Check
2. Then Post the results following | THIS METHOD
3. Download SeaTools for DOS if you don't want to use a CD to test the HDD you can use YUMI – Multiboot USB Creator to create a bootable USB (instructions are found at the bottom of both pages).
4. If SeaTools for Windows is unable to recognize your HDD visit HDDdiag and follow the instructions.

Keep updating .

 

[Dannyx28]

Wow, i'd just read this and started looking into testing the RAM and it crashed again while having nothing open but firefox. Not sure if i'm unlucky or if the crashes are becoming more frequent.

Anyway I'll upload the SFDT file and then go onto doing the RAM and hard drive stuff.

 

[YoYo155]

Thanks for the update.
Unfortunately the errors are consistent as well are the parameters.
At this point I'm pretty sure it's the TLB/L1 cache that's at fault meaning a defective CPU .

 

[Dannyx28]

I did the hard drive stuff and the SeaTools test finished with a success. The log for the Disc check is attached.

 

[Dannyx28]

Hmm, great the broken part would have to be the most expensive to replace I was going to buy a new CPU and motherboard relatively soon anyway so if that is the case it isn't to bad.

 

[YoYo155]

I'm guessing it's out of warranty ?
On that note yes I guess you can find consultation in that, good luck with your new build! .

 

[Dannyx28]

If it is most likely the processor then its probably a good idea to take my computer to the local computer store to double check before i spend £200+ on a new processor and most likely buy another motherboard at the same time. Thanks for all the help, you have done a great job of helping me understand my problem and giving detailed advice

 

[YoYo155]

Happy to help .
And I'm even more happy about the fact that you understood what we are dealing with
and could see the reason behind it all , good luck with the future PC and enjoy your stay on the forums !