Share via

BSOD one to two times a day

Anonymous
2013-09-02T07:00:55+00:00

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.

https://skydrive.live.com/redir?resid=8906139F29F6F934!108&authkey=!AH36hdtyesHZtLc

Problem signature:

Problem Event Name: BlueScreen

OS Version: 6.1.7601.2.1.0.768.3

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:\Windows\Minidump\090113-18891-01.dmp

C:\Users\Brandon Simmons\AppData\Local\Temp\WER-42884-0.sysdata.xml

Windows for home | Previous Windows versions | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

Answer accepted by question author

  1. Anonymous
    2013-09-02T07:43:58+00:00

    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

    FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHEBUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE

    ^^ 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 - http://www.piriform.com/speccy

    2. Clear your CMOS (or load optimized BIOS defaults) to ensure there's no improper BIOS setting or to clear overclock settings - http://pcsupport.about.com/od/fixtheproblem/tp/clearcmos.htm

    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.

    Regards,

    Patrick

    Was this answer helpful?

    0 comments

13 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2013-09-02T08:53:49+00:00

    It could be possible, good call and thanks for bringing it up. Asus' EPU is essentially power saving. It's a lot more diverse and complicated than that, but at its most basic level, power saving is exactly what it does.

    I am assuming you have the EPU switch on your Asus motherboard? If you switch it off from EPU, it should disable. Don't switch it to TPU as that's Asus' 'factory overclocking' method.... which needless to say is very poor.

    If you have no switch on the board, just navigate to the BIOS and it'll be in there, most likely labeled 'EPU Power Saving Mode'. Set it to DISABLED.

    Regards,

    Patrick

    Was this answer helpful?

    0 comments
  2. Anonymous
    2013-09-02T08:35:33+00:00

    Would something called EPU that was on the computer when I first started it up possibly be like the Asus' AI Suite you mentioned? Not sure if it's the same thing or even similar.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2013-09-02T07:33:34+00:00

    Thanks for letting me know to do so, I added a link to the files in the original post.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2013-09-02T07:06:14+00:00

    Hi,

    In order to assist you, we will need the DMP files to analyze what exactly occurred at the time of the crash, etc.

    If you don't know where DMP files are located, here's how to get to them:

     1.    Navigate to the %systemroot%\Minidump folder.

     2.    Copy any and all DMP files in the Minidump folder to your Desktop and then zip up these files.

     3.    Upload the zip containing the DMP files to Skydrive or a hosting site of your choice and paste in your reply.

    If you are going to use Skydrive but don't know how to upload to it, please visit the following:

    http://www.wikihow.com/Use-SkyDrive

    Please note that any "cleaner" programs such as TuneUp Utilities, CCleaner, etc, by default will delete DMP files upon use.

    If your computer is not generating DMP files, please do the following:

    1. Start > type %systemroot% which should show the Windows folder, click on it. Once inside that folder, ensure there is a Minidump folder created. If not, CTRL-SHIFT-N to make a New Folder and name it Minidump.
    2. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Performance > Settings > Advanced > Ensure there's a check-mark for 'Automatically manage paging file size for all drives'.
    3. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Startup and Recovery > Settings > System Failure > ensure there is a check mark next to 'Write an event to the system log' > Ensure 'Automatically restart' is un-checked.

    Ensure Small Memory Dump is selected and ensure the path is %systemroot%\Minidump.

    1. Double check that the WERS is ENABLED:

    Start > Search > type services.msc > Under the name tab, find Windows Error Reporting Service > If the status of the service is not Started then right click it and select Start. Also ensure that under Startup Type it is set to Automatic rather than Manual. You can do this by right clicking it, selecting properties, and under General selecting startup type to 'Automatic', and then click Apply.

    If you cannot get into normal mode to do any of this, please do this via Safe Mode.

    Regards,

    Patrick

    Was this answer helpful?

    0 comments