Windows 10: DPC_WATCHDOG_VIOLATION 0x1330x1, 0x1E00, 0xFFFFF80533AFB320, 0x0 - BSOD Computer crashing

Discus and support DPC_WATCHDOG_VIOLATION 0x1330x1, 0x1E00, 0xFFFFF80533AFB320, 0x0 - BSOD Computer crashing in Windows 10 BSOD Crashes and Debugging to solve the problem; Hello,Would anyone be able to assist with identifying the cause of some recent BSODs I have had?They manifest when playing games and the following... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by blue.castle, Dec 2, 2024.

  1. DPC_WATCHDOG_VIOLATION 0x1330x1, 0x1E00, 0xFFFFF80533AFB320, 0x0 - BSOD Computer crashing


    Hello,Would anyone be able to assist with identifying the cause of some recent BSODs I have had?They manifest when playing games and the following takes place over ~2 minutes:1. Monitors go black but sound continues. If using Discord I can continue to talk.2. Audio input cuts out but I can still hear games/music/Discord.3. Audio cuts out. Fans whir loudly.4. Computer restarts. I have tried numerous fixes but still experienced crashes afterwards, here are the fixes I've tried:1. Used DDU to uninstall Nvidia graphics cards and installed an older version of Nvidia drivers.2. Updates CPU firmware.

    :)
     
    blue.castle, Dec 2, 2024
    #1

  2. DPC_WATCHDOG_VIOLATION. 0x133(0x1, 0x1E00, 0xFFFFF8033A71C340, 0x0)

    Hey,

    For the past few weeks, I’ve been experiencing crashes on my PC. Windows freezes for a few minutes and then restarts automatically (no blue screen). All drivers, Windows, and BIOS are updated to the latest versions available. I’ve updated and reinstalled everything several times. I’ve also checked the M.2 SSD and memory several times to ensure they are working correctly and reconfigured their locations.

    I’ve run WhoCrashed to analyze the .dmp files, but I need help finding the root cause.

    Minidump File -- Click here -- OR 061524-12718-01.zip

    Thank you

    --- --- --- --- --- ---

    WhoCrashed

    --- --- --- --- --- ---

    System Information (local)

    [table][tr][td]GPU: [/td][td]Asus TUF 4090, 24 GB[/td][/tr][tr][td]Windows version:[/td][td]Windows 11, 10.0, version 2009, build: 22631 (x64)[/td][/tr][tr][td]Windows dir:[/td][td]C:\WINDOWS[/td][/tr][tr][td]Hardware:[/td][td]Z790 AORUS MASTER X (v1.1), Gigabyte Technology Co., Ltd.[/td][/tr][tr][td]CPU:[/td][td]GenuineIntel Intel(R) Core(TM) i9-14900K 8664, level: 6[/td][/tr][tr][td]Processor count:[/td][td]32 logical processors, active mask: 4294967295[/td][/tr][tr][td]RAM:[/td][td]196370.4MB[/td][/tr][/table]

    Crash Dump Analysis

    Crash dumps are enabled on your computer. This system is not configured for complete or automatic crash dumps. For best results, configure your system to write out complete or automatic crash dumps. Select Tools->Crash Dump Configuration from the main menu to configure your system to write out complete memory dumps.

    Crash dump directories:

    C:\Windows

    C:\Windows\Minidump

    On Sat 6/15/2024 9:23:44 PM your computer crashed or a problem was reported

    [table][tr][td]Crash dump file:[/td][td]C:\Windows\Minidump\061524-12718-01.dmp (Minidump)[/td][/tr][tr][td]Bugcheck code:[/td][td]0x133(0x1, 0x1E00, 0xFFFFF8033A71C340, 0x0)[/td][/tr][tr][td]Bugcheck name:[/td][td]DPC_WATCHDOG_VIOLATION[/td][/tr][tr][td]Bug check description:[/td][td]The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue).[/td][/tr][tr][td]Analysis:[/td][td]This is likely caused by a hardware problem, but there is a possibility that this is caused by a misbehaving driver.This bugcheck indicates that a timeout has occurred. This may be caused by a hardware failure such as a thermal issue or a bug in a driver for a hardware device.Read this article on thermal issuesA full memory dump will likely provide more useful information on the cause of this particular bugcheck.[/td][/tr][tr][td][/td][td][/td][/tr][/table]

    Conclusion

    One crash dump has been found and analyzed. No offending third party drivers have been found. Consider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.

    Read the suggestions displayed in the bugcheck analysis above.

    The analysis process took 0:00:03 (h:mm:ss).


     
    Oleg Sukhorukov, Dec 2, 2024
    #2
  3. Thom's1 Win User
    I suddenly have repetitive crashes and "DPC_WATCHDOG_VIOLATION" when starting videogames

    Hello everyone,

    I'm facing a frustrating issue on my Windows 11 PC that keeps causing crashes with the error message "DPC_WATCHDOG_VIOLATION." I looked in the dump file with whocrashed and it appears that the problem is the "intelppm.sys" module.

    • Crash dump file: C:\WINDOWS\Minidump\052523-28093-01.dmp
    • Bugcheck code: 0x133 (0x1, 0x1E00, 0xFFFFF8040CB1C340, 0x0)
    • Error: DPC_WATCHDOG_VIOLATION
    • File path: C:\WINDOWS\system32\drivers\intelppm.sys
    The crashes are not random but consistently occur when I launch video games. It's a bit odd to me because I haven't encountered this issue before, and I haven't made any recent changes to my system that could have triggered it.

    I have tried to update most of my drivers and check the temperature of my hardware, but unfortunately the problem persists.

    I have created a folder with the minidump files and the memory.dmp here, I dont know if it helps : dmp – Google Drive

    Thanks a lot for the help,

    Thomas
     
    Thom's1, Dec 2, 2024
    #3
  4. ipaul Win User

    DPC_WATCHDOG_VIOLATION 0x1330x1, 0x1E00, 0xFFFFF80533AFB320, 0x0 - BSOD Computer crashing

    Daily BSOD (DPC_WATCHDOG_VIOLATION): ntoskrnl.exe? nvstor.sys?

    I just had my first BSOD since updating BIOS to the latest version *Sad

    Here's the crash report (it's the same two potential causes as before the BSOD update: ntoskrnl.exe and nvstor.sys).

    On Tue 12/6/2016 3:26:11 PM GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\120616-37484-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x14A510)
    Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0x0)
    Error: DPC_WATCHDOG_VIOLATION
    file path: C:\WINDOWS\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue). The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

    On Tue 12/6/2016 3:26:11 PM GMT your computer crashed
    crash dump file: C:\WINDOWS\memory.dmp
    This was probably caused by the following module: nvstor.sys (nvstor+0x7468)
    Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0x0)
    Error: DPC_WATCHDOG_VIOLATION
    file path: C:\WINDOWS\system32\drivers\nvstor.sys
    product: NVIDIA nForce(TM) SATA Driver
    company: NVIDIA Corporation
    description: NVIDIA® nForce(TM) Sata Performance Driver
    Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue). A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvstor.sys (NVIDIA® nForce(TM) Sata Performance Driver, NVIDIA Corporation).
    Google query: NVIDIA Corporation DPC_WATCHDOG_VIOLATION

    The above was run with "WhoCrashed". What else would you suggest I try next? Thanks for your time.
     
    ipaul, Dec 2, 2024
    #4
Thema:

DPC_WATCHDOG_VIOLATION 0x1330x1, 0x1E00, 0xFFFFF80533AFB320, 0x0 - BSOD Computer crashing

Loading...
  1. DPC_WATCHDOG_VIOLATION 0x1330x1, 0x1E00, 0xFFFFF80533AFB320, 0x0 - BSOD Computer crashing - Similar Threads - DPC_WATCHDOG_VIOLATION 0x1330x1 0x1E00

  2. Error 0x1330x1, 0x1e00, 0xfffff800738fb320, 0x0

    in Windows 10 BSOD Crashes and Debugging
    Error 0x1330x1, 0x1e00, 0xfffff800738fb320, 0x0: I have been having issues with my PC where I lose connection to my monitors randomly and can only fix it by restarting my PC through the power button. I used WhoCrashed and it says the Bugcheck is a DPC_WATCHDOG_VIOLATION: The DPC watchdog detected a prolonged run time at an...
  3. Error 0x1330x1, 0x1e00, 0xfffff800738fb320, 0x0

    in Windows 10 Gaming
    Error 0x1330x1, 0x1e00, 0xfffff800738fb320, 0x0: I have been having issues with my PC where I lose connection to my monitors randomly and can only fix it by restarting my PC through the power button. I used WhoCrashed and it says the Bugcheck is a DPC_WATCHDOG_VIOLATION: The DPC watchdog detected a prolonged run time at an...
  4. Error 0x1330x1, 0x1e00, 0xfffff800738fb320, 0x0

    in Windows 10 Software and Apps
    Error 0x1330x1, 0x1e00, 0xfffff800738fb320, 0x0: I have been having issues with my PC where I lose connection to my monitors randomly and can only fix it by restarting my PC through the power button. I used WhoCrashed and it says the Bugcheck is a DPC_WATCHDOG_VIOLATION: The DPC watchdog detected a prolonged run time at an...
  5. DPC_WATCHDOG_VIOLATION 0x1330x1, 0x1E00, 0xFFFFF80533AFB320, 0x0 - BSOD Computer crashing

    in Windows 10 Gaming
    DPC_WATCHDOG_VIOLATION 0x1330x1, 0x1E00, 0xFFFFF80533AFB320, 0x0 - BSOD Computer crashing: Hello,Would anyone be able to assist with identifying the cause of some recent BSODs I have had?They manifest when playing games and the following takes place over ~2 minutes:1. Monitors go black but sound continues. If using Discord I can continue to talk.2. Audio input cuts...
  6. DPC_WATCHDOG_VIOLATION 0x1330x1, 0x1E00, 0xFFFFF80533AFB320, 0x0 - BSOD Computer crashing

    in Windows 10 Software and Apps
    DPC_WATCHDOG_VIOLATION 0x1330x1, 0x1E00, 0xFFFFF80533AFB320, 0x0 - BSOD Computer crashing: Hello,Would anyone be able to assist with identifying the cause of some recent BSODs I have had?They manifest when playing games and the following takes place over ~2 minutes:1. Monitors go black but sound continues. If using Discord I can continue to talk.2. Audio input cuts...
  7. DPC_WATCHDOG_VIOLATION. 0x1330x1, 0x1E00, 0xFFFFF8033A71C340, 0x0

    in Windows 10 Gaming
    DPC_WATCHDOG_VIOLATION. 0x1330x1, 0x1E00, 0xFFFFF8033A71C340, 0x0: Hey,For the past few weeks, I’ve been experiencing crashes on my PC. Windows freezes for a few minutes and then restarts automatically no blue screen. All drivers, Windows, and BIOS are updated to the latest versions available. I’ve updated and reinstalled everything several...
  8. DPC_WATCHDOG_VIOLATION. 0x1330x1, 0x1E00, 0xFFFFF8033A71C340, 0x0

    in Windows 10 Software and Apps
    DPC_WATCHDOG_VIOLATION. 0x1330x1, 0x1E00, 0xFFFFF8033A71C340, 0x0: Hey,For the past few weeks, I’ve been experiencing crashes on my PC. Windows freezes for a few minutes and then restarts automatically no blue screen. All drivers, Windows, and BIOS are updated to the latest versions available. I’ve updated and reinstalled everything several...
  9. BSOD Crashes DPC_Watchdog_Violation

    in Windows 10 Drivers and Hardware
    BSOD Crashes DPC_Watchdog_Violation: Hi.My computer seems to continuously BSOD at random times. Sometimes upon startup, sometimes after 10-20 minutes of use. Sometimes but not every time I hear the sound Windows make when a USB is inserted just before the crash even though no USB has been inserted.Thanks in...
  10. Bugcheck code: 0x133 0x1, 0x1E00, 0xFFFFF8022C4FB320, 0x0

    in Windows 10 BSOD Crashes and Debugging
    Bugcheck code: 0x133 0x1, 0x1E00, 0xFFFFF8022C4FB320, 0x0: Hi, For a few days I'm experiencing some crashes on my laptop. Windows freezes for a few minutes and restarts automatically no bluescreen. I've checked the Event Viewer but nothing relevant was found. The issue appears once a day: Crash + reboot and working fine again....