New PC Build BSOD Error WHEA_UNCORRECTABLE_ERROR

Lucid92 · 23 May 2015

I have recently built my first PC however it keeps randomly crashing

Who Crashed tells me:
On Sat 23/05/2015 15:39:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052315-23265-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5BCB65)
Bugcheck code: 0x124 (0x0, 0xFFFFE0008AC294B8, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

My temperatures/voltages/drivers are all fine. Is it likely that this is a hardware problem?

I have attached the file mentioned in the posting instructions.

Thanks!

essenbe · 23 May 2015

Hello, Lucid92 and welcome to the forums. you had 3 dump files, all dated today. If you are running any disk cleanup utilities, pleas do not use them until we get this figured out. They all delete dump files and error reports by default. The reason was as you said.

Code:

 
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 condition.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffe0009e33d788, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

An 0X124 means a hardware component has failed/is failing or it can mean that a bad driver is causing a component to act as though it is failing.

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

Let us know the results of the scan.

Lucid92 · 23 May 2015

Thanks very much for the response. I'll do the scans tomorrow and let you know what happens.

essenbe · 23 May 2015

No problem, just whenever you can, and let me know.

Lucid92 · 24 May 2015

I ran the scan twice this morning and on the third scan it said there were no integrity violations however it is still crashing. I have noticed though that today's crashes have not produced any minidump files and don't show up on WhoCrashed. Is it possible that this is a separate issue? Something to do with faulty hardware?

essenbe · 24 May 2015

yes, it is possible. Please make sure your system is configured for Small Memory Dumps.
Dump Files - Configure Windows to Create on BSOD

Layback Bear · 24 May 2015

You say your computer still crashes. Please explain what crash means.

Do you or do you not get a BSOD?

Lucid92 · 24 May 2015

Sorry, I have been a complete idiot. I am new to building PC's and thought BSOD was a term to describe a computer crashing not an acronym for Blue Screen Of Death as a quick Google search has revealed, please forgive me. No, I do not get a BSOD. My computer freezes for a few seconds, makes a buzzing noise through the speakers, and then reboots.

Also does this mean I am in the wrong section? And if so could you redirect me?

Thanks! (and sorry for being an idiot)

Layback Bear · 24 May 2015

No you are not a idiot. Easy mistake to make.
I was just trying to make sure that we understood your problem.

Just follow essenbe instructions when he post again.
I will go back to watching.

Lucid92 · 24 May 2015

Thanks very much for your help.

Also essenbe, I configured my system for small memory dumps but I still can't find any after crashing twice more since then. Should I run the DM Log collector again?