New PC Build BSOD Error WHEA_UNCORRECTABLE_ERROR

[Lucid92]

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]

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.

[COLOR=black][COLOR=red]WHEA_UNCORRECTABLE_ERROR (124)[/COLOR]
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.[/COLOR]

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]

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

 

[essenbe]

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

 

[Lucid92]

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]

yes, it is possible. Please make sure your system is configured for Small Memory Dumps.
http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html

 

[Layback Bear]

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

Do you or do you not get a BSOD?

 

[Lucid92]

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]

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]

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?

 

[essenbe]

Yes, Please do and I will take a look. Your System Specs say you are running Windows 8 also. We can deal with that here, but we usually deal with Windows 7. What you were getting in your 3 dump files for 5/23 were all 0X124 errors. That is a generic code for a hardware error. But it can also be caused by a bad driver causing some component to act as though it is failing. What I would like to do is test for bad drivers first. It will be simple, but if it goes wrong it can require a clean install of the operating system. We make every effort so that does not happen, and it has never happened to me. But, the possibility still exists. If you are willing, this is what I would like to do. Be sure to create a Restore Point before enabling Driver verifier. The link to how to do that is below.

   Warning

Be sure to create a System Restore point before proceeding further http://www.sevenforums.com/tutorials/697-system-restore-point-create.html

Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

What is Driver Verifier:
It puts stress on the drivers, and tries to make the faulty driver crash the computer. It is designed this way, to attempt to trap the offending driver.

What you will notice:
It will tend to make the computer rather slow and sluggish because the drivers are being stressed.

   Warning

Before enabling DV, make sure you have created a system restore point before enabling Driver Verifier. make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any. Also, do not be upset if you get a BSOD. Driver Verifier is designed to make your computer BSOD if there is a bad driver, so hopefully we will catch the bad driver in the dump file.

If you have any questions, please let feel free to ask.

 

[Lucid92]

Thanks so much for the help! I'll do it now and get back to you either in 24 hours or when I crash.

 

[Lucid92]

Deleted

 

[Lucid92]

Is there anyway to check if the device verifier is running whilst I use my PC.

Also, my screen just went black and I received the following notification from Host Process for Windows Tasks:

Display driver AMD driver has stopped responding and has recovered

 

[essenbe]

Your graphics driver crashed, just reboot and it will be back. You should notice it being a little slow and sluggish, when Verifier is running. If you followed the instructions in that link, it is working. I hope you sorted Drivers by provider and only enabled drivers NOT provided by Microsoft. Don't enable DV to run on any Microsoft Drivers.

 

[Lucid92]

Hi again. I have crashed quite a few times since last night however I still can't find any crash dumps.

 

[essenbe]

Lucid92, now again, when you say crash do you mean BSOD or do you mean freezing? have you changed you page file amount or location? Try to make yours look like this

View attachment 360304

Then go to C:/Windows and make sure you have a folder named Minidump. If you don't, create one there named Minidump. Also, how much free space do you have on your Operating System Hard Drive?

Follow these steps:

1. Configure Windows to create minidumps:
Dump Files - Configure Windows to Create on BSOD

2. Set the paging file on C: to be the same size as the physically installed RAM:
Virtual Memory Paging File - Change

3. Set the Windows Error Reporting service to MANUAL:
Services - Start or Disable

This image has been resized. Click this bar to view the full image. The original image is sized 715x414 and weights 83KB.

4. Test to see that dump files are created:
- Open Windows Task Manager
- Navigate to the Processes tab
- Right-click on explorer.exe, and click Create Dump File

This image has been resized. Click this bar to view the full image. The original image is sized 800x501 and weights 244KB.

- Note the location of the saved file

- Check that location and confirm that explorer.dmp exists

This image has been resized. Click this bar to view the full image. The original image is sized 767x406 and weights 56KB.

 

[Lucid92]

Yes that seems to be working, however in order to find it I had to type %appdata% into my search tool, I couldn't find the AppData folder in my User folder.

I don't get any BSODs. My computer freezez for a few seconds, makes a buzzing noise through the speakers, then reboots.

 

[Lucid92]

I went onto device verifier manager and found that dump_diskdump.sys was "never loaded". Should I continue to run DV?

 

[essenbe]

The AppData Folder is a hidden folder. You have to change the options to view hidden files or search for it like you did. It is hidden for a reason. Don't make changes to it. If you had a BSOD, you could most likely find it now, couldn't you?

Do you have a Minidump folder in C:/Windows? %SystemRoot%\Minidump