Watchdog violation assume this is a bsod

Page 1 of 2 12 LastLast

  1. Posts : 7,724
    3-Win-7Prox64 3-Win10Prox64 3-LinuxMint20.2
       #1

    Watchdog violation assume this is a bsod


    Hi,
    Okay besides stop oc'ing to all core 48 is there anything meaningful in this ?
    Attachment 163071
    Code:
    Log Name:      System
    Source:        Microsoft-Windows-WER-SystemErrorReporting
    Date:          11/9/2017 8:07:33 PM
    Event ID:      1001
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      masqww-win-10-x299
    Description:
    The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000133 (0x0000000000000001, 0x0000000000001e00, 0xfffff8013b400370, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: d7dab68b-f98a-4ecf-b1c0-a2403509d90e.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />
        <EventID Qualifiers="16384">1001</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2017-11-10T02:07:33.759286500Z" />
        <EventRecordID>8488</EventRecordID>
        <Correlation />
        <Execution ProcessID="0" ThreadID="0" />
        <Channel>System</Channel>
        <Computer>masqww-win-10-x299</Computer>
        <Security />
      </System>
      <EventData>
        <Data Name="param1">0x00000133 (0x0000000000000001, 0x0000000000001e00, 0xfffff8013b400370, 0x0000000000000000)</Data>
        <Data Name="param2">C:\WINDOWS\MEMORY.DMP</Data>
        <Data Name="param3">d7dab68b-f98a-4ecf-b1c0-a2403509d90e</Data>
      </EventData>
    </Event>
      My Computers


  2. Posts : 14,903
    Windows 10 Pro
       #2

    Hi ThrashZone,

    Could you upload a kernel dump, C:\Windows\MEMORY.dmp :)

    Determining the cause of a stop 0x133 with a first parameter of 1 is a bit more difficult because the problem is a result of DPCs running from multiple drivers, so the call stack is insufficient to determine the culprit.

    Source: Determining the source of Bug Check 0x133 (DPC_WATCHDOG_VIOLATION) errors on Windows Server 2012 Ntdebugging Blog
    See BSOD Windows 10 build 1703 and 1709 - Page 2 - Windows 10 Forums
      My Computers


  3. Posts : 7,724
    3-Win-7Prox64 3-Win10Prox64 3-LinuxMint20.2
    Thread Starter
       #3

    Hi @axe0
    Okay I guess this is what you want
    Yep won't upload
    But I can give you a hint of which benchmark to look for ROG RealBench 2.56
    Memory zip uploaded here
    OneDrive
      My Computers


  4. Posts : 27,180
    Win11 Pro, Win10 Pro N, Win10 Home, Windows 8.1 Pro, Ubuntu
       #4

    Hey, Mike, one program I have installed for when OCing and benchmarking is the free version of WhoCrashed: http://www.resplendence.com/whocrashed_help.htm

    This program checks for drivers which have been crashing your computer. If your computer has displayed a blue screen of death, suddenly rebooted or shut down then this program will help you find the root cause as well as a solution.

    Whenever a computer suddenly reboots without displaying any notice or blue screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue screen unless they are configured for this. Instead these systems suddenly reboot without any notice.

    This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. If will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.
    It can tell you if it was a program driver or Windows driver.
    Attachment 163124

    Attachment 163125
      My Computers


  5. Posts : 7,724
    3-Win-7Prox64 3-Win10Prox64 3-LinuxMint20.2
    Thread Starter
       #5

    Hi,
    The top of the list is what that utility showed as crashing thanks for that but third party drivers well MS did not manufacture hardware so an MS driver is also third party
    The IDE Intel 200 series I installed because windows standard or what ever it was named as was crashing too long before 200 series was installed
    I did uninstall Panda free I searched the normal bios update.... was offered but also third party security was also named as Norton of course no news on that one
    But anyway tuned it down to x47 and realbench with out Panda finished although it did fine at x47 before
    I'll have to try x48 again to see for sure but I suspect the same norm watchdog blah... will happen :)
    Attachment 163137
      My Computers


  6. Posts : 27,180
    Win11 Pro, Win10 Pro N, Win10 Home, Windows 8.1 Pro, Ubuntu
       #6

    ThrashZone said:
    Hi,
    The top of the list is what that utility showed as crashing thanks for that but third party drivers well MS did not manufacture hardware so an MS driver is also third party
    The IDE Intel 200 series I installed because windows standard or what ever it was named as was crashing too long before 200 series was installed
    I did uninstall Panda free I searched the normal bios update.... was offered but also third party security was also named as Norton of course no news on that one
    But anyway tuned it down to x47 and realbench with out Panda finished although it did fine at x47 before
    I'll have to try x48 again to see for sure but I suspect the same norm watchdog blah... will happen :)
    Attachment 163137
    Also you've been fiddling with your RAM timings and settings, or was it set to "normal" XMP when this happened?
      My Computers


  7. Posts : 7,724
    3-Win-7Prox64 3-Win10Prox64 3-LinuxMint20.2
    Thread Starter
       #7

    Hi,
    Happens either way but started long before timings were adjusted even happened with my other ram so the ram is not the problem or the timings
    But they have been at default manual 3200 @1.35v and still happens at x48 but I have not tried since removing Panda free yet.

    First showing and search of pointed to the IDE.... driver it was using an MS standard and I switched it to the Intel 200 series.
    Calmed down until I started hitting x48 so I've been adjusting bumping up power settings to cpu.
      My Computers


  8. Posts : 7,724
    3-Win-7Prox64 3-Win10Prox64 3-LinuxMint20.2
    Thread Starter
       #8

    Hi,
    For the record these are the timings and I agree with @Dude c15 is better :)
    Attachment 163143
      My Computers


  9. Posts : 27,180
    Win11 Pro, Win10 Pro N, Win10 Home, Windows 8.1 Pro, Ubuntu
       #9

    Hey Mike, another thing I just remembered:
    When I used to have Intel's XTU and MSI's Command Center, I would get a lot of watchdog violation BSODs and errors.

    This happens because both communicate at a low level directly with BIOS, and there was (at least on my system) a conflict.

    Both have been uninstalled for quite some time now, XTU because of the watchdog errors, and Command Center, because the Windows 10 Creators Update broke the communication of Command Center to RAM, and could not load module to do with RAM.


    Do you have XTU installed?
      My Computers


  10. Posts : 7,724
    3-Win-7Prox64 3-Win10Prox64 3-LinuxMint20.2
    Thread Starter
       #10

    Hi,
    I have no idea what that is abbreviations are not very good to use :)
      My Computers


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 15:15.
Find Us




Windows 10 Forums