BSOD at random BCCode: 124

N0va

New member
Local time
5:47 PM
Messages
1
Hello Win7 friends,

I'm having this BSOD issue since a couple of weeks and its getting very frustrating, can't really tell what's the problem, I've uploaded the ZIP file from the Diagnostic Tool and here's some info the system display when it restarts:

"
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 5130

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

Files that help describe the problem:
C:\Windows\Minidump\111313-11887-01.dmp
C:\Users\Nova\AppData\Local\Temp\WER-25693-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
"


I've run the antivirus and got some infected files but the problem persists... If someone could help me I would really appreciate it as I'm totally lost on this subject.

Cheers
 

My Computer

Computer type
Laptop
Computer Manufacturer/Model Number
Dell
OS
Windows 7 Home Premium 64 bit
CPU
Intel Core i7-4700MQ @2.4GHz
Memory
16 GB
Graphics Card(s)
Nvidia GeForce GTX 770M
Hard Drives
250 SSD
700 HDD
Antivirus
Avast
Browser
Chrome
Welcome to 7F :).

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, although being a laptop not much you can do in terms of hardware unfortunately.

The errors are pretty much a consistent Generic L2 Cache error.
This is both a good thing and also not so much, the consistency of the errors (Processor 0 & 3/4 = Bank 6) usually means the fault is the CPU itself rather then being something else, which narrows things down
which is why I said it's both good and not.

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

Error         : [COLOR=Red][U]GCACHEL2_ERR_ERR (Proc 0 Bank 7)[/U][/COLOR]
  Status      : 0xae0000000040110a
  Address     : 0x00000000ffb07040
  Misc.       : 0x00000038a0000086

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

Error         : [COLOR=Red][U]GCACHEL2_ERR_ERR (Proc 0 Bank 6)[/U][/COLOR]
  Status      : 0xae0000000040110a
  Address     : 0x00000000ffb07080
  Misc.       : 0x00000078a0000086

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

Error         : [COLOR=Red][U]GCACHEL2_ERR_ERR (Proc 0 Bank 6)[/U][/COLOR]
  Status      : 0xae0000000040110a
  Address     : 0x00000000ffb07080
  Misc.       : 0x00000078a0000086

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

Error         : [U][COLOR=Red]GCACHEL2_ERR_ERR (Proc 0 Bank 6)[/COLOR][/U]
  Status      : 0xae0000000040110a
  Address     : 0x00000000ffb07080
  Misc.       : 0x00000078a0000086
Seeing how new the PC is I would get it RMA'd to be honest but there are a few things we can
test before going that route.


Test for thermals and stability:

  • Download HWinfo (64bit)and post a Screenshot of the sensors 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).

Testing the RAM:

Test and Diagnose RAM Issues 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.
:ar:When done with the testing procedure take a picture and upload it here.

Verify the following:

writhziden said:
you have an SSD, make sure the following are up to date:
  • SSD firmware
  • BIOS Version
  • Chipset Drivers
  • Hard disk controller drivers/SATA drivers
  • If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.
I found an available update to your BIOS, but it's best you use your service tag to find the matching link.

Keep us posted.
 

My Computer

Computer type
PC/Desktop
OS
Windows 10
CPU
Intel Core i5 3570K
Motherboard
Asus P8Z77V-PRO
Memory
16GB 1600Mhz G.Skill
Graphics Card(s)
Gigabyte GTX 970 G1-Gaming
PSU
Seasonic 1000W Platinum
Case
Fractal Design Define R4
Cooling
Noctua NH-D14
Back
Top