-
×InformationWindows update impacting certain printer icons and names. Microsoft is working on a solution.
Click here to learn moreInformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center.
-
×InformationWindows update impacting certain printer icons and names. Microsoft is working on a solution.
Click here to learn moreInformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center.
- HP Community
- Archived Topics
- Unanswered Topics - Notebook
- Who Me Too'd this topic
Create an account on the HP Community to personalize your profile and ask a question
03-11-2020 05:02 AM - edited 03-11-2020 09:13 AM
Hello guys
We're facing several random BSOD with many new Zbook laptops, mostly "Memory_management", "Bad_system_config_info", "System_service_exception"
All drivers are up to date, video/memory/hard drive tests were all done succesfully.
I've tried to reimage some of those laptops but the problem persists, most of those "Memory_management" blue screens occur on lock screen when the session is locked, and the modules that caused them are ntoskrnl.exe & ntkrnlmp.exe.
here is the last crash dump Analysis :
Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump
On Wed 11/03/2020 09:39:58 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!memset+0x50D6E)
Bugcheck code: 0x1A (0x41792, 0xFFFFC58027BF1E50, 0x1010100000, 0x0)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred. A corrupted PTE has been detected.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Thanks for your help.