-
×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 Hardware and Upgrade Questions
- Re: UEFI Diagnosis Failure indicated

Create an account on the HP Community to personalize your profile and ask a question
02-17-2026 09:29 AM - edited 02-17-2026 09:39 AM
This coincided with a BIOS update that made the system very unstable. It took some time but I did get the uefi diagnostics to run outside of Windows properly.
Basic system description -
AMD 5700G with integrated Radeon graphics. 32 GB Ram, plenty of hard drive space (>500GB free)
Extensive system tests fail almost immediately on the processor, core 4 to be precise. The errors look like these and as you can see from the sample dates are very repeatable. All the other tests pass.
2026-02-16 08:59:39 Starting Graphical System Diagnostic Menu
2026-02-16 09:00:00 [L]> TimeZone: 300
2026-02-16 09:00:00 CPU Test Started
2026-02-16 09:00:00 [W]> Operation: Core 4 is failed
2026-02-16 09:00:01 [L]> Error Code=0x1F, Warranty ID = 9C2NK0-BHBD1F-QF8WW1-07VT03
2026-02-16 09:00:01 CPU Test Completed - Result 3
2026-02-16 09:00:53 [L]> Total Memory 32155MB, Free 31990MB (8189447 Pages)
2026-02-17 09:55:26 CPU Test Started
2026-02-17 09:55:26 [W]> Operation: Core 4 is failed
2026-02-17 09:55:27 [L]> Error Code=0x1F, Warranty ID = 9C2NK0-BHBD1G-QF8WW1-07SA03
2026-02-17 09:55:27 CPU Test Completed - Result 3
2 different error codes, information found for them is very sparse.
I should add - Running the AMD Ryzen Master Utility within Windows indicates no issues with the cores at all. It stress tests the processor and all items pass.
Given these conflicting results and the timing, right after a BIOS update, I continue to question whether the update had something to do with this error. Is there any way to rollback the BIOS on this machine as a final test, all the normal methods are locked out by HP.
I really don't want to pay for support for an issue that I question was caused by an HP recommended update.
Is this system most likely toasted?
Thanks
Solved! Go to Solution.
Accepted Solutions
02-18-2026 07:51 AM
Thank you Bill for your reply.
I downloaded and attempted to run OCCT. I am not familiar with the interface but it seemed to run without indicating errors initially. I cannot say it was 100% stable.
BIOS Update - Those procedures won't work for this system. I'd already tried them all but HP locks out a downgrade in BIOS version. The software picks that up and shuts down. Since I was already on the latest, F.39, I've been unable to fallback to any earlier ones.
That said, given the hours I've spent with this and the multitude of fixes attempted - I am moving on and have already ordered a replacement PC. Sadly, it's not an HP given this experience. I wanted something less proprietary and more open. So after a long succession of purely HP computers I am putting an end to it.
Thanks again
02-18-2026 06:30 AM - edited 02-18-2026 06:43 AM
Greetings @Train45
Download and run a CPU/memory stress test using OCCT (free) to confirm a processor problem.
You should back up system drive data before doing any modifications to your PC.
It is possible to do a USB BIOS recovery to an older BIOS version. The steps are available at this HP Site.
Scroll down to "Recover the BIOS using a USB recovery drive".
I believe this HP Site has the latest BIOS for your PC (F.39).
You can download BIOS version F.37 or earlier at the second HP site. Scroll down to "Revision history".
Make a USB recovery drive.
One problem you might encounter after reverting to a previous BIOS version is: HP stores the last Windows initiated BIOS update, the F.39 Windows executable: .bin and .sig files in the Windows EFI System partition.
So you may have to either clear those files located in the EFI System partition or back up data. Then do a clean Windows installation or a HP Cloud Recovery.
The unwanted BIOS version (F.39), located in the EFI System partition, might overwrite the older BIOS recovery version update, you have just completed, when you restart Windows.
Regards
02-18-2026 07:51 AM
Thank you Bill for your reply.
I downloaded and attempted to run OCCT. I am not familiar with the interface but it seemed to run without indicating errors initially. I cannot say it was 100% stable.
BIOS Update - Those procedures won't work for this system. I'd already tried them all but HP locks out a downgrade in BIOS version. The software picks that up and shuts down. Since I was already on the latest, F.39, I've been unable to fallback to any earlier ones.
That said, given the hours I've spent with this and the multitude of fixes attempted - I am moving on and have already ordered a replacement PC. Sadly, it's not an HP given this experience. I wanted something less proprietary and more open. So after a long succession of purely HP computers I am putting an end to it.
Thanks again