Crashes During Gaming on Newly Built PC

[CoffeeBean50]

I built my new gaming PC about 2-3 weeks ago and got a WHEA error the next day while playing Battlefield 4. I played each day the following 10 days or so, and both the pc and game ran perfectly. However, I received the WHEA Uncorrectable error two times recently while gaming. I have had no issues doing anything other than playing Battlefield, and crashed about 4 times in approximately 50 hours of playing. Does anyone have advice on how I should begin to resolve this issue or what may be causing it? Please let me know if you need more information.

Specs:

Asus Z 97-A Motherboard
Intel Core I7 4790k 4.0 ghz(stock)
EVGA 780ti Superclocked
Corsair 1866 MHz 16 GB
Asus 128 GB SSD
WD 1 TB HDD
Corsair 750 Watt Gold Certified PSU

 

[Ketchup]

What version of Windows?

Do you ever see a blue screen, or does it just crash to desktop?

Try the steps in the first post of this thread and see what you find:
http://www.overclock.net/t/1317335/whea-error-alert-guide-or-how-i-got-out-of-wheaville

 

[CoffeeBean50]

What version of Windows?

Do you ever see a blue screen, or does it just crash to desktop?

Try the steps in the first post of this thread and see what you find:
http://www.overclock.net/t/1317335/whea-error-alert-guide-or-how-i-got-out-of-wheaville

Thank you for responding. I was actually unable to find the WHEA errors in the log the way the link described, but I am certain I got them. However, under administrative events I found "fatal error 43" and a warning that read, "The driver \DriverWUDFRd failed to load for the device ACPI\PNPOAOA\2&daba3ff&". Can these be related to my problem?

By the way, I am on windows 8, and I did get a blue screen when the error appeared.

 

[Batmeat]

Your specs look good. Your issue sounds like driver problems. Almost all hardware issues ,except your video card, will crash your entire system. Video card and driver issues generally crash to the desktop. Infrequently your vid card will crash the entire system.

 

[crashtech]

Did you do a fresh install of Windows when you built your machine?

Have you run bootable Memtest overnight to see if your memory is OK?

 

[Ketchup]

Usually an app crash creates a minidump. Download and run the WhoCrashed app from this page:

http://www.resplendence.com/downloads

Let's see if it can direct us to the application/driver causing the issue.

 

[CoffeeBean50]

Usually an app crash creates a minidump. Download and run the WhoCrashed app from this page:

http://www.resplendence.com/downloads

Let's see if it can direct us to the application/driver causing the issue.

Here is the report I got...

On Sun 8/10/2014 8:07:35 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081014-10906-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]hal.dll[/FONT] (hal+0x37203)
Bugcheck code: 0x124 (0x0, 0xFFFFE001F168B028, 0xBF800000, 0x124)
Error: [FONT=Segoe UI, Arial]WHEA_UNCORRECTABLE_ERROR[/FONT]
file path: C:\Windows\system32\hal.dll
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

Looks as if its either a faulty piece of hardware or an unidentified driver issue.

 

[Ketchup]

Put the computer under load and tell us what temps your cpu cores and gpu core are maxing out at.

If you can attach a pic from CPUID HWMonitor, that might be the easiest.

Have you adjusted any voltages on your build?

Is ANYTHING overclocked or running tight timings (RAM)?

How many sticks of RAM are you running?

 

[Smoove910]

I've read where people have the same problem and they go into their BIOS and disable 'Intel C-State' to resolve the problem. Give that a try and see if it helps.