What It Means
A data recording malfunction means the ELD cannot fulfill its core obligation of recording and retaining required HOS records. This can result from insufficient internal storage, a corrupted data store, a failed memory component, or an internal software fault that prevents records from being written or read correctly.
ELDs are required to store a minimum of 8 days of records and to be able to retrieve them on demand. If the device cannot write new records, cannot retain records it has written, or cannot retrieve stored records in a readable format, it has a data recording malfunction.
What To Record
Record any error messages the ELD displays, the time the malfunction was detected, the driver, and the vehicle. Note the last date and time for which records are confirmed to be accessible on the device. If you can still access some records but not others, document the date range of the gap.
What Drivers Should Do
Notify the carrier within 24 hours. Reconstruct the previous 7 days of records on paper if the ELD has lost those records and cannot recover them. Begin on paper for the period the malfunction is active if the device cannot record new data.
Do not attempt to factory reset or clear the ELD's internal storage without direction from the ELD provider or carrier — doing so may permanently delete records that are still required to be maintained.
What Not To Do
Do not continue operating and assume the ELD will recover on its own if it is actively failing to record driving events. If the malfunction indicator is on and the device is not logging duty status changes, every mile driven without a record creates a compliance gap. Contact the ELD provider for device-specific recovery steps before continuing.
Related Pages
Related Fault Code Pages
Sources
- ELD Malfunctions and Data Diagnostic Events Federal Motor Carrier Safety Administration · government · accessed 2026-05-05 · confidence high
Source: Federal Motor Carrier Safety Administration, ELD Malfunctions and Data Diagnostic Events. This page paraphrases factual fields only and is not a substitute for the original document.
Open source - 49 CFR 395.34 - ELD malfunctions and data diagnostic events Electronic Code of Federal Regulations · government · accessed 2026-05-05 · confidence high
Source: Electronic Code of Federal Regulations, 49 CFR 395.34 - ELD malfunctions and data diagnostic events. This page paraphrases factual fields only and is not a substitute for the original document.
Open source - 49 CFR Part 395 Appendix A to Subpart B - Functional Specifications for ELDs Electronic Code of Federal Regulations · government · accessed 2026-05-05 · confidence high
Source: Electronic Code of Federal Regulations, 49 CFR Part 395 Appendix A to Subpart B - Functional Specifications for ELDs. This page paraphrases factual fields only and is not a substitute for the original document.
Open source
FAQ
Can a full ELD storage cause a data recording malfunction?
An ELD that has exceeded its storage capacity may be unable to write new records, which would trigger this malfunction. However, compliant ELDs are required to retain a minimum period of records and must manage storage accordingly. If a device consistently runs out of storage, it may not meet the technical specification requirements — contact the ELD provider to assess whether the device is functioning correctly.
If the ELD has a data recording malfunction, do I need to go back and recreate all lost records?
Under 49 CFR 395.34, a driver must reconstruct records for the previous 7 days if the ELD cannot produce them. Records before that 7-day window are subject to the carrier's and FMCSA's standard record retention requirements. The reconstruction must be done on paper logs with available supporting documents — odometer readings, fuel receipts, dispatch records — as evidence of actual duty status.
Is a data recording malfunction different from a data transfer malfunction?
Yes. A data recording malfunction means the device cannot record or retain records internally. A data transfer malfunction means the device can record internally but cannot successfully transfer records to an authorized safety official via the required FMCSA transfer methods (wireless or USB/Bluetooth). Both are defined malfunctions with the same driver notification and paper log requirements, but they indicate different failure points.