HP DeskJet 3520 getting different errors

[Cherrynic]

Initially code 0X00759C98 error code came on with Watchdog C below that

Did a hard reset, took printer cartridges out

Now I'm getting this error message 0X0000BA0

reset again

now code 0XB20002C

reset again

now code 0X00759C98 Watchdog C again

Now I can't get ink cartridges back in.  Its froze inside and I keep getting error messages.  

Am plugged in to wall and was running it wirelessly.

How do I make this printer work or clear the messages???

[Cherrynic]

So now the crazy thing is, that after all the repeat resets and changing plugs etc., I finally got it to work.  Got the ink in and even printed an item.

Next day it comes we this error message: OXB3103104

 Normally it has been  a workhorse going on 7 plus years!!!

[Cherrynic]

I Reset the printer again.  Its working.  So at end of day I will shut it off because I did get an  improperly shut off message.  Will let you know how it goes.

[Raj_05]

Hi @Cherrynic,

Welcome to HP Support Community.

Thank you for posting your query, I will be glad to help you.

It sounds like your HP DeskJet 3520 is having persistent error codes that might be linked to hardware or firmware issues. Since you’ve already tried several resets and had the printer briefly working, let’s try a few other troubleshooting steps to resolve the issue and stabilize the printer.

Steps to Fix HP DeskJet 3520 Error Codes:

Power Cycle the Printer:

• Turn off the printer.
• Unplug the power cord from the printer and the wall outlet.
• Wait for at least 60 seconds.
• Plug the printer back in directly to a wall outlet (avoid power strips/surge protectors).
• Turn the printer on.

Check for Firmware Updates:

• Go to the HP Support website and search for firmware updates for your DeskJet 3520. Sometimes error codes are caused by outdated firmware. Follow instructions to download and install any updates.
• You can also update the printer firmware using the HP Smart app.

Clear the Print Queue:

• Ensure no pending print jobs are stuck in the queue.
• On your PC/Mac, go to Devices and Printers > Right-click your printer and select See what's printing. Cancel any queued jobs and retry.

Reinsert Ink Cartridges Correctly:

• Turn off the printer.
• Open the ink cartridge door.
• Carefully reinsert the cartridges, making sure they are seated properly.
• Close the door and turn the printer back on.

Perform a Hard Reset:

• With the printer on, unplug the power cable from the back of the printer.
• Press and hold the power button for 15 seconds to clear any stored error conditions.
• Reconnect the power cable and turn on the printer.

Factory Reset: If the error codes persist, consider performing a factory reset. This will reset all settings on the printer.

• Turn the printer off.
• Hold down the Cancel and Wireless buttons simultaneously, then turn the printer on while holding them.
• Release the buttons when the printer turns on and see if the error persists.

[Raj_05]

Check for Mechanical Obstructions:

• Since the ink cartridges had issues getting back in, ensure there is no paper jam or any mechanical obstruction inside the printer. Open all accessible panels and carefully check for debris.

Error Code Specific Solutions:

• 0XB3103104: This code could indicate a firmware issue or memory corruption. Ensure the printer firmware is updated.
• 0X00759C98 Watchdog C: This typically relates to a communication problem between the printer’s internal components, often resolved with a reset or firmware update.
• 0XB20002C: Could indicate a more serious internal malfunction. If the reset doesn’t fix this, the printer might require service.

I hope this helps.

Take care and have a good day.

Please click “Accepted Solution” if you feel my post solved your issue, it will help others find the solution. Click the “Kudos/Thumbs Up" on the bottom right to say “Thanks” for helping!

Alden4

HP Support 

[Cherrynic]

This was very helpful information.  Problem still persists.  Thank you....

[Cherrynic]

Very much appreciate all the ideas.  Did try them all and problem still persists.