Windows 10: DPC_WATCHDOG_VIOLATION (Kernel symbols are WRONG)

Hi guys!

First, thank you for all the help you give to the communities.

I have an issue and I'm unable to find the culprit. The computer reboot without warning at different time (random)

I used osronline.com to scan the dump file, but it says "Kernel symbols are WRONG".

Someone can help me to find the solution for my issue? dump file included

Attachment 113756

:)

 

BSOD in windows 10 build 10586, version 1511

I reinstalled win10 th2 freshly.

But the blue screen often occurred.

The following is part of the MEMORY.DMP.

Can somebody help me to figure it out? Thank you.

Loading Dump File [C:\Users\tp\Desktop\MEMORY.DMP]

Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.
Symbol search path is: *** Invalid ***

****************************************************************************

* Symbol loading may be unreliable without a symbol search path. *

* Use .symfix to have the debugger choose a symbol path. *

* After setting your symbol path, use .reload to refresh symbol locations. *

****************************************************************************

Executable search path is:

*********************************************************************

* Symbols can not be loaded because symbol path is not initialized. *

* *

* The Symbol Path can be set by: *

* using the _NT_SYMBOL_PATH environment variable. *

* using the -y <symbol_path> argument when starting the debugger. *

* using .sympath and .sympath+ *

*********************************************************************

*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -

Windows 10 Kernel Version 10586 MP (4 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 10586.3.amd64fre.th2_release_sec.151104-1948

Machine Name:

Kernel base = 0xfffff801`f127b000 PsLoadedModuleList = 0xfffff801`f1559cb0

Debug session time: Mon Nov 16 16:48:53.722 2015 (UTC + 8:00)

System Uptime: 0 days 6:17:02.785

*********************************************************************

* Symbols can not be loaded because symbol path is not initialized. *

* *

* The Symbol Path can be set by: *

* using the _NT_SYMBOL_PATH environment variable. *

* using the -y <symbol_path> argument when starting the debugger. *

* using .sympath and .sympath+ *

*********************************************************************

*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -

Loading Kernel Symbols

.............................................................Page 3654 not present in the dump file. Type ".hh dbgerr004" for details

..

................................................................

........................................................

Loading User Symbols
Loading unloaded module list

............
************* Symbol Loading Error Summary **************

Module name Error

ntkrnlmp The system cannot find the file specified
You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.

You should also verify that your symbol search path (.sympath) is correct.

No .natvis files found at C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\Visualizers.

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7E, {ffffffffc0000005, 0, ffffd0008711c938, ffffd0008711c150}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*** ERROR: Module load completed but symbols could not be loaded for rtwlane.sys

 

Getting BSOD in Windows 10 several times per day

While I am generally a fan of Nirsofts software BSV is wrong more often than it is correct because it takes a quick snapshot of what is going on and does not analyze the entire sequence.

The gold standard for doing BSOD analysis is called Window Debugger

Microsoft (R) Windows Debugger Version 10.0.10586.567 AMD64

Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\zigza\Desktop\minidump\011916-10312-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

************* Symbol Path validation summary **************

Response Time (ms) Location

Deferred SRV*E:\symbols*Symbol information.

Symbol search path is: SRV*E:\symbols*Symbol information.

Executable search path is:

Windows 10 Kernel Version 10586 MP (6 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 10586.63.amd64fre.th2_release.160104-1513

Machine Name:

Kernel base = 0xfffff803`20a7f000 PsLoadedModuleList = 0xfffff803`20d5dc70

Debug session time: Tue Jan 19 09:03:04.337 2016 (UTC - 5:00)

System Uptime: 0 days 9:06:38.068

Loading Kernel Symbols

...............................................................

................................................................

..........................................

Loading User Symbols

Loading unloaded module list

..........................

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 139, {3, ffffd00025e22550, ffffd00025e224a8, 0}

*** WARNING: Unable to verify timestamp for kltdf.sys

*** ERROR: Module load completed but symbols could not be loaded for kltdf.sys (Kaspersky) which IMHO is garbage anyway.

 

Please use the BSOD posting instruction to provide the Dumpfile BSOD - Posting Instructions - Windows 10 Forums
And fill in your System Specs.

 

Hi,

The machine have crashed 3 times today

I included the minidump (and all the things) zipped below

Attachment 116856

 

All 3 dumpfiles blames your NVdiadriver, update to the latest version.