Victus 16-d1000 (650R1PA) - Constant ACPI_BIOS_ERROR after adding NVMe SSD > 1TB

[alireza_futir]

Hello HP Support Team and Community,

I am writing to report a critical and highly reproducible firmware bug on my HP Victus laptop. I am reporting this as a detailed technical issue for your engineering team to investigate for a future BIOS update, as it severely impacts the machine's core functionality and upgradeability.

System Information:

• Model: Victus by HP 16.1 inch Gaming Laptop PC 16-d1000

• CPU 12700, GPU 3060

• Current BIOS Version: AMI F.19 (Note: msinfo32 reports the date as 4/1/2025, which is highly unusual and may indicate an issue with this BIOS version itself).
  
  
  

---

Detailed Problem Description:

The system is perfectly stable with its stock 1TB NVMe SSD. However, the moment the total installed NVMe capacity exceeds 1TB (by adding a second SSD or replacing the primary with a larger one, e.g., 2TB), the system becomes critically unstable.

This instability manifests in two primary ways:

1. Boot Failure: The system frequently fails to boot, crashing with a Blue Screen of Death (BSOD) displaying the error code: ACPI_BIOS_ERROR.

2. Hardware Detection Failure: On the rare occasions the system successfully boots into the operating system, critical hardware components are not detected and are completely missing from the Device Manager. This specifically affects:

   • The NVIDIA GeForce RTX 3060 discrete GPU.

   • The High Definition Audio Controller.

This behavior is 100% OS-independent. I have confirmed the exact same hardware detection failures (missing GPU and audio) when booting from a Linux . This conclusively proves the issue lies within the low-level firmware (BIOS) and is not a Windows driver or OS problem.

This leads to a critical resource conflict: the memory address space that the BIOS incorrectly assigns to the new NVMe drive overlaps with the addresses already reserved for other essential PCIe devices, namely the NVIDIA GPU and the HD Audio controller.

This conflict perfectly explains all the symptoms:

• The ACPI_BIOS_ERROR is the OS reporting the invalid/conflicting ACPI tables it received from the BIOS.

• The disappearing GPU and Audio are the direct result of this resource conflict, as the OS cannot initialize two devices that claim the same address space.
  

Tested NVME SSD
1 TB samsung p990 + 1 TB samsung p980 
Single 2 tb Curssial MP600 Pro ( on Gen 4 Slot )
1 Tb SN550 + 256 GB NVME GEN 3
Combine 2 Low Voltage NVME GEN 3 => 1 Tb Sn550 + 1 Tb Patroit p300

Thank you for your time and for looking into this serious issue.
I can provide the serial number via a Private Message (PM) to an official HP representative if needed for further investigation.

[Hawks_Eye]

Hi @alireza_futir 

Welcome to the HP Support Community! We're here to help you get back up and running.

Thank you for detailing the issue so thoroughly. Based on the behavior you've described and the extensive testing you've conducted, this appears to be a firmware-level conflict affecting PCIe resource allocation when NVMe capacity exceeds 1TB on the Victus 16-d1000 series.

The symptoms — ACPI_BIOS_ERROR, missing GPU and audio controller, and OS-independent failures — strongly suggest that the BIOS is not correctly handling address space mapping for multiple or high-capacity NVMe SSDs. This results in overlapping memory regions between the SSD and other critical PCIe devices.

Suggested Actions

Here are steps you can take to help isolate and potentially mitigate the issue:

1. Reset BIOS to Default Settings

• Enter BIOS Setup by pressing Esc or F10 during startup.
• Navigate to Exit or Advanced tab and select Load Setup Defaults.
• Save and exit.

This has resolved similar detection issues for other users when installing multiple SSDs. You can refer to this HP Community thread for context.

 

2. Check Slot Configuration

• Ensure the Gen 4 SSD is installed in the designated Gen 4 slot (usually Slot 1).
• Use a Gen 3 SSD in the secondary slot if available.
• Avoid mixing high-power Gen 4 SSDs in both slots simultaneously, as this may increase resource demand.

 

3. Update BIOS

• Visit the HP Software and Driver Downloads page and enter your product model.
• Check for the latest BIOS version and compare it with your current version (F.19).
• If a newer version is available, follow the instructions to update safely.

 

4. Limit NVMe Capacity Temporarily

• If stability is critical, consider operating with a single SSD ≤1TB until a firmware update resolves the conflict.

 

You can also reference this HP Support Community post which outlines similar symptoms and SSD combinations.

Also, the serial number via private message and include all relevant logs for further assistance.

If my response helped, please mark it as an Accepted Solution! ✅ It helps others and spreads support. 💙 Also, tapping "Yes" on "Was this reply helpful?" makes a big difference! Thanks! 😊

Take care, and have an amazing day!

Regards, 

Hawks_Eye

[alireza_futir]

Thank you for your response @Hawks_Eye. I would like to confirm that I have already performed all suggested actions — and significantly more — across a comprehensive range of hardware and firmware configurations:

BIOS reset to defaults, including full CMOS clear via battery disconnect
Multiple NVMe combinations tested:
High-power Gen4 + Low-power Gen3 (e.g., Samsung 990 Pro + SN550)
Dual low-power Gen3 (e.g., 1TB SN550 + 1TB Patriot P300)
Single 2TB Gen4 SSD (Crucial MP600 Pro) in primary slot
Various brands, power draws, and firmware versions
Correct slot usage verified (Gen4 SSD in Slot 1)
All available BIOS versions tested, including F.19 and earlier releases

The result is 100% consistent:
With ≤1TB total NVMe capacity, the system operates normally.
When total NVMe capacity exceeds 1TB, the system fails with:

• ACPI_BIOS_ERROR (BSOD) during boot
• Complete disappearance of the NVIDIA GPU and HD Audio Controller in Device Manager
• Identical behavior on Windows and Linux, confirming this is firmware-level, not OS or driver-related

This reproducible failure indicates a BIOS-level PCIe resource allocation bug, where memory address space for larger NVMe drives overlaps with critical devices like the GPU and audio controller.

Given that:
The system is equipped with a 12th Gen Intel CPU (12700) and RTX 3060, both fully capable of handling multi-terabyte NVMe storage
Even older and budget laptops from other brands support >1TB NVMe without issue

…it is clear this is not a hardware limitation, but either a firmware bug or an undocumented artificial restriction imposed by HP in the BIOS.

This limitation severely undermines the laptop’s upgradeability. The second M.2 slot becomes effectively useless, and users are forced into a 1TB storage ceiling at a time when modern applications, games, and content routinely exceed this size.

I expect HP to immediately address this issue by releasing a corrected BIOS update to resolve the NVMe capacity limitation.

Until then, the lack of transparency and functionality is unacceptable for a device marketed as a gaming and performance laptop.
Thanks

[Hawks_Eye]

@alireza_futir 

Thanks for your clear and detailed report — you’ve done exceptional diagnostic work, and your conclusions are technically sound.

We sincerely thank you for your patience and co-operation during this troubleshooting process.

I'm sending you a private message to guide you on the next steps.

To access it, click the private message icon in the upper-right corner of your HP Support Community profile, next to your name.

If this resolves your issue, kindly mark this post as "Accepted Solution" and click "Yes" if it was helpful.

Take care and have a great day!

Regards,

Hawks_Eye

[alireza_futir]

@Hawks_Eye

Thank you for your response. However, I must clarify:

This is not a hardware issue, and no service order or physical repair can resolve it.

The problem is a firmware-level bug in the BIOS that fails to allocate PCIe resources correctly when total NVMe capacity exceeds 1TB — resulting in ACPI_BIOS_ERROR, GPU/audio disappearance, and OS-independent failure.

I have tested multiple drives, slots, BIOS versions, and operating systems. The behavior is 100% reproducible and directly tied to NVMe capacity, not hardware failure.

Raising a service ticket will not fix a software/firmware limitation.

What is needed is a BIOS update from HP's engineering team to correct the ACPI table handling and PCIe resource mapping.

I kindly request that this issue be escalated to the BIOS/firmware development team, as it affects the core upgradeability and functionality of the Victus 16-d1000 series.

I am ready to provide my serial number, logs, or assist in testing any pre-release firmware.

This is not a user-side problem — it’s a platform-level limitation that HP must address through a firmware update.

[Hawks_Eye]

@alireza_futir 

I understand your concern.

Looks like we may have to take remote access on your computer and assist yo further.

Again, these requests are best resolved by our phone support team.

Please check with them for further assistance.

Regards,

Hawks_Eye.

[alireza_futir]

@Hawks_Eye

I appreciate your response, but I must clarify — once again — that:

• This issue occurs before the OS loads (BSOD: ACPI_BIOS_ERROR)
• It happens on Windows, Linux, and even in BIOS setup
• There is no OS installed when I test drive detection
• The GPU and audio controller vanish from Device Manager due to PCIe resource conflict
• It is 100% tied to total NVMe capacity exceeding 1TB, regardless of brand, model, or power draw
• I have tested all BIOS versions, reset CMOS, tried all slot configurations

👉 This is not a software issue.
👉 This is not a driver issue.
👉 This is not something remote access can fix.
👉 This is not something phone support or a service order can resolve.

This is a firmware-level bug in the HP Victus 16-d1000’s BIOS that incorrectly maps PCIe memory regions when >1TB NVMe storage is installed.

Remote access cannot fix ACPI table errors.
Phone support cannot patch the BIOS.
A service center cannot repair a design flaw in firmware.

What is needed is a BIOS update from HP’s engineering team to fix PCIe resource allocation.

I have offered my full cooperation: serial number, logs, testing pre-release firmware — but instead, I’m being redirected to remote sessions and phone support.