BSOD During Battlefield 4 Beta, Error 0x00000124

AngelDeath82 · 07 Oct 2013

I've been playing the Battlefield 4 Beta since October 1, but this is the first time I've had a BSOD while playing (though I've had previous crash-to-desktops from the beta).

YoYo155 · 07 Oct 2013

Welcome to SF :) .
I wouldn't worry too much about one bugcheck only when they are becoming more often
is when we can consider we have a problem on out hands.

Code:

BugCheck 124, {0, fffffa8006e67028, be000000, 100110a}


Error         : GCACHEL2_ERR_ERR (Proc 1 Bank 8)
Error Type    : Cache error
Operation     : Generic

Your PC tends to overheat quite often:

Code:

Event[21471]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Power
  Date: 2013-10-06T23:04:05.788
  Event ID: 89
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: Artemis
  Description: 
ACPI thermal zone ACPI\ThermalZone\TZ00 has been enumerated.             
_PSV = 0K             
_TC1 = 0             
_TC2 = 0             
_TSP = 0ms             
_AC0 = 353K             
_AC1 = 328K             
_AC2 = 273K             
_AC3 = 273K             
_AC4 = 273K             
_AC5 = 0K             
_AC6 = 0K             
_AC7 = 0K             
_AC8 = 0K             
_AC9 = 0K             
_CRT = 378K             
_HOT = 0K             
_PSL - see event data.

Event[21472]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Power
  Date: 2013-10-06T23:04:05.788
  Event ID: 89
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: Artemis
  Description: 
ACPI thermal zone ACPI\ThermalZone\TZ01 has been enumerated.             
_PSV = 381K             
_TC1 = 1             
_TC2 = 5             
_TSP = 1000ms             
_AC0 = 0K             
_AC1 = 0K             
_AC2 = 0K             
_AC3 = 0K             
_AC4 = 0K             
_AC5 = 0K             
_AC6 = 0K             
_AC7 = 0K             
_AC8 = 0K             
_AC9 = 0K             
_CRT = 378K             
_HOT = 0K             
_PSL - see event data.

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.

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.

Test for thermals and stability:

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.
- Before running Prime95 make sure to enable Round-off checking (see 1st post under the tutorial).

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.

Note

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

Good places to read more: