Windows 10: Need help to read a memory dump file to figure out why pc crashesh. Thanks a lot in advance !

Hello hello,Lastly my pc crashes every day, when the pc crashes I don't get a blue screen or error messages but a black screen before restarting by itself. I ran 2 days ago 2 stress-tests on my cpu, my rams and my graphics cards with Memtest 86, OCCT and Furmark, I even reinstalled my graphics card driver with ddu. But none of the programs show even the slightest problem. So I'm trying to understand the source of the problem with memory dumps that indicate ntkrnlmp.exe but I don't know what the pronleme is in my memory dump. If someone could tell me what the problem is, thanks again in advance

:)

 

Need help to read a memory dump file to figure out why pc crashesh. Thanks a lot in advance !

Hello hello,

Lastly my pc crashes every day, when the pc crashes I don't get a blue screen or error messages but a black screen before restarting by itself. I ran 2 days ago 2 stress-tests on my cpu, my rams and my graphics cards with Memtest 86, OCCT and Furmark, I even reinstalled my graphics card driver with ddu. But none of the programs show even the slightest problem. So I'm trying to understand the source of the problem with memory dumps that indicate ntkrnlmp.exe but I don't know what the pronleme is in my memory dump. If someone could tell me what the problem is, thanks again in advance!

Here is my memory dump:

Microsoft (R) Windows Debugger Version 10.0.22621.3233 AMD64

Copyright (c) Microsoft Corporation. All rights reserved.





Loading Dump File [C:\Users\movic\OneDrive\Bureau\livedump (2).DMP]

Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.



Symbol search path is: srv*

Executable search path is:

Windows 10 Kernel Version 22631 MP (16 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Edition build lab: 22621.1.amd64fre.ni_release.220506-1250

Machine Name:

Kernel base = 0xfffff802`3d600000 PsLoadedModuleList = 0xfffff802`3e213110

Debug session time: Thu Apr 25 17:52:07.845 2024 (UTC + 2:00)

System Uptime: 0 days 0:04:33.456

Loading Kernel Symbols

...............................................................

................................................................

................................................................

........................

Loading User Symbols

UserMode Module List Address is NULL (Addr= 00007ffa`407f53f0)

This is usually caused by being in the wrong process

context or by paging

Loading unloaded module list

........

For analysis of this file, run !analyze -v

0: kd> !analyze -v

Page 87a773 too large to be in the dump file.

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************



LIVE_SYSTEM_DUMP (161)

The system administrator requested the collection of a live system memory dump.

(This code can never be used for a real BugCheck.)

Arguments:

Arg1: 005461736b6d6772

Arg2: 0000000000000000

Arg3: 0000000000000000

Arg4: 0000000000000000



Debugging Details:

------------------



Page 79059a not present in the dump file. Type ".hh dbgerr004" for details

Page 87a773 too large to be in the dump file.



KEY_VALUES_STRING: 1



Key : Analysis.CPU.mSec

Value: 1718



Key : Analysis.DebugAnalysisManager

Value: Create



Key : Analysis.Elapsed.mSec

Value: 2118



Key : Analysis.Init.CPU.mSec

Value: 156



Key : Analysis.Init.Elapsed.mSec

Value: 9606



Key : Analysis.Memory.CommitPeak.Mb

Value: 100



Key : WER.OS.Branch

Value: ni_release



Key : WER.OS.Timestamp

Value: 2022-05-06T12:50:00Z



Key : WER.OS.Version

Value: 10.0.22621.1





FILE_IN_CAB: livedump (2).DMP



DUMP_FILE_ATTRIBUTES: 0x10

Live Generated Dump



BUGCHECK_CODE: 161



BUGCHECK_P1: 5461736b6d6772



BUGCHECK_P2: 0



BUGCHECK_P3: 0



BUGCHECK_P4: 0



PROCESS_NAME: Taskmgr.exe



STACK_TEXT:

ffffac07`c3b66d50 fffff802`3e0990c3 : 00000000`00000000 ffffac07`c3b66e20 00000000`00000000 00000000`00000000 : nt!IopLiveDumpCollectPages+0xd9

ffffac07`c3b66da0 fffff802`3e0aa9fb : ffffffff`ffffffff ffffffff`ffffffff ffffac07`c3b66e20 00000000`00000000 : nt!IopLiveDumpEndMirroringCallback+0x33

ffffac07`c3b66dd0 fffff802`3df4c204 : 00000000`00000000 00000000`00000000 ffff9c08`98902620 ffffac07`c3b66fc0 : nt!MmDuplicateMemory+0x2ff

ffffac07`c3b66e60 fffff802`3e0988a3 : 00000000`00000001 ffffac07`c3b66ed0 ffff9c08`9fa49cb0 00000000`00000000 : nt!IopLiveDumpCapture+0x78

ffffac07`c3b66ec0 fffff802`3df4a11e : ffff9c08`98902620 ffff9c08`98902620 ffffaf08`f3343508 00000000`00000000 : nt!IopLiveDumpCaptureMemoryPages+0x4b

ffffac07`c3b67000 fffff802`3db39d1c : 00000000`00000000 ffffac07`c3b67360 00000000`00000000 7fffffff`fffffffc : nt!IoCaptureLiveDump+0x406

ffffac07`c3b67240 fffff802`3ded25ab : ffff9c08`00000020 ffffffff`800068b4 ffff9c08`b684d960 ffff9c08`b6d54350 : nt!DbgkCaptureLiveKernelDump+0x354

ffffac07`c3b672d0 fffff802`3da2d938 : ffff9c08`00000025 00000028`dd72e430 00000000`00000048 00000000`00000000 : nt!NtSystemDebugControl+0x18461b

ffffac07`c3b673f0 00007ffa`40712cf4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28

00000028`ddd7fa58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`40712cf4





SYMBOL_NAME: nt!IopLiveDumpCollectPages+d9



MODULE_NAME: nt



IMAGE_NAME: ntkrnlmp.exe



STACK_COMMAND: .cxr; .ecxr ; kb



BUCKET_ID_FUNC_OFFSET: d9



FAILURE_BUCKET_ID: LKD_0x161_nt!IopLiveDumpCollectPages



OS_VERSION: 10.0.22621.1



BUILDLAB_STR: ni_release



OSPLATFORM_TYPE: x64



OSNAME: Windows 10



FAILURE_ID_HASH: {c95dd00b-6eb9-64bd-a19e-51918d07cbac}



Followup: MachineOwner

 

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

 

Need Help in reading memory dump

Hi Tawqeer Khursheed,

Your memory dump files just indicates a generic memory (RAM) corruption no specific driver is listed.

Did you PC only crash once?

Is there no minidump files in C:\Windows\Minidump?