[SOLVED] BSOD with the error DPC_WATCHDOG_VIOLATION

Hi Thanks for your reply.

Let’s break down the clues from your logs and minidump to find the root cause and fix this for good.

The DPC_WATCHDOG_VIOLATION error (bugcheck 0x00000133) typically means a driver or hardware component took too long to complete a task, causing the system to crash. Your minidump points to a few key suspects:

• nvlddmkm.sys: NVIDIA GPU driver (likely tied to your graphics card).
• nvhda64v.sys: NVIDIA High Definition Audio driver.
• monitor.sys: Possibly related to display or monitor drivers.
• BEDaisy.sys: Often linked to Bitdefender antivirus or similar security software.
• StartMenuExperienceHost.exe: A Windows process for the Start menu, which might hint at a system file conflict or software clash.

The repeated crashes during system activity (like waking from sleep or general use) suggest a driver or hardware component is failing to respond properly under certain conditions.

• Driver Conflicts: Outdated, corrupted, or incompatible drivers (especially NVIDIA-related ones) are prime suspects here. Windows 11 can clash with older driver versions after updates.
• Antivirus/Software Interference: Security tools like Bitdefender (BEDaisy.sys) sometimes hook deeply into the system, causing instability.
• Power Management Issues: Sleep/hibernation states often trigger driver timeouts, especially if hardware isn’t handling power transitions smoothly.
• Hardware Faults: While less likely given your description, failing RAM, SSD, or GPU components could also cause this error.

How to Fix It

1. Tackle NVIDIA Drivers First

• Clean Reinstall Graphics Drivers:
  Use Display Driver Uninstaller (DDU) in Safe Mode to wipe all NVIDIA drivers, then reinstall the latest version from NVIDIA’s website. This resolves conflicts caused by leftover files.
• Disable NVIDIA HD Audio:
  If you don’t use HDMI/DisplayPort audio, disable the NVIDIA HD Audio driver in Device Manager under Sound, video, and game controllers to rule it out.

2. Check for Software Conflicts

• Temporarily Uninstall Bitdefender:
  BEDaisy.sys is linked to Bitdefender. Uninstall it completely (use their removal tool) and test the system for a day. If crashes stop, switch to Windows Defender or another AV temporarily.
• Disable Start Menu Experience Host:
  While rare, corruption here can destabilize the OS. Run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth in an admin Command Prompt to repair system files.

3. Adjust Power and Sleep Settings

• Disable Fast Startup:
  Go to Control Panel > Power Options > Choose what the power buttons do > Change settings currently unavailable > Uncheck "Turn on fast startup". This prevents driver reinitialization issues during boot.
• Disable Hybrid Sleep:
  In Power Options > Edit Plan Settings > Change advanced power settings, set Sleep > Allow hybrid sleep to Off.

4. Update Firmware and Hardware Drivers

• SSD/NVMe Firmware:
  Check your SSD manufacturer’s site (e.g., Samsung Magician, WD Dashboard) for firmware updates. Outdated firmware can cause storage-related DPC errors.
• Chipset/Storage Controllers:
  Update your motherboard’s chipset drivers (from ASUS or your PC manufacturer’s site) and ensure your SATA/AHCI controller is using the Standard SATA AHCI Controller driver (via Device Manager).

5. Test Hardware Stability

• Run Memory Diagnostics:
  Use Windows Memory Diagnostic or other tools to check for RAM errors. Faulty RAM often causes random crashes.
• Check SSD Health:
  Tools can flag SSD issues. Replace the drive if it shows warnings like "Reallocated Sectors".

• Reset Windows 11:
  A clean install (keeping your files) can eliminate persistent software corruption. Back up data first.

Let me know how it goes! If the crashes persist, we can dig deeper into the memory dump or explore BIOS/UEFI tweaks.

Today i experienced no crash but they were not very frequent (once or twice a day), so I'll wait a bit more before calling it solved. I'll update you in a a few days if everything keeps working fine

Thank you so mutch for all the support. I did everything you suggested except for the Bitfender disinstallation because I don't have Bitfender on my system.

Do you suggest to try and remove BEDaysi.sys anyway? I don't really know how to proceed to do that.

For reference I'm currently on Windows 10, I don't know if that changes something but more info is better i think.

Here you can find the minidump.

Opening it with windbg it looks like what caused the crash were nvlddmkm.sys with FAILURE_BUCKET_ID: 0x133_DPC_nvlddmkm!unknown_function

Hi Welcome to Microsoft community.We need you to provide the blue screen log (minidump) to analyze your problem. Finally, upload the file to a suitable network drive and send the sharing link in the reply. Please make sure to set the sharing link as public and without the need for login or permission.To find the minidump file in Windows, you can follow these steps:Open File Explorer by pressing the Windows key + E.Navigate to the following location: C:\Windows\Minidump (replace C with the drive where Windows is installed if it is different).If you cannot find the Minidump folder at the specified location, it might be hidden. To show hidden files and folders, click on the "View" tab in the File Explorer, and check the "Hidden items" option.If the Minidump folder is still not present, it might be because your system is not configured to create Minidump files. To enable this feature, follow these steps:Press the Windows key + X and select "System".Click on "Advanced system settings" on the left-hand side.In the System Properties window, go to the "Advanced" tab and click on the "Settings" button under the "Startup and Recovery" section.In the Startup and Recovery window, make sure that the "Write debugging information" drop-down menu is set to "Small memory dump (256 KB)" or "Kernel memory dump".Click "OK" to save the changes.Restart your computer for the changes to take effect.Once you have located the Minidump folder, you will find the Minidump files inside it. These files have the .dmp extension and are named with a combination of date and time.Note: Minidump files are created when your system encounters a blue screen of death (BSOD) or a crash. If you have not experienced any crashes, the Minidump folder may be empty.Please feel free to let me know if you have any further updates, thanks.Best regardsDerrick Qian | Microsoft Community Support Specialist