Windows 10: Windows 10 Memory dump file

I want help here to analyze this Memory.dmp file created.


[COLOR=rgba30, 30, 30, 1]Microsoft R Windows Debugger Version 10.0.21306.1007 AMD64Copyright c Microsoft Corporation. All rights reserved.Loading Dump File [C:\Windows\MEMORY.DMP]Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.************* Path validation summary **************Response Time ms LocationDeferred srv*Symbol search path is: srv*Executable search path is: Windows 10 Kernel Version 19041 MP 4 procs Free x64Product: WinNt, suite: TerminalServer SingleUserTSEdition build lab: 19041.1.amd64fre.vb_release.191206-1406Machine Name:Kernel base = 0xfffff802`16400000 PsLoadedModuleList = 0xfffff802`1702a490Debug session time: Thu Mar 25 20:56:13.587 2021 UTC + 5:30System Uptime: 5 days 23:19:52.727Loading Kernel Symbols........................................................................................................................................................................................................Loading User SymbolsLoading unloaded module list..................................................For analysis of this file, run [/COLOR][COLOR=rgba0, 0, 255, 1]!analyze -v[/COLOR][COLOR=rgba30, 30, 30, 1]nt!KeBugCheckEx:fffff802`167f5c50 48894c2408 mov qword ptr [rsp+8],rcx ss:fffff682`796ed740=000000000000013a0: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************KERNEL_MODE_HEAP_CORRUPTION 13aThe kernel mode heap manager has detected corruption in a heap.Arguments:Arg1: 0000000000000012, Type of corruption detectedArg2: ffff9f03eee02100, Address of the heap that reported the corruptionArg3: ffff9f03f276b000, Address at which the corruption was detectedArg4: 0000000000000000Debugging Details:------------------KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 18921 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 22862 Key : Analysis.Init.CPU.mSec Value: 2233 Key : Analysis.Init.Elapsed.mSec Value: 11144 Key : Analysis.Memory.CommitPeak.Mb Value: 73 Key : WER.OS.Branch Value: vb_release Key : WER.OS.Timestamp Value: 2019-12-06T14:06:00Z Key : WER.OS.Version Value: 10.0.19041.1BUGCHECK_CODE: 13aBUGCHECK_P1: 12BUGCHECK_P2: ffff9f03eee02100BUGCHECK_P3: ffff9f03f276b000BUGCHECK_P4: 0CORRUPTING_POOL_ADDRESS: ffff9f03f276b000 Nonpaged poolBLACKBOXBSD: 1 [/COLOR][COLOR=rgba0, 0, 255, 1]!blackboxbsd[/COLOR][COLOR=rgba30, 30, 30, 1]BLACKBOXNTFS: 1 [/COLOR][COLOR=rgba0, 0, 255, 1]!blackboxntfs[/COLOR][COLOR=rgba30, 30, 30, 1]BLACKBOXPNP: 1 [/COLOR][COLOR=rgba0, 0, 255, 1]!blackboxpnp[/COLOR][COLOR=rgba30, 30, 30, 1]BLACKBOXWINLOGON: 1PROCESS_NAME: SystemSTACK_TEXT: fffff682`796ed738 fffff802`1698da88 : 00000000`0000013a 00000000`00000012 ffff9f03`eee02100 ffff9f03`f276b000 : nt!KeBugCheckExfffff682`796ed740 fffff802`1698dae8 : 00000000`00000012 fffff682`796ed850 ffff9f03`eee02100 00000000`00000a44 : nt!RtlpHeapHandleError+0x40fffff682`796ed780 fffff802`1698d715 : ffff9f03`f277f4c0 ffff9f03`eee02280 ffff9f03`eee02100 fffff802`1664caf2 : nt!RtlpHpHeapHandleError+0x58fffff682`796ed7b0 fffff802`1682d5df : 00000000`00000000 ffffd38e`14000100 fffff802`17050d40 fffff802`1664cc64 : nt!RtlpLogHeapFailure+0x45fffff682`796ed7e0 fffff802`1664cc64 : 00000000`00000103 00000000`00000000 00000000`00000000 00000000`00000000 : nt!RtlpHpVsContextFree+0x1df48ffffff682`796ed880 fffff802`16db1019 : 00000000`00000000 00000000`00000000 00000000`00000000 01000000`00100000 : nt!ExFreeHeapPool+0x4d4fffff682`796ed960 fffff802`166b95ef : ffff9f03`f277f720 ffff9f03`f277f4e0 ffff9f03`f277f520 00000000`00000000 : nt!ExFreePool+0x9fffff682`796ed990 fffff802`166b6fb0 : 00000000`00000000 ffffd38e`2b58a1d0 ffff9f03`f277f4e0 01000000`00100000 : nt!MiDeleteControlArea+0x77fffff682`796ed9e0 fffff802`16a3e368 : 00000000`000000a6 00000000`000800a1 fffff802`17050d40 ffffd38e`2b58a1d0 : nt!MiDereferenceControlAreaProbe+0x24fffff682`796eda10 fffff802`167843bd : 00000000`00000001 00000000`00000000 fffff682`796edae0 ffff9f03`f277f4e8 : nt!MiSegmentDelete+0xf4fffff682`796eda60 fffff802`167b9249 : 00000000`00000000 fffff802`00000001 00000000`00000000 00000000`00000000 : nt!MiProcessDereferenceList+0xc1fffff682`796edb20 fffff802`16717e85 : ffff9f03`f215b040 ffff9f03`f215b040 00000000`00000080 fffff802`167b9120 : nt!MiDereferenceSegmentThread+0x129fffff682`796edd50 fffff802`167fd2a8 : fffff802`12859180 ffff9f03`f215b040 fffff802`16717e30 00000000`00000000 : nt!PspSystemThreadStartup+0x55fffff682`796edda0 00000000`00000000 : fffff682`796ee000 fffff682`796e8000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28SYMBOL_NAME: nt!ExFreePool+9IMAGE_NAME: Pool_CorruptionMODULE_NAME: [/COLOR][COLOR=rgba0, 0, 255, 1]Pool_Corruption[/COLOR][COLOR=rgba30, 30, 30, 1]STACK_COMMAND: .thread ; .cxr ; kbBUCKET_ID_FUNC_OFFSET: 9FAILURE_BUCKET_ID: 0x13a_12_nt!ExFreePoolOS_VERSION: 10.0.19041.1BUILDLAB_STR: vb_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {0e8bc89c-9b1f-e697-ed6c-83210db041e2}Followup: Pool_corruption---------[/COLOR]

:)

 

Memory dump file?

Don't know if this will help you or not?
http://support.theplanet.com/kb/ope...d-memory-dump-files-windows-creates-debugging

 

Windows 10 Tweaks

Pressing “Windows+Pause Break” (it’s up there next to scroll lock) opens the “System” Window.

Windows 10: In the new version of Windows, Explorer has a section called Quick Access. This includes your frequent folders and recent files. Explorer defaults to opening this page when you open a new window. If you’d rather open the usual This PC, with links to your drives and library folders, follow these steps:

• Open a new Explorer window.
• Click View in the ribbon.
• Click Options.
• Under General, next to “Open File Explorer to:” choose “This PC.”
• Click OK

credit to Lifehacker.

 

Windows 10 isnt creating memory dumps

It should still be doing a dump whether it's just from kernel space or kernel plus user space. It's possible the crashes your PC is experiencing are not allowing for a memory dump to be created. It's happened to me before when I've been pushing my overclock to far. Instead of the sad face BSOD I've gotten a hard lockup that prevented a memory dump.

This might be worth looking over.
Configure Windows 10 to Create Minidump on BSOD