PAGE_FAULT_IN_NONPAGED_AREA caused by ntoskrnl.exe BSOD

redsun66 · Nov 6, 2023

Hi everyone, please help me out by identifying the source of the BSOD and how to solve it. Much appreciated! Here is a WeTransfer link for my dump file: MIHAIROG-Mon_11_06_2023_222943_34.zip

Here's my specs
Microsoft Windows 11 Home (64-bit) 22H2 (10.0.22621)
13th Gen Intel® Core™ i7-13650HX

NVIDIA GeForce RTX 4050 Laptop GPU

16 GB

zbook · Nov 6, 2023

Whenever possible we would like to improve the website.

How come the posting instructions were not seen or followed?

What modifications if any would be useful?

redsun66 · Nov 6, 2023

My bad, I edited my post now hope it is okay.

zbook · Nov 6, 2023

For share links please use: OneDrive, Google Drive, or Dropbox

ubuysa · Nov 7, 2023

It's always risky making a diagnosis based on one dump, if you have other related dumps please upload those as well. However, in this one dump, the problem driver is nvlddmkm.sys, the Nvidia graphics driver. You can clearly see that the page fault bugcheck happens immediately after (and thus because of) the call to nvlddmkm.sys...

Code:

7: kd> knL
 # Child-SP          RetAddr               Call Site
00 ffffa804`6894efb8 fffff804`11e8b086     nt!KeBugCheckEx
01 ffffa804`6894efc0 fffff804`11cc0b3c     nt!MiSystemFault+0x207ab6
02 ffffa804`6894f0c0 fffff804`11e27529     nt!MmAccessFault+0x29c
03 ffffa804`6894f1e0 fffff804`3b91187a     nt!KiPageFault+0x369
04 ffffa804`6894f370 00000000`00000000     nvlddmkm+0x9187a

If we look more closely at frame 4, where nvlddmkm.sys is called...

Code:

7: kd> .frame /r 4
04 ffffa804`6894f370 00000000`00000000     nvlddmkm+0x9187a
rax=0000000000000000 rbx=ffffa57a7f9810f0 rcx=0000000000000a80
rdx=0000000000000000 rsi=ffffd485ff4274b8 rdi=ffffa57a7f9810f0
rip=fffff8043b91187a rsp=ffffa8046894f370 rbp=ffffd485ff4272d0
 r8=0000000000000a80  r9=ffffa8046894f420 r10=ffffa8046894f420
r11=0000000000000000 r12=0000000000000000 r13=ffffd48615e9b960
r14=ffffd485ff2d9000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00040246
nvlddmkm+0x9187a:
fffff804`3b91187a f3aa            rep stos byte ptr [rdi]

You can see at the bottom there that the failing instruction was a REP STOS BYTE instruction (used here to fill a string buffer) pointed to by the RDI register. Why was this a problem? If we look at the contents of the RDI address we can see...

Code:

7: kd> db ffffa57a7f9810f0
ffffa57a`7f9810f0  ?? ?? ?? ?? ?? ?? ?? ??-?? ?? ?? ?? ?? ?? ?? ??  ????????????????
ffffa57a`7f981100  ?? ?? ?? ?? ?? ?? ?? ??-?? ?? ?? ?? ?? ?? ?? ??  ????????????????
ffffa57a`7f981110  ?? ?? ?? ?? ?? ?? ?? ??-?? ?? ?? ?? ?? ?? ?? ??  ????????????????
ffffa57a`7f981120  ?? ?? ?? ?? ?? ?? ?? ??-?? ?? ?? ?? ?? ?? ?? ??  ????????????????
ffffa57a`7f981130  ?? ?? ?? ?? ?? ?? ?? ??-?? ?? ?? ?? ?? ?? ?? ??  ????????????????
ffffa57a`7f981140  ?? ?? ?? ?? ?? ?? ?? ??-?? ?? ?? ?? ?? ?? ?? ??  ????????????????
ffffa57a`7f981150  ?? ?? ?? ?? ?? ?? ?? ??-?? ?? ?? ?? ?? ?? ?? ??  ????????????????
ffffa57a`7f981160  ?? ?? ?? ?? ?? ?? ?? ??-?? ?? ?? ?? ?? ?? ?? ??  ????????????????

The address pointed to by the RDI register is invalid (not allocated, paged out (which is what the bugcheck indicates), or bad RAM). This is clearly either a problem with the nvlddmkm.sys driver or with the graphics card itself. The version of the nvlddmkm.sys driver you have installed is fairly recent, dating from 27th October 2023...

Code:

7: kd> lmDvmnvlddmkm
Browse full module list
start             end                 module name
fffff804`3b880000 fffff804`3f198000   nvlddmkm T (no symbols)         
    Loaded symbol image file: nvlddmkm.sys
    Image path: nvlddmkm.sys
    Image name: nvlddmkm.sys
    Browse all global symbols  functions  data
    Timestamp:        Fri Oct 27 00:24:56 2023 (653AD928)
    CheckSum:         0380BA63
    ImageSize:        03918000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

However, laptops often used customised versions of their graphics driver (and some others) for performance, operational, or power-saving reasons. This means that some generic drivers (such as from Nvidia) may not work properly in some laptops - because they lack the necessary customisation. I would be tempted to use DDU to remove the current graphics driver and then download and install the latest driver from the Asus website for your model of laptop. The one there is dated 24th July 2023.