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
Attachment 161337
Last edited by diznanl; 30 Oct 2017 at 22:07.
Prime95 Results:
Temps got up to 100 on the first core so I halted it.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.
Attachment 161341
Open the case > clean fans > leave case open > repeat prime95 and abort testing as needed again.
It appears to be fixed, but took significantly longer (perhaps due to write-cache being off?)
Attachment 161537
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:
Attachment 161545
I cleaned the fans with compressed air and am still gett 100 degree temps. I guess I may need to re-seat the CPU.
Attachment 161548Code:[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.
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)
Last edited by diznanl; 31 Oct 2017 at 23:28.
Quote