Two of the dumps are Driver Verifier trapped problems. Has somebody asked you to enable Driver Verifier? It's not normal to run with it enabled unless you're troubleshooting.
That said, these two dumps show that a driver is misbehaving in the way it handles interrupts. The IRP (Interrupt Request Packet) shows that it was a PCIe device having the problem..
Code:
16: kd> !irp ffffd70ea5a76e10
Irp is active with 2 stacks 2 is current (= 0xffffd70ea5a76f28)
No Mdl: No System Buffer: Thread ffffd70e8a0cf040: Irp stack trace.
cmd flg cl Device File Completion-Context
[N/A(0), N/A(0)]
0 10 00000000 00000000 00000000-00000000
Args: 00000000 00000000 00000000 00000000
>[IRP_MJ_CREATE(0), N/A(0)]
0 0 ffffd70e953f7370 ffffd70e9529cd60 00000000-00000000
\Driver\pci
Args: ffffcd8e415d4168 01000040 00030000 00000000
Irp Extension present at 0xffffd70ea5a76f70:
The call stack reveals that the device driver thjat actually faouled up was nvlddmkm.sys, the Nvidia graphics driver.
Code:
.....
0xffffcd8e415d3b38 : 0xfffff8042d3e2b9b : nt!CarInitiateBugcheck+0x47
0xffffcd8e415d3b50 : 0xfffff8042e7600e0 : pci!PciDispatchCreate
0xffffcd8e415d3b68 : 0xfffff8042d266000 : !da ""DRIVER VERIFIER IOMANAGER VIOLATION""
0xffffcd8e415d3b70 : 0xffffd70e9f8a79e0 : 0xfffff8042e7600e0 : pci!PciDispatchCreate
0xffffcd8e415d3b78 : 0xfffff8042d3e182a : nt!CarReportRuleViolationForTriage+0x14a
0xffffcd8e415d3b88 : 0xfffff8042d266000 : !da ""DRIVER VERIFIER IOMANAGER VIOLATION""
0xffffcd8e415d3b90 : 0xfffff8042d266000 : !da ""DRIVER VERIFIER IOMANAGER VIOLATION""
0xffffcd8e415d3ba0 : 0xfffff8042d266000 : !da ""DRIVER VERIFIER IOMANAGER VIOLATION""
0xffffcd8e415d3bb8 : 0xffffd70e9f8a79e0 : 0xfffff8042e7600e0 : pci!PciDispatchCreate
0xffffcd8e415d3bc8 : 0xfffff8042d3e1324 : nt!CarQueryReportActionForTriage+0xa4
0xffffcd8e415d3bd0 : 0xfffff8042e7600e0 : pci!PciDispatchCreate
0xffffcd8e415d3bd8 : 0xfffff8042e7600e0 : pci!PciDispatchCreate
0xffffcd8e415d3bf8 : 0xfffff8042d8db33c : nt!VerifierBugCheckIfAppropriate+0xc8
0xffffcd8e415d3c20 : 0xfffff8042e7600e0 : pci!PciDispatchCreate
0xffffcd8e415d3c40 : 0xfffff8042e7600e0 : pci!PciDispatchCreate
0xffffcd8e415d3c98 : 0xfffff8042d8e1830 : nt!ViErrorFinishReport+0x11c
0xffffcd8e415d3cb8 : 0xfffff8042db83d90 : nt!ViErrorDescriptions
0xffffcd8e415d3cc8 : 0xfffff8042d8e1707 : nt!ViErrorDisplayDescription+0x47
0xffffcd8e415d3cd8 : 0xfffff8042d8c6201 : !da ""ned a status that is incorrect.(0xFFFFFFFF). This is probably due to an uninitia...""
0xffffcd8e415d3cf0 : 0xfffff8042e7600e0 : pci!PciDispatchCreate
0xffffcd8e415d3cf8 : 0xfffff8042d3dd1a7 : nt!ViErrorReport1+0x63
0xffffcd8e415d3d30 : 0x41746972706c7543 : !da ""CulpritAddress = FFFFF8042E7600E0, Irp = FFFFD70EA5A76E10..""
0xffffcd8e415d3d38 : 0x3d20737365726464 : !da ""ddress = FFFFF8042E7600E0, Irp = FFFFD70EA5A76E10..""
0xffffcd8e415d3d40 : 0x3038464646464620 : !da "" FFFFF8042E7600E0, Irp = FFFFD70EA5A76E10..""
0xffffcd8e415d3d48 : 0x4530303637453234 : !da ""42E7600E0, Irp = FFFFD70EA5A76E10..""
0xffffcd8e415d3d50 : 0x3d20707249202c30 : !da ""0, Irp = FFFFD70EA5A76E10..""
0xffffcd8e415d3d58 : 0x3037444646464620 : !da "" FFFFD70EA5A76E10..""
0xffffcd8e415d3d60 : 0x3145363741354145 : !da "EA5A76E10.."
0xffffcd8e415d3d98 : 0xfffff8042d8da8c0 : nt!IovpCallDriver2+0x204
....
0xffffcd8e415d52d8 : 0xfffff8042d621d1c : nt!PnpCallDriverEntry+0x54
0xffffcd8e415d5328 : 0xfffff8042d57fd1b : nt!IopLoadDriver+0x523
0xffffcd8e415d5390 : 0xffff85846795b1e0 : !du "\SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660..."
0xffffcd8e415d53d8 : 0xffffd70e9f4e26a0 : !du "\Driver\nvlddmkm"
0xffffcd8e415d53e0 : 0xfffff80577b30000 : nvlddmkm
0xffffcd8e415d53f0 : 0xffffd70e9bb35050 : 0xfffff8042da31470 : nt!PsLoadedModuleList
0xffffcd8e415d5480 : 0xffff8584672b4d20 : !du "nvlddmkm"
0xffffcd8e415d5488 : 0xfffff8042d57f658 : nt!PnpGetServiceStartType+0x60
0xffffcd8e415d54a8 : 0xffffd70e9f4f3c70 : !du "nvlddmkm"
0xffffcd8e415d54e8 : 0xfffff8042d57de98 : nt!PipCallDriverAddDeviceQueryRoutine+0x244
0xffffcd8e415d5538 : 0xffff8584672b4d20 : !du "nvlddmkm"
0xffffcd8e415d5548 : 0xffffd70e9f4e2820 : !du "\Driver\nvlddmkm"
0xffffcd8e415d5558 : 0xffffcd8e415d56c0 : 0xffff8584672b4d20 : !du "nvlddmkm"
0xffffcd8e415d5578 : 0xfffff8042d57cb52 : nt!PnpCallDriverQueryServiceHelper+0xfe
0xffffcd8e415d5590 : 0xffffd70e8a7e6530 : !du "PCI\VEN_10DE&DEV_1E07&SUBSYS_24873842&REV_A1\4&1d81e16&0&0019"
0xffffcd8e415d55d8 : 0xfffff8042d57bb4a : nt!CmOpenInstallerClassRegKey+0x3a
0xffffcd8e415d5628 : 0xfffff8042d57b222 : nt!PipCallDriverAddDevice+0x4ba
0xffffcd8e415d5650 : 0xffffd70e8a7e6530 : !du "PCI\VEN_10DE&DEV_1E07&SUBSYS_24873842&REV_A1\4&1d81e16&0&0019"
0xffffcd8e415d5688 : 0xffffd70e9f8a77a0 : !du "\_SB.PCI0.GPP1.BYUP.BYD8.XHC1.RHUB.PRT6"
0xffffcd8e415d56c0 : 0xffff8584672b4d20 : !du "nvlddmkm"
0xffffcd8e415d56f8 : 0xffffcd8e415d5750 : !du "{4d36e968-e325-11ce-bfc1-08002be10318}"
0xffffcd8e415d5750 : 0x003300640034007b : !du "{4d36e968-e325-11ce-bfc1-08002be10318}"
0xffffcd8e415d5758 : 0x0036003900650036 : !du "6e968-e325-11ce-bfc1-08002be10318}"
0xffffcd8e415d5760 : 0x00330065002d0038 : !du "8-e325-11ce-bfc1-08002be10318}"
0xffffcd8e415d5768 : 0x0031002d00350032 : !du "25-11ce-bfc1-08002be10318}"
0xffffcd8e415d5770 : 0x002d006500630031 : !du "1ce-bfc1-08002be10318}"
0xffffcd8e415d5778 : 0x0031006300660062 : !du "bfc1-08002be10318}"
0xffffcd8e415d5780 : 0x003000380030002d : !du "-08002be10318}"
0xffffcd8e415d5788 : 0x0065006200320030 : !du "02be10318}"
0xffffcd8e415d5790 : 0x0031003300300031 : !du "10318}"
0xffffcd8e415d57e8 : 0xfffff8042d50a471 : nt!PipProcessDevNodeTree+0x1b9
0xffffcd8e415d5860 : 0xfffff8042d63aef0 : nt!PiMarkDeviceTreeForReenumerationWorker
0xffffcd8e415d58a8 : 0xfffff8042d589092 : nt!PiProcessReenumeration+0x92
.....
The version of nvlddmkm.sys that you have installed is current...
Code:
16: kd> lmDvmnvlddmkm
Browse full module list
start end module name
fffff805`77b30000 fffff805`7b3c8000 nvlddmkm T (no symbols)
Loaded symbol image file: nvlddmkm.sys
Image path: \SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e34a87a86b660c23\nvlddmkm.sys
Image name: nvlddmkm.sys
Browse all global symbols functions data
Timestamp: Tue Apr 25 21:16:05 2023 (644818E5)
CheckSum: 0379289F
ImageSize: 03898000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Information from resource tables:
That would lead me to wonder whether you're running any anti-cheat tools? These often cause errors in the display driver.
If you're not running any anti-cheat tools then try rolling back to the previous driver version. Use
DDU to remove the current driver version first.
The other possibility is that the fault is not in the graphics driver but the graphics card.
The DPC_WATCHDOG_VIOLATION dumps are almost certainly the result of these nvlddmkm.sys issues, but it's not possible to analyse these BSODs from a minidump. Whenever you get a DPC_WATCHDOG_VIOLATION BSOD copy the file C:\Windows\Memory.dmp to another location (because it will be overwritten by any subsequent BSOD) and upload it for us to analyse.
no bsod, system just stopped responding so I pressed the restart button
Facebook
Twitter
Instagram