Solved! BSOD nvlddmkm.sys

enochjohn90

Junior Member
Dec 9, 2022
8
1
11
Hi, so the issue that I'm currently having is my laptop suddenly got BSOD with nvlddmkm.sys and the first error was system thread exception not handled. and then I follow some instructions from internet and do a clean installation of windows but still got the same error. I noticed that I don't have nvlddmkm.sys inside my C:\Windows\System32\drivers. then i do the expand command and copy the nvlddmkm.sys from the nvidia to system32\drivers. Now still got the BSOD and the error turned to Page Fault In Non-Paged Area. Do you guys have any clues that I can use to fix this? Thank you! (Here's the link for the mini dump https://drive.google.com/file/d/1nh_y_nhl6X5zkdle21tDVVv_hXXpxb4A/view?usp=sharing)
 

enochjohn90

Junior Member
Dec 9, 2022
8
1
11
here's the content of the mini dump to make it easier for u guys.


*******************************************************************************
* *
* 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: ffffda79fc5df058, 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: fffff8084c5e8703, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)

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


KEY_VALUES_STRING: 1

Key : AV.Type
Value: Write

Key : Analysis.CPU.mSec
Value: 2967

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 18206

Key : Analysis.IO.Other.Mb
Value: 31

Key : Analysis.IO.Read.Mb
Value: 0

Key : Analysis.IO.Write.Mb
Value: 39

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

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

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

Key : Bugcheck.Code.DumpHeader
Value: 0x50

Key : Bugcheck.Code.Register
Value: 0x50

Key : Dump.Attributes.AsUlong
Value: 8

Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1


FILE_IN_CAB: 121022-13156-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

BUGCHECK_CODE: 50

BUGCHECK_P1: ffffda79fc5df058

BUGCHECK_P2: 2

BUGCHECK_P3: fffff8084c5e8703

BUGCHECK_P4: 2

READ_ADDRESS: fffff806558fb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
ffffda79fc5df058

MM_INTERNAL_CODE: 2

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

TRAP_FRAME: fffff204ceba6960 -- (.trap 0xfffff204ceba6960)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffda79b0000000 rbx=0000000000000000 rcx=0000000013177c16
rdx=000000004c5df05a rsi=0000000000000000 rdi=0000000000000000
rip=fffff8084c5e8703 rsp=fffff204ceba6af0 rbp=00000000bdafd300
r8=00000000bdafd300 r9=fffff204ceba6b10 r10=ffff8f8fae9a4a90
r11=fffff204ceba6b10 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe cy
nvlddmkm+0x88703:
fffff808`4c5e8703 891c88 mov dword ptr [rax+rcx*4],ebx ds:ffffda79`fc5df058=????????
Resetting default scope

STACK_TEXT:
fffff204`ceba66b8 fffff806`5503421d : 00000000`00000050 ffffda79`fc5df058 00000000`00000002 fffff204`ceba6960 : nt!KeBugCheckEx
fffff204`ceba66c0 fffff806`54e399e0 : fffff204`ceba6908 00000000`00000002 fffff204`ceba69e0 00000000`00000000 : nt!MiSystemFault+0x1dc80d
fffff204`ceba67c0 fffff806`55008dd8 : ffff8f8f`ae4d5000 fffff204`ceba6a09 ffff8f8f`aebd8710 ffff8f8f`ae4d6a5c : nt!MmAccessFault+0x400
fffff204`ceba6960 fffff808`4c5e8703 : 00000000`bdafd300 00000000`bdafd300 ffff8f8f`ae9a3028 ffff8f8f`ae9a3028 : nt!KiPageFault+0x358
fffff204`ceba6af0 00000000`bdafd300 : 00000000`bdafd300 ffff8f8f`ae9a3028 ffff8f8f`ae9a3028 00000000`4c5df000 : nvlddmkm+0x88703
fffff204`ceba6af8 00000000`bdafd300 : ffff8f8f`ae9a3028 ffff8f8f`ae9a3028 00000000`4c5df000 00000000`00000000 : 0xbdafd300
fffff204`ceba6b00 ffff8f8f`ae9a3028 : ffff8f8f`ae9a3028 00000000`4c5df000 00000000`00000000 00000000`00000020 : 0xbdafd300
fffff204`ceba6b08 ffff8f8f`ae9a3028 : 00000000`4c5df000 00000000`00000000 00000000`00000020 fffff808`4c680c71 : 0xffff8f8f`ae9a3028
fffff204`ceba6b10 00000000`4c5df000 : 00000000`00000000 00000000`00000020 fffff808`4c680c71 00000000`4c5df05a : 0xffff8f8f`ae9a3028
fffff204`ceba6b18 00000000`00000000 : 00000000`00000020 fffff808`4c680c71 00000000`4c5df05a ffff8f8f`ae9a2000 : 0x4c5df000


SYMBOL_NAME: nvlddmkm+88703

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 88703

FAILURE_BUCKET_ID: AV_W_(null)_nvlddmkm!unknown_function

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {838100fa-f28b-2ef7-d702-e31713cb338c}

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

Shmee

Memory & Storage, Graphics Cards Mod Elite Member
Super Moderator
Sep 13, 2008
7,407
2,440
146
It's Lenovo Legion Y520 with Nvidia GTX1050Ti.
1050Ti isn't too old, is the laptop under warranty still with Lenovo? One more thing you could try would be to run memtest86, to be sure it is not just bad system RAM. But it sounds like a GPU problem.
 
  • Like
Reactions: enochjohn90

enochjohn90

Junior Member
Dec 9, 2022
8
1
11
1050Ti isn't too old, is the laptop under warranty still with Lenovo? One more thing you could try would be to run memtest86, to be sure it is not just bad system RAM. But it sounds like a GPU problem.
Okay so I just finished the memtest86 and there's no error. So what could be the problem? :'