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.
I tried to update the Intel GNA Scoring Accelerator driver and the Realtek LAN driver. When I tried to disable the Realtek USB network driver, I couldn't find anything related to it even though I enabled "Show hidden devices". I ran the DISM command with RestoreHealth option, it did not find any issue.
I was surprised when you mentioned that amdwps.sys file. I built this PC completely from scratch and I only used i9-14900k and no other processor. Unfortunately even though I did update the drivers you mentioned, the BSODs still remain. I was able to replicate one just before through a VRAM benchmark test.
I managed to get the kernel type of memory dump. You can find it here:
https://drive.google.com/file/d/1uc3suYk...sp=sharing
Although, it's 3 GB :/
Thanks for the help man! Much appreciated!
PonySwag619
11-03-2025, 09:49 AM #21Wow, thanks for this very detailed analysis!
I tried to update the Intel GNA Scoring Accelerator driver and the Realtek LAN driver. When I tried to disable the Realtek USB network driver, I couldn't find anything related to it even though I enabled "Show hidden devices". I ran the DISM command with RestoreHealth option, it did not find any issue.
I was surprised when you mentioned that amdwps.sys file. I built this PC completely from scratch and I only used i9-14900k and no other processor. Unfortunately even though I did update the drivers you mentioned, the BSODs still remain. I was able to replicate one just before through a VRAM benchmark test.
I managed to get the kernel type of memory dump. You can find it here:
https://drive.google.com/file/d/1uc3suYk...sp=sharing
Although, it's 3 GB :/
Thanks for the help man! Much appreciated!
re enable this
ServiceName is "nvvad_WaveExtensible"
looks like you have some thread that does not complete.
1.3 million attempts for other threads to access the lock.
(in 12 minutes)
I will poke around in the dump and see if I can find a cause but
renable the "nvvad_WaveExtensible"
looks like a lot of threads waiting on a lock.
most look like they are actually gpu related but this one looks strange:
SearchIndexer.exe
I do not know why it would be using a graphics driver.
I would stop the service and maybe reset its database.
ie something like this:
How to Reset & Rebuild Windows Search Index Completely
When you search for files on your computer using Windows Search via File Explorer or Cortana, the files you expect to find may not appear in the search results. This happens even though the files…
www.winhelponline.com
system32\drivers\fxvad.sys Wed Mar 17 10:48:36 2021
anther 3rd party sound driver
https://forum.fxsound.com/t/bsod-related...d-sys/5804
might want to remove it for testing. or update to the 6/2024 version (on same link)
looks like you were also running:
GpuMemtest.exe 20760640 Kb
(using a lot of memory)
you might consider removing
ProcessLasso.exe
Download Process Lasso
Process Lasso is free to use indefinitely, but some advanced features may disable over time and a nag may be shown. See Pro versus Free for more information. Download Process Lasso Latest Release
…bitsum.com
looks like you have a windows insider build also. Might just be some bug.
one of the threads that was waiting was trying to change the power state of some gpu device.
You might want to run in high performance mode to avoid this.
looks like you have some hardware disabled.
re enable this
ServiceName is "nvvad_WaveExtensible"
looks like you have some thread that does not complete.
1.3 million attempts for other threads to access the lock.
(in 12 minutes)
I will poke around in the dump and see if I can find a cause but
renable the "nvvad_WaveExtensible"
looks like a lot of threads waiting on a lock.
most look like they are actually gpu related but this one looks strange:
SearchIndexer.exe
I do not know why it would be using a graphics driver.
I would stop the service and maybe reset its database.
ie something like this:
How to Reset & Rebuild Windows Search Index Completely
When you search for files on your computer using Windows Search via File Explorer or Cortana, the files you expect to find may not appear in the search results. This happens even though the files…
www.winhelponline.com
system32\drivers\fxvad.sys Wed Mar 17 10:48:36 2021
anther 3rd party sound driver
https://forum.fxsound.com/t/bsod-related...d-sys/5804
might want to remove it for testing. or update to the 6/2024 version (on same link)
looks like you were also running:
GpuMemtest.exe 20760640 Kb
(using a lot of memory)
you might consider removing
ProcessLasso.exe
Download Process Lasso
Process Lasso is free to use indefinitely, but some advanced features may disable over time and a nag may be shown. See Pro versus Free for more information. Download Process Lasso Latest Release…
bitsum.com
looks like you have a windows insider build also. Might just be some bug.
one of the threads that was waiting was trying to change the power state of some gpu device.
You might want to run in high performance mode to avoid this.
Regarding nvvad_WaveExtensible, I turned it off after seeing other reports where disabling Nvidia HD Audio in the device manager resolved their problems, but not mine.
The GpuMemtest.exe was a benchmark I performed to mimic the crash and BSOD (used 80% of the GPU VRam = 20760640 Kb).
I was unsure if it was Windows 11 which was faulty, so I reinstalled Windows 10 (fresh install), but the issues persisted. This seems to be a hardware problem rather than software.
But hey, thanks for the help man!
1.3 million attempts????!!! That's insane.
Regarding nvvad_WaveExtensible, I turned it off after seeing other reports where disabling Nvidia HD Audio in the device manager resolved their problems, but not mine.
The GpuMemtest.exe was a benchmark I performed to mimic the crash and BSOD (used 80% of the GPU VRam = 20760640 Kb).
I was unsure if it was Windows 11 which was faulty, so I reinstalled Windows 10 (fresh install), but the issues persisted. This seems to be a hardware problem rather than software.
But hey, thanks for the help man!
new items and old drivers tend to receive the blame.
i would start with a clean build, apply updates, enable verifier testing, and then execute stress tests.
verifier testing will make the machine run slower but it can catch bugs early if an issue exists.
i would install only the essential nvidia drivers and exclude all extras (nvidia container) to minimize potential problems. that way, if the system freezes or bugs appear with the basics, it’s more likely a hardware issue. even then, i would set the base clocks to standard reference values.
make sure they pass stress tests before increasing overclocks or adding more software. it’s a bit time-consuming.
there were several tasks happening that I usually overlook.
new items and old drivers tend to receive the blame.
i would start with a clean build, apply updates, enable verifier testing, and then execute stress tests.
verifier testing will make the machine run slower but it can catch bugs early if an issue exists.
i would install only the essential nvidia drivers and exclude all extras (nvidia container) to minimize potential problems. that way, if the system freezes or bugs appear with the basics, it’s more likely a hardware issue. even then, i would set the base clocks to standard reference values.
make sure they pass stress tests before increasing overclocks or adding more software. it’s a bit time-consuming.
iKegreenS_
11-03-2025, 09:49 AM #251.3 million tries to gain access in 12 minutes. 1800 attempts each second.