0x61011bed error code

[pauledinger]

Error code 0x6011bed appears after the printer completes a print and to enable the printer to print again requires many button pushes on the message display of  "OK."  

I have powered down the Officejet 7500,  unplugged the power, waited a minute,  removed and reinstalled the ink tanks and the printhead, vacuumed and blew away visible dust but still can't make the error go away for very long, with the error code usually returning after any print job (print or receipt of a fax).

What additional step or cleaning need I perform to get more that a single print job after the error code clears?

Additional observation: If the print job is multiple pages, once started the Officejet 7500 completes the task but getting is started after the error code appears is the problem.

[X-23]

Hello @pauledinger,

I understand that you're getting the message '0x6011bed' on the front panel of your HP Officejet 7500A Wide Format e-All-in-One Printer. I would like to assist you today with resolving this issue. Thank you for including all of the troubleshooting steps that you have attempted prior to reaching out for support. Now, there are different variations of '0x' error codes. Some error codes indicate print system failures within your printer. Others may indicate a Firmware Programming issue within your printer. For the error code that you're seeing, you may also see an additional message on the display of your printer that may alter what troubleshooting steps need to be completed. Therefore, I am going to provide you with the two methods of troubleshooting the '0x' error code you're seeing. Please just follow the steps below that match the exact error code message that you're seeing.

• (1) The 0x6011bed error code or message includes the words 'Problem With Printhead,' 'Printer Failure,' or 'Ink System Failure':

If you see one of these messages with the 0x code on the printer, can you please click here to access the appropriate troubleshooting steps. Once the support document opens please follow the steps under Step 1, Step 3, Step 4, Step 5, Step 6, and Step 7. Should the error code persist once troubleshooting is complete a replacement Printhead will likely be needed. The Printhead is the part that the cartridges fit into. It controls 'reading' the cartridges and putting ink on the pages. If the Printhead is defective, then the print system within your product is defective.

• (2) The 0x6011bed error code does not include the words 'Problem With Printhead,' 'Printer Failure,' or 'Ink System Failure': 

If you see just a 0x error code on your printer, and no additional messages, then it is likely that your printer is experiencing a Firmware issue. Troubleshooting steps for this error are limited. Please click here to access the appropriate support document. Once the support document opens you will notice that there is only Step 1 that you can complete. This step would be the Power Reset, which you have already completed. Should the Reset fail to resolve the error code then a replacement printer would be needed.

Should you require a replacement I would suggest that you reach out to our Technical Support queue by phone to explore hardware replacement options.

HP Technical Support can be reached by clicking on the following link:

HP Contact Support


(1) Once the support page opens please select the country in which you're located. Next, enter your HP model number (C9309A) on the right.

(2) Choose the 'Contact Support' tab at the top and scroll down to the bottom of the 'HP Support- Contact' page to fill out the form provided with your contact information.

(3) Once completed click the 'Show Options' icon on the bottom right.

(4) Lastly, scroll down to the bottom of the page and select 'Get phone number.' A case number and phone number will now populate for you.

Please respond to this post with the result of your troubleshooting. I look forward to hearing from you. Good luck! 🙂

[pauledinger]

Since no messages appear about  'Problem With Printhead,' 'Printer Failure,' or 'Ink System Failure' but sometimes a message regarding paper jam does, something like clear jam and press okay but there isn't any paper visible that would be cause for such a message, it suggests that perhaps there is a sensor with dust or dirt on it but don't know where or what the sensor looks like. With enough persistance of pressing okay or whatever appears to acknowledge the error code, the printer does eventually print, isn't there more that can be done short of replacement of this otherwise fine printer?

[X-23 · Accepted solution]

Hey @pauledinger,

Thanks for getting back to me regarding this issue.

Because you're also getting a Paper Jam error you may want to click here to access the proper Paper Jam troubleshooting steps. Once the support document opens just review the Solutions provided to ensure that no paper or debris is hidden within the paper path in your product. The support document also walks you through the rollers to clean on the printer. In terms of a paper sensor, you cannot clean the sensor itself. Also, should the sensor be defective, it is a non-replaceable part on this consumer model of product. Therefore, a whole unit replacement would be required.

After completing the Paper Jam troubleshooting steps provided, please test printing. Should the error persist, can you please click here to send the latest Firmware Programming Update to your printer. The Firmware is the 'brains' of your printer and controls what your printer does and how your printer does it. If there is a corruption within the internal programming in your printer it may cause performance issues. Your printer must be in a 'ready' state to 'send' the Firmware Update to the product. If your printer shows an error state on the front panel the Firmware Update will likely fail. Once the Firmware Update is complete test printing to verify if the issue has been resolved.

Should the error state persist after checking for jams and completing the Firmware Update a whole unit replacement would be the next step.

Please let me know if the troubleshooting steps I've provided resolve this error state. Best of luck! 🙂