Windows BSOD KMODE_EXCEPTION_NOT_HANDLED (volmgr.sys) + DPC_WATCHDOG_VIOLATION

Rong Jie 20 Reputation points
2026-08-23T13:27:48.43+00:00

Timeline (all in one day):

  • First BSOD with KMODE_EXCEPTION_NOT_HANDLED (volmgr.sys). Laptop's speaker was producing a constant bzzz sound.
  • AI suggested me to run chkdsk C: /f /r and restart, so I did
  • Halfway in chkdsk, encountered another BSDO DPC_WATCHDOG_VIOLATION
  • I restart laptop in safe mode, frantically backup some important files to external HDD
  • Ran mdsched.exe and restart. No issue detected.
  • Ran sfc /scannow. No issue detected.
  • Ran DISM /Online /Cleanup-Image /RestoreHealth. No issue detected.
  • CrystalDiskInfo looks ok

For the past 2 months I kinda also have a few device driver crash that I needed to reset with Win + Ctrl + Shift + B.

Minidumps: https://1drv.ms/f/c/79f07c01480dbb1d/IgBDC8K3tMSFQb-iwbjfhIyuAeedA4QGq7pAYDXIjQodKYE?e=sk107S

Edition	Windows 10 Home Single Language (with ESU)

Version	22H2

Installed on	‎3/‎11/‎2021

OS Build	19045.7663

Processor	AMD Ryzen 5 3550H with Radeon Vega Mobile Gfx     2.10 GHz

Installed RAM	16.0 GB (13.9 GB usable)

Storage	477 GB SSD INTEL SSDPEKNW512G8

Graphics Card	NVIDIA GeForce GTX 1050 (3 GB), AMD Radeon(TM) Vega 8 Graphics (2 GB)

System Type	64-bit operating system, x64-based processor

Pen and touch	Pen support
Windows for home | Windows 10 | Performance and system failures
0 comments
Answer accepted by question author
TaoLi 110.9K Reputation points Independent Advisor
2026-08-23T14:08:06.96+00:00

Hi

I checked the dumps. The KMODE_EXCEPTION_NOT_HANDLED crash occurred in the storage/NVMe path (volmgr.sys, storport.sys, stornvme.sys), while the second crash was DPC_WATCHDOG_VIOLATION. This points more toward SSD firmware/storage or chipset drivers than RAM.

Your SSD SMART looks normal: 82% health, 42°C, and no media errors. However, the Intel 660p is still on firmware 002C, which is quite old. I suggest backing up your data first, then updating the SSD firmware with Solidigm Storage Tool:

https://www.solidigm.com/support-page/drivers-downloads/ka-00085.html

Also update the laptop BIOS, AMD chipset drivers, and AMD/NVIDIA graphics drivers from ASUS:

https://www.asus.com/support/faq/1035376/

Disclaimer: This link points to a non-Microsoft website. While the content appears accurate and safe, the site may contain third-party advertisements. Please distinguish between advertisements and official download links to avoid accidentally clicking on content that might promote PUPs/PUAs (Potentially Unwanted Programs). It is recommended to verify the source and file name before downloading or installing any files.

For now, avoid repeatedly running chkdsk /r. After updating the firmware/drivers, run chkdsk C: /scan and see whether the BSOD returns.

Microsoft reference: https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x133-dpc-watchdog-violation

At this stage I would update the SSD firmware and drivers first, rather than replace the SSD immediately.

Was this answer helpful?

1 person found this answer helpful.
0 comments

3 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Rong Jie 20 Reputation points
    2026-08-25T14:39:47.2666667+00:00

    Hi TaoLi,

    Didn't know that my SSD firmware was that ancient. I updated to 005C and ran chkdsk C: /scan, it seems ok now

    I don't know if I should/need to run chkdsk C: /f /r again

    Was this answer helpful?

    0 comments
  2. Rong Jie 20 Reputation points
    2026-08-23T13:37:37.9233333+00:00

    ASUS tuf fx505d

    AttUser's imageCry

    Was this answer helpful?

    0 comments

  3. AI answer

    2026-08-23T13:28:12.17+00:00

    volmgr.sys in the stop screen is often not the true root cause. The documented guidance for KMODE_EXCEPTION_NOT_HANDLED and other stop codes is to focus on recently added or faulty drivers, hardware issues, Event Viewer errors, and memory or storage-related diagnostics.

    Based on the steps already completed:

    • mdsched.exe found no memory issue.
    • sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth found no system file corruption.
    • CrystalDiskInfo looks normal.
    • The earlier need to reset the graphics stack with Win + Ctrl + Shift + B points to a possible display driver problem.
    • A DPC_WATCHDOG_VIOLATION during chkdsk can still be caused by a driver problem, not only the disk.

    Recommended next steps:

    1. Check Device Manager for faulting devices
      • Right-click Start > Device Manager.
      • Look for devices with an exclamation mark.
      • Open the device properties and review any related events.
      • Update or uninstall/reinstall any device that shows errors, especially display, storage, and chipset-related devices.
    2. Check Event Viewer around the crash times
      • Open Event Viewer.
      • Review the System log for critical or error events that occurred at the same time as the BSODs.
      • Look for entries that identify a device, driver, disk, or controller issue.
    3. Focus on recently added or unstable drivers
      • For KMODE_EXCEPTION_NOT_HANDLED, if a driver is identified, disable or remove that driver.
      • If the crashes started after a driver change, remove or update that driver first.
      • Since display resets were already happening, prioritize the AMD and NVIDIA graphics drivers.
    4. Boot in Safe Mode if normal mode is unstable
      • Safe Mode can be used to disable or remove a suspected driver when the system is unstable during normal startup.
    5. Run hardware diagnostics from the laptop manufacturer
      • The stop-code guidance recommends running the hardware diagnostics supplied by the system manufacturer.
      • This is especially important for memory and other onboard hardware when multiple different bug checks occur.
    6. Check free disk space
      • Keep at least 10% to 15% free space available on the system drive.
    7. Install the latest Windows updates
      • Go to Start > Settings > Update & Security > Windows Update.
      • Select Check for Windows updates.
    8. Use Driver Verifier if crashes remain generic
      • DPC_WATCHDOG_VIOLATION and SYSTEM_SERVICE_EXCEPTION guidance in the context shows Driver Verifier can help expose a misbehaving driver when dumps only show generic memory corruption.
      • Start it from an elevated command prompt with verifier.
      • Verify the smallest possible set of suspected third-party drivers to reduce overhead.
      • Warning: Driver Verifier adds stress to drivers and can make the system crash more often while testing.
      • If the system becomes hard to boot, enter Safe Mode and run:
        • verifier /reset
        • verifier /bootmode resetonbootfail
    9. If new hardware was added recently, remove it temporarily
      • New hardware incompatibility is a documented cause of stop errors.
    10. If the issue persists after driver checks, use System Restore or recovery options
    • If none of the above helps, restore Windows using a restore point or another recovery option.

    For the specific pattern described, the strongest documented path is:

    • check Event Viewer,
    • inspect Device Manager,
    • update/remove suspected graphics or other third-party drivers,
    • run manufacturer hardware diagnostics,
    • then use Driver Verifier carefully if dumps remain inconclusive.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.