How to read system crash logs when you have no idea what you're doing
When you have to handle both end-user support and sysadmin tasks with very little time, figuring out where to start with unfamiliar crash logs feels like guessing. This lack of deep debugging experience makes it difficult to decide whether to spend precious time investigating the issue or just give up and reimage the device.
What people tried
Every workaround mentioned in the threads below. We haven’t tested any of them — and nobody here is claiming they worked.
Found another way around this?
Share your steps and trade-offs so fellow engineers don't have to reinvent the wheel. No account required.
- 1Reimaging the machine or swapping the hardware instead of spending hours on kernel-level debugging.Did this help you?
- 2Asking as much detail as possibleDid this help you?
- 3Using a logical schema of application architectureDid this help you?
- 4Relying on basic monitoring and logsDid this help you?
In their words
Unedited, grouped by where they were said, most upvoted first within each place, each linked to the thread it came from.
“Sometimes the difficult part is figuring out where to start.”source ↗
“Not a ton of time, but I have a weird job where I have to do both end user support and sysadmin stuff. Never really had the chance to do a lot of windows debugging so no, I don't really know what I'm doing in this regard.”source ↗
“Reading this hurts because it's so real.”source ↗
“The actual troubleshooting method. Are you guys just guessing?”source ↗
“This is a new function of my job so I'm unfamiliar with these types of logs.”source ↗
Where this came up
People with this problem also raised
- 76HubSpot is down and timing out right now
- 7How to diagnose an intermittent equipment problem that only happened once
- 12Thermostat showing low voltage and no power
- 3Website crashed after updating PHP version
- 2Why does OE error happen at the end of the cycle?
- 2Floqast running slow and freezing during month-end close