Question Can someone help with my dmp file please ?

[paddymk01]

HI there, my pc is acting really weird and slow, the discord loading logo spins at like 5 fps and my whole system feels really unresponsive. It was find a couple days ago, but is now really messed up. Anyways, here's my dump file... Any help appreciated

Microsoft (R) Windows Debugger Version 10.0.25111.1000 AMD64
Copyright (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.

Dump completed successfully, progress percentage: 100


Path validation summary *
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 22000 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 22000.1.amd64fre.co_release.210604-1628
Machine Name:
Kernel base = 0xfffff8015080f000 PsLoadedModuleList = 0xfffff80151438650
Debug session time: Wed Jul 20 21:33:28.035 2022 (UTC + 1:00)
System Uptime: 0 days 0:30:31.699
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...............................
Loading User Symbols

Loading unloaded module list
.............................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff80150c26d00 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff808c2cb66d60=0000000000000050
10: kd> !analyze -v
***

• *
• Bugcheck Analysis *
• *

***

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: ffffc800411bf000, memory referenced.
Arg2: 0000000000000002, X64: bit 0 set if the fault was due to a not-present PTE.
bit 1 is set if the fault was due to a write, clear if a read.
bit 3 is set if the processor decided the fault was due to a corrupted PTE.
bit 4 is set if the fault was due to attempted execute of a no-execute PTE.
- ARM64: bit 1 is set if the fault was due to a write, clear if a read.
bit 3 is set if the fault was due to attempted execute of a no-execute PTE.
Arg3: fffff80361eca706, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)

Debugging Details:
------------------

KEY_VALUES_STRING: 1

Key : AV.Type
Value: Write

Key : Analysis.CPU.mSec
Value: 2092

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 6649

Key : Analysis.Init.CPU.mSec
Value: 1156

Key : Analysis.Init.Elapsed.mSec
Value: 7125

Key : Analysis.Memory.CommitPeak.Mb
Value: 101

Key : Bugcheck.DumpVsMemoryMatch
Value: True

Key : Dump.Attributes.AsUlong
Value: 1000

Key : WER.OS.Branch
Value: co_release

Key : WER.OS.Timestamp
Value: 2021-06-04T16:28:00Z

Key : WER.OS.Version
Value: 10.0.22000.1


FILE_IN_CAB: MEMORY.DMP

DUMP_FILE_ATTRIBUTES: 0x1000

BUGCHECK_CODE: 50

BUGCHECK_P1: ffffc800411bf000

BUGCHECK_P2: 2

BUGCHECK_P3: fffff80361eca706

BUGCHECK_P4: 0

READ_ADDRESS: ffffc800411bf000

MM_INTERNAL_CODE: 0

IMAGE_NAME: nvlddmkm.sys

MODULE_NAME: nvlddmkm

FAULTING_MODULE: fffff803616d0000 nvlddmkm

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME: System

TRAP_FRAME: ffff808c2cb67000 -- (.trap 0xffff808c2cb67000)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffc800411be000 rbx=0000000000000000 rcx=0000000000000400
rdx=000000000007f013 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80361eca706 rsp=ffff808c2cb67190 rbp=0000000000000000
r8=0000000000002e14 r9=000000000007e069 r10=0000000000000000
r11=ffff808c2cb671d0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nvlddmkm+0x7fa706:
fffff80361eca706 893488 mov dword ptr [rax+rcx*4],esi ds:ffffc800411bf000=????????
Resetting default scope

STACK_TEXT:
ffff808c2cb66d58 fffff80150ca68db : 0000000000000050 ffffc800411bf000 0000000000000002 ffff808c2cb67000 : nt!KeBugCheckEx
ffff808c2cb66d60 fffff80150a84cf6 : 0000000000000005 0000000000000002 ffff808c2cb66f60 0000000000000000 : nt!MiSystemFault+0x1d36ab
ffff808c2cb66e60 fffff80150c358f5 : fffff80353b405b1 0000000000000001 0000000000000003 0000000000000000 : nt!MmAccessFault+0x2a6
ffff808c2cb67000 fffff80361eca706 : ffffde867b3ce0b0 0000000000000028 fffff80361efbf69 fffff80361ec0100 : nt!KiPageFault+0x335
ffff808c2cb67190 fffff80362318a22 : 0000000000000003 ffffde867b3ce0b0 000000000000000f 0000000000000000 : nvlddmkm+0x7fa706
ffff808c2cb671e0 fffff803616e3603 : ffffde867b3c5000 fffff8030000000f 0000000000000000 0000000000050201 : nvlddmkm+0xc48a22
ffff808c2cb67280 fffff803622652a0 : 0000000000000001 ffff808c2cb67329 ffffde866b877000 00953cb300b3fcd1 : nvlddmkm+0x13603
ffff808c2cb672c0 fffff8036226dcfe : 0000000000000000 0000000000000005 0000000000000001 ffffde866b877000 : nvlddmkm+0xb952a0
ffff808c2cb67390 fffff80362542788 : 0000000000000001 0000000000000005 ffffde866b855000 0000000000000001 : nvlddmkm+0xb9dcfe
ffff808c2cb67410 fffff80362541fa7 : 0000000000000000 0000000000000000 0000000000000000 ffff808c00000002 : nvlddmkm+0xe72788
ffff808c2cb674e0 fffff8036256d2e6 : ffffde866b855000 ffff808c2cb67650 0000000000000001 0000000000000007 : nvlddmkm+0xe71fa7
ffff808c2cb67540 fffff80362580431 : fffff8036256d18f 0000000000000001 0000000000000002 00000000ffffffff : nvlddmkm+0xe9d2e6
ffff808c2cb67680 fffff80353b405b1 : 3042323932303200 ce010a3032313030 fffff88c38f296ed ffff808c2cb67781 : nvlddmkm+0xeb0431
ffff808c2cb676c0 fffff80353b3fe4e : 0000000000000080 ffff808c2cb67781 0000000000000000 0000000000000000 : dxgkrnl!DpiDxgkDdiSetPowerState+0x59
ffff808c2cb67720 fffff80353b40a2a : ffffde8677efc010 0000000000000000 0000000000000001 0000000000000000 : dxgkrnl!DpiFdoSetAdapterPowerState+0x17a
ffff808c2cb677e0 fffff80353b400c1 : ffffde866b6bf030 ffffde866c22a500 ffffde86697e4120 ffffde8677efc000 : dxgkrnl!DpiFdoHandleDevicePower+0x2ea
ffff808c2cb67880 fffff80353b41a30 : ffffde8677efc010 ffffde866b6bf180 ffffde866b6bf030 0000000000000000 : dxgkrnl!DpiFdoDispatchPower+0x21
ffff808c2cb678b0 fffff8036257d230 : 0000000000000000 ffff808c2cb67a79 0000000000000000 ffffde866b855000 : dxgkrnl!DpiDispatchPower+0xe0
ffff808c2cb679d0 fffff8036257c62e : ffffde866b6bf030 ffffde866b855000 ffffde86767b5040 ffffde8600000000 : nvlddmkm+0xead230
ffff808c2cb67ae0 fffff80150bbb277 : ffffde86767b5040 ffff808c2cb67b90 0000000000000000 ffff808c2cb67b00 : nvlddmkm+0xeac62e
ffff808c2cb67b10 fffff80150b3f415 : fffffffffa0a1f00 fffff80150bbb070 ffffde86794f8bb0 0000000000000094 : nt!PopIrpWorker+0x207
ffff808c2cb67bb0 fffff80150c2adb4 : ffffc80033c40180 ffffde86767b5040 fffff80150b3f3c0 0000000000000246 : nt!PspSystemThreadStartup+0x55
ffff808c2cb67c00 0000000000000000 : ffff808c2cb68000 ffff808c2cb61000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x34


SYMBOL_NAME: nvlddmkm+7fa706

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 7fa706

FAILURE_BUCKET_ID: AV_VRF_W_(null)_nvlddmkm!unknown_function

OS_VERSION: 10.0.22000.1

BUILDLAB_STR: co_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {3268b33e-4a6a-c96b-85fa-8ac0003be8dd}

Followup: MachineOwner
---------

10: kd> lmvm nvlddmkm
Browse full module list
start end module name
fffff803616d0000 fffff80364178000 nvlddmkm (no symbols)
Loaded symbol image file: nvlddmkm.sys
Image path: \SystemRoot\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_246e95e4066041ad\nvlddmkm.sys
Image name: nvlddmkm.sys
Browse all global symbols functions data
Timestamp: Fri Jun 24 00:18:39 2022 (62B4F4CF)
CheckSum: 029B99BD
ImageSize: 02AA8000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Information from resource tables:

 

[Colif]

Nvidia drivers caused it

Try running DDU in safe mode, remove old Nvidia drivers, restart into normal mode and either
1, get new drivers from Nvidia
2. Run windows update and let windows find older nvidia drivers

How To - How to perform a CLEAN install of your video card drivers.

Updated 9-19-19 How to do a CLEAN install of your graphics card drivers using the Wagnard tools Display Driver Uninstaller A major issue on many systems is the presence of multiple graphics card drivers or drivers that have been incompletely uninstalled followed by the installation of...

forums.tomshardware.com

I edited your post and removed a lot of unnecessary info in dump

 

[johnbl]

generally, it is best to also put the memory dump on a cloud server, share it for public access and post a link.

just looking at the text, I can see the memory address looks valid but was not. The first fix attempt would be to update the graphics driver as the above post recommends.

by posting the text only. We can not recommend other fixes for common issues that occur that cause the graphic driver to have this failure. For example, if you posted the dump file, we could look for these common root causes of this problem:
cpu overclock drivers,
gpu overclock drivers,
some game drivers known to corrupt memory,
modified windows files,
sound driver versions that corrupt GPU sound drivers,
storage driver versions that corrupt pagefile.sys
since the address look like a kernel address, this could also be a bios issue with memory timings.

just fyi,