Blue Screen - Stopcode DPC_WATCHDOG_VIOLATION

Melanie Springer 1 Reputation point
2021-09-24T12:10:23.727+00:00

I've been experiencing this crash every few days for a few weeks. I have tried various solutions in other forums, but have not had any success. Any help would be appreciated.

Generally, it's occurred when I've been watching a video and/or playing a game.

Here is the information from the Reliablity Monitor report on the crash:

Problem Event Name: BlueScreen
Code: 133
Parameter 1: 1
Parameter 2: 1e00
Parameter 3: fffff80419cfa320
Parameter 4: 0
OS version: 10_0_19041
Service Pack: 0_0
Product: 768_1
OS Version: 10.0.19041.2.0.0.768.101
Locale ID: 1033

Extra information about the problem
Bucket ID: 0x133_ISR_rt640x64!MPMessageIsr_RSS_4_CPUs

As for the memory dump, here it is - https://www.dropbox.com/s/a4tiuz00di8xlrp/MEMORY.DMP?dl=0

Windows 10
Windows 10
A Microsoft operating system that runs on personal computers and tablets.
10,660 questions
0 comments No comments
{count} votes

20 answers

Sort by: Newest
  1. Docs 15,146 Reputation points
    2021-10-27T20:35:22.85+00:00

    Read these links on Windows driver verifier:

    a) learn how to use the Windows Recovery Environment (RE) commands: reset and bootmode to turn off the tool

    b) do not use the tool until it is communicated in the thread

    https://www.tenforums.com/tutorials/5470-enable-disable-driver-verifier-windows-10-a.html
    https://answers.microsoft.com/en-us/windows/forum/windows_10-update/driver-verifier-tracking-down-a-mis-behaving/f5cb4faf-556b-4b6d-95b3-c48669e4c983

    Windows driver verifier is designed to stress test drivers.

    If there are misbehaving drivers the computer will crash.

    If dump files are created they can be debugged.

    Misbehaving drivers are then uninstalled or uninstalled and reinstalled.

    The tool is run for approximately 48 hours and then an additional 36 hours after the last BSOD.

    If there are no further BSOD this concludes the use of the tool.

    After each BSOD you must turn off the tool in order to return to the desktop.

    Learn the Windows RE commands reset and bootmode.

    These are run in safe mode or safe mode with command prompt.

    In case these fail the next option is system restore.

    If system restore fails you can restore a backup image or use registry commands.

    Start the tool with the 3 customized test settings in the Ten Forums link.

    Increase the simultaneous customized test settings by 3 - 5 / hour up to the 19 customized test settings in the Microsoft link.

    There can be performance problems and / or slow boot while using the tool.

    If necessary the customized test settings can be modified.

    Summary:
    a) make a new restore point
    b) test all non-Microsoft drivers
    c) test no Microsoft drivers
    d) after each BSOD use the reset command to turn off the tool
    e) if the reset command does not work then use the bootmode command
    f) only if both reset and bootmode command fail to turn off the tool then use restore
    g) start with the 3 customized test settings in the Ten Forums link
    h) increase the customized test settings up to the 19 customized test settings in the Microsoft link
    i) report any performance problems or very slow boot so that the customized settings can be modified

    .
    .
    .
    .
    .
    Please remember to vote and to mark the replies as answers if they help.

    On the bottom of each post there is:

    Propose as answer = answered the question

    On the left side of each post: Vote = a helpful post
    .
    .
    .
    .
    .

    0 comments No comments

  2. Docs 15,146 Reputation points
    2021-10-27T12:39:58.063+00:00

    Almost always the 3 or 4 methods work to turn off the tool.
    In the future it's always best to make backup images.

    These are some free and pay software to make backup images:

    Acronis
    Aoemi
    EaseUS
    Macrium
    Paragon
    etc.

    Let me know when you want to run the tool and I'll post the instructions.

    .
    .
    .
    .
    .
    Please remember to vote and to mark the replies as answers if they help.

    On the bottom of each post there is:

    Propose as answer = answered the question

    On the left side of each post: Vote = a helpful post
    .
    .
    .
    .
    .


  3. Docs 15,146 Reputation points
    2021-10-26T15:07:00.317+00:00

    The tool ordinarily is turned off by the reset command.
    If the reset command fails then the bootmode command is used.
    If both the reset and bootmode commands fail then the system restore is used.
    In very rare cases the registry is needed.
    And in extremely rare cases a backup image is used.

    So you had expressed worry and the backup image was for the extremely rare cases.

    To turn off the tool the end users has to boot to safe mode and run the command prompt commands.
    Only if these fail is the system restore used.
    This is because the dump files may not be created or may disappear when system restore is used.

    When you're ready I'll post more detailed instructions on how to use the tool.

    .
    .
    .
    .
    .
    Please remember to vote and to mark the replies as answers if they help.

    On the bottom of each post there is:

    Propose as answer = answered the question

    On the left side of each post: Vote = a helpful post
    .
    .
    .
    .
    .


  4. Docs 15,146 Reputation points
    2021-10-25T19:37:06.31+00:00

    Please make free backup images and save the images to another disk drive or the cloud:

    https://www.tenforums.com/tutorials/61026-backup-restore-macrium-reflect.html
    https://www.macrium.com/reflectfree

    The WDV tool is used in the background.
    The computer can be used as usual.
    If there are crashes the tool must be turned off to return to the desktop.
    The log collector is then ran to collect the applicable files.

    The purpose of using the tool is to find misbehaving drivers by stress testing them.
    If misbehaving drivers are found while using the tool they will present as BSOD.

    The misbehaving drivers can then be uninstalled.
    The tool is then restarted to find the next misbehaving driver.
    At the end all drivers that had been uninstalled can be reinstalled.

    Alternatively, once a misbehaving driver is uninstalled, a new driver can be installed.
    The end result is the same.
    All installed and reinstalled drivers are tested.

    After there are no longer any BSOD during the first 48 hours the tool is run for an additional 36 hours to make sure that there are no misbehaving drivers.

    In the first 48 hours the end user must understand how to turn off the tool and recover from the WDV BSOD.
    In order to turn off the tool the computer is rebooted into safe mode.
    In safe mode either the reset or bootmode commands or both are ran to turn off the tool.

    Sometimes the above commands do not turn off the tool.
    If this happens a system restore is performed.

    WDV has customized test settings.
    While the WDV tool is on there can be changes in computer performance.
    If there are significant changes then the customized settings are modified.

    Once you've made backup images I'll post instructions on how to use the tool.

    .
    .
    .
    .
    .
    Please remember to vote and to mark the replies as answers if they help.

    On the bottom of each post there is:

    Propose as answer = answered the question

    On the left side of each post: Vote = a helpful post
    .
    .
    .
    .
    .


  5. Docs 15,146 Reputation points
    2021-10-24T21:18:03.873+00:00

    It took more than one week for there to be spontaneous BSOD.

    The WDV tool should find any misbehaving drivers.

    The tool will be run to stress test all of the non-Microsoft drivers.

    The unstable drivers should crash or produce BSOD.

    The drivers are then replaced.

    The tool will run in the background if there are no immediate BSOD.

    The testing is done for 48 hours of typical computer use.

    Then it is run for an additional 36 hours after the last BSOD.

    If there are no further BSOD this will conclude the use of the tool.

    If there are any new BSOD after the 48 + 36 hours runs then there may be malfunctioning hardware.

    There are stress tests for hardware.

    If there is malfunctioning hardware then you can swap test (RAM).

    If there is a component that is malfunctioning that is not easy to remove or replace then it will need to be serviced at a local repair shop.

    Some BSOD are easy others take more time to find one or more causes of the BSOD.

    .
    .
    .
    .
    .
    Please remember to vote and to mark the replies as answers if they help.

    On the bottom of each post there is:

    Propose as answer = answered the question

    On the left side of each post: Vote = a helpful post
    .
    .
    .
    .
    .