-
×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
- AI PCs
- Computer keeps crashing

Create an account on the HP Community to personalize your profile and ask a question
10-12-2026 05:37 PM
My HP keeps crashing and I keep getting these messages. I just reset my computer two days ago because I was having issues with my audio. My computer was working find for a day and it started giving me issues today.
Solved! Go to Solution.
Accepted Solutions
10-14-2026 09:13 AM
Hi @Jesmp
Welcome to the HP Support Community! We're happy to have you on board!
To help us get started on resolving your issue, could you please share the product number of your device?
Meanwhile, I would request you to please follow the steps:
MEMORY_MANAGEMENT (0x1A) means Windows detected a severe memory management error. Since the crashes continue after reinstalling Windows, updating drivers, and updating BIOS, the next useful step is to identify whether the cause is hardware corruption or a specific driver.
Check the bug check details in the dump files.
- The stop code 0x0000001A is only the top-level bug check.
- Parameter 1 identifies the exact violation. Examples from Microsoft documentation include:
- 0x3f: in-page operation failed with a CRC error
- 0x403: page table and PFNs are out of sync, probably hardware error
- 0x411: a PTE has been corrupted
- 0x5003: working set free list is corrupted, probably hardware error
- 0x5200: free pool page corruption, possibly write-after-free in a driver
- Use the !analyze debugger extension on a minidump or memory dump to see which parameter value is being reported and what component is implicated.
Collect the crash dumps if the cause is still unclear.
- For ongoing random crashes, collect the minidump files from C:\Windows\Minidump.
- If deeper analysis is needed, collect a full OS memory dump.
Check for unstable drivers even if they are updated.
- Similar cases showed MEMORY_MANAGEMENT crashes caused by graphics drivers and anti-cheat or virtual drivers.
- If any third-party anti-cheat, low-level security, motherboard utility, or graphics driver software is installed, test without it where possible.
- For graphics drivers, one accepted resolution in a similar case was to completely remove the current Nvidia driver and install a slightly older stable version.
Recheck RAM and firmware-related stability.
- Microsoft documentation recommends running the Windows Memory Diagnostic tool.
- Similar cases recommend a more thorough RAM test such as MemTest86 with multiple passes when crashes continue.
- If memory overclocking or XMP is enabled, disable it and test at default settings. This is especially relevant when memory corruption appears random.
If dump analysis is inconclusive, use Driver Verifier carefully.
- In a similar case, Driver Verifier was suggested to force Windows to expose a faulty driver.
- Warning: Driver Verifier can intentionally trigger additional crashes while testing. Create a restore point first.
- If Windows becomes hard to start afterward, boot to Recovery, enter Safe Mode, and run:
- verifier /reset
- verifier /bootmode resetonbootfail.
We're looking forward to helping you get back up and running!
Best regards,
I'm an HP Employee.
If this reply helped resolve your issue, please select the Accept as Solution as it helps others in the community quickly find the answer they’re looking for.
And if you found this reply helpful, clicking Yes below is a great way to let us know we’re providing the support you need, as it encourages us to keep improving and sharing helpful guidance.
10-14-2026 09:13 AM
Hi @Jesmp
Welcome to the HP Support Community! We're happy to have you on board!
To help us get started on resolving your issue, could you please share the product number of your device?
Meanwhile, I would request you to please follow the steps:
MEMORY_MANAGEMENT (0x1A) means Windows detected a severe memory management error. Since the crashes continue after reinstalling Windows, updating drivers, and updating BIOS, the next useful step is to identify whether the cause is hardware corruption or a specific driver.
Check the bug check details in the dump files.
- The stop code 0x0000001A is only the top-level bug check.
- Parameter 1 identifies the exact violation. Examples from Microsoft documentation include:
- 0x3f: in-page operation failed with a CRC error
- 0x403: page table and PFNs are out of sync, probably hardware error
- 0x411: a PTE has been corrupted
- 0x5003: working set free list is corrupted, probably hardware error
- 0x5200: free pool page corruption, possibly write-after-free in a driver
- Use the !analyze debugger extension on a minidump or memory dump to see which parameter value is being reported and what component is implicated.
Collect the crash dumps if the cause is still unclear.
- For ongoing random crashes, collect the minidump files from C:\Windows\Minidump.
- If deeper analysis is needed, collect a full OS memory dump.
Check for unstable drivers even if they are updated.
- Similar cases showed MEMORY_MANAGEMENT crashes caused by graphics drivers and anti-cheat or virtual drivers.
- If any third-party anti-cheat, low-level security, motherboard utility, or graphics driver software is installed, test without it where possible.
- For graphics drivers, one accepted resolution in a similar case was to completely remove the current Nvidia driver and install a slightly older stable version.
Recheck RAM and firmware-related stability.
- Microsoft documentation recommends running the Windows Memory Diagnostic tool.
- Similar cases recommend a more thorough RAM test such as MemTest86 with multiple passes when crashes continue.
- If memory overclocking or XMP is enabled, disable it and test at default settings. This is especially relevant when memory corruption appears random.
If dump analysis is inconclusive, use Driver Verifier carefully.
- In a similar case, Driver Verifier was suggested to force Windows to expose a faulty driver.
- Warning: Driver Verifier can intentionally trigger additional crashes while testing. Create a restore point first.
- If Windows becomes hard to start afterward, boot to Recovery, enter Safe Mode, and run:
- verifier /reset
- verifier /bootmode resetonbootfail.
We're looking forward to helping you get back up and running!
Best regards,
I'm an HP Employee.
If this reply helped resolve your issue, please select the Accept as Solution as it helps others in the community quickly find the answer they’re looking for.
And if you found this reply helpful, clicking Yes below is a great way to let us know we’re providing the support you need, as it encourages us to keep improving and sharing helpful guidance.