WHEA_UNCORRECTABLE_ERROR while playing games

Anonymous
2014-03-21T00:28:25+00:00

I recently installed Windows 8.1 on my PC.  I've had nine BSOD's so far, all while playing World of Tanks (that's the only game I've been playing).   The blue screen says WHEA_UNCORRECTABLE_ERROR.  I've tried troubleshooting myself, but I can't figure out what the problem is.  What should I do?

Windows for home | Previous Windows versions | Windows update

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 No comments
{count} votes
Answer accepted by question author
  1. Anonymous
    2014-03-21T02:34:19+00:00

    Thanks very much for the Kernel!

    It's of the WHEA_UNCORRECTABLE_ERROR (124) bug check.

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

    If we run an !errrec on the 2nd parameter of the bugcheck (address of the WER structure) we get the following:

    ===============================================================================

    Section 0     : Processor Generic


    Descriptor    @ ffffe000043df0a8

    Section       @ ffffe000043df180

    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         : 0

    CPU Version   : 0x00000000000306c3

    Processor ID  : 0x0000000000000002

    ^^ Cache Error, let's go further...

    ===============================================================================

    Section 2     : x86/x64 MCA


    Descriptor    @ ffffe000043df138

    Section       @ ffffe000043df2c0

    Offset        : 664

    Length        : 264

    Flags         : 0x00000000

    Severity      : Fatal

    Error         : DCACHEL0_WR_ERR (Proc 1 Bank 1)

      Status      : 0xbf80000000000124

      Address     : 0x000000011a11c900

      Misc.       : 0x0000000000000086

    ^^ The specific type of error is DCACHEL0_WR_ERR. This implies a L0 Cache Write error.

    ---------------------

    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 - 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

    0 comments No comments

6 additional answers

Sort by: Most helpful
  1. Anonymous
    2014-03-23T15:42:40+00:00

    Clearing the CMOS fixed the problem.  Thanks for the help.

    0 comments No comments
  2. Anonymous
    2014-03-23T21:37:38+00:00

    My pleasure! Likely an improper BIOS setting, glad to hear.

    Regards,

    Patrick

    0 comments No comments
  3. Anonymous
    2014-03-21T00:35:54+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 Onedrive or a hosting site of your choice and paste in your reply. Prefered sites: Onedrive, Mediafire, Dropbox, etc. Nothing with wait-timers.

    4 (optional): The type of .DMP files located in the Minidump folder are known as Small Memory Dumps. In %systemroot% there will be what is known as a Kernel-Dump (if your system is set to generate). It is labeled MEMORY.DMP. The difference between Small Memory Dumps and Kernel-Dumps in the simplest definition is a Kernel-Dump contains much more information at the time of the crash, therefore allowing further debugging of your issue. If your upload speed permits it, and you aren't going against any strict bandwidth and/or usage caps, etc, the Kernel-Dump is the best choice. Do note that Kernel-Dumps are much larger in size due to containing much more info, which is why I mentioned upload speed, etc.

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

    Upload photos and files to Onedrive.

    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 Small Memory Dump is selected and ensure the path is %systemroot%\Minidump.

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

    0 comments No comments