§395.34 sets the malfunction protocol. When an ELD malfunctions, the driver must (1) note the malfunction and provide written notice to the carrier within 24 hours (§395.34(a)(1)), (2) reconstruct the current 24-hour period and the prior 7 consecutive days on paper graph-grid logs (§395.34(a)(2)), and (3) continue paper logs until the ELD is repaired. The carrier must take action to correct the malfunction within 8 days of discovery or driver notification (§395.34(d)).
Severity weight
Severity weight 1 in the HOS Compliance BASIC. The weight is low, but a §395.34 finding combined with a §395.22 ELD-not-required-information finding is what auditors aggregate — and a prolonged malfunction without repair escalates the carrier-side penalty quickly.
The 8-day clock
The 8-day repair window in §395.34(d)(1) starts at discovery or driver notification, whichever is earlier. A carrier that needs more time must request an extension from the FMCSA Division Administrator within 5 days of the driver's notice (§395.34(d)(2)). Letting an ELD remain in service "malfunctioning but kind of working" past the 8-day mark is a carrier-side §395.34(d) violation stacked on top of the driver-side finding.
How to prevent it
- Stock paper logs and §395 instructions in every CMV — the §395.34(a)(2) reconstruction starts the moment the malfunction is detected.
- Train drivers to report malfunctions immediately. The 24-hour written-notice clock starts at detection.
- Track ELD malfunctions in dispatch. The 8-day repair deadline needs a system to enforce it.
How Roadworthy HQ helps
Roadworthy HQ has no hours-of-service screen. It does not import ELD data, store records of duty status or supporting documents, or detect HOS violations. On the ELD side it keeps a per-vehicle registry of the device (provider, model, serial, FMCSA registration ID) and checks it daily against FMCSA's revoked-device list, with warnings ahead of the replacement deadline. A driver can be marked short-haul on their profile so the audit-readiness check stops expecting logs from them. It does not time the 8-day malfunction repair window or store reconstructed paper logs.