> For the complete documentation index, see [llms.txt](https://commanderhelp.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://commanderhelp.verifone.com/fuel-dcr-help/fuel-dcr-help/dcr-help/gilbarco-crind-bios-errors.md).

# Gilbarco CRIND BIOS Errors

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

{% hint style="warning" %}
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.
  {% endhint %}

***

### 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)

<details>

<summary><strong>1) Firmware/version mismatch (Base 55.02.04 / 56.01.0 + Gilbarco M7)</strong></summary>

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:&#x20;

<figure><img src="/files/PYM8lBadLXrrgGHxTQpg" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/89KWJyNjJcEFoRk92ait" alt=""><figcaption></figcaption></figure>

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](https://support.verifone.com/s/) for further assistance.

{% hint style="warning" %}
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)**.
  {% endhint %}

</details>

<details>

<summary><strong>2) General troubleshooting</strong> (<strong>all other Bases / DCR types</strong>)</summary>

1. **Initialize the impacted DCRs (Download to DCRs)**

From the register:

<kbd>CSR Functions</kbd> → <kbd>Fuel Manager Menu</kbd> → <kbd>Download to DCRs</kbd>

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

{% hint style="warning" %}
If only **1–2** DCRs are impacted, target only those DCRs first. Avoid **All (0)** unless required.
{% endhint %}

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

2. **Verify there are no stuck fuel sales**

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

3. **Check for changes after resolving stuck sales**

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

4. **If the error persists: Reset the Controller**

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

<div align="left"><figure><img src="/files/pV9jMjtgXzTCROie2HHX" alt=""><figcaption></figcaption></figure></div>

5. **Contact Pump Technician**

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

{% hint style="info" %}
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
  {% endhint %}

</details>

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://commanderhelp.verifone.com/fuel-dcr-help/fuel-dcr-help/dcr-help/gilbarco-crind-bios-errors.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.