HP Desktop with Memphis2-S (HP 2B2C) motherboard does 6 long beeps and then boots normally

[hibreak]

Good day,

today after turing power on on my extension cord today, and booting up my pc, the pc tried to boot and it failed, afterwards I think it automatically tried again, giving me beeps in response. Tried restarting it then, more beeps. Later on, I tried replugging the power cable, and all the other ones on the extension cord, but nothing changed. Although, after hearing the beeps, the computer seemed to keep running normally, so I pressed F1, (which I normally do to turn on my PC, beacuse it doesn't detect my fan and it gives me a warning every time I boot it up, but I doubt this issue is conntected to the beeps) and after some time, my mouse lights up and so too my two monitors, and it just starts normally as nothing happened. Tried restarting it, beeps again, F1, starts normally. Below I am attaching the output of running Open Hardware Monitor with temps and such:

 

What seems to be the problem? How can I get rid of the beeps? Thank you for all your help upfront 🙂

[A_Gayathri · Accepted solution]

Hi @hibreak,

Welcome to The HP Support Community.  

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

I understand you are getting the 6 long beeps you're hearing from your HP Pavilion Desktop with the Memphis2-S motherboard typically indicate a hardware issue. 

Here’s a breakdown of what these beeps might mean and some steps to troubleshoot the issue:

1. Understanding the Beep Codes:

• 6 Long Beeps: This often points to a problem with the keyboard controller. It might also indicate an issue with the motherboard or other hardware components.

2. Troubleshooting Steps:

Check the Keyboard:

• Reconnect the Keyboard: Disconnect and reconnect the keyboard to ensure it's securely connected. Try a different keyboard if you have one available.
• Inspect the Keyboard: Look for any visible damage or issues with the keyboard.

Check Internal Components:

• Reseat Components: Open the case and reseat components such as RAM, GPU, and any other expansion cards. Ensure that all cables and connections are secure.
• Check for Dust: Dust buildup can cause poor connections. Clean the inside of your PC with compressed air.

Update BIOS:

• Check for BIOS Updates: Sometimes, updating the BIOS can resolve hardware compatibility issues. Visit the HP support website to see if there’s a BIOS update available for your model.

Perform a Hard Reset:

• Power Down: Turn off the PC, unplug it from the power source, and hold down the power button for 30 seconds. Then, plug it back in and try booting it up.

Test with Minimal Hardware:

• Boot with Minimal Components: Disconnect all peripherals except for the keyboard and monitor. Remove any additional hardware such as extra RAM sticks or expansion cards and try booting up.

Check System Health:

• Run Diagnostics: Use HP’s built-in diagnostics tool (if available) or third-party tools to check the health of your system components.

3. Fan Detection Issue:

Since you mentioned a fan detection warning and pressing F1 to continue, this could be related to the beeping. Ensure that:

• Fan is Properly Connected: Check if the fan is properly connected to the motherboard.
• Fan is Functional: Verify that the fan is working correctly.

Refer to this document:  HP Pavilion Desktop - 500-502nw 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. 

[hibreak]

Hello, thank you for your reply,

the issue went away after one day of posting this thread, I believe, the only thing that changed, is that the warning screen for the fan is gone, but still needs me to press f1 for the computer to boot, although I am used to pressing it so quickly that I might be pressing it before it even appears hah, something to test for later. If the issue comes back, your advice might prove helpful. Thanks for the link to the manual as well.

Once more, I appreciate your reply, have a good one.

PS. Not sure if I should set your reply as the answer here, as it sort of fixed itself generally speaking.

[A_Gayathri]

HI @hibreak ,

Thank you for your response. If you need further assistance feel free to reach out to us. 

If the information I've provided was helpful, give us some reinforcement by clicking the Accept as Solution and on the public post, that'll help us and others see that we've got the answers!

Have a great day ahead!