What this code means
Every time a driver card is inserted, the tachograph is supposed to close out the previous session cleanly before starting a new one. Card not closed 44 means that didn't happen: the last session recorded on the card wasn't properly closed by the tachograph that was using it before.
This is an event, not a fault — the tachograph itself isn't broken. The event is written both to the driver card and to the vehicle unit's own memory, so it shows up in data downloaded from either one. On a Stoneridge SE5000, this is event code 044 when it happens in the driver slot (slot 1); the same event in the co-driver slot (slot 2) is logged as 062. The display message on a Stoneridge unit reads "Card not closed 44".
On a VDO DTCO 4.1, the equivalent message is "!1 card not closed xx", with the manual explaining it as: "The driver card was not properly removed from the previous tachograph. Some driver-based data may not have been saved." VDO rates this Medium severity; Stoneridge rates it Low — which is why the hero card above shows Low–Medium, depending on which manufacturer's tachograph wrote the event.
Card not closed 44 is an event about a previous session that wasn't closed correctly — the card reader itself worked fine. Card fault 41 is a different message: a communication problem between the card and the reader while the card is inserted. If your display shows "41" rather than "44", you're looking at a reader/card communication fault, not this event.
What to do now
There's no repair to make — the tachograph you're using now isn't at fault. Work through this instead:
- Acknowledge the message on the tachograph display.
- Check that your last recorded session actually has an end. Pull a "24 h card" printout, or check via download/evaluation software, to see whether the previous shift on the card shows a closing time.
- If activity is missing, add it back with a manual entry for the period that wasn't captured — most tachographs let you enter missed activity manually the next time the card is inserted.
- Going forward, always wait for the tachograph to fully release the card (the eject cycle completing) before pulling it out, and avoid removing the card if the vehicle has just lost power.
If code 44 keeps appearing on the same vehicle regardless of which driver is using it, the card slot lock or the tachograph's power supply may be the underlying problem — that's a workshop job, not a driver one.
If the same event keeps recurring across several vehicles or drivers, tachograph analysis software shows it for the entire fleet in one place.
Your card and vehicle unit log this event — TAGRA reads it
TAGRA can't close a session retroactively — only the missing manual entry on the card can do that. But once event 44 is written to the card and the vehicle unit's memory, TAGRA finds it in your downloaded data with the exact time and vehicle, evaluates it and documents it — so you can show it was a one-off, not a pattern, and so your fleet manager can see which driver or vehicle keeps generating it.
Stop looking up codes by hand — try TAGRA TRUCKER free for 30 daysWhy it happens
Card not closed 44 happens when a driver card is pulled out before the previous tachograph finished writing the end of its session. Common causes:
- the card was removed before the eject cycle completed, often because the ignition was already off when the driver got out;
- a power interruption to the vehicle unit while the card was still inserted — a dead battery, disconnected wiring, or a workshop power-down;
- the card was pulled out forcibly, for example from a stuck or sticking card slot; or
- a fault in the card slot lock itself, which prevents a clean release even when the driver waits correctly.
Whatever the cause, the result is the same: the end of the previous session is missing from the card. Depending on what was happening at that moment, some driver activity from the previous vehicle may be incomplete. Both the card and the vehicle unit record an event describing this as the "last card session not correctly closed".
Can you keep driving?
Yes. Card not closed 44 doesn't restrict driving in any way — it's a record of what happened to the previous session, not a condition of the current one.
At a roadside check, an inspector may ask about the event if they see it in the downloaded data. Be ready to explain it and, if activity was missing, show the manual entry you added to cover it. For a fleet, one occurrence is nothing to act on; if the same driver triggers it repeatedly, it's usually worth a quick reminder to wait for the card to release before pulling it. If the same vehicle triggers it across different drivers, treat it as a workshop matter — check the card slot and power connections.
Also displayed as
Drivers across Europe see the same event under different on-screen wording. These are the real search terms used for event 44:
- Card not closed 62 — Stoneridge, co-driver slot
- Karte nicht geschlossen 44 — German
- Karta nie zamknięta 44 — Polish
- Card neînchis 44 — Romanian
- Kártya nincs lezárva 44 — Hungarian
- Last card session not correctly closed — event name in downloaded data
Related codes
Frequently asked questions
Is "card not closed 44" a fault I need to get repaired?
No. It's an event, not a device fault — the tachograph you're using isn't broken. It records that the previous session on the card wasn't closed properly by the tachograph that was using it before. Acknowledge it, check the last session for a missing end, and add a manual entry if needed.
What's the difference between Stoneridge codes 044 and 062?
They're the same event on a Stoneridge SE5000 — 044 is logged when it happens in the driver slot (slot 1), and 062 is logged when it happens in the co-driver slot (slot 2). Both display as "Card not closed" with the relevant number.
Can I keep driving with a "card not closed 44" event?
Yes, without restriction. It doesn't affect the current session. At a check, be ready to explain the event and show any manual entry you added to cover missing activity from the previous session.
How do I stop this from happening again?
Always wait for the tachograph to finish its eject cycle and fully release the card before pulling it out, and avoid removing the card right after the vehicle loses power. If it keeps happening on one specific vehicle no matter who's driving, have the card slot and power supply checked by a workshop. See also ejection not possible (code 34).