-
×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
- Notebooks
- Notebook Hardware and Upgrade Questions
- IRQ Test Failed/100% Disk Use Issues

Create an account on the HP Community to personalize your profile and ask a question
07-31-2018 05:57 PM
After running HP PC Hardware Diagnostics, the IRQ Test failed (Failure ID: 0LPT3D-7NW96L-GXGJMF-88ET13). I was told that replacing my hard drive would fix the issue. However, I previously ran a full disk check and no issues were found. Furthermore, I read in a similar thread that enabling virtualization in the BIOS will result in the IRQ Test failing as a result of a glitch within the testing software, and since my virtualization is enabled this could have resulted in a potential false positive test fail.
On the other hand, I do find my disk usage constantly at 100% when checking Task Manager during startup and throughout use. I have tried disabling Windows Update, Windows Search Indexer, Windows BITS, updated drivers, etc. and still have 100% usage. It could make sense that my disk would need replacing but I also read that there could also be other issues within the motherboard that flagged the IRQ Test fail.
I greatly appreciate any assistance!
Solved! Go to Solution.
08-01-2018 03:50 PM
My ethernet driver was disabled which led to the failed IRQ Test. However, my disk usage still is usually 100% on startup and throughout use despite many different implemented efforts to correct it. Thank you for the reference to the other thread!
08-01-2018 08:30 PM - edited 08-01-2018 08:37 PM
You're very welcome. Happy to hear you at least solved the IRQ error. As for the 100% disk useage-that is the subject of several posts here on the forum.An internet search shows many people complaining about this on machines from several of the big OEMs. Most here seem convinced it is an HP problem when it is reported on numerous sites on numerous machines.
You may find a suggestion that helps as some claim to have found-while others still have the problem after a year or longer.
For instance, MS offers this:
**Click Accept as Solution on a Reply that solves your issue**
***Click the "YES" button if you think this response was helpful.***