I've been using Debian for years without crashes, so I don't think it's a software issue. It sounds like a hardware issue to me; it could be your motherboard or power supply.
Debian
❤️ Debian
Rules
- Keep it about Debian.
- Be respectful.
- Engage in constructive discussions.
- Please, no harassment, hate speech, or trolling.
I've already replaced the cpu and the hard drives. I could try swapping out the ram even though its never failed any kind of ram check. I have evga 450br psu which is supposedly a good budget psu but I guess I could try replacing it. When I'm done with my gaming watercooling build I'll have a spare motherboard I could try but if I change the motherboard, I'd likely have to reinstall just to get all the chipset drivers to work and if I'm reinstalling an os, I should choose something other than Debian because I would be changing 2 things in the same amount of time and effort it takes to change 1 thing which double the chances arriving on a combination of things that results in it not crashing anymore.
If the only way to get this working is seriously to randomly replace more parts and hope something finally works, I might make a serious effort to go back to using my known stable Athlon Xp I was using before I "upgraded" to this one. I'd have to install Gentoo and probably lose compatibility with a few things but i am so sick and tired of dealing with this server crashing all the time that it might be worth it.
Yeah, unfortunately it's damn near impossible to pin down the failing part exactly without a bunch of spares parts.
You could look around your mobo for bulging capacitors, but that could be a long shot.
You could also try sifting through your journalctl looking for warnings and errors.
Sorry to come so late to the post, but have you checked the logs to see what was going on before the crash?
try journalctl -b -1 -e
as it will show the last of the logs of the previous boot.
- Define "crashing". What stops working?
- Same troubleshooting steps as any other computer program, start by checking the logs (
/var/log/syslog
orjournalctl
or application-specific logs depending on what exactly is "crashing")