Skip to content

Instantly share code, notes, and snippets.

Embed
What would you like to do?
Memory Dump ovsext
Microsoft (R) Windows Debugger Version 10.0.18303.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.
Error: Change all symbol paths attempts to access 'srv' failed: 0x2 - Das System kann die angegebene Datei nicht finden.
************* Path validation summary **************
Response Time (ms) Location
Error srv
OK C:\Program Files\Cloudbase Solutions\Open vSwitch\driver\
Symbol search path is: srv;C:\Program Files\Cloudbase Solutions\Open vSwitch\driver\
Executable search path is:
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_MMPTE_TRANSITION ***
*** ***
*************************************************************************
Windows 10 Kernel Version 17134 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 17134.1.amd64fre.rs4_release.180410-1804
Machine Name:
Kernel base = 0xfffff803`a5e0d000 PsLoadedModuleList = 0xfffff803`a61bb150
Debug session time: Mon Jan 7 00:18:24.973 2019 (UTC + 1:00)
System Uptime: 1 days 0:28:16.811
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_MMPTE_TRANSITION ***
*** ***
*************************************************************************
Loading Kernel Symbols
...............................................................
................................................................
................................................................
................................................................
..
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.
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff803`a5fb70a0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff8c0f`6a71c970=0000000000000019
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 0000000000000020, a pool block header size is corrupt.
Arg2: ffffb5823fde7d30, The pool entry we were looking for within the page.
Arg3: ffffb5823fde7da0, The next pool entry.
Arg4: 0000000004070019, (reserved)
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!PVOID ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_EPROCESS ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPCR ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KTHREAD ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_MI_SYSTEM_INFORMATION ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_MI_SYSTEM_INFORMATION ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_MMPTE ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_MMPTE ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
KEY_VALUES_STRING: 1
PROCESSES_ANALYSIS: 1
STACKHASH_ANALYSIS: 1
TIMELINE_ANALYSIS: 1
DUMP_CLASS: 1
DUMP_QUALIFIER: 401
BUILD_VERSION_STRING: 17134.1.amd64fre.rs4_release.180410-1804
SYSTEM_MANUFACTURER: Microsoft Corporation
SYSTEM_PRODUCT_NAME: Surface Book 2
SYSTEM_SKU: Surface_Book_1793
SYSTEM_VERSION: D:0B:08K:1F:5C:10P:38
BIOS_VENDOR: Microsoft Corporation
BIOS_VERSION: 389.2370.769
BIOS_DATE: 10/02/2018
BASEBOARD_MANUFACTURER: Microsoft Corporation
BASEBOARD_PRODUCT: Surface Book 2
ADDITIONAL_DEBUG_TEXT:
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.
WRONG_SYMBOLS_TIMESTAMP: 5c135351
WRONG_SYMBOLS_SIZE: 953000
FAULTING_MODULE: fffff803a5e0d000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 5c135351
DUMP_TYPE: 1
BUGCHECK_P1: 20
BUGCHECK_P2: ffffb5823fde7d30
BUGCHECK_P3: ffffb5823fde7da0
BUGCHECK_P4: 4070019
POOL_ADDRESS: *************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_MMPFN ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_MMPTE ***
*** ***
*************************************************************************
Unable to get size of nt!_MMPTE - probably bad symbols
ffffb5823fde7d30
CPU_COUNT: 8
CPU_MHZ: 840
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 8e
CPU_STEPPING: a
CPU_MICROCODE: 0,0,0,0 (F,M,S,R) SIG: 8E'00000000 (cache) 0'00000000 (init)
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXPNP: 1 (!blackboxpnp)
CURRENT_IRQL: 0
ANALYSIS_SESSION_HOST: XXXXX
ANALYSIS_SESSION_TIME: 01-07-2019 10:56:15.0539
ANALYSIS_VERSION: 10.0.18303.1000 amd64fre
LAST_CONTROL_TRANSFER: from fffff803a60f912c to fffff803a5fb70a0
STACK_TEXT:
ffff8c0f`6a71c968 fffff803`a60f912c : 00000000`00000019 00000000`00000020 ffffb582`3fde7d30 ffffb582`3fde7da0 : nt!KeBugCheckEx
ffff8c0f`6a71c970 fffff80c`759f13fe : ffffb582`3fde7d40 fffff80c`782f0b1a fffff803`000002d3 ffff8c0f`646e444e : nt!ExFreePoolWithTag+0x10cc
ffff8c0f`6a71ca50 fffff80c`75a0a501 : 00000000`0000ff02 00000000`00001001 ffffb582`35200000 ffffb582`38e55000 : ndis!NdisFreeFragmentNetBufferList+0x2be
ffff8c0f`6a71ca80 fffff80c`75a2cee2 : ffffb582`424e45e0 00000000`000005d6 ffffb582`431fb200 00000000`00000000 : ndis!NdisGetDeviceReservedExtension+0x4fe1
ffff8c0f`6a71cab0 fffff803`b7e0404b : ffffb582`431fb3b0 00000000`00000530 00000000`00000000 ffffb582`45a638c0 : ndis!NdisAdvanceNetBufferListDataStart+0x32
ffff8c0f`6a71cae0 fffff803`b7e164fe : 00000000`00000000 00000000`00000000 ffffb582`45e762b0 00000000`00000004 : OVSExt!OvsCompleteNBL+0xd7 [c:\build\openvswitch_branch-2.9-cloudbase\build\ovs\datapath-windows\ovsext\buffermgmt.c @ 1671]
ffff8c0f`6a71cb60 fffff80c`759e1af9 : ffffb582`4242e380 ffffb582`39fe8af0 ffffb582`38bd71a0 ffffb582`42055000 : OVSExt!OvsCompleteNBLIngress+0x3a [c:\build\openvswitch_branch-2.9-cloudbase\build\ovs\datapath-windows\ovsext\packetio.c @ 434]
ffff8c0f`6a71cbb0 fffff80c`782e8486 : ffffb582`38bd71a0 ffff8c0f`6a71cd29 00000000`00000004 00000000`3a95aa02 : ndis!NdisMSendNetBufferListsComplete+0x179
ffff8c0f`6a71cca0 fffff80c`782e7778 : ffffb582`45e762b0 ffffb582`45e762b0 00000000`00000000 ffffb582`45e762b0 : vmswitch+0x18486
ffff8c0f`6a71cd90 fffff80c`759e62f3 : ffff8c0f`6a71cec9 ffffb582`41b4f308 ffffb582`38bd71a0 ffffb582`4acec270 : vmswitch+0x17778
ffff8c0f`6a71cdc0 fffff80c`759e625d : ffff8c0f`6a71d090 ffffb582`00000002 ffffb582`4216eb40 00000000`00000000 : ndis!NdisReturnNetBufferLists+0x553
ffff8c0f`6a71ce00 fffff80c`782e83ed : 00000000`00000002 00000000`00000000 ffffb582`460e1e40 00000000`00000002 : ndis!NdisReturnNetBufferLists+0x4bd
ffff8c0f`6a71cf30 fffff80c`782e7179 : fffff803`b7e22830 ffffb582`45e762b0 00000000`00000000 ffffb582`45e762b0 : vmswitch+0x183ed
ffff8c0f`6a71d020 fffff80c`782e63c4 : ffffb582`3525d000 ffffb582`45e762b0 00000000`00000000 ffffb582`42064001 : vmswitch+0x17179
ffff8c0f`6a71d120 fffff80c`759e32aa : ffffb582`45e7ff02 00000000`0000c001 ffff8c0f`6a71d201 ffffb582`38bd71a0 : vmswitch+0x163c4
ffff8c0f`6a71d190 fffff80c`75a08eff : ffffb582`45e76201 ffffb582`35260000 ffffb582`00000000 00000000`00000001 : ndis!NdisMIndicateReceiveNetBufferLists+0xfca
ffff8c0f`6a71d260 fffff80c`759e3907 : ffffb582`38bd71a0 00000000`00000000 ffffb582`38bd71a0 00000000`00000000 : ndis!NdisGetDeviceReservedExtension+0x39df
ffff8c0f`6a71d360 fffff80c`759e2b74 : 00000000`00560833 00000000`00000003 00000000`00000000 00000000`00000000 : ndis!NdisMIndicateReceiveNetBufferLists+0x1627
ffff8c0f`6a71d3b0 fffff80c`782d32ae : 00000000`00000000 ffff8c0f`6a71d5c0 00000000`00000031 00000000`00000000 : ndis!NdisMIndicateReceiveNetBufferLists+0x894
ffff8c0f`6a71d5c0 fffff80c`782d2766 : ffff8c0f`6a71d600 ffffb582`45e762b0 ffffb582`45e76200 ffff8c0f`6a71d600 : vmswitch+0x32ae
ffff8c0f`6a71d690 fffff80c`759e5b53 : 00000000`00000000 bd5b82ff`10ac0000 ffffb582`393f5902 00000000`00000000 : vmswitch+0x2766
ffff8c0f`6a71d880 fffff80c`759e1392 : fffff80c`759e5a00 ffffb582`45e762b0 00000000`00000000 ffffb582`45a63710 : ndis!NdisFreeNetBufferList+0x4a3
ffff8c0f`6a71d940 fffff80c`782dccc7 : ffffb582`35df41d0 ffffb582`35c60030 ffffb582`00000000 fffff80c`00000021 : ndis!NdisSendNetBufferLists+0x332
ffff8c0f`6a71dac0 fffff80c`782dbf49 : 00000000`00000000 00000000`00000000 ffffb582`35c60030 00000000`00000001 : vmswitch+0xccc7
ffff8c0f`6a71dbe0 fffff80c`75f73943 : 00000000`00000001 ffffb582`393f41a0 00000000`00000001 ffffb582`00000001 : vmswitch+0xbf49
ffff8c0f`6a71dd00 fffff80c`759e5b53 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : VmsProxyHNic+0x3943
ffff8c0f`6a71dd40 fffff80c`759e1392 : 00000000`00000000 ffffb582`35c60030 00000000`00000000 00000000`00000000 : ndis!NdisFreeNetBufferList+0x4a3
ffff8c0f`6a71de00 fffff80c`75c0c1d4 : ffffb582`38e4d180 ffffb582`35c60030 ffff8c0f`00000000 fffff803`00000000 : ndis!NdisSendNetBufferLists+0x332
ffff8c0f`6a71df80 fffff80c`75c0bf27 : ffffb582`397c5ba0 00000000`00000000 00000000`00000800 00000000`00000000 : tcpip+0xc1d4
ffff8c0f`6a71e020 fffff80c`75c0f428 : 00000000`00000000 ffffb582`39582710 ffff8c0f`6a71e160 ffff8c0f`6a71e0c9 : tcpip+0xbf27
ffff8c0f`6a71e050 fffff80c`75d67f92 : 00000000`00000004 00000000`00000000 00000000`000000ff 00000000`00000000 : tcpip+0xf428
ffff8c0f`6a71e130 fffff80c`75d67879 : 00000000`00000000 00000000`00000000 ffffb582`3fc67640 ffffb582`42484960 : tcpip+0x167f92
ffff8c0f`6a71e2f0 fffff80c`75d66c67 : 00000000`00000000 00000000`00000006 00000000`00000001 ffff8c0f`6a71e5a0 : tcpip+0x167879
ffff8c0f`6a71e330 fffff80c`75d670ee : ffffb582`35c60030 ffffb582`35c60030 ffff8c0f`6a71e5a0 ffff8c0f`6a71e4c0 : tcpip+0x166c67
ffff8c0f`6a71e3c0 fffff80c`75c99c93 : 00000000`00000000 ffffb582`3834b000 ffffb582`48831910 ffffb582`3834b000 : tcpip+0x1670ee
ffff8c0f`6a71e920 fffff80c`75c0b9ec : ffffb582`39aef180 00000000`00000000 00000000`00000001 ffffb582`4074c900 : tcpip+0x99c93
ffff8c0f`6a71ea30 fffff80c`75c0b746 : ffffb582`48831910 ffffb582`4074c9c0 ffff8c0f`6a71eaa8 ffff8c0f`6a71eaac : tcpip+0xb9ec
ffff8c0f`6a71ea60 fffff80c`75c0f776 : ffffb582`4074c901 ffffb582`39588000 fffff80c`75c664b0 ffff8c0f`6a71edf0 : tcpip+0xb746
ffff8c0f`6a71eb40 fffff803`a5ecc17a : ffffb582`37d238d0 fffff80c`75c0f600 00000000`00000000 ffffb582`37d3b700 : tcpip+0xf776
ffff8c0f`6a71ec80 fffff803`a5ecc0dd : fffff80c`75c0f600 ffff8c0f`6a71ee20 ffffb582`3832b380 00000000`00000000 : nt!KeExpandKernelStackAndCalloutEx+0xba
ffff8c0f`6a71ece0 fffff80c`75c66357 : ffffb582`409a0830 ffffb582`408d3090 00000000`0000000c ffffb582`484d1ba0 : nt!KeExpandKernelStackAndCalloutEx+0x1d
ffff8c0f`6a71ed20 fffff80c`75c65b43 : 00000000`00000001 ffff8c0f`6a71ee80 ffffb582`4074c9c0 ffffb582`00000000 : tcpip+0x66357
ffff8c0f`6a71ed80 fffff80c`759e32aa : 00000000`00000020 ffffb582`388ec3d1 00000000`00000001 00000000`00000001 : tcpip+0x65b43
ffff8c0f`6a71efa0 fffff80c`759e2f90 : ffffb582`39ca6001 ffffb582`39700000 00000000`00000000 ffffb582`00000003 : ndis!NdisMIndicateReceiveNetBufferLists+0xfca
ffff8c0f`6a71f070 fffff80c`759e3907 : ffffb582`391d01a0 ffff8c0f`00000000 ffffb582`391d01a0 ffffb582`40764010 : ndis!NdisMIndicateReceiveNetBufferLists+0xcb0
ffff8c0f`6a71f170 fffff80c`759e2b74 : 00000000`00560833 fffff80c`778a4b44 ffffb582`398a3b00 ffffb582`39869a60 : ndis!NdisMIndicateReceiveNetBufferLists+0x1627
ffff8c0f`6a71f1c0 fffff80c`77a43aba : ffff8c0f`6a71f478 ffffb582`3a53c010 ffff8c0f`6a71f430 00000000`00000000 : ndis!NdisMIndicateReceiveNetBufferLists+0x894
ffff8c0f`6a71f3d0 fffff80c`779fb1f5 : ffffb582`00000003 ffffb582`398aa0e0 00000000`00000000 ffff4e37`00000001 : wdiwifi+0x53aba
ffff8c0f`6a71f470 fffff80c`779fa598 : fffff80c`77a9f3f0 ffffb582`39e60000 ffff8c0f`6a71f599 ffffb582`398ac970 : wdiwifi+0xb1f5
ffff8c0f`6a71f4e0 fffff80c`779fac0c : ffffb582`398ac970 00000000`00000001 ffffb582`398ac970 00000000`0000001f : wdiwifi+0xa598
ffff8c0f`6a71f600 fffff80c`779f7413 : ffffb582`481d3380 fffff803`00000001 ffff8c0f`6a71f750 00000000`000000d3 : wdiwifi+0xac0c
ffff8c0f`6a71f6a0 fffff80c`778924f7 : 00000000`00000000 ffffb582`398a3700 ffffb582`398a3728 00000000`00000000 : wdiwifi+0x7413
ffff8c0f`6a71f6e0 fffff80c`7789233c : ffffb582`00000000 00000000`00000000 ffffb582`398a3728 00000000`00000000 : mrvlpcie8897+0x124f7
ffff8c0f`6a71f750 fffff80c`778a4fc1 : 00000000`00000000 00000000`00000001 00000000`00000004 ffffb582`4633df30 : mrvlpcie8897+0x1233c
ffff8c0f`6a71f7a0 fffff80c`778a5e49 : ffffb582`398a3b01 ffffb582`398a3b00 fffff80c`00000013 fffff803`00000013 : mrvlpcie8897+0x24fc1
ffff8c0f`6a71f8c0 fffff80c`778a1f33 : 00000000`00000000 ffffb582`3902c0c0 ffffb582`398a3ad0 ffff8c0f`00000008 : mrvlpcie8897+0x25e49
ffff8c0f`6a71f960 fffff80c`759e7c37 : 00000000`00000000 ffffb582`37d2cab0 00000000`00000000 ffff8c0f`6a71fa61 : mrvlpcie8897+0x21f33
ffff8c0f`6a71f9b0 fffff80c`759ff5ef : ffffb582`37d2cab0 ffffb582`37d2ca90 fffff80c`759ff400 ffffb582`3991d6e8 : ndis!NdisGetThreadObjectCompartmentId+0x367
ffff8c0f`6a71fac0 fffff803`a5f3d2d7 : ffffb582`37d3b700 ffffb582`37d3b700 fffff80c`759ff490 00000000`00000000 : ndis!NdisInitializeTimer+0x179f
ffff8c0f`6a71fb90 fffff803`a5fbe516 : ffffdb80`10fdd180 ffffb582`37d3b700 fffff803`a5f3d290 00000000`00000000 : nt!IoIsFileOriginRemote+0x407
ffff8c0f`6a71fbe0 00000000`00000000 : ffff8c0f`6a720000 ffff8c0f`6a719000 00000000`00000000 00000000`00000000 : nt!KeSynchronizeExecution+0x63b6
THREAD_SHA1_HASH_MOD_FUNC: 1437803e40c60bb1b438d006bf0ed877a26dc2d1
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: b6155a04a2b09cdac713b4e2eb4060b66a52e862
THREAD_SHA1_HASH_MOD: b38d89ee8028e6e541674346e90a6b30d6dcf39e
FOLLOWUP_IP:
OVSExt!OvsCompleteNBL+d7 [c:\build\openvswitch_branch-2.9-cloudbase\build\ovs\datapath-windows\ovsext\buffermgmt.c @ 1671]
fffff803`b7e0404b 40f6c520 test bpl,20h
FAULT_INSTR_CODE: 20c5f640
FAULTING_SOURCE_LINE: c:\build\openvswitch_branch-2.9-cloudbase\build\ovs\datapath-windows\ovsext\buffermgmt.c
FAULTING_SOURCE_FILE: c:\build\openvswitch_branch-2.9-cloudbase\build\ovs\datapath-windows\ovsext\buffermgmt.c
FAULTING_SOURCE_LINE_NUMBER: 1671
FAULTING_SOURCE_CODE:
No source found for 'c:\build\openvswitch_branch-2.9-cloudbase\build\ovs\datapath-windows\ovsext\buffermgmt.c'
SYMBOL_STACK_INDEX: 5
SYMBOL_NAME: nt_wrong_symbols!5C135351953000
FOLLOWUP_NAME: MachineOwner
STACK_COMMAND: .thread ; .cxr ; kb
BUGCHECK_STR: 5C135351
EXCEPTION_CODE: (NTSTATUS) 0x5c135351 - <Unable to get error code text>
EXCEPTION_CODE_STR: 5C135351
EXCEPTION_STR: WRONG_SYMBOLS
PROCESS_NAME: ntoskrnl.wrong.symbols.exe
IMAGE_NAME: ntoskrnl.wrong.symbols.exe
MODULE_NAME: nt_wrong_symbols
BUCKET_ID: WRONG_SYMBOLS_X64_17134.1.amd64fre.rs4_release.180410-1804_TIMESTAMP_181214-065305
DEFAULT_BUCKET_ID: WRONG_SYMBOLS_X64_17134.1.amd64fre.rs4_release.180410-1804_TIMESTAMP_181214-065305
PRIMARY_PROBLEM_CLASS: WRONG_SYMBOLS
FAILURE_BUCKET_ID: WRONG_SYMBOLS_X64_17134.1.amd64fre.rs4_release.180410-1804_TIMESTAMP_181214-065305_5C135351_nt_wrong_symbols!5C135351953000
TARGET_TIME: 2019-01-06T23:18:24.000Z
OSBUILD: 17134
OSSERVICEPACK: 0
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 272
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2018-12-14 07:53:05
BUILDDATESTAMP_STR: 180410-1804
BUILDLAB_STR: rs4_release
BUILDOSVER_STR: 10.0.17134.1.amd64fre.rs4_release.180410-1804
ANALYSIS_SESSION_ELAPSED_TIME: ff
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:wrong_symbols_x64_17134.1.amd64fre.rs4_release.180410-1804_timestamp_181214-065305_5c135351_nt_wrong_symbols!5c135351953000
FAILURE_ID_HASH: {ae8a9cbf-3bf8-1828-c1a2-94d04248d54a}
Followup: MachineOwner
---------
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.