Stop printing if the same fault returns after one careful restart or basic recovery step.
HP / PageWide 300 / 400 / 500 series

0x610000CC - The printer reported a printer-system failure and needs a restart or power reconnect before it can recover.

The printer reported a printer-system failure and needs a restart or power reconnect before it can recover.

This guide is scoped to the PageWide 300 / 400 / 500 series family. Exact menu wording, cartridge naming, and service behavior can still vary by model variant and firmware.

Severity

High

Most likely cause

The print system hit an internal fault during startup or printing.

Can you keep using it?

Usually no - see below

Consumables involved

Not usually the first suspect

Can you keep using it?

Can you keep using it?

Contact customer support if any of these apply

  • !0x610000CC returns after a restart and power reconnect.
  • !The printer cannot reach a ready state or keeps repeating the same printer-failure message.
If the printer still starts normally: Try one careful restart or the first official recovery step, then stop if the same error comes back straight away.

What to check first

Step-by-step checks

  1. 1

    Safe first step

    Turn the printer off, then back on once.

    Start with the official recovery step before moving on to parts or deeper servicing.

  2. 2

    Safe first step

    If the error persists, unplug the power cord and reconnect it before trying again.

  3. 3

    Safe first step

    Run one small test print only after the printer reaches ready cleanly.

Background

What this message usually means

HP uses 0x610000CC for a PageWide printer-failure state. The official support guidance treats it as a broader print-system problem rather than a routine paper or consumables warning, so the first recovery step is a restart and, if needed, a power cord reconnect before escalating to HP support.

Before the message

What users usually notice first

Messages like this often appear after the printer fails one of its normal startup, supply, or paper-path checks and cannot return to ready state cleanly.

Diagnosis

Likely causes

Most common

The print system hit an internal fault during startup or printing.

Common

The printer could not clear a prior error state cleanly.

Possible

A mechanism or transport problem left the device in a repeated failure state.

Service

When service or replacement is more likely

  • -Treat this as a printer-failure code rather than a consumables or paper-only issue.
  • -Repeated retrying is unlikely to help if the printer never recovers on power cycle.

Avoid wrong turns

Common misreads of this message

  • -Treating the message like a confirmed failed part instead of a support clue about which system has stopped the printer.
  • -Assuming no physical path issue exists just because no full sheet is visible at first glance.

See also

Related codes in this family

Explore more

More HP printer families

Read this next

Helpful guides for this problem

Boundary

When to stop troubleshooting and move to support

If the same message returns immediately after one careful recovery attempt or the printer cannot reach ready state, stop there and use the family-specific support path.

Keep browsing

Where to go next

Source notes

HP's PageWide support article identifies 0x610000CC as a printer-failure code and recommends turning the printer off and back on, then reconnecting power if the fault persists.

Built around HP PageWide 300, 400, and 500 series support guidance. Exact wording can vary by firmware and regional support site.

Printer error codes can vary a little by firmware, region, and exact model variant. Use this guide as a family-level starting point and stop if the next step would require disassembly or service-mode changes.

Known family variants: PageWide 352, PageWide 377, PageWide 452, PageWide 477, PageWide 552, PageWide 577

Last reviewed: 2026-04-12

Reference: Open reference

Privacy and advertising

Choose whether to allow ad personalization

FixThisError may use Google AdSense on broad browse pages. Your choice controls whether advertising-related cookies and ad requests can be used. Core site content remains available either way.