BSOD one to two times a day

Recently I've been getting a BSOD 1 to two times a day. It doesn't seem to be associated with anything particular. I can be playing a game or doing nothing and the computer blue screens and then reboots and runs fine until the next crash. Every time it reboots I get a "Windows has recovered from an unexpected crash" pop-up, but I'm not computer literate enough to know what to do with that info. I'm running Windows 7 Home Premium. If anyone could tell me what the info means then I would be very appreciative.

Edit: Here's a link to the DMP files my computer had.!108&authkey=!AH36hdtyesHZtLc

Problem signature:
  Problem Event Name: BlueScreen
  OS Version: 6.1.7601.
  Locale ID: 1033

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

Files that help describe the problem:
  C:\Users\Brandon Simmons\AppData\Local\Temp\WER-42884-0.sysdata.xml

Great, thanks!

All of the attached DMP files are of the WHEA_UNCORRECTABLE_ERROR (124) bugcheck.

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

BugCheck 124, {0, fffffa800abc2028, b6544000, 68000135}

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    @ fffffa800abc2138
Section       @ fffffa800abc22c0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : DCACHEL1_DRD_ERR (Proc 1 Bank 0)
  Status      : 0xb654400068000135
  Address     : 0x000000030ace0600
  Misc.       : 0x0000000000000000

In all of the dumps, it's a consistent DCACHEL1_DRD_ERR (always Proc 1 and Bank 0 as well).

DCACHEL1_DRD_ERR = Implies there was a Cache L1 Data Read error.

MODULE_NAME: hardware

IMAGE_NAME:  hardware



^^ Implies that this was NOT caused by any sort of software complication (drivers, etc) but hardware... processor cache also furthers our diagnosis in the CPU itself (L1 Cache) possibly being faulty.

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 -

2. Clear your CMOS (or load optimized BIOS defaults) to ensure there's no improper BIOS setting or to clear overclock settings -

3. Ensure your BIOS is up to date.

4. The only 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.



Debugger/Reverse Engineer.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.


Question Info

Last updated December 24, 2017 Views 377 Applies to: