Minimal hardware‑fault tolerance (no WHEA‑equivalent)

Linux avoids heavy hardware‑error mediation layers because they add complexity and overhead.
Sacrifice:

• No unified hardware‑fault recovery architecture
• Many errors escalate to freezes or kernel panics
• Non‑ECC RAM bit flips often cause silent corruption or crashes
• PCIe AER recovery is inconsistent and driver‑dependent

Aggressive kernel‑panic philosophy instead of subsystem restart

Linux chooses correctness over uptime.
Sacrifice:

• Kernel panics on corruption Windows would isolate
• GPU driver faults often freeze the session instead of resetting
• Audio/USB stack failures often require full reboot
• No equivalent to Windows TDR (reliable GPU reset)

Drivers run closer to the metal (less isolation, fewer guardrails)

Linux drivers are lean and often run in kernel space.
Sacrifice:

• Higher blast radius for driver bugs
• More crashes from flaky consumer hardware
• No mandatory driver verification framework like Windows HLK/WDF
• Volunteer‑written drivers with varying defensive coding quality

No hypervisor‑enforced kernel integrity (VBS/HVCI equivalent)

Linux avoids the overhead of virtualization‑based kernel protection.
Sacrifice:

• Kernel memory is not shadow‑protected
• Bit flips can corrupt kernel structures directly
• No hardware‑isolated code integrity enforcement

Simpler memory‑error handling (bad page retirement rarely enabled)

Linux can retire bad RAM pages, but distros rarely enable it because it adds overhead and complexity.
Sacrifice:

• Soft memory errors often kill processes or freeze the system
• No unified consumer‑grade memory‑integrity pipeline
• ECC is treated as the “real” solution

Windows compensates for bad RAM; Linux expects good RAM.

Less defensive user‑session architecture

Linux desktops are modular and lightweight.
Sacrifice:

• Xorg/Wayland sessions can collapse from minor driver faults
• Compositors crash more easily
• No unified fallback path for desktop recovery
• Freeze > crash > restart hierarchy is inconsistent

Lean system services (fewer watchdogs, fewer recovery daemons)

Linux avoids heavyweight watchdog frameworks.
Sacrifice:

• Fewer automated subsystem restarts
• More “silent hangs” with no logs
• More reliance on user rebooting manually

Assumption of server‑grade hardware

Linux’s design roots are in server environments.
Sacrifice:

• ECC assumed for correctness
• Stable power assumed
• Stable PCIe assumed
• Stable RAM assumed

Linux is 'often' lighter because it does less to protect you from bad hardware.