Crash when using x265 with avx512 option about staxrip HOT 13 CLOSED

I left the selection on avx512 and replaced the default installed .exe encoder with "3.5+153+15-813ccbff0-.Mod-by-Patman.-x64-avx512-msvc1937"

This would be my solution No. 1. 😅

In fact for the same file it was faster, about 2% and completed without any problem.

So I guess the issue was the combination you had before. So that means for the next releases you give up the AVX512 advantage or you have to (download and) replace the encoder with every StaxRip version you download. It's up to you, the important part is that your encodes finish without issues.

however I use a CPU cooler with ARCTIC Liquid Freezer II 280 A-RGB

And it seems to do a good job. Just thought because of the report, that it could be cloaked up, but that does not seem to be the case.

So I guess we can close this....

from staxrip.

yes. I thank you for your help, however I still reserve the right to perform a test with the default encoder (avx2) by deselecting from the settiung avx521 (solution2).

from staxrip.

Interestingly there were absolutely no changes made in v2.35 that could explain that. Demuxers, encoders, muxers, all the same.

A log file would be nice to see if there is something that could help identifying the issue.

from staxrip.

You are right it is happening even with version 2.34. I don't understand what is happening.
The ..staxrip.log file how lop I attach it?

from staxrip.

Let's see if the log file can help us a bit...

how lop I attach it?

Maybe this could help: 😅

from staxrip.

CIao I attach the file of my x265 encoding process, with my Ryzen 9 7950x processor I use 3 Chunks.
Indy 5 Regrade_staxrip.log

from staxrip.

Are you using the x265.exe that is delivered with StaxRip or did you replace it?

from staxrip.

I use the version contained in StaxRip "3.5+153+15-813ccbff0-.Mod-by-Patman.-x64-avx2-msvc1937"

from staxrip.

I restored the operating system image and installed version 2.35 again and started a new encoding process let it go overnight, and entered the "Hibernate" command for the end of the process.
Let's see what happens tomorrow.

from staxrip.

You use --asm avx512 with a x265.exe version, that is just build for AVX2. That could be the culprit.

So you could try to remove this parameter or you can try another build from here: https://github.com/Patman86/x265-Mod-by-Patman/releases/tag/3.5%2B153%2B15

Regarding your Hibernate command:
The error message seems to prevent the system from hibernating, so if you want to turn off your PC, you could also disable the error message in Options, so there will be just a warning in the log file.

from staxrip.

Thank you very much for the advice.
Although I find it very strange that this problem has emerged only a few days ago, and I have never deselected the AVX512 parameter and have always used the x265 encoder embedded in StaxRip.
Maybe thinking about it with the characteristics of my processor maybe it is better to choose the Mod by Patman -x64 avx512 encoder or am I wrong?
Thanks

from staxrip.

If your CPU supports AVX512 then you should at least try it out. There should also be a very small speed up of about 1-3%, but it should also generate more heat.

Nevertheless it would be interesting if that replacing or the removing of --asm avx512 solves your issues.

In case it worked for a longer time period and now starts to make issues, I suggest checking your hardware.
Maybe one or more fans and/or your CPU cooler is/are cloaked up and can't provide the little amount of air your CPU needs for the hard job. Especially when the problem occurs always after/at different times/progresses.
There are many reasons possible. But when you run one encode multiple times and it stops always at different frames, it's probably a hardware issue.

You maybe want to play with the number of chunks, as this might lower the stress on your CPU.

from staxrip.

Hello.
In StaxRip I left the selection on avx512 and replaced the default installed .exe encoder with "3.5+153+15-813ccbff0-.Mod-by-Patman.-x64-avx512-msvc1937" and set the hibernate command as I often do overnight.
You were right about the advice you gave me and I thank you.
In fact for the same file it was faster, about 2% and completed without any problem.
At this point I don't know if I should uncheck avx512 and leave the encoder by Patman avx2
I will do more processing to test the stability, however I use a CPU cooler with ARCTIC Liquid Freezer II 280 A-RGB

from staxrip.