Thanks for the update. This fix shall be incorporated into the next public release.
How exactly do you download the 11.4 version?
Collapse
X
-
-
Is there a way to find a specific log? I have tweaked and rebooted and rerun Memtest several times since then and am not sure what log it is. I will look though and try to find it. In theory I can go to Windows Props on that pic for the creation time and then go look at the logs for a matching time, or at least close...
Attached FilesLast edited by Roxxors; Oct-28-2025, 01:18 AM.Comment
-
This is as close as I can get, but it should be the correct log file. The pic I took had a creation date of 10/26 at 11:16pm, this log file has a creation date of 10-26 at 11:19pm. It has to be the right one I would think... Between my phone's time, the computers time, and how often Memtest does an fflush() of the write buffer, it should be the correct log file.Attached FilesComment
-
A question... I got the CL36 8000 Corsair Vengeance DDR5 ram, on the 1st pass of Memtest it runs 69c, normal, but with the heat buildup on the 2ed pass, it runs 77-80c which is a little high and seems to be causing a couple of thermal errors, specially on test 6... Do you know of a good heatsink for that ram that can drop that temp by 10c or so? I see several on the web, but none of them look very good...Comment
-
According to the logs, it seems you are using the public build but the tempreature fix was made after the release. Can you see if the debug build we sent previously has the temperature issue.
(the bug, that was fixed, can cause the temperature to be random, positive or negative on a few systems)Comment
-
Gonna test something. Ordered a new motherboard and CPU. Will assemble it Monday and move this motherboard and CPU to box #2 and run them side by side. They are the same motherboard and the same CPU and will use 2 of the same memory sticks out of the 4. We will see what that does... I will have more information then...
Comment
BTW, just tossing it out. I used to get this all the time if I tried to copy an unsigned var into a signed var (or the other way around) without the (cast) in front of it...
Comment