My OS keeps freezing after 20 30 minutes of use, every time this happens I have to reset it and it works again for another 20 30 mins before freezing again. Any ideas?
No one would be able to help with this limited information.
Welcome to the community @d4n1k4r7 
Let’s see if we can start to gather some information that may point to possible causes. The system log leading up to the point of a freeze would be the first thing I’d look at.
Note the eos-sendlog command used below. This will create a link you can share here, so we can review what the commands output.
The below command will retrieve the last 50 lines of the previous boot log. This would be used immediately after a freeze and restart, retrieving the log from the previous session:
journalctl -k -b -1 | tail -n 50 | eos-sendlog
The other thing that could be helpful, is some general system details:
inxi -Fxxc0z | eos-sendlog
2 Likes
Thank you, the links are:
https://0x0.st/8inU.txt
https://0x0.st/X6Us.txt
What other information would you like me to add?
Your second link you shared there (for inxi) failed. I suspect the inxi command had an error. That information may still be useful.
ene 06 19:12:28 daniel-f0em0027ld kernel: [drm:amdgpu_dm_atomic_check [amdgpu]] *ERROR* [CRTC:73:crtc-0] hw_done or flip_done timed out ene 06 19:12:38 daniel-f0em0027ld kernel: [drm:amdgpu_dm_atomic_check [amdgpu]] *ERROR* [CRTC:77:crtc-1] hw_done or flip_done timed out
There are reported issues (eg: here and here) with AMD GPU’s and mesa version 24.3.x.
You might try downgrading mesa to version 24.2.7 and see if that resolves the issue.
sudo downgrade mesa
Then select the number corresponding with version 24.2.7 from the list, to downgrade it.
What @Bink has asked for will suffice for now. All new users should provide at minimum the hardware info using the proper command when asking for help so those trying to help know what desktop they are using, what window manager, and what hardware such as motherboard, cpu, gpu and it shows whether the proper drivers are installed and the modules are loading for the appropriate hardware devices. This saves a lot of back & forth right from the beginning. Then if more info is required those trying to help will ask for it if necessary.
Welcome to EOS. We really want to help new users or new users to an Arch based OS learn while they endeavour to work through any issues that might come up. This just makes it much easier in most cases.
1 Like
Thank you so much I will have it in mind for next questions.
Can you try uploading your hardware again. The link isn’t working.
inxi -Faz | eos-sendlog
Post the link.
@d4n1k4r7
From the one log i see it’s using amdgpu. Have you tried the following kernel parameter?
amdgpu.noretry=0
Are you using the default systemd-boot? Or grub bootloader?
Everything was working fine with the Mesa solution but today it doesn’t want to start and is stuck saying: 1.536972 Disabling IRQ #7
Grub
I think you’re going to have to post the output of these errors so it can be seen.
It stuck in there flashing the screen
I was referring to this. Your images are fine but i have no idea what’s stopping it or making it hang. 
Did you downgrade mesa to avoid the crashes?
This is no longer possible, as the ‘llvm-libs’ package no longer allows this.
You also have to downgrade this package, but it is better to update ‘mesa’ again. Try one of these two options first.
If you then can boot normally again you can install the package from Lone_Wolf until a fix for AMD vega graphics (mesa) is available.
https://bbs.archlinux.org/viewtopic.php?pid=2219910#p2219910
https://bbs.archlinux.org/viewtopic.php?pid=2220233#p2220233
Give some feedback this time. Other people are affected too.
What Type AMD APU do you have? (e.g. AMD Ryzen 5 3400g)