FFMPEG freezing whole PC (linux)

[space_enjoyer1]

This is the command I am using:
for i in *.mp4; do ffmpeg -i "$i" -map_metadata -1 -c:v libvpx-vp9 -c:a libopus -crf 19 "${i%.*}.webm"; done

It will run fine for a while, it got about 75% through the first file last time I ran it. But then it hard freezes, the whole system is locked up. The only way I can reset is to hold down the power button.

Specs of computer:

i5-3330s
8GB RAM
256GB SSD
Running Latest Zorin OS Lite (reinstalled yesterday, so nothing on it except what is preinstalled and ffmpeg)

I ran prime95 for half an hour and it didn't crash there, and the cpu temps never went over 55 degrees, so I don't think it's an overheating issue.

FFMPEG doesn't "crash" really, so there is no error output, it just completely freezes.

[Selur]

Have you checked syslog, journalctl ? (could be ram issues, cpu issue, driver issue,...)

[space_enjoyer1]

Have you checked syslog, journalctl ? (could be ram issues, cpu issue, driver issue,...)

I'm not sure the exact time of the freeze as I was afk when it happened, Around the time I think it happened there is a download in the syslog. "fwupdmgr" and "updating lvfs". Not really sure what that means tbh.
The first line that seems to be related to it says *pc name* CRON[3841]. I looked it up and CRON is apparently a task schedueler, so I'm guessing this was just a schedueled firmware update.

Could that have caused it, or is there something else I should look for in the logs files?

[Selur]

Hardware issues usually show up in the kernel log file, software issues basically can show up in any log file and shape

[space_enjoyer1]

Hardware issues usually show up in the kernel log file, software issues basically can show up in any log file and shape

Nothing unexpected in the kern.log file, just a bunch of usb disconnects and reconnects which is me plugging and unplugging my mouse to switch betweens pcs. Is there anywhere else I should look?

[Selur]

syslog, kernel.log and journalctl are the first things I would look at then X0rg or similar log files, that are associated with the display manager&co, might be an over active power management option going wrong or similar.

[space_enjoyer1]

syslog, kernel.log and journalctl are the first things I would look at then X0rg or similar log files, that are associated with the display manager&co, might be an over active power management option going wrong or similar.

Yeah I've checked those, doesn't seem to be anything there that would cause a crash beyond possibly the firmware update thing in syslog. Nothing in X0RG that looks out of place either.

[Selur]

Okay, if you can't find anything, try to reproduce the issue while having a tail on the logs, so if it freezes you might see something