Windows

[Melkiy]

Вітаю) підкажіть, маю ноутбук hp, при спробі установки системи не ініціалізується(синій екран відновлення) в uefi жорсткий диск (ssd поставив точно робочий) ініціалізацію проходить, все ок, може щось підкажете як вилікувати?

[NonSequitur777]

@Melkiy,

The fact that the SSD is visible in the UEFI settings is a good sign, but it only confirms that the motherboard can detect the drive. It does not necessarily mean that Windows can initialize or boot from it.

A few things could cause the blue recovery screen during OS installation:

1. Confirm the exact error message/code

   The blue recovery screen usually provides a stop code (for example: INACCESSIBLE_BOOT_DEVICE, 0xc000000f, etc.). Please provide the exact message because it will help identify the cause.

2. Check the BIOS storage settings

   Enter BIOS Setup (usually by pressing F10 during startup) and check:

   • Boot mode: UEFI (recommended for Windows 10/11)
   • Secure Boot: enabled or disabled can both work, depending on the installation media
   • Storage controller mode: if there is an option for AHCI versus RAID/Intel VMD, the setting must match what Windows expects.

   Many newer HP laptops use Intel VMD/RAID mode, and Windows Setup may require the Intel Rapid Storage Technology (RST) driver to see or properly initialize the SSD.

3. Try reinstalling Windows cleanly

   If you have already attempted an installation:

   • Boot from a freshly created Windows installation USB using Microsoft's Media Creation Tool.
   • At the drive selection screen, delete all existing partitions on the SSD (after confirming there is no important data).
   • Allow Windows Setup to recreate the required GPT/UEFI partitions automatically.

4. Check the SSD health and compatibility

   Even if the SSD works in another computer, verify:

   • Is it an NVMe M.2 SSD or a SATA SSD?
   • Is it the original HP drive or a replacement?
   • Is the laptop model compatible with that SSD type?

5. Run HP diagnostics

   Press Esc during startup, then select F2 HP PC Hardware Diagnostics and run the storage test. This can sometimes detect issues that are not obvious in BIOS.

Could you provide:

• The exact HP laptop model (for example: EliteBook 840 G8, Pavilion 15, etc.)
• The Windows version you are installing (Windows 10 or 11)
• The exact blue recovery screen message/error code
• The SSD model (for example Samsung 990 Pro, WD Black SN770, etc.)

With those details, I can narrow down whether this is a driver, BIOS configuration, or SSD compatibility issue.

Kind Regards / З повагою,

NonSequitur777

[Melkiy]

Вибачте, не мав доступу до інтернету(( в тестах hp пише що все ок, але взагалі без ссд проблема така ж сама...  є підозра що проблема в південному мості, але це не точно... хоча при різних збірках самого віндовса( при ініціалізації флешки) помилка не завжди однакова, тобто іноді видає картинку з надписами іноді просто синій екран... 

[Melkiy]

hp rtl8723be це модель ноутбука, ссд стоїть працюючий, перевіряв в іншому пк(велрам 512гб звичайний )

[NonSequitur777]

@Melkiy,

OK, based on this crucial update, you can immediately eliminate the SSD as the source of the problem. If the laptop exhibits shifting, inconsistent blue screens or text errors while merely initializing the USB installer -even with the SSD completely removed- the issue lies entirely in the hardware environment handling the initial boot phase.

Additionally, "HP RTL8723BE" is not the laptop's model number; it is the model of the internal Realtek Wi-Fi / Bluetooth network card. However, this is actually an excellent clue, as it identifies the laptop as an older generation model (manufactured roughly between 2014 and 2017, such as the HP 15-f, 15-ay, 15-ba, or 250 G4/G5 series).

The changing nature of the errors ("sometimes inscriptions, sometimes just a blue screen") strongly points to data corruption or hardware instability during the boot process.

Please follow these targeted troubleshooting steps:

1. Test the RAM Modules (The Highest Probability Cause):

Inconsistent, shifting blue screen errors during the OS initialization phase are the classic hallmark of failing or unstable RAM. When a specific memory block is corrupted, Windows will throw a completely different error depending on what file it tried to load into that broken sector.

• The Fix: open the laptop's back panel. If there are two sticks of RAM, remove one and try booting the USB installer. If it still crashes, swap it with the other stick. Testing the modules individually in different slots will quickly isolate a bad RAM stick or a failing motherboard slot.

2. Physically Remove the Wi-Fi Card:

Ironically, because you specifically read the model off the Wi-Fi card, it warrants attention. On this specific era of HP budget laptops, a failing or short-circuiting mini-PCIe/M.2 wireless card is notorious for causing erratic hardware interrupts. This can crash the motherboard right as the Windows kernel attempts to initialize generic network drivers during setup.

• The Fix: unscrew and physically pull the Realtek RTL8723BE card out of its slot, then try booting the USB installer again.

3. Change How the Windows USB Drive is Created:

Because this generation of HP laptops sits right on the generational fence of UEFI maturity, its BIOS can behave erratically with modern, strictly-partitioned UEFI installation media. If the flash drive was burned with a corrupt segment or a partition scheme the motherboard doesn't fully support, it will drop data during initialization.

• The Fix: Recreate the installation media using a different, high-quality USB flash drive. Instead of the standard Media Creation Tool, use a program like Rufus.
• If the laptop BIOS is set to UEFI, configure Rufus to GPT / UEFI (non-CSM).
• If the laptop BIOS has Legacy Support / CSM enabled, configure Rufus to MBR / BIOS or UEFI.

4. Hardware Fault (Southbridge / APU):

Your suspicion regarding a failing chip (like the Southbridge or the integrated processor/PCH) is a valid final resort. If the chip handling the USB controllers or the low-power PCIe lanes is failing under load due to degraded solder joints or thermal stress, it will cause sporadic crashes.

• However, you should absolutely rule out the RAM, Wi-Fi card, and a faulty USB stick first, as these are much easier and cheaper to fix than a dead motherboard.

To help you narrow this down further, let me know:

• Did you run the Extensive/Looping RAM test in HP Diagnostics, or just the Quick Test?
• Do you have the ability to try a different USB flash drive or a different USB port (switching between a USB 2.0 and USB 3.0 port)?

Kind Regards,

NonSequitur777

[Melkiy]

Дякую за підказки, вечором зроблю) ще в мене є підозра на біос... коли я намагаюся завантажити його відновлення з материнки(win+b потім павер 2-3 сек і відпускаю, ) ноут дає ознаки життя, запускає куллер, є моргання капса(2 рази, як на мене короткі) але екран не показує жодної інфи...

[NonSequitur777]

@Melkiy,

Thank you for the update. The fact that BIOS recovery (Win + B) does not display anything on the screen is not, by itself, proof that the BIOS is corrupted.

The 2-blink Caps Lock code is actually significant. On many HP consumer notebooks from that generation, 2 blinks typically indicate a BIOS corruption or BIOS authentication failure, although the exact meaning varies somewhat by model and BIOS family.

However, before assuming the BIOS chip is damaged, consider the following:

1. Win+B recovery only works under very specific conditions.
   • The recovery partition or recovery image must still be intact.
   • The embedded recovery code in the BIOS must still be functional.
   • The key combination timing must be correct.
   • On some models, Windows + V works instead of Windows + B.
2. A blank screen during BIOS recovery can also occur if the system never reaches the recovery routine.
   This can happen because of:
   • defective RAM
   • motherboard faults
   • failed embedded controller (EC)
   • unstable power delivery

3. The most important clue remains this:

   The laptop crashes while booting Windows installation media even with the SSD completely removed.

   At that stage, Windows is running entirely from the USB drive and RAM. The SSD is not involved yet, so the problem is almost certainly elsewhere.

   I would still troubleshoot in this order:

• Test each RAM module individually (or reseat the single module if only one is installed).
• Try another USB flash drive and recreate the Windows installer.
• Try another USB port.
• Disconnect the Wi-Fi card temporarily.
• Reset the BIOS to factory defaults (if you can still enter BIOS Setup).

 

Regarding the BIOS:

If the notebook consistently gives a 2-blink Caps Lock code on every power-on, then a BIOS problem becomes much more likely.

Could you also tell me:

• What is the exact HP product number (P/N) from the bottom sticker? It will look something like N5Y32EA#UUW or X7J56EA#ABA.
• Does the notebook still enter BIOS Setup (F10), or is the screen always blank?
• Does it always blink exactly two times, or does the pattern repeat continuously?

Those answers will help determine whether this is likely a recoverable BIOS issue or whether the motherboard itself is beginning to fail.

Kind Regards,

NonSequitur777

[Melkiy]

Дякую за допомогу) память перевіряв, і плашки і слоти, навіть запускав без неї( запускається режим схожий до відновлення біоса, але капс моргає інакше), міняв і плашки і місця, те саме..., викручував вай фай, теж результат той самий, помилка та сама... змінював накопичувачі, їх обєми, способи запису, юсб порти, і так далі... в біос заходив, все скидав, те саме...

[Melkiy]

Product:Z5A81EA#ACB

Serial:CND703486T

[NonSequitur777]

@Melkiy,

You've done an excellent job eliminating the common causes! At this point, there are very few possibilities left.

The fact that your notebook:

• passes the HP hardware diagnostics,
• enters BIOS normally,
• detects the SSD,
• produces the correct "no RAM" blink code when memory is removed,
• but crashes before Windows Setup can initialize,

suggests that the firmware is reaching POST successfully but something fails when control is handed over to the operating system.

Since you mentioned earlier that BIOS Recovery (Win+B) never displays the recovery screen, I would now focus on the BIOS itself.

Could you check which BIOS version is currently installed? You can usually find it on the BIOS Main page (something like F.xx).

If it is not the latest version available from HP, I would try updating the BIOS using HP's official BIOS update package or, if necessary, by creating an HP BIOS Recovery USB drive on another Windows PC.

If the BIOS is already the latest version and the behavior remains unchanged after reflashing it, then I believe the problem is most likely a motherboard hardware fault. It may be a failing SPI flash chip, embedded controller, chipset (PCH), or another component involved in handing control from the firmware to the Windows boot environment.

One final question:

Can you successfully boot from anything other than Windows?

For example:

• Ubuntu Live USB
• Linux Mint Live USB
• MemTest86 (the standalone USB version)

If none of those boot either, that would strongly indicate a hardware or firmware problem rather than a Windows installation issue.

One additional suggestion:

I would actually add Linux or MemTest86 to the troubleshooting before declaring the motherboard bad.

If:

• Windows 10 installer crashes,
• Windows 11 installer crashes,
• Ubuntu Live also crashes,
• MemTest86 won't even start,

-then you've essentially proven that the failure occurs before any operating system is involved. At that point, I'd be comfortable saying the motherboard (or its firmware) is almost certainly at fault.

This is a very systematic troubleshooting process, and thanks to your testing, you're now down to the last few plausible causes.

Kind Regards,

NonSequitur777