FATAL ERROR: Could not determine the stress test program process ID! (looking for 00-x86)

[Dahjiir]

I have downloaded an exact copy of someone elses corecycler folder and it still gives me this error.

[Dahjiir]

update to this, ycruncher had been running in the background through core cycler and suddenly just popped up

[sp00n]

If this is still a problem, please provide the log files and a screenshot of what's happening if possible. Also make sure you're running the latest version of CoreCycler (mentioning this because 00-x86 is only available if you specifically select YCRUNCHER_OLD as the test program now).

[Dahjiir]

yCruncher_2024-07-15_12-08-36_mode_00-X86.txt

seemed to launch right away, still gives me the error, seems like it runs but it tells me theres an error, im using corecruncher v0.9.5.0alpha 2. im guessing it works as it should its just telling me its not

[sp00n]

Huh, apparently I forgot to hit the Comment button a couple of days ago when I intended to post.

Please update to the latest version, your alpha version is now over a year old now. Be aware that it includes a new y-Cruncher version, which doesn't support the 00-x86 test mode anymore, so you'd need to change is accordingly. As well as the selected tests, since those have changed as well with the new y-Cruncher. You can still run the old y-Cruncher version by selecting YCRUNCHER_OLD as the stress test program though.

And make sure to also upload the CoreCycler log file if you still encounter this error with the latest version.

[senposage]

same issue window opens but script fails to find threads yCruncher_2024-08-30_01-00-35_mode_04-P4P.log

[sp00n]

same issue window opens but script fails to find threads yCruncher_2024-08-30_01-00-35_mode_04-P4P.log

That log file is for the stress test program (y-cruncher), which doesn't tell anything about the problem in this situation. The main CoreCycler log file would have the information and the corresponding error message.

[senposage]

CoreCycler_2024-09-03_01-34-43_YCRUNCHER_04-P4P.log

[sp00n]

CoreCycler_2024-09-03_01-34-43_YCRUNCHER_04-P4P.log

In this log file the thread that is running the stress test couldn't be found. From the list of all possible threads, it should've probably been the thread with the ID 7496, since it is the only one "Running" from y-cruncher. But it didn't report back any used processor time ( = CPU utilization so far), which is why it was disregarded.

Did y-cruncher actually run fine during this test, or did it take some time before starting it's calculations (e.g. more than the 30+ seconds the script was trying to get the thread)?

Also, does this always happen for you, or just occasionally?

[senposage]

ycruncher starts in a second window and its everytime I went back all the way to version 8.x same issue

[sp00n]

Hm. It's a wild guess, but maybe your Windows Performance Counters are somehow damage. I've had reports of problems with the Performance Counters quite regularly when I was still directly using them in the script, but since I ditched these for the TotalProcessorTime I haven't received any new issues.

Here are some instructions on how you could reset / rebuild them: https://docs.microsoft.com/en-US/troubleshoot/windows-server/performance/manually-rebuild-performance-counters https://leansentry.zendesk.com/hc/en-us/articles/360038645792-How-to-Fix-performance-counter-issues

I've also tried to automate this process in a batch file named enable_performance_counter.bat, which you can find in the \tools directory.

Besides that, I currently do not know what else could be wrong here. Do the other stress tests work, like Prime95 and Linpack?

[kboom]

Unfortunately, the same issue happens for me when I use ycruncher or linpack. It works fine for prime95...

[sp00n]

Unfortunately, the same issue happens for me when I use ycruncher or linpack. It works fine for prime95...

So which error is it, this one here or the one you reported in https://github.com/sp00n/corecycler/issues/90?