BSOD - DPC_WATCHDOG_VIOLATION.

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • phillpower2
    PCHF Administrator
    • Sep 2016
    • 15209

    #31
    Check the version details of those drivers against the latest on offer from MSI here

    I still don`t get how network drivers crashed the system when you were offline, strange :unsure:

    Comment

    • Exyztence
      PCHF Member
      • Apr 2020
      • 126

      #32
      Those drivers on intel’s website are from yesterday, MSI has drivers from a month ago.
      Maybe I will create a restore point and update them?
      It’s also strange for me, like 2 days in a row everything was fine and when I was idle, the pc crashed.

      EDIT:
      I checked those drivers release notes of their update and found this:
      Windows* Stop Errors (BSOD) caused by the Intel Wireless Driver. Win10 (fixed)

      https://downloadmirror.intel.com/295...Fi_21.90.3.pdf ← its in this one (wifi)

      Comment

      • phillpower2
        PCHF Administrator
        • Sep 2016
        • 15209

        #33
        Restore point and drivers from Intel it is then.

        Comment

        • Exyztence
          PCHF Member
          • Apr 2020
          • 126

          #34
          New crash right now

          Comment

          • Exyztence
            PCHF Member
            • Apr 2020
            • 126

            #35
            Hi,
            it crashed again when I was idle. The same reason as yesterday - audiodg.exe

            Comment

            • phillpower2
              PCHF Administrator
              • Sep 2016
              • 15209

              #36
              What was the computer being used for at the time of each crash.

              Comment

              • Exyztence
                PCHF Member
                • Apr 2020
                • 126

                #37
                I was idle again.

                Comment

                • phillpower2
                  PCHF Administrator
                  • Sep 2016
                  • 15209

                  #38
                  Something that was running in the background caused Windows to crash and the best way to check to see if you can identify what may have caused the problem is to check the Event Viewer to see if anything is identified there that corresponds with the exact time that the computer blue screened, let us know what if anything you find in Event Viewer.

                  I can only see the one way out of this atm and because you install so much stuff on the computer it will be real long winded.

                  Comment

                  • Exyztence
                    PCHF Member
                    • Apr 2020
                    • 126

                    #39
                    The driver \Driver\WudfRd failed to load for the device HID\VID_19F7&PID_0003&MI_03&Col02\7&1049b0e0&0&000 1.
                    The driver \Driver\WudfRd failed to load for the device ROOT\WindowsHelloFaceSoftwareDriver\0000.

                    Those are right before BSOD, nothing more. I’ve read on the internet they are USB and audio related.

                    Comment

                    • phillpower2
                      PCHF Administrator
                      • Sep 2016
                      • 15209

                      #40
                      Apologies for the delay, couldnt find my cnned txt for disabling Hibernation.

                      Those two errors look more like graphics and Windows issues to me.

                      Press Windows+ R > Run box > type services.msc > OK.

                      In the Services window > go to the Windows Driver Foundation – User-mode Driver Framework service, double click on it to open the Properties
                      From the Windows startup type menu choose Automatic.
                      Check that the service is running in the dialog box below, click on Apply and then OK to save the settings

                      Restart the computer then do the following;

                      To disable Hibernation:

                      [ol]
                      [li]The first step is to run the command prompt as administrator. In Windows 10, you can do this by right clicking on the start menu and clicking β€œCommand Prompt (Admin)”[/li][li]Type in β€œpowercfg.exe /h off” without the quotes and press enter. If you typed it in correctly, the cursor will simply start at a new line asking for new input[/li][li]Now just exit out of command prompt[/li][/ol]
                      Restart and see how things go.

                      Comment

                      • Exyztence
                        PCHF Member
                        • Apr 2020
                        • 126

                        #41
                        I don’t have Windows Driver Foundation in services.msc
                        And I disabled Hibernation and restarted PC.

                        Comment

                        • phillpower2
                          PCHF Administrator
                          • Sep 2016
                          • 15209

                          #42
                          That`s not good, if the following does not fix it I recommend you download the latest Windows 10 ISO and clean install Windows.

                          Download then run the Windows All in One Repair tool from here, disregard the malware guidance but follow the other steps to the letter and in particular ensuring that you first create a new restore point and perform a proper Windows clean boot before running the repair, details for the clean boot here.

                          Comment

                          • Exyztence
                            PCHF Member
                            • Apr 2020
                            • 126

                            #43
                            I ran this app, it took some time but didnt help me. Still no Windows Driver Foundation in services.msc. Should it be there? I read that in few versions of windows, its not installed or something like that. If it should be there, what more can I do? I am after clean install, I didnt do anything more except installing drivers and games. No trustless apps.
                            My windows:
                            Version 10.0.18363 Build 18363

                            Comment

                            • phillpower2
                              PCHF Administrator
                              • Sep 2016
                              • 15209

                              #44
                              Originally posted by Exyztence
                              My windows:
                              Version 10.0.18363 Build 18363
                              My apologies you are correct, it has been replaced with something else in later versions which makes the error even more puzzling, can you for now just see how things go after running the AIO repair tool, Ive got a big job on here so may not be around for a couple of hrs but will check back later.

                              There should have been an AIO repair log generated, can you look for it and if found go through it to see what has been repaired.

                              Comment

                              • Exyztence
                                PCHF Member
                                • Apr 2020
                                • 126

                                #45
                                I don’t really know how to check logs, but I found the folder.
                                I will attach it and if u could have a look at it in free time, because I don’t know to what pay attention.
                                I think it made a lot of changes.
                                Thanks in advance.

                                Comment

                                Working...