-
×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-130 Randomly Started Failing

Create an account on the HP Community to personalize your profile and ask a question
06-10-2025 01:30 PM
Can HP Omen PC 880-130 motherboard, MS-7A61 be updated without getting into Windows? It is currently running 8437 vF .52 06/15/2020. Online suggestions were reinstall Windows and that isn't working. Second suggestion was update the BIOS/Fireware. More details below about why.
Used some ChatGPT on the dmp files:
Summary
👉 Both of your dump files show identical Bugcheck codes:
KMODE_EXCEPTION_NOT_HANDLED (1e)
Exception code: c0000005 → Access violation (illegal memory access)
👉 The crashes are happening inside core Windows kernel functions:
First crash:
KeQueryInterruptTimePrecise
Second crash:
KiSetNextClockTickDueTime
👉 Common patterns:
Crashes are happening very early (System uptime only 43–97 seconds).
The exception address suggests this is happening deep inside Windows kernel, not in a 3rd-party driver.
You have Hyper-V enabled (Hypervisor present).
The same driver warning is showing up:
WARNING: Check Image - Checksum mismatch - BTHport.sys
→ BTHport.sys is the Bluetooth driver stack.
Computer will no longer boot into Windows 10 without BSOD. I can't get into safe mode. Initially I thought it might be a heat issue because if I let it sit for a bit, it seemed to load into Windows and work for about 1-2 minutes before BSOD. When it restarts and it shows on the screen it is trying to go into the HP Recovery, it will BSOD. Now it just BSOD constantly.
I attempted to rebuild it from USB drive create per Microsoft directions and it says hit any key to boot... starting up and then it too will BSOD.
I removed all extra components from the system. I had 4 memory chips so I tried them in sets of 2 attempting to find the issue. The MB has onboard video, so I used that and removed the 1080TI. I disconnected the SATA HD. I guess I did leave in the SSD, I didn't remove that. CD Drive removed.
BIOS appears to identify all components when they were installed.
Thanks.
06-11-2025 02:09 PM - edited 06-11-2025 02:11 PM
Welcome to our HP Community forum!
Based on the details provided by you about your OMEN by HP Desktop 880-130 with MS-7A61 motherboard, the system is experiencing consistent BSODs with KMODE_EXCEPTION_NOT_HANDLED (0x1E) and c0000005 access violations, which suggest kernel-level crashes due to illegal memory access. Here's a breakdown and analysis:
Key Observations:
BSODs occur within 1–2 minutes of booting, including while attempting:
Standard boot
Safe Mode
HP Recovery
Windows 10 USB installation media
DMP file analysis indicates:
Crash inside core Windows kernel routines
No third-party drivers involved
Checksum mismatch on BTHport.sys (Bluetooth stack)
Hyper-V is enabled
Attempts to isolate hardware (RAM, GPU, storage) did not resolve the issue
BIOS recognizes all hardware
Current BIOS version is F.52 (06/15/2020) -the latest official release from HP for this motherboard
Diagnosis:
These symptoms strongly suggest one of the following:
1. Faulty Motherboard or CPU (more likely the board):
Crashes occur even with minimal components attached.
Crashing during Windows Setup implies it's not a corrupted OS install, but a deeper hardware issue.
Crashes in fundamental kernel routines (KeQueryInterruptTimePrecise, KiSetNextClockTickDueTime) point to CPU instruction timing or chipset-related faults (e.g., a damaged clock controller, VRM instability, or northbridge-related issues on the motherboard).
2. RAM Slot or Controller Issue:
Even though RAM modules were swapped and tested in pairs, if a specific slot or the memory controller itself is defective, it can cause similar kernel crashes.
Recommend trying a single stick in different slots or running a MemTest86+ bootable test from USB if possible.
3. Corrupt BIOS (less likely, but possible):
If the BIOS is partially corrupted or experiencing voltage instability, it can pass POST but crash in OS kernel handoff.
A corrupted BTHport.sys could also be misleading, especially if the issue is happening at the instruction fetch level.
Recommendations:
1. Try Updating or Re-Flashing BIOS (outside Windows)
Yes, you can update the BIOS without Windows using the following:
How to Recover/Update BIOS Without Windows:
Download the BIOS .exe for your model
Visit HP Support and download the BIOS update package (F.52 or whichever the latest for OMEN 880‑130).Extract the firmware files onto a USB drive
On another Windows PC, run the downloaded .exe.
It should extract BIOS files and create a USB-ready image—don't install, just extract.
Copy the generated files to a FAT32-formatted USB flash drive (should include a .bin file or BIOS folder) HP Desktop PCs - Recovering the BIOS (Basic Input Output System) | HP® Support
Insert the USB into your OMEN and trigger recovery
With the PC turned off, insert the USB flash drive into a USB port.
Press and HOLD Windows + B, then press the Power button.
Continue holding Windows + B until you see a BIOS recovery prompt or hear beeps/see lights — this can take ~2 minutes: HP omen with bad bios flash… recovery? : r/HPOmen
Follow on-screen instructions
The system should locate the BIOS image and begin recovery or flashing.
The screen might go blank briefly, followed by rebooting once complete.
Tips & Troubleshooting:
Use a rear USB port directly on the motherboard—not front-panel ports.
If nothing happens: Try the Windows + V key combo on some HP models reddit.com.
If still unsuccessful:
Reformat the USB and re-copy the BIOS files.
Ensure the USB is FAT32 (not exFAT).
Try different USB ports and key combos.
2. Try Booting a Linux Live USB:
To eliminate OS-level or NT kernel-related causes:
Use Ubuntu or Fedora Live USB to check if the system crashes within minutes.
If it runs fine under Linux, the issue may be driver/Windows-related.
If it crashes in Linux, that all but confirms hardware failure.
3. Reset BIOS to Defaults:
Before doing anything else:
Enter BIOS (F10 at startup).
Load optimized defaults.
Disable Overclocking, if enabled.
Disable Hyper-V or virtualization, if possible.
4. Remove SSD:
Try booting from USB without the SSD connected at all.
If the SSD is failing (e.g., controller fault), it may BSOD when accessed.
5. Inspect Motherboard for Damage:
Look for:
Bulging/leaky capacitors
Burn marks or corrosion
Damaged VRMs near CPU socket
Conclusion:
At this point, it's very likely the motherboard is failing, especially since:
Crashes happen early and consistently
All software routes (repair, recovery, reinstall) fail
Hardware tests isolate no other faulty component
BSODs involve core kernel routines and occur even during fresh boot media startup
Next Steps:
Attempt BIOS recovery from USB as a last resort
If Linux Live USB also BSODs or hangs → replace the motherboard
- Your OMEN by HP Desktop PC - 880-130 is fitted with a Tampa2 motherboard (SSID: 8437)
- You can buy a replacement Tampa2 motherboard starting around $102: https://www.ebay.com/sch/i.html?_nkw=HP+Tampa2+motherboard+&_sacat=0&_from=R40&_sop=15.
Kind Regards,
NonSequitur777