-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update check fails #83
Comments
Huh. You could try to disable the update check in the config.ini by setting Do you maybe need a proxy/VPN to access Github? The scripts tries to access https://api.github.com to check for an update, but should "fail successfully" (i.e. without a FATAL ERROR) when it can't reach it. It may be freaked out by some setting though. Let me know if it works after that. There's not much feedback from running on a Chinese OS yet. |
Oh ! thanks, it works. |
Reopening this as a reminder for myself that I need to do more tests what happens if the domain cannot be reached. |
I also encountered another problem 5800X |
I do see an error in the log file at the end:
I also see errors while trying to suspend/resume the threads of Prime95 starting at 04:13:33, which may have been a precursor of the "true" error:
|
According to the log file, this happened on iteration 4 of 10. Interestingly, the log file doesn't seem to be complete, i.e. it ends early when trying to close Prime95. There should still be messages after that, but here there aren't. The only times I've seen this happen so far is: |
"b" Where should I look a: uncertain (But there was no blue screen, Windows was still running) c :I don't have "DropBox" installed , have disabled "OneDrive" after installing Windows Time ≈ 04:31:54 |
a) Yeah, that only happens when the PC reboots The previous errors starting at 04:13:33 in the log when trying to suspend and resume the process threads are "156 - ERROR_SIGNAL_REFUSED", indicating that it somehow couldn't access Prime95 anymore. You could try to update to the 0.10.0.0 alpha version, where I did some refactoring, and/or you could also switch the suspend & resume method from |
VSS is Volume Shadow Copy, I have these entries as well. |
- Fixed a bug where Linpack wouldn't start from a directory including a space (fixes #84) - Fixed a bug where resuming after a crash with a "default" coresToTest order would result in an index out of bounds error (fixes #85) - Also it didn't resume on the crashed core - the config file's content is now put into the log file for easier debugging - Fixed a bug where the log file for y-cruncher was actually using the naming scheme for Linpack (under unclear circumstances, but it happened at least once) - Fixed a bug when the update check doesn't return any output at all (fixes #83)
- Fixed a bug where Linpack wouldn't start from a directory including a space (fixes #84) - Fixed a bug where resuming after a crash with a "default" coresToTest order would result in an index out of bounds error (fixes #85) - Also it didn't resume on the crashed core - the config file's content is now put into the log file for easier debugging - Fixed a bug where the log file for y-cruncher was actually using the naming scheme for Linpack (under unclear circumstances, but it happened at least once) - Fixed a bug when the update check doesn't return any output at all (fixes #83)
Starting CoreCycler v0.9.6.2...
Press CTRL+C to abort
FATAL ERROR: 无法对 Null 数组进行索引。
Line Number: 11189
You can find more information in the log file:
Y:\CoreCycler-v0.9.6.2\logs\CoreCycler_2024-08-25_05-07-59_PRIME95_SSE.log
When reporting this error, please provide this log file.
Press Enter to exit:
CoreCycler_2024-08-25_05-07-59_PRIME95_SSE.log
The text was updated successfully, but these errors were encountered: