CompTIA Server+ (SK0-005)TroubleshootingHard
A server is experiencing frequent, unexpected reboots. The event logs show a 'Kernel Panic' error message immediately before each reboot, but no other specific error codes or device failures are consistently reported. The server's memory has been tested and passed, and the operating system has been reinstalled. Which of the following is the MOST likely remaining cause?
- AA failing network interface card (NIC).
- BA faulty CPU or motherboard.
- CInsufficient disk space on the system volume.
- DCorrupted system files on the boot drive.
Show answer & explanationAnswer & explanation
Correct answer: B. A faulty CPU or motherboard.
A Kernel Panic is a critical error where the operating system cannot safely recover. After ruling out memory issues (tested and passed) and OS-level corruption (reinstalled OS), the remaining most likely candidates for persistent, unrecoverable system crashes like Kernel Panics are core hardware components such as the CPU or motherboard, which can cause low-level, uncatchable errors.
Why the other options are wrong
- A. A failing NIC might cause network issues or even system instability, but usually not consistently lead to 'Kernel Panic' reboots without other specific network-related errors.
- C. Insufficient disk space typically leads to application failures, system slowdowns, or inability to save files, not direct 'Kernel Panic' reboots without other specific disk-related errors.
- D. Corrupted system files are addressed by reinstalling the operating system; if the issue persists after a fresh OS install, this is less likely.
Kernel Panic
A critical error in the operating system kernel that prevents normal system operation, often leading to a system crash and reboot, indicating a severe software or hardware issue.
- Indicates an unrecoverable system state.
- Can be caused by faulty drivers, corrupted OS, or failing hardware.
- Often points to core hardware issues if software/memory are ruled out.
Memory trick: If the kernel panics and everything's clean, suspect the core hardware's unseen.