-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
- HP Community
- Desktops
- Desktop Boot and Lockup
- HP OMEN 880-160se bricked in a firmware upgrade during W11 ...

Create an account on the HP Community to personalize your profile and ask a question
02-27-2022 10:55 AM
HP OMEN 880-160se appeared to have bricked in a firmware upgrade during W11 update. No display on booting up. Three long beeps followed by two short beeps, repeatedly. Tried recovery by turning off the computer. Press and hold the Windows + b keys, and continue to press those keys while pressing and holding the power button for 2 to 3 seconds. Release the power button, but continue pressing the Windows + b keys. The power light remains on, and the screen remains blank for about at least 20 minutes. No HP BIOS Update screen was displayed for a BIOS update.
Tried to press and release the power button, and then immediately press Windows + b keys at the same time, repeatedly, no HP BIOS Update screen. Press F2 repeatedly during start up did not bring up display. Appears to be bricked. It had been normally operating before a W11 update that prompted the fatal HP firmware update. Don't remember the firware version being upgraded to.
02-27-2022 12:04 PM
Hi:
According to the troubleshooting guide, it seems to me like there is a memory issue of some kind.
02-27-2022 05:19 PM
Thx. The HP PC had been normally operating before the W11 update that prompted the fatal HP firmware update. If there was a memory issue before the upgrade, the PC wouldn't have been operating normally, unless that version of firmware somehow killed the memory?
02-27-2022 05:52 PM
You're very welcome.
It may have been an unfortunate coincidence.
The easiest thing to do is if your PC has more than one memory chip, remove all of them and test each one in the primary memory slot and see if the PC will boot up.
If it does, keep testing the memory chips until you find the bad one. Then replace the defective chip.
If the PC fails to boot after testing all of the chips, then most likely something has happened to the motherboard.
The code is indicating bad memory.
How or why it happened is anybody's guess.
03-02-2022 08:37 AM
Thx. The plot thickens a bit here. The good news is that, by removing two 8 Gb ram chips from the two red slots, the PC came back to life. However, both removed ram chips are good when plugged in to the two black slots. So all four ram chips are good. However, when plugging back to red slots, the PC is dead again. It appears the the previous unsuccessful firmware upgrade killed a part of the motherboard as it relates to the two red slots only. Any was to further perform further diagnosis on the motherboard to pinpoint the issue or is this something else?