My machine became slow/freeze

[cscs]

@hdao133

i cant even boot the system on now, it just keep spinning

In the future you may consult;

[Tutorial] How to resolve an unbootable CachyOS system (black screen, login failed, cant boot, etc)

Introduction When we have problems gaining access to our systems it is difficult to gather information, let alone fix any problems. Here we will cover common causes and solutions to ‘cachyos wont boot’. TTY If your desktop does not load properly then you might still be able to use most, if not all, functionality by dropping to a non-graphical TTY. By default your system will have multiple TTYs, with each corresponding to an Fx key. Your desktop is assigned to one as well - most often F1. Yo…

As to the issue .. I dont see anything related to OpenRGB.

But I do see a lot of failures.

Oct 24 22:40:14 hdao systemd[1]: systemd-udevd.service: start operation timed out. Terminating.
Oct 24 22:40:20 hdao systemd[1]: systemd-resolved.service: start operation timed out. Terminating.
Oct 24 22:40:24 hdao systemd[1]: systemd-udevd.service: State 'stop-sigterm' timed out. Killing.
Oct 24 22:40:25 hdao systemd[1]: systemd-udevd.service: Main process exited, code=killed, status=9/KILL
Oct 24 22:40:25 hdao systemd[1]: systemd-udevd.service: Failed with result 'timeout'.
Oct 24 22:40:25 hdao systemd[1]: Failed to start Rule-based Manager for Device Events and Files.
Oct 24 22:40:26 hdao systemd[1]: systemd-resolved.service: Failed with result 'timeout'.
Oct 24 22:40:26 hdao systemd[1]: Failed to start Network Name Resolution.
Oct 24 22:40:40 hdao systemd[1]: systemd-udevd.service: start operation timed out. Terminating.
Oct 24 22:40:48 hdao systemd[1]: systemd-udevd.service: Failed with result 'timeout'.
Oct 24 22:40:48 hdao systemd[1]: Failed to start Rule-based Manager for Device Events and Files.
Oct 24 22:41:04 hdao systemd[1]: plymouth-start.service: start operation timed out. Terminating.
Oct 24 22:41:04 hdao systemd[1]: plymouth-start.service: Failed with result 'timeout'.
Oct 24 22:41:04 hdao systemd[1]: Failed to start Show Plymouth Boot Screen.
Oct 24 22:41:11 hdao systemd[1]: dev-disk-by\x2duuid-34131f52\x2d2a12\x2d4efb\x2da1a7\x2d280c6d4e2474.device: Job dev-disk-by\x2duuid-34131f52\x2d2a12\x2d4efb\x2da1a7\x2d280c6d4e2474.device/start timed out.
Oct 24 22:41:11 hdao systemd[1]: Timed out waiting for device /dev/disk/by-uuid/34131f52-2a12-4efb-a1a7-280c6d4e2474.
Oct 24 22:41:11 hdao systemd[1]: Dependency failed for /var/tmp.
Oct 24 22:41:11 hdao systemd[1]: Dependency failed for Local File Systems.
Oct 24 22:41:11 hdao systemd[1]: Dependency failed for /var/cache.
Oct 24 22:41:11 hdao systemd[1]: Dependency failed for /home.
Oct 24 22:41:11 hdao systemd[1]: Dependency failed for /srv.
Oct 24 22:41:11 hdao systemd[1]: Dependency failed for /root.
Oct 24 22:41:11 hdao systemd[1]: Dependency failed for /var/log.
Oct 24 22:41:11 hdao systemd[1]: Dependency failed for Flush Journal to Persistent Storage.
Oct 24 22:41:11 hdao systemd[1]: Dependency failed for Record System Boot/Shutdown in UTMP.
Oct 24 22:41:11 hdao systemd[1]: dev-disk-by\x2duuid-765C\x2d6754.device: Job dev-disk-by\x2duuid-765C\x2d6754.device/start timed out.
Oct 24 22:41:11 hdao systemd[1]: Timed out waiting for device /dev/disk/by-uuid/765C-6754.
Oct 24 22:41:11 hdao systemd[1]: Dependency failed for File System Check on /dev/disk/by-uuid/765C-6754.
Oct 24 22:41:11 hdao systemd[1]: Dependency failed for /boot.

So do you have some odd entries in /etc/fstab ?
And maybe also compare to lsblk -f or similar.