search

sp00n / corecycler

Script to test single core stability, e.g. for PBO & Curve Optimizer on AMD Ryzen or overclocking/undervolting on Intel processors
Other
663 stars 30 forks source link

FATAL ERROR: A counter with a negative denominator value was detected. [CoreCycler stopped, Prime95 still running] #23

Closed PinoTucana closed 2 years ago

PinoTucana commented 2 years ago

Was running a ALL AVX2 for 5900X, and error appeared: cmd_2021-08-11_1628689402

When I noticed this, I found something interesting.

The problem is: according to CoreCycler log, CoreCycler seems stopped @ 08:28:16, but Prime95 didn't stop, it seems started a new test?

I remembered the Prime95 was still running something, but I forgot which core it was running after error, sorry for it.

Tail of CoreCycler_2021-08-09_10-29-01_PRIME95_AVX2.log:

                 + 08:27:27 - Getting new log file entries
                 +            Getting new log entries starting at position 125076 / Line 4835
                 +            The new log file entries:
                 +            - [Line 4836] Self-test 38400K passed!
                 +            New file position: 125102 / Line 4836
                 + 
                 + 08:27:27 - Automatic runtime per core selected
                 +            The last passed FFT result lines:
                 +            - [Line 4836] Self-test 38400K passed!
                 +            All found FFT size lines:
                 +            - [Line 4836] Self-test 38400K passed!
                 + 
                 + Checking line 4836
                 +            Line number of this entry:         4836
                 +            Line number of the previous entry: 4835
                 +            + Adding this line to the allFFTLogEntries array
                 + 
                 +            Checking Line 4836
                 +            - The previous passed FFT size - old: 51200
                 +            - The current passed FFT size  - new: 38400
                 +            - All passed FFTs:
                 +            - 60, 64, 72, 8192, 80, 84, 96, 8960, 100, 112, 120, 9216, 128, 144, 160, 168, 9600, 192, 200, 224, 10240, 240, 256, 280, 10752, 288, 320, 336, 384, 11200, 400, 448, 480, 11520, 512, 560, 640, 12288, 672, 768, 800, 896, 12800, 960, 1024, 1120, 13440, 1152, 1280, 1344, 13824, 1440, 1536, 1600, 1680, 14336, 1792, 1920, 2048, 15360, 2240, 2304, 2400, 16000, 2560, 2688, 2800, 2880, 16128, 3072, 3200, 3360, 16384, 3584, 3840, 4096, 17920, 4480, 4608, 4800, 5120, 18432, 5376, 5600, 5760, 19200, 6144, 6400, 6720, 20480, 7168, 7680, 8000, 8064, 21504, 8192, 8960, 9216, 22400, 9600, 10240, 10752, 23040, 11200, 11520, 12288, 12800, 24576, 13440, 13824, 14336, 25600, 15360, 16000, 16128, 26880, 16384, 17920, 18432, 19200, 28672, 20480, 21504, 22400, 30720, 23040, 24576, 25600, 32000, 26880, 28672, 30720, 32000, 32768, 32768, 35840, 38400, 35840, 40960, 44800, 51200, 38400
                 +            - All unique passed FFTs:
                 +            - 60, 64, 72, 8192, 80, 84, 96, 8960, 100, 112, 120, 9216, 128, 144, 160, 168, 9600, 192, 200, 224, 10240, 240, 256, 280, 10752, 288, 320, 336, 384, 11200, 400, 448, 480, 11520, 512, 560, 640, 12288, 672, 768, 800, 896, 12800, 960, 1024, 1120, 13440, 1152, 1280, 1344, 13824, 1440, 1536, 1600, 1680, 14336, 1792, 1920, 2048, 15360, 2240, 2304, 2400, 16000, 2560, 2688, 2800, 2880, 16128, 3072, 3200, 3360, 16384, 3584, 3840, 4096, 17920, 4480, 4608, 4800, 5120, 18432, 5376, 5600, 5760, 19200, 6144, 6400, 6720, 20480, 7168, 7680, 8000, 8064, 21504, 22400, 23040, 24576, 25600, 26880, 28672, 30720, 32000, 32768, 35840, 38400, 40960, 44800, 51200
                 + 08:27:27 - The last passed FFT size: 38400K
                 +            The number of FFT sizes to test:        130
                 +            The number of FFT sizes already tested: 109
                 + 
                 + 08:27:37 - checking CPU usage: 4.19%
                 +            ...current CPU frequency: ~4514 MHz (121.97%)
                 + Suspending the stress test process
                 + Suspended: True
                 + Resuming the stress test process
                 + Resumed: True
                 + 
                 + 08:27:39 - Getting new log file entries
                 +            No file size change for the log file
                 + 
                 + 08:27:39 - Automatic runtime per core selected
                 +            No new log file entries found
                 + 
                 + 08:27:49 - checking CPU usage: 4.18%
                 +            ...current CPU frequency: ~4518 MHz (122.08%)
                 + Suspending the stress test process
                 + Suspended: True
                 + Resuming the stress test process
                 + Resumed: True
                 + 
                 + 08:27:51 - Getting new log file entries
                 +            No file size change for the log file
                 + 
                 + 08:27:51 - Automatic runtime per core selected
                 +            No new log file entries found
                 + 
                 + 08:28:01 - checking CPU usage: 4.19%
                 +            ...current CPU frequency: ~4514 MHz (121.98%)
                 + Suspending the stress test process
                 + Suspended: True
                 + Resuming the stress test process
                 + Resumed: True
                 + 
                 + 08:28:03 - Getting new log file entries
                 +            No file size change for the log file
                 + 
                 + 08:28:03 - Automatic runtime per core selected
                 +            No new log file entries found
                 + 
                 + 08:28:13 - checking CPU usage: 4.17%
                 +            ...current CPU frequency: ~4479 MHz (121.03%)
                 + Suspending the stress test process
                 + Suspended: True
                 + Resuming the stress test process
                 + Resumed: True
                 + 
                 + 08:28:16 - Getting new log file entries
                 +            No file size change for the log file
                 + 
                 + 08:28:16 - Automatic runtime per core selected
                 +            No new log file entries found
                 + 
                 + There has been some error in Test-ProcessUsage, checking (#1)
FATAL ERROR:
A counter with a negative denominator value was detected.
At \CoreCycler-v0.8.2.4\script-corecycler.ps1:3242 char:49
+ ... h]::Round(((Get-Counter $processCounterPathTime -ErrorAction Ignore). ...
+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidResult: (:) [Get-Counter], Exception
    + FullyQualifiedErrorId : CounterApiError,Microsoft.PowerShell.Commands.GetCounterCommand

Tail of Prime95_2021-08-09_10-29-01_AVX2_ALL_FFT_4K-51200K.txt:

[Wed Aug 11 08:25:20 2021]
Self-test 40960K passed!
Self-test 44800K passed!
[Wed Aug 11 08:26:46 2021]
Self-test 51200K passed!
Self-test 38400K passed!
[Wed Aug 11 08:28:18 2021]
Self-test 4K passed!
Self-test 5K passed!
[Wed Aug 11 08:30:28 2021]
Self-test 6K passed!
[Wed Aug 11 08:31:46 2021]
Self-test 8K passed!
[Wed Aug 11 08:32:49 2021]
Self-test 40960K passed!
[Wed Aug 11 08:33:52 2021]
Self-test 10K passed!
Self-test 12K passed!
[Wed Aug 11 08:35:36 2021]
Self-test 15K passed!
Self-test 44800K passed!
[Wed Aug 11 08:36:59 2021]
Self-test 16K passed!
Self-test 18K passed!
[Wed Aug 11 08:38:49 2021]
Self-test 20K passed!
Self-test 51200K passed!
[Wed Aug 11 08:40:33 2021]
Self-test 21K passed!
Self-test 24K passed!
sp00n commented 2 years ago

This seems to be another problem with the Windows Performance Counters that pops up from time to time according to Google. You're the first to report this specific one though, so congrats. :zany_face:

You can safely ignore this error if it doesn't occur regularly. If it does, rebuilding the Performance Counters might help. Or not. They seem to be constant cause of issues.