Gilbarco CRIND BIOS Errors

This guide assists in resolving Gilbarco CRIND BIOS errors that lead to Card Transaction failures and DCR reboots.

Use this page when card transactions fail and/or DCRs reboot with a CRIND-related error.

Symptoms

• CRIND BIOS error on the dispenser
• DCRs rebooting
• Card transactions failing

Before you run Download to DCRs (Initialize DCRs) or Reset Controller:

• If you target one DCR, make sure that pump/fueling position is Idle.
• If you target All DCRs (0), make sure all pumps/fueling positions are Idle.
• Clear/finish any Prepay, Post-pay, Pay-at-pump, or DCR sales first.

---

Pick the correct path

1. Firmware/version mismatch (Base 55.02.04 or 56.01.0 + Gilbarco M7)
2. General troubleshooting (all other Bases and DCR types)

1) Firmware/version mismatch (Base 55.02.04 / 56.01.0 + Gilbarco M7)

Use this path when the site is on Base 55.02.04 or 56.01.0 and the impacted positions use Gilbarco M7.

To determine if your site's issues are caused by the Dispenser Firmware version, follow these steps:

1. Confirm your site is on Commander Base 55.02.04 or 56.01.0.
2. Confirm the affected positions/pumps use Gilbarco M7 DCRs.
3. For each affected position, check the dispenser firmware:

   1. Open Configuration Client
   2. Go to Reporting > Site Asset Data > Dispenser Data
   3. Select the affected position (pump #), Note the firmware version shown

Minimum versions reference screenshot:

If firmware is below the minimum required shown above, contact a Pump Technician to update the firmware.

If firmware is at or above the minimum required, contact the Helpdesk for further assistance.

If dispenser firmware is below the minimum required version:

• Do not continue to General troubleshooting.
• Do not use Reset Controller.
• Contact Helpdesk via Chat or call 1.800.VERIFONE (837.4366).

2) General troubleshooting (all other Bases / DCR types)

1. Initialize the impacted DCRs (Download to DCRs)

From the register:

CSR Functions → Fuel Manager Menu → Download to DCRs

• Enter the affected DCR number.
• Enter 0 to download to All DCRs.

If only 1–2 DCRs are impacted, target only those DCRs first. Avoid All (0) unless required.

Expected result: the impacted DCR should show any screen change (Downloading/Loading, reboot, new prompt).

1. Verify there are no stuck fuel sales

• Check and clear any stuck fuel sales on the affected pumps.

1. Check for changes after resolving stuck sales

• After clearing stuck sales, verify whether the impacted DCRs clear the error or show any screen change.

1. If the error persists: Reset the Controller

• If the error remains, press option 8. Reset Controller

1. Contact Pump Technician

• If the steps above do not resolve the issue, consult a Pump Technician for on‑site hardware diagnostics and repair.

For Technicians, When escalating, note the information given below:

• Commander Base version
• DCR type (M7 vs other)
• Affected pump/DCR numbers
• Dispenser firmware version(s) (if M7)
• Exact dispenser/DCR message text

---