Hello, I’ll do my best to explain my weird situation.
I’m currently running:
(the integrated GPU is disabled, I have it in case if my GPU ever breaks)
I noticed this thing happening like 5 days ago, I don’t know if this matters, but I updated the BIOS like 2 days ago and it still persists.
When my issue takes place, I cannot run any command or start any program, Steam games close themselves before even (properly) launching, opening Terminal also doesn’t work. I get a “KDE Daemon - Process Crashed” error box, the only ways to “fix” this is by waiting some time till it “solves” by itself or force-reboot. (the Applications Launcher’s Power Options don’t work).
This issue I am having is quite a discomfort which I want to get rid off.
Any help is welcomed.
PS: If I have to include any logs which can help us find a solution, please let me know
I put myself in your situation (virtually) and the first routine I do is :
1 only use basic hardware
2 make sure fans and heat sinks are clean
3 check all cables and jumpers by pulling them out and visually inspecting each contact. Look for burnt discoloration or melting of plastic.
4 pull ram module(s) and inspect the contacts of the board and socket. A pencil eraser works great for cleaning contacts.
5 boot from a live os that I know works on usb or optical
6 try to recreate the problem
If I cannot recreate the problem then introduce 1 variable at a time (video) and in different combinations until the problem appears. If you have a 2nd power supply try that.
Just basic troubleshooting techniques can go a long way.
Kde is showing an error but that does not necessarily mean KDE is faulty.
Hello vektor,
the issue was that somehow 2 contact pads from one of my RAM sticks were dirty. No idea how. Anyways, I left my PC on and all alone for the last 12hrs and it seems that the problem is gone!
First off thank you for responding with an update. So many people just disappear after they get what they want.
I live in Florida, USA and the humidity is a killer on any kind of metallic contacts. Especially power points like batteries in remote controls as well as nearly any kind of connectors. That failure mode is always the first thing I look for.
Hello again vektor.
My sorrow came back. Today I took a long “nap” and my problem happened again! Fell asleep at 6pm, woke up at 3am. Wanted to open Firefox via the task bar and it automatically closed, Ctrl Alt T to open Terminal - “KDE Daemon - Process Crashed”. I had to reboot by holding the power button on my PC case.
I did clean the RAM contacts as I stated before. I just cleaned the Tower Air Cooler Blades with a tissue, the heat sink (the part with lots of metal blades and pipes if that’s what’s called) didn’t need cleaning, I spotted no dust. (Thermal Paste was reapplied, no worries)
I don’t know if it’s important, but my motherboard is an MSI A520M-A Pro with the most up-to-date BIOS update
You did not mention updates in your OP. I would revert back to a day or two before the problem occured. You make backups, right?
Also you did not say whether you tried steps 1, 3 or 5 to find the problem, so from my point of view you are still back to square one. Until you eliminate the most basic steps (hardware) you cannot know for sure.
If you move your OS drive and run it on another computer that would be very telling.
Hello again,
I swapped the nvme from my PC to my Laptop, laptop’s got basic hardware, AMD Ryzen 5 3500U, 8GB RAM with only 6 usable.
I left my Laptop running for half a day and it happened again, swapped back to my PC, left it run for like 5 hours and it happened again. (I should’ve taken a photo with my phone before force rebooting the PC )
While swapping the nvme, I took a look at the jumpers and cables as you said in Step 3, everything looks normal.
I don’t understand what you meant in step 5, could you rephrase that please?
I think I missed a really important thing!
From April til June (this year) I installed Windows 11 on my secondary drive, an SSD. The day the CrowdStrike Incident took place, I decided to wipe the SSD and turn it into a games SSD.
So you put the drive in another computer and it happened the same way.
If the only change is the computer then there you go.
Either the drive is bad or there is a software problem.
My step #5 is about booting from a usb or cd with a live OS to check hardware. Moving the drive to a different computer is the same thing kinda.
If your drive turns out to be ok then you can start to troubleshoot the software. If the drive is bad I would not do anything with it until you copy any important info to a known good drive. That is probably a good idea anyway. Always have a backup or two if you can afford it.
I always had issues with sleep/wake in linux. Never worked as expected. Most times I just had to create simple udev rules for problematic usb/bluetooth devices or just put some cryptic directive in grub, other times it just didn’t work. Thankfully my last workstation (a Dell with linux preinstalled) doesn’t suffer from these issues.
I guess most of the time it’s just bad bios, and there’s nothing you can do about it.
I guess most of the times it’s just a bad (or untested in linux) BIOS.
Hello everyone, I have solved the issue.
The problem was some bad BIOS/UEFI settings. Sadly I don’t remember exactly which settings did I play around with, but it fixed my issue. I will make @vektor 's first comment as the “Solution”.
)
