Solved BSOD - Bug Check 124 WHEA_UNRECOVERABLE_ERROR new system

[fullshred]

Hi everyone, I've just assembled a new PC and am getting frequent BSOD's with error code 124 (unrecoverable hardware error).

** edit: mini-dumps and logs are attached **

On day 1, the blue screens were about an hour apart... now (day two), it blue screens within 30 seconds of Windows loading.

It doesn't blue screen in safe mode.

The motherboard is an Asrock Fatal!ty Killer Z97X. I've downloaded and installed the latest drivers. I didn't install esoteric things like Intel Rapid Start Driver or Intel Management Engine Driver.

CPU is an i7-4790K running at stock clock speed and voltages.

CPU cooler is a Noctua NH-D15.

Power supply is a Cooler Master V850.

Memory is 16GB (2x8GB) RipjawsX DDR3 2400 (PC3 19200) (F3-2400C11D-16GXM)

OS is Windows 7 with Windows Update turned on and all updates installed.

I removed the video card (Gigabyte R2 290X) and am using the onboard graphics for now. I uninstalled the Gigabyte software and drivers.

I picked six mini dumps at random, and consistently the error is:

FAILURE_BUCKET_ID:* X64_0x124_GenuineIntel_PROCESSOR_CACHE

The specific errors were:

Error******** : DCACHEL0_EVICT_ERR (Proc 6 Bank 1)
Error******** : DCACHEL0_EVICT_ERR (Proc 6 Bank 1)
Error******** : DCACHEL0_EVICT_ERR (Proc 6 Bank 1)
Error******** : DCACHEL0_EVICT_ERR (Proc 6 Bank 1)
Error******** : DCACHEL0_EVICT_ERR (Proc 7 Bank 1)
Error******** : DCACHEL0_SNOOP_ERR (Proc 7 Bank 1)

I stripped the system to bare bones: mainboard, 16GB RAM, CPU + cooler, one drive (OCZ Vertex SSD), 850W power supply, PS2 keyboard, USB wireless mouse.

Is it a bad CPU? Or could there be something else wrong?

 

[essenbe]

Fullshred, Please upload the BSOD Posting Instructions http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html. Upload the files here, this will tell you how. http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

Please go to your Motherboard's web site and update your drivers. Make sure this is your Motherboard and you can get drivers here, ASRock > Fatal1ty Z97X Killer. The DVD Drivers are always pretty old. They were the current ones when that Motherboard was first made. Make sure you have the Intel Graphics driver loaded.

Boot into safe mode with command prompt, and open an elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.

Also, boot into BIOS and look at what your sata controller is set to (IDE, AHCI or Raid) unless you changed it, Asrock usually sets it to IDE by default. Set optimized defaults, make sure your ram is set to manufacturer's specs (timings, frequency and Dram Voltage), set your sata controller to whatever it is right now, or you won't boot, set your boot order save and exit. Don't set anything else.

You may try to go into bios and just idle there for a while to see if you BSOD in bios or not.
Also, please add your PSU manufacturer and model and your CPU cooler to your system specs. We often need to look up a component and need that info to do so. By putting everything in your system specs, they will be available on every post.

Also, please upload the BSOD posting instructions here. I hope you understand, but we work many of these cases and I have to download the files to my computer if they are posted somewhere else. I can just open them from here. Also, when you built the computer, you did do a clean install didn't you?

 

[fullshred]

Thanks for your suggestions. I've attached the output of DM Log Collector to my original post.

I ran sfc /scannow - no errors

SATA controller is set to AHCI mode.

I updated the BIOS to the latest (version 2.10)

I downloaded the latest drivers, and installed these ones:

ASMedia USB 3 drivers
Atheros Lan driver
INF driver
Intel USB driver
Realtek highd ef audio driver
VGA driver

I ignored these:

AppCharger
Intel Management Engine driver
Intel Rapid Start driver
Intel Rapid Storage Technology driver
Intel Smart Connect driver
SATA floppy image

CPU cooler is a Noctua NH-D15.

Power supply is a Cooler Master V850. I haven't seen the temperature go above 40C (104F).

I'm about to reboot and check the memory timings.

 

[essenbe]

Thanks, I appreciate it. I'll take a look at the dump files. If you don't mind, at the bottom left of you last post please click 'My System Specs and click the update system Specs and put the PSU and Cooler in and be sure to click save at the bottom of the page. Let me know if you notice any improvement in your computer after updating the drivers and setting BIOS to optimized defaults. Also, after you idle for a while in BIOS, let me know if you get a BSOD.

 

[essenbe]

What I am seeing is a General Hardware error. It can be caused by failed/failing Hardware or a bad driver which causes hardware to act in unexpected ways.

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa800de6a028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000bb800000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000174, Low order 32-bits of the MCi_STATUS value.

Please go to device manager and see if any devices have a yellow triangle next to them.

 

[essenbe]

fullshred, Please make sure your SSD Firmware is up to date. Also, Please run either Seatools for DOS on your Mechanical Hard drives (http://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html#Part3) or the WD tool, Data Lifeguard for DOS (WD Support / Downloads / SATA & SAS / WD Black). Whichever one you use, please run the Short and the Long tests.

I am seeing a lot of storage related errors, but no blame on them. Your Symantec Endpoint Protection is a well know cause of BSODs, I would remove it and then use the Norton Removal tool, https://support.norton.com/sp/en/us/home/current/solutions/kb20080710133834EN_EndUserProfile_en_us and replace it with Microsoft Security Essentials (Microsoft Security Essentials - Microsoft Windows).

If you have Dameon Tools or Alcohol120% or any SPTD Pass through, please uninstall any of them. This will help.

Daemon Tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known cause of BSOD's.

1. Uninstall Daemon Tools.
2. Download the SPTD standalone installer and follow these steps:
- Double click the executable to open it
- Click the button shown below



If the button it is grayed out, as shown in the image, there is no more SPTD installation on your system, and you can just close the window.

 

[essenbe]

Whether you have any of the above programs installed or not, I would suggest you run the Standalone SPDT utility. Also, please run these online scans

Scan with Kaspersky TDSSKiller:
http://support.kaspersky.com/viruses/disinfection/5350#block1
Anti-rootkit utility TDSSKiller
ESET online scanner:
Free Virus Scan | Online Virus Scanner from ESET
Free Online Virus Scanner | ESET

 

[Layback Bear]

Steve could you point me to this? (Standalone SPDT utility)

 

[essenbe]

Steve could you point me to this? (Standalone SPDT utility)

Disk-Tools.com, it says it is an installer, but when you run it, if it finds a SPDT, you have the option to uninstall it, or you could install it if you really wanted to. It says it is an Installer, but if you have it installed, the option to uninstall it is there. If you don't have it, the uninstall button is grayed out, but you could then install it, if you were so inclined, which I am not.

 

[Layback Bear]

Thanks Steve!

 

[fullshred]

After looking at the dump files, I concluded it was a bad CPU and exchanged it for another one. Problem solved! Looks like it was faulty.

 

[essenbe]

Thanks for letting us know.