cancel
Showing results for 
Search instead for 
Did you mean: 

Processors

khal_bob
Adept I

Ryzen 7 5700X: black screens and system halt during gaming

Hello, everybody! 

Recently, I've been having issues with my system. During some gameplay sessions (I usually do some Assetto Corsa Competizione), and even while watching some videos, my system halts, video signal dies and the computer becomes unresponsive. 

In my research for a solution, I have come across this topic in this forum, with a similar issue. The processor series is the same, Ryzen 7 5700, main difference is the specific model: mine is a 5700X, while theirs is a 5700G.

My setup is as follows:

  • Processor: Ryzen 7 5700X
  • Motherboard: Asus TUF GAMING X570-PLUS/BR
  • 2x Kingston Fury 16GB 3200 GHz DDR4 KF432C16BB/16
  • Asus DUAL-RTX2060-O6G-EVO
  • Storage:
    • 1x 240 GB NVMe SSD
    • 1x 480 GB SATA SSD
    • 1x 1 TB SATA SSD
    • 1x 4 TB SATA HD

Is there a way to find something in the system logs (I run Windows 10 Pro 21H2) that might point me towards a solution?

Thanks in advance!

1 Solution
khal_bob
Adept I

It happened again today, friends. Since this error first appeared when I switched my mobo and CPU 2 months ago, I thought the new processor would be the culprit. The following memory dump proves me wrong. Anyway, I deeply thank each and every one of you who commented here. I will mark this as solved and run to the Nvidia forums to find a solution.

Microsoft (R) Windows Debugger Version 10.0.25200.1003 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\112122-11265-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff800`6dc00000 PsLoadedModuleList = 0xfffff800`6e82a2b0
Debug session time: Mon Nov 21 20:40:38.185 2022 (UTC - 3:00)
System Uptime: 0 days 2:32:04.800
Loading Kernel Symbols
...............................................................
................................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
......
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff800`6dff92d0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffc808`a786f3f0=0000000000000050
14: 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: ffffc808a7870058, memory referenced.
Arg2: 0000000000000000, 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: fffff80089f50684, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)

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

*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

Key : AV.Type
Value: Read

Key : Analysis.CPU.mSec
Value: 3764

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 78059

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

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

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

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

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

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

Key : Bugcheck.Code.DumpHeader
Value: 0x50

Key : Bugcheck.Code.Register
Value: 0x50

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.1


FILE_IN_CAB: 112122-11265-01.dmp

BUGCHECK_CODE: 50

BUGCHECK_P1: ffffc808a7870058

BUGCHECK_P2: 0

BUGCHECK_P3: fffff80089f50684

BUGCHECK_P4: 2

READ_ADDRESS: fffff8006e8fb390: 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
ffffc808a7870058

MM_INTERNAL_CODE: 2

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

TRAP_FRAME: ffffc808a786f690 -- (.trap 0xffffc808a786f690)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000006 rbx=0000000000000000 rcx=0000000000000012
rdx=00000000000000ff rsi=0000000000000000 rdi=0000000000000000
rip=fffff80089f50684 rsp=ffffc808a786f820 rbp=ffffc808a786f878
r8=0000000000000001 r9=0000000000000002 r10=00000000000003b0
r11=fffff8008a985990 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz ac po nc
nvlddmkm+0x120684:
fffff800`89f50684 4c396cd5e8 cmp qword ptr [rbp+rdx*8-18h],r13 ss:0018:ffffc808`a7870058=????????????????
Resetting default scope

STACK_TEXT:
ffffc808`a786f3e8 fffff800`6e03421d : 00000000`00000050 ffffc808`a7870058 00000000`00000000 ffffc808`a786f690 : nt!KeBugCheckEx
ffffc808`a786f3f0 fffff800`6de399e0 : fffff800`6dff5440 00000000`00000000 ffffc808`a786f710 00000000`00000000 : nt!MiSystemFault+0x1dc80d
ffffc808`a786f4f0 fffff800`6e008dd8 : 00000000`00000000 fffff800`6df9cca2 00000000`00000003 00000000`00000100 : nt!MmAccessFault+0x400
ffffc808`a786f690 fffff800`89f50684 : fffff800`8a985a86 00000000`00000000 00000000`00000000 ffffa38a`12c68000 : nt!KiPageFault+0x358
ffffc808`a786f820 fffff800`8a985a86 : 00000000`00000000 00000000`00000000 ffffa38a`12c68000 ffffa38a`12c68056 : nvlddmkm+0x120684
ffffc808`a786f828 00000000`00000000 : 00000000`00000000 ffffa38a`12c68000 ffffa38a`12c68056 ffffc808`000003ba : nvlddmkm+0xb55a86


SYMBOL_NAME: nvlddmkm+120684

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 120684

FAILURE_BUCKET_ID: AV_R_(null)_nvlddmkm!unknown_function

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {f899ea14-805d-2454-345d-ba405310c43d}

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

14: kd> lmvm nvlddmkm
Browse full module list
start end module name
fffff800`89e30000 fffff800`8d65d000 nvlddmkm T (no symbols)
Loaded symbol image file: nvlddmkm.sys
Image path: \SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_ade64cd54ec2f9ed\nvlddmkm.sys
Image name: nvlddmkm.sys
Browse all global symbols functions data
Timestamp: Tue Oct 25 16:58:05 2022 (63583FCD)
CheckSum: 0373C52C
ImageSize: 0382D000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Information from resource tables:

View solution in original post

0 Likes
30 Replies
ThreeDee
Paragon

What power supply make/model are you running?

You can check your systems Event Viewer for logged errors under Windows Logs>System


ThreeDee PC specs
0 Likes

My power supply is a Corsair RM750x, 750W. More than enough to power this system and with a breathing room for a GPU upgrade.

I'll be sure to check Event Viewer when I get home, thank you for the info.

0 Likes

PSU's go bad .. just something to consider

Are you running any cable extenders INSIDE your case? ..and/or a PCIe riser cable?


ThreeDee PC specs
0 Likes

I checked the event viewer. Unfortunately, there was nothing there that could provide a hint to a solution. However, there is an error log message about an unexpected shutdown ocurred on november 10th, at 01:03 (GMT+3).  I forced a shutdown due to the error I reported on my original post.

khal_bob_0-1668349737504.png

 

0 Likes
strahyp
Journeyman III

I'm currently having the same issue and i've never had it happen before until the last few days. It's driving me insane and i can't play any game without fully losing signal to all my monitors forcing me to restart. my event timer always gives me these two errors 

SCEP Certificate enrollment initialization for WORKGROUP\DESKTOP-JUQ9R9D$ via https://AMD-KeyId-578c545f796951421221a4a578acdb5f682f89c8.microsoftaik.azure.net/templates/Aik/scep failed:

GetCACaps

Method: GET(16ms)
Stage: GetCACaps
The server name or address could not be resolved 0x80072ee7 (WinHttp: 12007 ERROR_WINHTTP_NAME_NOT_RESOLVED) 

and 

SCEP Certificate enrollment initialization for Local system via https://AMD-KeyId-578c545f796951421221a4a578acdb5f682f89c8.microsoftaik.azure.net/templates/Aik/scep failed:

GetCACaps

Method: GET(31ms)
Stage: GetCACaps
The server name or address could not be resolved 0x80072ee7 (WinHttp: 12007 ERROR_WINHTTP_NAME_NOT_RESOLVED)

I have no idea what to do about this situation 

0 Likes
DimkaTsv
Miniboss

Try to disable MPO
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Dwm]
"OverlayTestMode"=dword:00000005

Currently there are a lot of issues that are caused by MPO. So won't hurt to try

0 Likes

What is MPO?

0 Likes

DimkaTsv_0-1668355670113.png

2 second search

0 Likes
Volkdude85
Challenger

You might have a trojan or your firewall is blocking stuff, some of those errors are definitely outbound. I have had better luck with Malwarebytes for getting rid of (most stuff). it does not like windows hacks in any way shape or form so babysit if you are KMS edition. Might be easier to just nuke the OS and start fresh. 

0 Likes

Have you tried https://learn.microsoft.com/en-us/sysinternals/downloads/process-explorer 

it contains an option to scan all running processes against virustotal, which is like 76 antivirus programs. Do not be alarmed if some chinese one returns a false positive. 

0 Likes
MADZyren
Paragon

From your link: "system is not responsive anymore and needs a hard reset via power off/on switch at the PSU"

When I encountered this, it was with overclocked memory pushed too far. 

First thing I would to is disable XMP/DOCP from BIOS to lower memory clockspeed. If this fixes it, you could try enabling XMP again and increasing memory voltage to 1.375-1.4V but not really higher than those.

If you have overclocked your CPU, you might have to increase CPU voltage a bit or simply let it run at designed speed. (disable PBO or whatever manual overclock you use)

If neither of those fix it, try running the machine with one memory stick installed at a time. Before removing anything, take a picture of where memory sticks are installed if this is something new to you so you know where they are supposed to be (in which slots)

What is your power supplies brand, model, wattage, age?

If your computer is connected to an extension cord, try connecting straight to wall or to another wall socket.

0 Likes
Volkdude85
Challenger

Yeah im questioning wattage a 2060 is a 180watt card and you are running two of them. 340 watt/12V 28.33 amps on your 12 volt rail for the GPUs alone.  pull a GPU, if it is stable get a gigger PSU.  voltage does drop the more wire it travels through because copper is not a super conductor. Id go large single 12v rail as it will mean a bigger capacitor.  I would not SLI under 1000w and Really I would try to go bigger, and really you are better off buying one Great card then 2 base.   Panasonic makes the best caps.  I also like pwm fans in my PSU so it stays quiet. 

0 Likes
Darkowler
Journeyman III

you are not alone, 

rx6600

3700x

asus B450M gaming plus II

Using the GPU Smart Access Memory Function in bios. 

1tb sk hynix gold ssd

500gb sk ssd

2x 4 tb wb external my books

64 gigs Vengeance RT

2 1080p monitors, 

one monitor set at 240hz

the other at 60hx

I have been getting black screens

ctrl alt del, with sometimes cause it to reanimate the system, 

it has also been corrupting the windows operating system, but I use Acronis backup thanks to wd HDDs so in a matter of minutes I am back up and running with a good known install. I have done everything to remedy the situation. today screens went black and the file explorer state in windows was completely unresponsive. 

going into cmd prompt, using cmd SFC /scannow it will find errors in windows after a black screen situation.

i was hoping the last update fixed this but its still remains. 

 

 

0 Likes

Wattage?? Your card is 132 watt. your running alot of drives. are the mybooks powered off the mb?  

0 Likes

no, they have their own dedicated power supply. and even if they are removed the problem is still there. As I said the AMD Driver is corrupting the operating system when it goes black. I am also running an EVGA 750 GQ Power Supply it has no issues at all. verified in another system I have during extended load and benchmark testing. 

0 Likes
Darkowler
Journeyman III

I only have 2 external drives with their own power supply. 

0 Likes
ed6698
Adept III

Is anyone having this issue happened to of used MSI Afterburner?

I just got over having a issue similar to this. I recently changed my gpu, I used to run AB on my old card. Before changing gpu I set AB to no longer start with Windows. After changing gpu I would have constant crashes of video. DDU and new drivers did nothing to help. I just so happened to start AB a few days later, low and behold even though it was not set to start with Windows anymore, it was still applying the OC profile to card at startup, that OC was more than the new gpu could handle. I hit reset on AB, which removed the applied OC profile and uninstalled AB, never have had a problem anymore. 

Just thought I would post this, as I found this with AB just by chance.

Asus ROG Crosshair VIII Dark Hero - Ryzen 5950X - Noctua NH D15 Chromax Black - 4x8GB 32Gb GSkill DDR4 3800 - Asus RTX 3070 TUF OC V2 - Samsung 980 Pro, 970 Evo Plus, Corsair Force GT - Super Flower 1000W Leadex SE Platinum
0 Likes

that is a common issue in the silicon lottery but you have to make sure the system is stable first. 

as per my previous post, this is a driver-related issue. I simply unplugged the second monitor and no more black screen. keeping the cable plugged into the PC to verify the cable was not at fault, then removing the first monitor the same way as the first and second monitor is stable. only when both are hooked up is it causing a flickering or full freeze black screen. the only thing I haven't verified is setting both refresh rates the same as the slower second. I would rather just use my one 240hz monitor until they sort out the driver issues. I still love you AMD. Just keep making driver updates for the bugs. I want to buy a 7900xt but I need stability for Competition use. 

0 Likes

The issue I mentioned about has nothing to do with silicone lottery. I was pointing out a potential bug with MSI Afterburner, applying a OC profile even though it was not set to start with Windows. I should have specified in my post to original OP, just in case OP happened to use AB at some point in time. Sorry for the confusion.

Asus ROG Crosshair VIII Dark Hero - Ryzen 5950X - Noctua NH D15 Chromax Black - 4x8GB 32Gb GSkill DDR4 3800 - Asus RTX 3070 TUF OC V2 - Samsung 980 Pro, 970 Evo Plus, Corsair Force GT - Super Flower 1000W Leadex SE Platinum
0 Likes

at the very least the more information we get out the better no matter the issue for the devs. stay away from update 2h22 until they fix it. I'm currently running windows 10, windows 11 still has issues playing friendly with ryzen hardware. 

0 Likes

Tbh sitting at Win 11 22H2 myself. Have no obvious performance issues.
Because problems only can appear if you have 2 CCD CPU (~900X, ~950X), and not 1 CCD (~600 ~700 ~800 ~800X3D)

0 Likes

i was still seeing 15 to 20 fps drops on 2h22

0 Likes

Shader cache rebuilding possibly?
They can happen irregularly. 
Like here.

DimkaTsv_0-1668436749632.png

DimkaTsv_1-1668436755300.png


Looks like stuttery mess on graph, but in fact it is all right in game. Shader caching and transitions between locations and cutscenes.

0 Likes

AB done did me dirty Yo, Wasn't working so good for me either. 

I like https://getfancontrol.com/

It was recommended on Jayz2cents YouTube channel it is free and plays nice with ALL my fans it also does multi sensor monitoring and curves 

https://www.youtube.com/watch?v=uDPKVKBMQU8&t=831s

0 Likes

Well, for me FanControl can only monitor my GPU fan speed. It cannot actually set such speed. But only for GPU. I still use it for other fans. Good stuff

0 Likes
Darkowler
Journeyman III

I did some custom tuning on my 6600 and got 30 fps more on average, stock specs were watt limited to around 80 for some reason. I have always had constant crash issues with the 6600 but now it seems way more stable, I haven't tried hooking up the other monitor back up yet to see if that issue is fixed yet. I noticed during testing it wasn't even reaching the factory setting boost clock no matter how much of a stress test I put on the card.

increased power draw limits by 2 percent at a time until it would reach max boost frequency it was stable, increased the allowed boost frequency by 10 percent increased voltage until it would reach max frequency, increased fan curve significantly and it hovers around 80c under full extended load.  

0 Likes
khal_bob
Adept I

So, it happend once again last tuesday. I had a look at the event viewer and at the memory dump, and the error was *drumroll* the NVIDIA driver. More specifically, Nvlddmkm.sys. I will provide the details when I get home.

khal_bob
Adept I

It happened again today, friends. Since this error first appeared when I switched my mobo and CPU 2 months ago, I thought the new processor would be the culprit. The following memory dump proves me wrong. Anyway, I deeply thank each and every one of you who commented here. I will mark this as solved and run to the Nvidia forums to find a solution.

Microsoft (R) Windows Debugger Version 10.0.25200.1003 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\112122-11265-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff800`6dc00000 PsLoadedModuleList = 0xfffff800`6e82a2b0
Debug session time: Mon Nov 21 20:40:38.185 2022 (UTC - 3:00)
System Uptime: 0 days 2:32:04.800
Loading Kernel Symbols
...............................................................
................................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
......
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff800`6dff92d0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffc808`a786f3f0=0000000000000050
14: 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: ffffc808a7870058, memory referenced.
Arg2: 0000000000000000, 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: fffff80089f50684, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)

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

*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

Key : AV.Type
Value: Read

Key : Analysis.CPU.mSec
Value: 3764

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 78059

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

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

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

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

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

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

Key : Bugcheck.Code.DumpHeader
Value: 0x50

Key : Bugcheck.Code.Register
Value: 0x50

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.1


FILE_IN_CAB: 112122-11265-01.dmp

BUGCHECK_CODE: 50

BUGCHECK_P1: ffffc808a7870058

BUGCHECK_P2: 0

BUGCHECK_P3: fffff80089f50684

BUGCHECK_P4: 2

READ_ADDRESS: fffff8006e8fb390: 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
ffffc808a7870058

MM_INTERNAL_CODE: 2

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

TRAP_FRAME: ffffc808a786f690 -- (.trap 0xffffc808a786f690)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000006 rbx=0000000000000000 rcx=0000000000000012
rdx=00000000000000ff rsi=0000000000000000 rdi=0000000000000000
rip=fffff80089f50684 rsp=ffffc808a786f820 rbp=ffffc808a786f878
r8=0000000000000001 r9=0000000000000002 r10=00000000000003b0
r11=fffff8008a985990 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz ac po nc
nvlddmkm+0x120684:
fffff800`89f50684 4c396cd5e8 cmp qword ptr [rbp+rdx*8-18h],r13 ss:0018:ffffc808`a7870058=????????????????
Resetting default scope

STACK_TEXT:
ffffc808`a786f3e8 fffff800`6e03421d : 00000000`00000050 ffffc808`a7870058 00000000`00000000 ffffc808`a786f690 : nt!KeBugCheckEx
ffffc808`a786f3f0 fffff800`6de399e0 : fffff800`6dff5440 00000000`00000000 ffffc808`a786f710 00000000`00000000 : nt!MiSystemFault+0x1dc80d
ffffc808`a786f4f0 fffff800`6e008dd8 : 00000000`00000000 fffff800`6df9cca2 00000000`00000003 00000000`00000100 : nt!MmAccessFault+0x400
ffffc808`a786f690 fffff800`89f50684 : fffff800`8a985a86 00000000`00000000 00000000`00000000 ffffa38a`12c68000 : nt!KiPageFault+0x358
ffffc808`a786f820 fffff800`8a985a86 : 00000000`00000000 00000000`00000000 ffffa38a`12c68000 ffffa38a`12c68056 : nvlddmkm+0x120684
ffffc808`a786f828 00000000`00000000 : 00000000`00000000 ffffa38a`12c68000 ffffa38a`12c68056 ffffc808`000003ba : nvlddmkm+0xb55a86


SYMBOL_NAME: nvlddmkm+120684

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 120684

FAILURE_BUCKET_ID: AV_R_(null)_nvlddmkm!unknown_function

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {f899ea14-805d-2454-345d-ba405310c43d}

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

14: kd> lmvm nvlddmkm
Browse full module list
start end module name
fffff800`89e30000 fffff800`8d65d000 nvlddmkm T (no symbols)
Loaded symbol image file: nvlddmkm.sys
Image path: \SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_ade64cd54ec2f9ed\nvlddmkm.sys
Image name: nvlddmkm.sys
Browse all global symbols functions data
Timestamp: Tue Oct 25 16:58:05 2022 (63583FCD)
CheckSum: 0373C52C
ImageSize: 0382D000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Information from resource tables:

0 Likes

Can you also check RAM stability?
Page fault in nonpaged area is usually error related to RAM timings.
Ofc software conflict still can cause such problem, but you definitely should sort out RAM.

RAM modules are pretty new, I've had the same error with Kllisre modules (2x16 GB, 3200 MHz) before. Replaced them with the ones listed in the original post, but the problem persisted.

0 Likes