Windows 10: WHEA_UNCORRECTABLE_ERROR - Random reboots and 0x124 error

What do you mean, "please use HD Sentinel as before to see if there are BSOD." ... do another surface scan?

Here are the last BSOD results:
Attachment 161328

 

Is it safe to run the Prime95 testing even when CPU is at 95 degrees? That's what they jump to and hover around the entire time.

FuMark GPU results will be posted in about an hour.

 

Can you re-post the information on Prime95 as you remember it.
If you can run it for a few minutes and abort if it goes over 95 that will work.
Do not let it remain hot but a temporary rise is sufficient to document it in the thread.
This way there is some verifying information in the thread.

in the earlier post you were able to trigger BSOD using HD Sentinel. Please see if that has been fixed.
There were 14 BSOD on 10/26 and all were WHEA 0x124 bugchecks.

 

FurMark results below:
Avg temp: 64 degrees
Max temp: 65 degrees
No artifacts

 

Prime95 Results:

Code: [Main thread Oct 30 21:50] Mersenne number primality test program version 28.10 [Main thread Oct 30 21:50] Optimizing for CPU architecture: Unknown Intel, L2 cache size: 256 KB, L3 cache size: 8 MB [Main thread Oct 30 21:50] Logical CPUs 1,2 form one physical CPU. [Main thread Oct 30 21:50] Logical CPUs 3,4 form one physical CPU. [Main thread Oct 30 21:50] Logical CPUs 5,6 form one physical CPU. [Main thread Oct 30 21:50] Logical CPUs 7,8 form one physical CPU. [Main thread Oct 30 21:50] Starting workers. [Main thread Oct 30 21:52] Stopping all worker threads. [Main thread Oct 30 21:52] Execution halted.[/quote] Temps got up to 100 on the first core so I halted it.

 

Open the case > clean fans > leave case open > repeat prime95 and abort testing as needed again.

 

Done... will be running another test shortly.

Should I try re-seating the CPU cooler on the CPU (cleaning / re-apply arctic thermal paste?)

 

It appears to be fixed, but took significantly longer (perhaps due to write-cache being off?)

 

There were testing results indicating problems with the CPU and drive that need further evaluation.
So with another day or two the DM log collector event log can be reevaluated with the cache available.
Perform any steps to reduce the heat or improve the cooling of the CPU. And then repeat testing and post images into the thread.
Please update the status of the yellow triangles in device manager.

 

After running Memtest86+ 5.01 version on my "good" RAM module, I decided to test with the "bad" stick that the other MemTest86+ recorded. I ran it all night and it came up with no errors. I decided to add it back to my machine:

 

I cleaned the fans with compressed air and am still gett 100 degree temps. I guess I may need to re-seat the CPU.

Code: [Main thread Oct 31 20:17] Mersenne number primality test program version 29.3 [Main thread Oct 31 20:17] Optimizing for CPU architecture: Core i3/i5/i7, L2 cache size: 256 KB, L3 cache size: 8 MB [Main thread Oct 31 20:17] Starting workers. [Main thread Oct 31 20:32] Stopping all worker threads. [Main thread Oct 31 20:32] Execution halted.[/quote]

 

The triangles won't go away... I haven't been able to figure out how to keep them from coming back after uninstalling.

On a side note, I'm also not able to access my start menu after the latest Fall Creator's update (installed 10/26), making it difficult to access my Device Manager ... Going to be using devmgmt.msc via command line to see if that helps.

*EDIT*

I found out what device was creating the yellow triangles, but still don't know why they are showing. I have a mouse/keyboard combo that I haven't had connected to the computer for ages; I have been using it on my PS4. I decided to test plugging this in and the yellow triangles immediately went away.

This said, I don't know why they come back when they dongle is disconnected. I've just disconnected it and will restart to see if they remain.

For reference, the mouse/keyboard combo model number is IOGear GKM561R. Will update this thread after confirming whether yellow triangles still remain.

**EDIT 2**
They are still there after the device is removed and after a reboot. I will attempt rebooting with the device plugged in and attempt to update drivers (though non exist from IOGear)

 

Click Start, and then click Run.
In the Open box, type devmgmt.msc, and then click OK.
Device Manager opens.
Expand each listing with a yellow triangle.
Right-click the listing with yellow triangles, and then click Uninstall to remove it.
Restart the computer.
After the computer starts, Windows will automatically scan for hardware changes and reinstall the needed drivers.

If the above fails try the same steps again but this time instead of uninstall click update > browse my computer for driver software > choose the last known working driver for the device.

If the above fail post the driver details into the thread and see the prior post with the URLs for fixing the device manager drivers.



These are some troubleshooting links for the start menu:

[How To] Re-register Start Menu In Windows 10: [How To] Re-register Start Menu In Windows 10


Troubleshoot problems opening the Start menu or Cortana: https://support.microsoft.com/en-us/...t-menu-cortana


http://www.thewindowsclub.com/start-...pen-windows-10

 

Thanks, I've tried all of this ... changing drivers (to other compatible ones), uninstalling both drivers, scanning for hardware changes.

I've also tried the Powershell tricks to re-download Windows Apps and ... nothing.

 

Post the driver info displayed in device manager along with an image for each yellow triangle into the thread.

Please post an updated zip:
BSOD - Posting Instructions - Windows 10 Forums