Windows 10 DPC Watchdog violation

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Cappy2234
    PCHF Member
    • Aug 2018
    • 7

    #1

    Windows 10 DPC Watchdog violation

    Hi,
    So after installing WIndows 10 and updating all my drivers this happened.Can someone help fix this error & is it possible that changing paging file caused this?
  • jmarket
    PCHF Owner
    • Jan 2015
    • 7635

    #2
    HI @Cappy2234 and Welcome to PCHF

    Please read the BSOD Prework before doing the following.

    Please download the Sysnative BSOD Dump + System File Collection App - save to Documents folder.

    Run the app - Double-click on the downloaded EXE file
    Output = new folder created in Documents + a zipped version – SysnativeFileCollectionApp folder + SysnativeFileCollectionApp.zip.

    Please note that the app averages ~3 minutes to run on most systems; other systems - it my take as long as 10-15 minutes to run. Please be patient.

    Also note: The app auto-zips the SysnativeFileCollectionApp output folder. It is located in your Documents folder.
    Windows Explorer should open and highlight the zipped folder

    Please attach the SysnativeFileCollectionApp.zip to your post and await further instructions

    Comment

    • Cappy2234
      PCHF Member
      • Aug 2018
      • 7

      #3
      I’ve attached minidump and sysnative file collection app (both files were created after I got the DPC Watchdog violation) . If these 2 files don’t help I’ll force DPC Watchdog violation and do sysnativefilecollectionapp again.Hopefully I don’t have to force this error since its really annoying.

      Comment

      • jmarket
        PCHF Owner
        • Jan 2015
        • 7635

        #4
        Thanks for those.

        With the Watchdog Violation, it’s extremely difficult to pinpoint the exact cause. Let’s run some tests first.

        [ul]
        [li]Click on the Start button and in the search box, type Command Prompt[/li][li]When you see Command Prompt on the list, right-click on it and select Run as administrator[/li][li]When command prompt opens, copy and paste the following command into it, press Enter.[/li]
        [ICODE]sfc /scannow[/ICODE]
        [li]Wait for this to finish before you continue[/li][li]Copy and paste the following command, press Enter.[/li]
        [ICODE]findstr /c:"[SR]" %windir%\logs\cbs\cbs.log > %userprofile%\Desktop\sfc.txt[/ICODE]
        [/ul]
        That will create sfc.txt on your Desktop. Please attach sfc.txt to your next post:
        [ul]
        [li]Open Reply window. Click β€˜More Reply Options’.[/li][li]Go to the end of your text (if any).[/li][li]Click β€˜Choose Files..’[/li][li]For β€˜File name’ paste this: %userprofile%\Desktop\sfc.txt[/li][li]Click the β€˜Add to Post’ link which will appear on the right when the file has been uploaded.[/li][li]Click β€˜Add Reply’.[/li][/ul]
        Let’s test your RAM to ensure your RAM is OK

        [ul]
        [li]Click Start, type mdsched.exe in the Search box, and then press Enter.[/li][li]Choose whether to restart the computer and run the tool immediately or schedule the tool to run at the next restart.[/li][li]Windows Memory Diagnostics runs automatically after the computer restarts and performs a standard memory test automatically. If you want to perform fewer or more tests, press F1, use the Up and Down arrow keys to set the Test Mix as Basic, Standard, or Extended, and then press F10 to apply the desired settings and resume testing.[/li][li]When testing is completed, the computer restarts automatically. You’ll see the test results when you log on.[/li][/ul]

        Comment

        • Cappy2234
          PCHF Member
          • Aug 2018
          • 7

          #5
          Here it is,it does have some corrupted files that it couldn’t fix.

          Comment

          • jmarket
            PCHF Owner
            • Jan 2015
            • 7635

            #6
            Go ahead and run:
            [ICODE]chkdsk /f[/ICODE]
            and let it run. After doing so, let us know if it finds errors and then try repeating the action that caused the BSOD in the first place.

            Comment

            • jmarket
              PCHF Owner
              • Jan 2015
              • 7635

              #7
              Any updates for us @Cappy2234?

              Comment

              • Cappy2234
                PCHF Member
                • Aug 2018
                • 7

                #8
                Hi,sorry for not replying for so long.
                I discovered the problem,it’s the newest driver for my graphics card (398.82 version for my gtx 1050ti).I get dpc watchdog violation when I install this driver,so I’m going to ask people on nVidia forums.

                Comment

                • jmarket
                  PCHF Owner
                  • Jan 2015
                  • 7635

                  #9
                  Glad to hear @Cappy2234

                  Do let us know what you find out

                  Comment

                  • Cappy2234
                    PCHF Member
                    • Aug 2018
                    • 7

                    #10
                    Hi,just a quick update:it turns out it’s some kind of error with nVidia’s latest drivers.I can’t download the latest driver yet,but maybe I’ll be able to download the driver when they fix it.
                    Thanks for the help !

                    Comment

                    • system
                      PCHF Owner
                      • Jan 2015
                      • 7635

                      #11
                      Ensure you get your Video drivers from your card manufacturers website, AND NOT FROM WINDOWS.

                      Comment

                      • veeg
                        PCHF Director
                        • Jul 2016
                        • 8977

                        #12
                        Any updates for us?

                        Comment

                        • Cappy2234
                          PCHF Member
                          • Aug 2018
                          • 7

                          #13
                          I can’t do anything with this error.I’ll just use a bit older drivers until they fix the new one.

                          Comment

                          • veeg
                            PCHF Director
                            • Jul 2016
                            • 8977

                            #14
                            Thanks for the update. So you are saying you found a work around?

                            Comment

                            • Cappy2234
                              PCHF Member
                              • Aug 2018
                              • 7

                              #15
                              I think so,yeah.

                              Comment

                              Working...