BSOD playing GTA V, error 0x124_AuthenticAMD

Hey guys.

I've all of a sudden started getting these BSODs playing GTA V (was playing online) in the last hour or so. I'm not sure what's wrong but it's directly pointing toward my CPU..but no idea why. The CPU temp is perfectly fine and isn't necessarily overheating. It's rating at about 50'C with the stock cooler. (I'm thinking of getting another liquid cooler though).

My dumps and what not are in the RAR archive attached with the required information.

Hey Kyle.

0x124 is a hardware failure, and it may point to the CPU but it might also be a RAM issue, outdated chipset drivers or BIOS.

I'm unfortunately off to bed but I'll look into your issue tomorrow morning if someone else haven't already helped!

Cheers, Boris :)

0x124's are typically related to a hardware issue and can only be isolated by stress testing the major components.

If overclocking, reset all overclocks back to their default settings and then follow these:

RAM - run for a minimum of 8 consecutive passes
RAM - Test with Memtest86+

CPU - run the HIGH test
CPU - Stress Test Using IntelBurnTest

Video - run the FURMARK test for 20mins
Graphics Card Problems - Diagnose
Video Card - Stress Test with Furmark

Storage - run the SHORT test using the DOS version
SeaTools for DOS and Windows - How to Use

Wouldn't stress testing my GPU and CPU result in one of them dying quicker? The last few BSOD threads I made I had a GTX 470 SuperClocked (by factory default) and it died due to the temps getting too hot and fan profiles not working. I don't really want to kill my Radeon R9 280X or my CPU. lol

Stress testing is a way to find out if that component is causing problems.
Yes, stress testing may cause problems, but only if you don't keep an eye on the temperatures and abort when the temperatures are getting to high (or when errors show what point to a faulty component/failure).

It's most probably the CPU that is having an issue, Section 2 below taken from the latest dump shows there is a Cache L1 Error!

5: kd> !errrec fffffa800be4f028
===============================================================================
Common Platform Error Record @ fffffa800be4f028
-------------------------------------------------------------------------------
Record Id : 01d17bee532beea8
Severity : Fatal (1)
Length : 928
Creator : Microsoft
Notify Type : Machine Check Exception
Timestamp : 3/12/2016 0:13:46 (UTC)
Flags : 0x00000000

===============================================================================
Section 0 : Processor Generic
-------------------------------------------------------------------------------
Descriptor @ fffffa800be4f0a8
Section @ fffffa800be4f180
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 : 1
CPU Version : 0x0000000000100fa0
Processor ID : 0x0000000000000005

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

Local APIC Id : 0x0000000000000005
CPU Id : a0 0f 10 00 00 08 06 05 - 09 20 80 00 ff fb 8b 17
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 @ fffffa800be4f240

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

Error : DCACHEL1_DRD_ERR (Proc 5 Bank 0)
Status : 0xb6002000d7000135
Address : 0x000000008832c200
Misc. : 0x0000000000000000

IoNGeNeRaL, considering that you have already done OCing I'm surprised that you are so against stress testing your CPU.

That is the error, but not the cause.
The CPU reports the errors, but that doesn't mean it is the cause.

axe0 said:

That is the error, but not the cause.
The CPU reports the errors, but that doesn't mean it is the cause.

I think it is since both dumps have the exact same error.

axe0 said:

Stress testing is a way to find out if that component is causing problems.
Yes, stress testing may cause problems, but only if you don't keep an eye on the temperatures and abort when the temperatures are getting to high (or when errors show what point to a faulty component/failure).

BorisTheAnimal said:

It's most probably the CPU that is having an issue, Section 2 below taken from the latest dump shows there is a Cache L1 Error!

IoNGeNeRaL, considering that you have already done OCing I'm surprised that you are so against stress testing your CPU.

I've only overclocked my CPU a tiny bit compared to what I have a couple years ago. The highest OC with a Corsair Hydro H70 cooler was 4.67GHz but it was rather unstable with the CPU voltage varying between 1.4v - 1.522v. The best stable OC I ever archived was 4.48GHz at 1.38v/1.42v. I'm only running my CPU clock between 3.3GHz and 3.7GHz (Turbo mode enabled). The temperature of the CPU currently is 40C. Usually when I'm running more than 15-20 programs it temps up to 50/55C. It's never gotten higher than 55C nor has it ever crashed with a CPU overheat. (to my knowledge anyway) Usually if my system crashes it'll say in the BIOS "CPU Overclocking failed. Please re-configure your system" but it always comes up with that if my system randomly crashed or just rebooted. (even when I force shutdown which sometimes I have to do because it takes like 5 minutes or more to shut down. Boot up is nice, fast and smooth (SSD) but for shutting down...nah. It likes to take it's time. -_-

It's definitely not the CPU or GPU that's problematic/faulty. My system only seems to sometimes crash when playing GTA V with modding turds (cheaters) spawning a s*it load of things or doing some sorcerous black magic with their hack. Other than that, the system doesn't crash at all.



Additionally, I would never perform a potentially dangerous overclock with a stock AMD heatsink. I've only ever "properly" overclocked with a liquid cooler because I personally don't think that CPUs should be "normal" temps of 60+C. I try to keep my CPU temp below 60 if I can help it.

Still, the only way to solve 0x124's is to stress test properly. If you choose not to, there is nothing further we can do to help you. Your choice.