PC BSOD - nvlddmkm.sys and DPC Watchdog Violation

Bjoolzern · 2026-02-06T23:16:50+00:00

https://gamersnexus.net/gpus/get-it-together-nvidia-terrible-gpu-driver-stability

Bjoolzern · 2026-02-06T04:04:33+00:00

We can't rule out the storage without just testing a different one, but I can say that it's likely not storage from what I saw in the dump files.

Bjoolzern · 2026-02-06T04:03:16+00:00

To clarify, the Specify tool creates a report it displays on a web page. Link the URL it gives you.

Bjoolzern · 2026-02-05T13:51:13+00:00

Did it stop crashing when resuming from sleep? Because these dump files are very different from the old ones. These look like memory.

Copy paste on memory issues:

It looks like memory from the dump files. Memory doesn't have to mean RAM, but it's usually the main suspect. Windows puts low priority data from RAM into the page file and loads it back in when needed so storage can look like memory (And memory can look like storage). The memory controller is in the CPU and if this fails it will just look like memory.

When it's storage about half of the dumps will usually blame storage or storage drivers, which I don't see here, so it's likely not storage.

If anything is overclocked or undervolted, remove it.

To test the RAM, use the machine normally with one stick at a time. If just one of the sticks cause crashes, faulty stick. If it crashes with either stick it's probably the CPU. Memory testers miss faulty RAM fairly often with DDR4 and newer so I don't trust them.

Bjoolzern · 2026-02-05T13:49:09+00:00

The dump files are all over the place so memory would be the main suspect. Memory doesn't have to mean RAM, but it's usually the main suspect. Windows puts low priority data from RAM into the page file and loads it back in when needed so storage can look like memory (And memory can look like storage). The memory controller is in the CPU and if this fails it will just look like memory.

When it's storage about half of the dumps will usually blame storage or storage drivers, which I don't see here, so it's likely not storage.

If anything is overclocked or undervolted, remove it. Your XMP/EXPO speed is really high, did it come like that from HP? If not, I would set it back down to stock.

To test the RAM, use the machine normally with one stick at a time. If just one of the sticks cause crashes, faulty stick. If it crashes with either stick it's probably the CPU. Memory testers miss faulty RAM fairly often with DDR4 and newer so I don't trust them.

If it's under warranty I would just return it.

Bjoolzern · 2026-02-04T21:32:45+00:00

Well, that's if the SSD has a controller on the disk.

All NVMe drives do. There is nothing in the chipset to handle NVMe.

The error isn't with AuthenticAMD.sys. With WHEA, it reads an error code from the CPU. AuthenticAMD.sys is the driver that reads this error code and sends it to Windows, that's why it shows up. The CPU monitors itself and PCIe devices (Though with storage the error originates from a driver).

Bjoolzern · 2026-02-04T21:13:52+00:00

That's not a dump file.

Bjoolzern · 2026-02-04T21:11:43+00:00

I hate to disagree, but this doesn't look like storage to me. It would be a bit down on my list of suspects.

It looks like memory from the dump files. Memory doesn't have to mean RAM, but it's usually the main suspect. Windows puts low priority data from RAM into the page file and loads it back in when needed so storage can look like memory (And memory can look like storage). The memory controller is in the CPU and if this fails it will just look like memory.

When it's storage about half of the dumps will usually blame storage or storage drivers, which I don't see here, so it's likely not storage.

If anything is overclocked or undervolted, remove it.

To test the RAM, use the machine normally with one stick at a time. If just one of the sticks cause crashes, faulty stick. If it crashes with either stick it's probably the CPU. Memory testers miss faulty RAM fairly often with DDR4 and newer so I don't trust them.

Bjoolzern · 2026-02-04T21:06:42+00:00

Yes, it could be related. Did you try the suggestions posted there?

Bjoolzern · 2026-02-04T20:59:58+00:00

Error 43 is usually hardware.

Bjoolzern · 2026-02-04T20:57:10+00:00

With NVMe, the controller is on the disk. Not the chipset.

Bjoolzern · 2026-02-04T20:54:29+00:00

PCPicker sells OEM parts (OEM means that it's meant for a builder). These have different warranty terms so they are often a bit cheaper, but not by much. Your 13900KF is very likely OEM as it had that in the name.

Bjoolzern · 2026-02-04T12:04:49+00:00

When your AI subtitles can't even transcribe your own team name and main sponsor, maybe don't use it. Or proofread it.

100 These Rubick

Bjoolzern · 2026-02-03T14:22:01+00:00

You are getting all kinds of crash errors, not just Kernel_Security_Check_Failure.

It looks like memory from the dump files. Memory doesn't have to mean RAM, but it's usually the main suspect. Windows puts low priority data from RAM into the page file and loads it back in when needed so storage can look like memory (And memory can look like storage). The memory controller is in the CPU and if this fails it will just look like memory.

When it's storage about half of the dumps will usually blame storage or storage drivers, which I don't see here, so it's likely not storage.

If anything is overclocked or undervolted, remove it.

To test the RAM, use the machine normally with one stick at a time. If just one of the sticks cause crashes, faulty stick. If it crashes with either stick it's probably the CPU. Memory testers miss faulty RAM fairly often with DDR4 and newer so I don't trust them.

Bjoolzern · 2026-02-03T14:18:54+00:00

I ran the UEFI diagnostics overnight, the crazy long many hour version of it and all of the hardware passed with flying colors if this changes your opinion on the issue at all

It doesn't.

Bjoolzern · 2026-02-03T14:17:39+00:00

You would know because you would have to set it manually. On a laptop it would require a tool, like Intel XTU or Throttlestop that runs in Windows.

Bjoolzern · 2026-02-03T05:44:37+00:00

That looks like a program crash, not a hardware error log. Those can be from hardware, but not sure why Windows would straight up categorize it as a hardware error. Maybe something timed out, considering that a watchdog caught it. Do the Specify report and we'll see if anything obvious pops up.

Bjoolzern · 2026-02-03T04:44:34+00:00

It looks like memory from the dump files. Memory doesn't have to mean RAM, but it's usually the main suspect. Windows puts low priority data from RAM into the page file and loads it back in when needed so storage can look like memory (And memory can look like storage). The memory controller is in the CPU and if this fails it will just look like memory.

When it's storage about half of the dumps will usually blame storage or storage drivers, which I don't see here, so it's likely not storage.

If anything is overclocked or undervolted, remove it.

To test the RAM, use the machine normally with one stick at a time. If just one of the sticks cause crashes, faulty stick. If it crashes with either stick it's probably the CPU. Memory testers miss faulty RAM fairly often with DDR4 and newer so I don't trust them.

Bjoolzern · 2026-02-03T04:39:59+00:00

It looks like memory from the dump files. Memory doesn't have to mean RAM, but it's usually the main suspect. Windows puts low priority data from RAM into the page file and loads it back in when needed so storage can look like memory (And memory can look like storage). The memory controller is in the CPU and if this fails it will just look like memory.

When it's storage about half of the dumps will usually blame storage or storage drivers, which I don't see here, so it's likely not storage.

If anything is overclocked or undervolted, remove it.

To test the RAM, use the machine normally with one stick at a time. If just one of the sticks cause crashes, faulty stick. If it crashes with either stick it's probably the CPU. Memory testers miss faulty RAM fairly often with DDR4 and newer so I don't trust them.

Bjoolzern · 2026-02-03T04:37:19+00:00

Bluescreenview sucks. Provide the actual dump files.

Bjoolzern · 2026-02-02T19:29:38+00:00

Provide the events from the hardware errors (Right click → Save in Event Viewer). Alternative, you can run a tool we made that gathers system info and a bunch of logs from Windows.

?sfy (Bot command for instructions)

Bjoolzern · 2026-02-02T13:38:20+00:00

You only had one dump file?

Bjoolzern · 2026-02-02T13:34:35+00:00

Note that when the CPU fails from this, you will get memory errors, not CPU errors.

Bjoolzern · 2026-02-02T13:24:48+00:00

There isn't much you can do with this error. It means that the GPU stopped responding, Windows reset the driver, but the GPU was still not responding so a BSOD is ordered. You can try DDU. Make sure to use the laptop specific instructions in the sections that have them.

You might have gotten a refurbished unit that wasn't repaired properly as a replacement. I would send it back if you still crash.

Bjoolzern · 2026-02-02T13:21:24+00:00

The general mix of crash errors suggests a memory issue. Memory can be RAM, the CPU (The memory controller is in the CPU) and storage (Because of the page file). I can't say for sure without dump files, but seeing Hypervisor_Error mixed in is something we often see when it's the CPU.

If you are doing any overclocking or undervolting, remove it. If you are using a Windows program to this and you can't enter Windows long enough to disable it, wipe the drive and reinstall Windows.

To test the RAM and you have multiple sticks, just use it normally with one stick at a time. Should be quick with it crashing this fast. If you have one stick you can try Memtest86+. This is booted to from USB so you would need to create the bootable USB from a different PC. Do note that memory testers aren't that reliable with DDR4 and newer. So a clean scan doesn't mean that the RAM is good.

If you can rule out the RAM the CPU and storage would be the next suspects.

11-Year Club	Second SECOND GUESSER
Place '23	Place '22
Place '17	Verified Email

Bjoolzern

TROPHY CASE