Question about DPC_WATCHDOG_VIOLATION causing BSOD and Event ID 153, 14, 0 crashes with nvlddmkm.sys crash.
Question about DPC_WATCHDOG_VIOLATION causing BSOD and Event ID 153, 14, 0 crashes with nvlddmkm.sys crash.
The problem might stem from CPU pins not being properly aligned due to excessive force on a corner or side of the CPU in the socket. This is often seen in LGA 1700 systems when RAM problems occur.
When you refer to pressure, it could come from either the socket or the all-in-one liquid cooler block.
If the CPU latching system is involved or a contact frame is used (which replaces the LGA latch holding the CPU in the socket), sometimes the force applied isn't uniform across the CPU during installation. This may lead to certain CPU pins in the LGA socket becoming misaligned, potentially causing problems with RAM that could be mistaken for faulty modules. It might also relate to pins connected to memory channels that aren't making proper contact with the bottom pads of the CPU. Additionally, CPU coolers can sometimes exert excessive pressure on one side or corner of the CPU.
I'm not sure why, but adjusting the virtual memory paging file and changing CPU settings like disabling C-State and selecting CPU Lite Load Mode 15 in BIOS seems to eliminate the BSODs; though the nvlddmkm.sys crashes still occur but take longer to appear.
Windows is using part of the your SSD as virtual ram when you use page file. You're not fixing the problem, you're only delaying it. At this point, I would suggest you stop using the PC before you corrupt your Windows installation, because you clearly have a system ram issue.
You could try fixing it your self by removing each ram module one at a time and seeing if you still have the crashing. Which ever module does not cause crashing, swap it to the slot of the one that does and see if it still crashes. That will help diagnose if it's a faulty module issue or possibly a CPU pin issue, but if it is a CPU pin issue, it may require fully removing the CPU cooler to fix it. If you're not familiar with that process, just have the people that built the system do it for you.
The mini dump could be generated. You might also consider using this Windbg command: !dpcwatchdog. If you need a minidump, let me know.
Yeah it is a video timeout, I have attached the minidumps here:
https://drive.google.com/file/d/1lJjmspP...sp=sharing
I may actually be wrong on it being the ram specifically, and could actually be the SSD, but it's still very possible there is a CPU pin issue because that could still cause kind of similar issues with storage and corrupt the data on the SSD.
Whatever the cause of the issue is, I just know nearly every time I've had to deal with this kind of error, it was because something corrupted the driver files and often the Windows files. I've found it usually came down to being a ram issue for one of various reasons, usually unstable ram settings and less often being a CPU pin issue.
Overall your build appears quite satisfactory. There haven’t been any significant changes to the Windows files. My assumption is that gna.sys might be interfering with your graphics sound driver and causing issues with the GPU driver. Check the link provided for an update to gna.sys.
I haven’t explored what the AMD Workload Profiling Scheduling Driver actually does. I wasn’t expecting to find it.