WHEA Uncorrectable Error Message

Hi Odysseus,

Welcome to the 10forums :)

Please run CPU-Z | Softwares | CPUID, open it and make screenshots of the following tabs

• CPU
• Mainboard
• Memory
• SPD*
• Graphics

*SPD shows the details of each stick, you can show the details by choosing different slots in the left upper corner.
Please make screenshots of each stick.
Please post each screenshot in your next reply/replies.


Please check Dell for BIOS updates.

Please reinstall or update the Broadcom Gigabit Controller driver, do you use the USB adapter or the Broadcom Gigabit Controller driver for internet?

Code:

Event[2629]:
  Log Name: System
  Source: b57nd60a
  Date: 2016-07-28T18:00:42.493
  Event ID: 4
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-GBEK53U
  Description: 
Broadcom NetXtreme 57xx Gigabit Controller: The network link is down.  Check to make sure the network cable is properly connected.

Some errors are 0x124 WHEA_UNCORRECTABLE_ERROR (Windows Hardware Error Architecture)
This means that there are problems with your hardware, but this error is also caused by overclocking, faulty drivers, overheating, improper seating or BIOS problems.

STOP 0x124 Troubleshooting

Read carefully before proceeding.

   Warning

If you're overclocking your system, revert back to stock clocks now.

   Note

Test the system once the overclock is removed before continuing with the steps outlined below.

Part One: CPU Stress Test
Part Two: MemTest86+ RAM Diagnostic
Part Three: Hard Drive Diagnostics
Part Four: GPU Stress Test

ONE

 CPU TEST

Run Prime95 and/or IntelBurnTest to stress test your CPU. Prime95 - Stress Test Your CPU - Windows 10 Forums & CPU - Stress Test Using IntelBurnTest - Windows 7 Help Forums

   Warning

Your CPU temperatures will rise quickly while under this stress test. Keep a keen eye on them and abort the test if overheating occurs.

Make a photo of the result and post it.

TWO

 RAM TEST

Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 10 Forums

   Note

MemTest86+ needs to be run for at least 8 complete passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

Make a photo of the result and post it please.

Addition:
If errors show up you can stop the test, remove all sticks but 1 and test this single stick in each slot for 8 passes or until errors show, switch sticks and repeat.
If errors show up and you see them a lot later, no problem, the errors don't affect the test.

THREE

 HDD TEST

Run SeaTools to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums
Run the long test.

   Note

Do not run SeaTools on an SSD as the results will be invalid.

Make a photo of the result and post it.

Run chkdsk using option TWO
with parameter /r
Disk Check - Windows 7 Help Forums
Upload the chkdsk log Chkdsk Log in Event Viewer - Read in Windows 10 - Windows 10 Forums

Run HDTune to

• scan for errors, no quick scan but full scan
• check the health,
• benchmark.

It may take some time, but please take the time you need to perform it properly.
When above is done please make screenshots of the following

• the error scan,
• the health,
• the benchmark incl. following
  
  • transfer rate,
  • access time,
  • burst rate,
  • cpu usage.

FOUR

 GPU TEST

Run Furmark to stress test your GPU. FurMark - GPU Stress Test - Windows 10 Forums

   Note

Run Furmark for around 30 minutes.

   Warning

Your GPU temperatures will rise quickly while Furmark is running. Keep a keen eye on them and abort the test if overheating occurs.

Make a photo of the result and post it.

In Furmark you can find a tool called 'GPU-Z' (if you want to install GPU-Z is up to you), when GPU-Z is open click on the 'Sensors' tab, on this tab you can monitor

• the frequency of the GPU,
• the GPU memory clock,
• the temperature,
• the power,
• the load on the GPU,
• Etc.

I would like you to make a screenshot of GPU-Z after you have either cancelled Furmark for any reason or Furmark is finished, post this screenshot in your next reply with the result of Furmark.

Please fill in your system specs

Please follow this tutorial and download the tool. The tool will give you detailed information about your system specs, please fill in your system specs more completely including PSU, cooling and other used stuff like mouse, keyboard, monitor, case, etc.
The PSU, cooling and other stuff are NOT mentioned in the tool.

How to fill in your system specs:

Hello Axe, Thanks for the quick reply and guidance. We are leaving our present location today and time for me to progress this is limited. I will give it all the time I can get to do so, but before I start, can I clarify a couple of things and mention something that had slipped from consciousness? When I was removing the HDD, I accidentally broke off one of the leads to the Wireless Card (delicate little things aren't they?), hence the wireless USB device. Could this be the source of the issue? If this sounds a likely suspect, I can try a different USB WiFi device when I return home.

Also following the initial part of your email, there are enumerated items. Shall I provide all of them, or start with the first part of your post?

Edit: Also when the WHEA message comes up, the message starts with a bit that says information is being collected (presumably to go to MS). Is that info recorded in a log on my computer, and if so would it be in one of the logs already submitted? Does anyone know what information is recorded?

To clarify my post, a 0x124 crash is as mentioned a hardware error. The CPU has detected a fatal problem with either of the components and calls the bugcheck functions what shows the BSOD, all we can do is find out why a BSOD was called, but not what caused it that a BSOD was called. Normally it is both, but a 0x124 usually doesn't provide enough information to point to a specific cause, based on the information we know, that it is a hardware error, we provide information for testing the hardware so we may get a better lead in what direction to go to, that is why my posts with a 0x124 are often a bit large.

Could this be the source of the issue?

I cannot say with any certainty, all I could find out is what the CPU reported for problem but it does not mean enough to point to something specificly.

Also when the WHEA message comes up, the message starts with a bit that says information is being collected (presumably to go to MS). Is that info recorded in a log on my computer, and if so would it be in one of the logs already submitted? Does anyone know what information is recorded?

That is shown with every BSOD :)
MS doesn't collect information to send to themself, if they did I'm fairly sure they would have problems with many countries regarding collecting data while there is never asked for permission to do this.
What happens is that all the information the RAM holds is send to the pagefile. After the system restarts the pagefile is called so this information can be dumped into a file (MEMORY.dmp, located in %systemroot%), which is why after a BSOD the reboot may take a bit longer than usual.
That is what MS means with 'collecting information'