TI-84 ERR:BAD TOKEN: Causes and Fixes
Quick answer: The TI-84 ERR BAD TOKEN fix is usually quick — find the corrupted variable with GOTO, delete it, and retype your calculation. Details below.
ERR:BAD TOKEN is one of the more confusing TI-84 errors because it rarely means you made a typo. Instead, it means the calculator choked on a *stored piece of data* — a variable, program, or transferred item — that doesn’t belong where you tried to use it. Here’s what causes it and how to fix each case.
TI-84 ERR BAD TOKEN Fix: What It Means
In plain terms: you asked the calculator to use a “token” (a variable name, program, list, or other stored item) in a place where that kind of token makes no sense. The calculator can’t interpret it, so it throws ERR:BAD TOKEN instead of guessing.
| Scenario | Example | Why it fails |
|---|---|---|
| Recalling a program into a calculation | Pasting prgmQUAD into 2+prgmQUAD | Programs aren’t numbers |
| Using a string as a number | A variable holding "HELLO" in 5+X | Text can’t be added |
| Recalling a list where a single value is expected | Using L1 inside a function that needs one number | Wrong data shape |
| Corrupted variable from a bad transfer | Variable received via cable with errors | Contents are garbled |
| Imaginary result forced into real context | Certain complex recalls in Real mode | Mode mismatch |
Fix 1: Find the Offending Spot with GOTO
When the error appears, don’t just quit — let the calculator show you the problem.
- When ERR:BAD TOKEN appears, select 2:Goto
- The cursor jumps to (or near) the token it couldn’t understand
- Look at what’s highlighted — is it a variable name, program name, or list?
- Check what that item actually contains (see Fix 2)
This alone solves most cases, because the highlighted token is almost always the culprit.
Fix 2: Inspect the Suspicious Variable
Once you know which variable is involved, look inside it.
- Press 2ND, then + (MEM)
- Select 2:Mem Mgmt/Del
- Go to the variable’s category (e.g., 2:Real for number variables, 4:List for lists)
- Find the variable and check: does it hold what you expect?
Common discoveries:
- A variable you thought was a number actually holds a string (text)
- A list variable got overwritten with a single value, or vice versa
- A program name was recalled where a variable was expected
Fix 3: Retype the Entry Cleanly
If the variable’s contents look wrong or garbled:
- Note down the correct value you intended
- Delete the corrupted variable: 2ND → + → 2:Mem Mgmt/Del → highlight it → DEL
- Re-store the correct value (e.g., type
5→ STO→ → X → ENTER) - Retype your original calculation from scratch — don’t recall the old entry, since the bad token may be hiding in it
Fix 4: Re-Transfer After a Bad Cable Transfer
BAD TOKEN often appears right after receiving variables or programs from another calculator or a computer.
- Delete the transferred item(s) that trigger the error
- Check the cable connection on both ends
- Re-send the variable or program
- If it fails again, the source file itself may be corrupt — get a fresh copy
Fix 5: Check for Mode Conflicts
Some BAD TOKEN errors come from complex/imaginary values used while the calculator is in Real mode.
- Press MODE
- Look at the complex number setting (bottom rows on newer OS versions)
- If your work involves imaginary numbers, switch to a+bi mode
- Retry the calculation
How BAD TOKEN Differs from ERR:SYNTAX
These two get confused constantly, but the distinction matters for fixing them:
| ERR:SYNTAX | ERR:BAD TOKEN | |
|---|---|---|
| Cause | Typo in what you *typed* — misplaced comma, parenthesis, or operator | Problem with *stored data* — wrong variable type or corrupted content |
| Fix | Retype carefully; check syntax | Inspect/delete the offending variable |
| GOTO shows | The typo location | The bad token |
If your error is a plain typo (missing parenthesis, double decimal), see our ERR:SYNTAX fix guide instead.
When Nothing Works: Reset RAM
If a corrupted variable is buried somewhere you can’t find, a RAM reset clears all variables at once while keeping your apps and archived data. Follow our TI-84 reset guide (Method 1: All RAM) — it takes under a minute.
Frequently Asked Questions
What does BAD TOKEN mean on a TI-84?
It means you used a stored item (variable, program, list) somewhere its type doesn’t fit — like putting a program name into an arithmetic expression. It’s a data problem, not a typing problem.
How is ERR:BAD TOKEN different from ERR:SYNTAX?
SYNTAX means your typed entry has a mistake (parentheses, commas). BAD TOKEN means a recalled variable or transferred item contains something invalid for that spot. Press 2:Goto — if it highlights a variable name rather than your typing, it’s BAD TOKEN territory.
Can a bad cable transfer cause ERR:BAD TOKEN?
Yes — it’s one of the most common causes. An interrupted transfer leaves a corrupted variable behind. Delete it and re-transfer with a solid connection.
Will resetting my calculator fix ERR:BAD TOKEN?
A RAM reset clears the corrupted variable, so yes, it usually works. But try deleting just the offending variable first — it’s faster and you keep everything else.
Why do I get BAD TOKEN when recalling a program?
Programs can’t be used as values in calculations. If you recalled prgmNAME onto the home screen by accident, press CLEAR and retype. To *run* a program, use PRGM, select it, and press ENTER.
*Practice on a fresh calculator anytime with our free TI-84 calculator online — no download needed. More fixes in our TI-84 guides hub.*



