[SOLVED] BSOD 124 Only While Idle? - Windows 7 x64

X

Xenoheart

New member
Joined
Jul 28, 2014
Posts
4
Hello,
I recently upgraded some hardware in my system, (motherboard, cpu, ram) and had to reinstall windows.
Since then I have been receiving BSOD error 124 only when Idle at the desktop. Once I went 5 hours playing games, then left idle for 40 minutes and crashed.
I have looked everywhere for help, but haven't found any.
I've ran memtest86+ for 8 passes and found nothing. I've ran chkdsk and found nothing. I've also ran intelburntest and found nothing.
I've raised CPU VCORE and VRING, thinking that lack of voltage was the issue, but to no avail.
I do not overclock, and I have also updated my motherboard bios which has not helped.
The crashes are sporadic, and I can go days or hours without getting them, or in once case (as mentioned) 40 minutes.
Attached are the dump files.

System Info:
Windows 7 Home Premium SP1 x64 Original Retail
Hard drive, psu, and gpu are around 2 years old with everything else brand new.
Windows 7 was installed a little over a week ago

i5-4690k
XFX Radeon HD 6850
Gigabyte Z97MX Gaming 5
750W PSU
 

Attachments

Hi,

All of the attached DMP files are 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 bug check (address of the WER structure) we get the following:

Code: 
BugCheck 124, {0, [COLOR=#ff0000]fffffa800a383028[/COLOR], bf800000, 200401}

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

[COLOR=#ff0000]Error         : Internal unclassified (Proc 3 Bank 1)[/COLOR]
  Status      : 0xbf80000000200401
  Address     : 0x00000000fee00040
  Misc.       : 0x0000000000000086

Internal unclassified, this implies there was a fatal micro-architectural error that's not publicly documented, therefore we cannot properly identity it.


Here's what I'd do:

1. Remove and replace Norton with Microsoft Security Essentials for temporary troubleshooting purposes:

 Norton removal - https://support.norton.com/sp/en/us/home/current/solutions/kb20080710133834EN_EndUserProfile_en_us;jsessionid=841A6D40BA6872C47697C6C6B19C8E11.4?entsrc=redirect_pubweb&pvid=f-home

MSE - Microsoft Security Essentials - Microsoft Windows

2. Uninstall all Gigabyte bloatware such as Easy Tune ASAP. Absolutely terrible software that's extremely outdated (nearly 8 years).


If the above fails, there is only so much you can do with a bug check 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 - Speccy - System Information - Free Download

2. Clear your CMOS (or load optimized BIOS defaults) to ensure there's no improper BIOS setting - How To Clear CMOS (Reset BIOS) [Easy, 10 to 15 Min]

3. Ensure your BIOS is up to date.

4. Run Memtest for NO LESS than ~8 passes (several hours):

Memtest86+:

Download Memtest86+ here:

Memtest86+ - Advanced Memory Diagnostic Tool

Which should I download?

You can either download the pre-compiled ISO that you would burn to a CD and then boot from the CD, or you can download the auto-installer for the USB key. What this will do is format your USB drive, make it a bootable device, and then install the necessary files. Both do the same job, it's just up to you which you choose, or which you have available (whether it's CD or USB).

Do note that some older generation motherboards do not support USB-based booting, therefore your only option is CD (or Floppy if you really wanted to).

How Memtest works:

Memtest86 writes a series of test patterns to most memory addresses, reads back the data written, and compares it for errors.

The default pass does 9 different tests, varying in access patterns and test data. A tenth test, bit fade, is selectable from the menu. It writes all memory with zeroes, then sleeps for 90 minutes before checking to see if bits have changed (perhaps because of refresh problems). This is repeated with all ones for a total time of 3 hours per pass.

Many chipsets can report RAM speeds and timings via SPD (Serial Presence Detect) or EPP (Enhanced Performance Profiles), and some even support changing the expected memory speed. If the expected memory speed is overclocked, Memtest86 can test that memory performance is error-free with these faster settings.

Some hardware is able to report the "PAT status" (PAT: enabled or PAT: disabled). This is a reference to Intel Performance acceleration technology; there may be BIOS settings which affect this aspect of memory timing.

This information, if available to the program, can be displayed via a menu option.

Any other questions, they can most likely be answered by reading this great guide here:

FAQ : please read before posting

4. If all of the above fail, the only left to do is replace your processor as it is faulty.

Regards,

Patrick
 
I uninstalled and replaced Norton, and removed ALL gigabyte software.
I will leave my computer on and idle tonight after I go to sleep and post results tomorrow.
Thanks for the quick response!
 
My pleasure, although I would restart after doing all of those uninstalls, etc, if you have not already before leaving it idle.

Regards,

Patrick
 
Going on 11 hours without a crash. Hopefully this fixed the problem, but I'm gonna leave it idle again tonight.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top