BSOD DPC_WATCHDOG_VIOLATION (133)

Topic

New Reply

In the past month I have experienced three BSOD 133 reboots.  All three have (via windbg) “Image Name: vsmraid,sys”.  Two were on 20H2, the one a few minutes ago was 21H1.  Win 10 Professional 64-bit.  I have run windbg “!analyze -f -v” on each dump, but I have no idea for what to look in the windbg output.  Each dump had a different PROCESS_NAME: procexp64.exe, sdupdate.exe, taskmgr.exe.  I have not done any searches to determine what vsmraid.sys is.  Any suggestions?

Reply | Quote

Replies

Try BSODView shown in this post.
https://www.askwoody.com/forums/topic/windows-10-june-2021-patch-tuesday-updates/#post-2370518

cheers, Paul

Reply | Quote

I installed the software, and it gives me summaries of my four BSODs (three 133 and one 1A).  The three 133 dumps, according to the utility, are caused by ntoskrnl.exe+3f____ (the last four hex digits depend upon the version of ntoskrnl.exe that I had installed at the time of the BSOD).  I believe that it was this NT Operating Systems Kernel that detected the 133 error, but it was not ntoskrnl.exe that caused the error.  There is a long list of drivers loaded, but ntoskrnl.exe is the only one listed in the stack.  Knowing an offset into this executable tells me nothing,   Is there anything else that I can learn from this utility?  This utility is looking at the minidunp files (the names of which MS no longer tells me when Windows 10 experiences a BSOD); I assume the same info will be in the full dumps (which I rename with a date and timestamp after each BSOD).

Reply | Quote

bsfinkel wrote:

vsmraid.sys

vsmraid.sys stands for Virtual Systems Management VIA RAID DRIVER FOR AMD-X86-64.

The latest version update [v7.0.9600,6352] for Windows 10 was released on 07/29/2015.

What sort of hardware do you have ?

Try running integrity checks/fix with these commands :

DISM /Online /Cleanup-Image /CheckHealth

DISM /Online /Cleanup-Image /RestoreHealth

sfc /scannow

Reply | Quote

I have a home-built computer that I built many years ago.  It had two IDE disks, but one failed a month ago, so I found space on a SATA disk and restored this data disk.  Besides this one IDE disk, I have a SATA SSD Win 7 boot disk, and a SATA (with my XP boot and my Win 7 boot),   I will now run the DISM and SFC commands and report back.

Reply | Quote

DISM /Online /Cleanup-Image /CheckHealth
Image Version: 10.0.19043.985
No component store corruption detected.
The operation completed successfully.

DISM /Online /Cleanup-Image /RestoreHealth
Image Version: 10.0.19043.985
[==========================100.0%==========================]
The restore operation completed successfully.
The operation completed successfully.

sfc /scannow
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection did not find any integrity violations.

 

As for vsmraid,sys:

12/07/2019 03:07AM
7.0.9600.6352
166,712

Reply | Quote

As the dumps point to “Image: vsmraid.sys”, I have sent a support e-mail to VIA Technologies. as the IDE card I have in my computer is from VIA.

Also, I noticed that the “DPC time allottment is  x’500” ticks.  I have no idea what this value represents, and I have no idea what bad effects would occur if I were to increase that value (assuming that I am able to change that value).

 

Reply | Quote

Have you happened to update an Nvidia graphics driver as of recently?  Version 466.77 is known to cause system crashes, and a friend of mine personally had the driver causing DPC_WATCHDOG_VIOLATION errors as well.  I’d recommend rolling the driver back if you did update to it.

Reply | Quote

I do not have an Nvidia graphics driver.  I had one when I was running Windows 7, but the driver was causing BSODs.  As I was not a “gamer”, Nvidia was not really interested in solving the problem.  So I spent $40 on a different graphics card, and I put the Nvidia graphics card on the shelf.

Reply | Quote

Possible solution to your problem:
Blue Screen – 0x00000133 – Microsoft Community

Reply | Quote

I looked at that thread.  AnalogKnight asked for a minidump, which was provided by the end-user.  Others have replied, but AnalogKnight has not yet responded with his/her analysis of the minidump.

Reply | Quote

Nvidia fixed : Blue screen of death (BSOD) related to error causes by DPC Watchdog violation
In version : Nvidia 466.77 Game Ready WHQL driver

Release Notes : https://us.download.nvidia.com/Windows/466.77/466.77-win10-win8-win7-release-notes.pdf

DCH : https://us.download.nvidia.com/Windows/466.77/466.77-notebook-win10-64bit-international-dch-whql.exe

Standard : https://www.nvidia.com/download/driverResults.aspx/176266/en-us

Reply | Quote