Corecycler picking / naming wrong core?

Open jdhau opened this issue 10 months ago • 3 comments

Hi,

Screenshot attached. CoreCycler says Core3, but HWINFO clearly shows that it's actually core 1 that's under load.

7800X3D, trying YCRUNCHER stability test. Version Alpha 0.10.0alpha5

Mar 01 '25 15:03 jdhau

Can you attach the log files for this run?

Mar 01 '25 17:03 sp00n

CoreCycler_2025-03-02_01-45-47_YCRUNCHER_04-P4P.log yCruncher_2025-03-02_01-45-47_mode_04-P4P.log

Mar 02 '25 00:03 jdhau

According to the log the affinity was at least set correctly to decimal 64 = logical CPU 6 = physical core 3.

Does this still happen? You can also check with the Task Manager which cores are being utilized, there might always be some stuff running on core 0 or 1, because that's the default for anything Windows does.

Mar 23 '25 17:03 sp00n