power failure on fax sending

[lanebqs]

I get a power failure message and printer reboot during a fax send transmission.  I have already set resolution to standard, speed to slow, and error correction off according to searched response.  It has NOT corrected the issue.  Please help

[A_Gayathri]

Hi @lanebqs,

Welcome to The HP Support Community.  

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

I understand you've already taken some steps to troubleshoot the issue, but let's delve a bit deeper. Here are some additional steps you can try:

• Check Power Source: Ensure that the printer is plugged into a stable power source and that there are no fluctuations or interruptions in the power supply. Sometimes, using a surge protector or a different power outlet can help stabilize the power flow.
• Update Firmware: Check if there are any firmware updates available for your HP Color LaserJet Pro MFP M283fdw. Updating the firmware can often resolve issues related to power failures and improve overall performance.  Update the firmware on an HP printer
• Check Fax Settings: Double-check all fax settings to ensure they are configured correctly. Pay special attention to settings related to fax transmission speed, resolution, and error correction.
• Test with Different Documents: Sometimes, specific documents can cause issues during fax transmission. Try sending different types of documents to see if the problem persists with all documents or if it's specific to certain ones.
• Reset Printer: If the issue continues, try performing a factory reset on your printer. This will reset all settings to their default values, which can sometimes resolve persistent issues.

Refer to this document: HP Color LaserJet Pro MFP M283fdw User manual

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. 

[lanebqs]

Ive done all that with no success.  This problem happened when I first bought the printer in 2021. There was a configuration fix that was applied and fixed it.  recently the factory reset button was inadvertently pushed and the issue has come back.  I dont recall the fix.