F5F Stay Refreshed Hardware Desktop The asterisk indicates a warning or potential issue with the result.

The asterisk indicates a warning or potential issue with the result.

The asterisk indicates a warning or potential issue with the result.

A
ApeEmperor
Member
Find
56
11-29-2019, 03:15 PM
#1
I can't find an answer anywhere... Also 8774(*) seems freaking low for 3600 multi core? Actually lower than 1700x... (although tbf i have steam and rainmeter running) PS: single core result doesn't have a "*"... what gives? At least I beat the pesky 1700x (1170)! PS: ok, turning off steam / rainmeter let me beat the 1700x, but it still says "*" so apparently something wrong?
Reply
Reply
A
ApeEmperor
11-29-2019, 03:15 PM #1

I can't find an answer anywhere... Also 8774(*) seems freaking low for 3600 multi core? Actually lower than 1700x... (although tbf i have steam and rainmeter running) PS: single core result doesn't have a "*"... what gives? At least I beat the pesky 1700x (1170)! PS: ok, turning off steam / rainmeter let me beat the 1700x, but it still says "*" so apparently something wrong?

Reply
Reply
T
Tuetme
Senior Member
Find
418
11-29-2019, 05:16 PM
#2
The score is normal. 3600x typically exceeds 9k. I’m 90% confident the asterisk indicates a minimum test duration is off. You can test enabling and disabling it to see if it removes the asterisk.
Reply
Reply
T
Tuetme
11-29-2019, 05:16 PM #2

The score is normal. 3600x typically exceeds 9k. I’m 90% confident the asterisk indicates a minimum test duration is off. You can test enabling and disabling it to see if it removes the asterisk.

Reply
Reply
X
xSudden
Member
Find
228
11-29-2019, 11:20 PM
#3
My prediction is accurate based on the results. The test was conducted by @Mark Kaine without a required minimum runtime in multi-core mode, and the score displayed an asterisk. After adjusting the test to enforce a 10-minute minimum duration (Test Throttling), the score changed and no asterisk appeared, confirming the theory. Updated April 21, 2021 by The_russian
Reply
Reply
X
xSudden
11-29-2019, 11:20 PM #3

My prediction is accurate based on the results. The test was conducted by @Mark Kaine without a required minimum runtime in multi-core mode, and the score displayed an asterisk. After adjusting the test to enforce a 10-minute minimum duration (Test Throttling), the score changed and no asterisk appeared, confirming the theory. Updated April 21, 2021 by The_russian

Reply
Reply
X
xFyUZx
Member
Find
158
12-02-2019, 12:13 AM
#4
Sure, disabling most background features (though GFE and Corsair links are a bit tricky) helped me finish the 1700x. Maybe I'll give it another shot. The odd part is it doesn't show the * symbol on single-core systems, just multi-core—still to be seen.
Reply
Reply
X
xFyUZx
12-02-2019, 12:13 AM #4

Sure, disabling most background features (though GFE and Corsair links are a bit tricky) helped me finish the 1700x. Maybe I'll give it another shot. The odd part is it doesn't show the * symbol on single-core systems, just multi-core—still to be seen.

Reply
Reply
C
Craftery
Member
Find
207
12-02-2019, 08:23 PM
#5
Likely due to the lengthy single-core evaluation, the required test time surpasses the allowed limit.
Reply
Reply
C
Craftery
12-02-2019, 08:23 PM #5

Likely due to the lengthy single-core evaluation, the required test time surpasses the allowed limit.

Reply
Reply
_
_PREDA
Junior Member
Find
10
12-22-2019, 06:20 AM
#6
Sure, I ran a 10-minute multi-test and everything made sense! So the mystery was solved.
Reply
Reply
_
_PREDA
12-22-2019, 06:20 AM #6

Sure, I ran a 10-minute multi-test and everything made sense! So the mystery was solved.

Reply
Reply