Stop 0x00000124 computer freezes at random windows 7

PvPTime · 26 Feb 2015

Keep getting blue screen error or computer freezes and I must turn it off manually.

After last blue screen I get this problem signature.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 2057

Additional information about the problem:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA8007231028
BCP3: 00000000BE200000
BCP4: 000000000005110A
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\022615-11434-01.dmp
C:\Users\Owner\AppData\Local\Temp\WER-17097-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

Tried to fix using 2 registry fixing software and now installed older version of graphics driver but still expecting for blue screen or computer freez.

All help appreciated.

Regards
PvPTime

**Pauly** · 26 Feb 2015

Blue Screen of Death (BSOD) Posting Instructions

PvPTime · 26 Feb 2015

Uploaded report.

PvPTime · 27 Feb 2015

Have a bit more information. When I was using computer or playing game such as Dota 2. I was getting less often computer blue scree.
Last night when installed Dragon Ball Xoneverse and played was getting much often. Even about 3-4 times almost at the same time of game, if not same time.
Uploaded picture of how my blue screen error looked like.
*Dumping physical memory to disk: 85* I waited about 5 minutes but didn't load to 100.
I hope this information will help.

**Pauly** · 28 Feb 2015

Your dump files are pointing at cache errors within the cpu itself

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa8007231028, be200000, 5110a}
Probably caused by : GenuineIntel
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
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: 0000000000000000, Machine Check Exception
Arg2: fffffa8007231028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be200000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000005110a, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
------------------

BUGCHECK_STR:  0x124_GenuineIntel
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
CURRENT_IRQL:  f
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
STACK_TEXT:  
fffff880`009c8b58 fffff800`0f023a3b : 00000000`00000124 00000000`00000000 fffffa80`07231028 00000000`be200000 : nt!KeBugCheckEx
fffff880`009c8b60 fffff800`0f1e6713 : 00000000`00000001 fffffa80`07238a60 00000000`00000000 fffffa80`07238ab0 : hal!HalBugCheckSystem+0x1e3
fffff880`009c8ba0 fffff800`0f023700 : 00000000`00000728 fffffa80`07238a60 fffff880`009c8f30 fffff880`009c8f00 : nt!WheaReportHwError+0x263
fffff880`009c8c00 fffff800`0f023052 : fffffa80`07238a60 fffff880`009c8f30 fffffa80`07238a60 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`009c8d50 fffff800`0f022f0d : 00000000`00000008 00000000`00000001 fffff880`009c8fb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`009c8d90 fffff800`0f016e88 : 00000000`00000001 fffff880`009c0180 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`009c8dc0 fffff800`0f0cd7ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`009c8df0 fffff800`0f0cd613 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`009c8f30 fffff880`04261c61 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`009e8b58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm!MWaitIdle+0x19

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_CACHE
BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE
ANALYSIS_SOURCE:  KM
FAILURE_ID_HASH_STRING:  km:x64_0x124_genuineintel_processor_cache
FAILURE_ID_HASH:  {270f58cb-a20a-a72d-6d81-eb8c82f01f7a}
Followup: MachineOwner
---------
1: kd> !errrec fffffa8007231028
===============================================================================
Common Platform Error Record @ fffffa8007231028
-------------------------------------------------------------------------------
Record Id     : 01d051c4a28bb0c4
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 2/26/2015 16:59:24 (UTC)
Flags         : 0x00000000
===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa80072310a8
Section       @ fffffa8007231180
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal
Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Cache error
Operation     : Generic
Flags         : 0x00
Level         : 2
CPU Version   : 0x00000000000206a7
Processor ID  : 0x0000000000000001
===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa80072310f0
Section       @ fffffa8007231240
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal
Local APIC Id : 0x0000000000000001
CPU Id        : a7 06 02 00 00 08 10 01 - bf e3 9a 1f 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  @ fffffa8007231240
===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa8007231138
Section       @ fffffa80072312c0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal
Error         : GCACHEL2_ERR_ERR (Proc 1 Bank 5)
  Status      : 0xbe2000000005110a
  Address     : 0x000000012a4f4000
  Misc.       : 0x000000d08001c086

This could be caused by several things

First step will be to check temperatures of the machine and clean if necessary

Look for bios update from manufacturers website if this is correct board most recent is sept 13 ROG - MAXIMUS V GENE - ASUS

Install latest 7 series chipset drivers found here updated jan 15 Latest Intel Chipset Device Software

After performing these steps I would try a stress test on the cpu to check for stability and to evaluate temps under load, be careful not to leave machine unattended during stress tests and if temperatures climb to high or quickly terminate the test

PvPTime · 01 Mar 2015

Just to inform. Doing fixing right now, CPU temperatures was very high, so I buy new cooling fan and testing from today. If, everything will be fixed or not. Will leave feedback after all.

PvPTime · 15 Mar 2015

After using new cooling fan for 10 days my computer shut it down once. As it's for sure temperature problem.
New cooling fan keeps CPU running at much better performance but still in soon future will buy new motherboard and after maybe new CPU until CPU temperature will be as it should.
So as problem is clear, closing my post.

Thank you for all help provided.

Regards
Karolis

**Pauly** · 15 Mar 2015

Glad to hear you got it sorted :)