BSoD 0x124 on Win7 x64

[Jeron]

Hi, I experience BSoD once or twice a month. My PC is kinda new, it runs 24/7 and crashes are a big issue for me. Usually it happens during games but sometimes while PC is idle.
PC specs:

Read More:

CPU Intel Core i5-4670K OEM 3.4 GHz
GigaByte GA-Z87-HD3 rev1.0 (RTL) LGA1150 <Z87> 2xPCI-E Dsub+DVI+HDMI GbLAN SATA RAID ATX 4DDR-III
GigaByte GeForce GTX 770 WINDFORCE 3X (GV-N770WF3-2GD)
Kingston < Kingston 99U5471-037.A00LF> DDR-III DIMM 8Gb (x2)
HDD Western Digital WD1003FBYX 1TB
Thermaltake < TRX-650MPCEU> TR2 RX 650W
ASUS Xonar Essence ST (RTL) PCI
Thermalright True Spirit 140 Cooler

• Win7 is up to date
• I have latest drivers from manufactures' websites (as well as updated BIOS)
• RAM is checked by memtest (24hrs) - no errors
• There is no overheating
• HDD is ok
• There is no overclock except x38 CPU multiplier (I'm sure it's stable), I had these BSoDs long before I bumped up multiplier
• I tried replacing RAM and GPU but with no results

Attached zip file contains five latest minidumps. I really appreciate any help you can provide.

 

[Patrick]

Hi,

[LIST]
[*]There is no overclock except x38 CPU multiplier (I'm sure it's stable), I had these BSoDs long before I bumped up multiplier
[/LIST]

I really hate to be the guy that tells you to please set the system to optimized defaults via the BIOS, or clearing the CMOS before I take a look at these crash dumps, but can you please do so and tell me if the crashes persist?

Regards,

Patrick

 

[Jeron]

Yup, crashes persist. Ever since I started to get BSoD, I updated BIOS and loaded "optimized defaults" profile but it didn't work out. Basicly I started to OC my CPU only like two weeks ago and you can see that most minidumps are two months old.

 

[Patrick]

Thanks, was just making sure.

WHEA_UNCORRECTABLE_ERROR (124) bug check.

A fatal hardware error has occurred. This fatal error displays data from the Windows Hardware Error Architecture (WHEA).

If we run an !errrec on the 2nd parameter of the bugcheck (address of the WER structure) we get the following:

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

[COLOR=#ff0000]Error         : GCACHEL2_ERR_ERR (Proc 1 Bank 5)[/COLOR]
  Status      : 0xbe0000000100110a
  Address     : 0x00000002602fe5c0
  Misc.       : 0x0000009086000086

Looks like an error with your L2 Cache, specifically on Processor #1 and Cache Bank #5.

-- Uninstall OpenHardwareMonitor, very old device drivers.

1: kd> lmvm openhardwaremonitor
start             end                 module name
fffff880`082a7000 fffff880`082ae000   OpenHardwareMonitor   (deferred)             
    Image path: \??\D:\OpenHardwareMonitor\OpenHardwareMonitor.sys
    Image name: OpenHardwareMonitor.sys
    Timestamp:        Sat Jul 26 09:29:37 [COLOR=#ff0000]2008[/COLOR]

---

If the above does not help, there is only so much you can do with a bugcheck like this until it comes down to a faulty processor that will need to be replaced. Start from 1 and work downward:

1. Ensure your temperatures are within standard and nothing's overheating. You can use a program such as Speccy if you'd like to monitor temps - Speccy - System Information - Free Download

2. Clear your CMOS (or load optimized BIOS defaults) to ensure there's no improper BIOS setting - How To Clear CMOS (Reset BIOS)

3. Ensure your BIOS is up to date.

4. Software conflict that can usually cause *124 bugchecks are OS to BIOS utilities from manufacturer's like Asus' AI Suite. If you have something like this software-wise, remove it ASAP.

5. If all of the above fail, the only left to do is replace your processor as it is faulty.

Regards,

Patrick

 

[Jeron]

Thanks for the help!

-- Uninstall OpenHardwareMonitor, very old device drivers.

Is it enough to unload OHM or should I somehow disable that driver? OHM is distributed as zip archive, there is no install/uninstall file.

If all of the above fail, the only left to do is replace your processor as it is faulty.

So if deleting OHM does not help, can I be sure it's definitely CPU? Or is there slight possibility that it's m/b or PSU?

 

[Patrick]

You can safely unload it by renaming the .sys to .old in its respected directory, and then restarting.

If the cleared CMOS does not help, and your BIOS is already up to date, this is very likely a faulty processor. There is virtually no way of me telling you if it's a motherboard vs a processor problem, due to there being no diagnostics for either. FWIW, L2 Cache errors generally imply a standalone processor failure, and not a board problem. Also, this does not look like a PSU problem at this time whatsoever. We'd have different symptoms/errors.

Regards,

Patrick