1. Joined : Jun 2015
    Posts : 224
    Win10 Pro x64
       05 Jun 2015 #1

    DPC_WATCHDOG_VIOLATION BSOD, Windbg unable to load symbols


    Windows 10 Insider Preview Build 10130
    WIN-A82HE7DTDIP-Fri_06_05_2015_172808_86.zip attached
    PC Specs are in profile :P

    So I have windbg, I followed the how to install guide (Using both the win8.1 and win10 SDK, both give the same errors, suggested fixes i tried failed on both) and regardless of what I do I have these errors throughout the console window:

    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    I tried !sym noisy/.reload which just brought up a whole bunch of HTTP errors and DLLs not found, and .symfix brought up this:

    DBGHELP: Symbol Search Path: srv*c:\symcache*http://msdl.microsoft.com/download/symbols
    DBGHELP: Symbol Search Path: cache*;SRV*http://msdl.microsoft.com/download/symbols
    DBGHELP: Symbol Search Path: cache*;SRV*http://msdl.microsoft.com/download/symbols

    So I guess what I'm looking for is both a way to get windbg functioning properly and also an answer to what is causing my watchdog violation. I have been running Windows 10 for a while, had 1 watchdog BSOD on a previous Build and now 1 again on this one. No it isn't super frequent but it does bother me!
      My System SpecsSystem Spec


  2. Joined : Oct 2013
    Wolves, England
    Posts : 1,634
    W7 Pro x64 | W10 IP x64 | Linux Mint VM
       05 Jun 2015 #2

    At the moment virtually all W10 BSODs give that output, there's nothing wrong with your WinDBG install. It's pretty hard to debug W10 BSODs at the moment until the symbols are released by MS.
      My System SpecsSystem Spec


  3. Joined : Jun 2015
    Posts : 224
    Win10 Pro x64
       05 Jun 2015 #3

    Boozad said: View Post
    At the moment virtually all W10 BSODs give that output, there's nothing wrong with your WinDBG install. It's pretty hard to debug W10 BSODs at the moment until the symbols are released by MS.
    I was unaware that they hadn't been released, and that would explain my trouble! I was sitting here like I know I did this right... Well thanks for confirming I'm not going nuts and I guess the thread is pointless until the symbols are available.
      My System SpecsSystem Spec


  4. Joined : Oct 2013
    Wolves, England
    Posts : 1,634
    W7 Pro x64 | W10 IP x64 | Linux Mint VM
       05 Jun 2015 #4

    Unfortunately there's not much any of us can do until the symbols become available, personally I don't think I've been able to read a single dump posted to 10F yet. If you ever want more info on WinDBG feel free to have a read thorough this WinDBG - The Basics for Debugging Crash Dumps in Windows 10 - Windows 10 Forums and as soon as we can help you we most certainly will.
      My System SpecsSystem Spec


  5. Joined : Jun 2015
    Posts : 224
    Win10 Pro x64
       11 Jun 2015 #5

    Ok so now I am slightly confused... According to https://msdn.microsoft.com/en-us/win.../gg463028.aspx The debug symbols for the insider preview are available for download? Which would mean the the symbol server also has these symbols, so why does it return a symbols are invalid error? Is it possibly because the latest update to the symbols was in April and build 10130 came afterwards? (Or i think it did?)
      My System SpecsSystem Spec


  6. Joined : Jun 2015
    Posts : 224
    Win10 Pro x64
       01 Aug 2015 #6

    Bumping my old thread, which I think I posted back on build 10130... I still get the DPC_WATCHDOG_VIOLATION BSODs, which WinDBG finds nvlddmkm.sys to be the culprit (as I expected), and returns "*** Memory manager detected 48 instance(s) of page corruption, target is likely to have memory corruption." It has happened with each build of Windows 10, and each driver released so far from Nvidia for Windows 10. I posted the problem and the WinDBG results both in the WIndows 10 driver feedback thread on GeForce forums, as well as filling out a feedback form and copy/pasting the results into that. Marking thread solved as I know what the problem is, and hopefully Nvidia remedies the situation shortly.
      My System SpecsSystem Spec


 


Similar Threads
Thread Forum
Solved Do we have debug symbols yet?
As stated clearly in the title, I wanna know when we are gonna get our debug symbols? Would have been nice to have my bsods debugged BEFORE RTM, but since that is tomorrow that obviously isn't going to happen. Does anyone know when the symbols will...
BSOD Crashes and Debugging
Solved Unable to load build 10162, error 0x800705b4
I successfully installed build 10159 when it came out (the prior builds were also successfully installed); however, when I tried to download 10162, the download appeared to be successful, but the install step failed, giving me the 0x800705b4 error...
Installation and Setup
Solved Need Help with setting up Windbg
I seem to be suffering from a severe lack of knowledge and experience in this area. I am trying to read dump file created by Windows 10 but keep seeing errors about ntoskrnl.exe and symbol errors. I have gone through the tutorial by Golden. I...
BSOD Crashes and Debugging
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 16:21.
Find Us
Twitter Facebook Google+



Windows 10 Forums