Login
Log in using an SSO provider:
Fedora Account System
Red Hat Associate
Red Hat Customer
Login using a Red Hat Bugzilla account
Forgot Password
Create an Account
Red Hat Bugzilla – Attachment 949654 Details for
Bug 1155891
[whql][netkvm]Job MPE failed while job was running on win2008R2 because of bsod (0A) on build 93 - 4 vcpus
Home
New
Search
Simple Search
Advanced Search
My Links
Browse
Requests
Reports
Current State
Search
Tabular reports
Graphical reports
Duplicates
Other Reports
User Changes
Plotly Reports
Bug Status
Bug Severity
Non-Defaults
Product Dashboard
Help
Page Help!
Bug Writing Guidelines
What's new
Browser Support Policy
5.0.4.rh90 Release notes
FAQ
Guides index
User guide
Web Services
Contact
Legal
[?]
This site requires JavaScript to be enabled to function correctly, please enable it.
dump analysis
MEMOR-2008R2-client-4-vcpus.txt (text/plain), 39.72 KB, created by
Min Deng
on 2014-10-23 06:23:07 UTC
(
hide
)
Description:
dump analysis
Filename:
MIME Type:
Creator:
Min Deng
Created:
2014-10-23 06:23:07 UTC
Size:
39.72 KB
patch
obsolete
> >Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64 >Copyright (c) Microsoft Corporation. All rights reserved. > > >Loading Dump File [I:\mdeng-Dumps\1154419\MEMOR-2008R2-client-4-vcpus.DMP] >Kernel Summary Dump File: Only kernel address space is 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 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 >Product: Server, suite: TerminalServer DataCenter SingleUserTS >Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850 >Machine Name: >Kernel base = 0xfffff800`01401000 PsLoadedModuleList = 0xfffff800`01646e90 >Debug session time: Wed Oct 22 13:31:10.937 2014 (UTC + 8:00) >System Uptime: 0 days 0:46:09.218 >********************************************************************* >* 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 >............................................................... >................................................................ >. >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. >******************************************************************************* >* * >* Bugcheck Analysis * >* * >******************************************************************************* > >Use !analyze -v to get detailed debugging information. > >BugCheck A, {fffff8000171ecce, 2, 0, fffff800014aba52} > >*** ERROR: Module load completed but symbols could not be loaded for ndprot62.sys >*** ERROR: Symbol file could not be found. Defaulted to export symbols for NDIS.SYS - >*** ERROR: Module load completed but symbols could not be loaded for netkvm.sys >*** ERROR: Symbol file could not be found. Defaulted to export symbols for hal.dll - >*** ERROR: Module load completed but symbols could not be loaded for pacer.sys >***** 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!_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!_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 *** >*** *** >************************************************************************* >Probably caused by : ndprot62.sys ( ndprot62+85754 ) > >Followup: MachineOwner >--------- > >1: kd> !analyze -v >******************************************************************************* >* * >* Bugcheck Analysis * >* * >******************************************************************************* > >IRQL_NOT_LESS_OR_EQUAL (a) >An attempt was made to access a pageable (or completely invalid) address at an >interrupt request level (IRQL) that is too high. This is usually >caused by drivers using improper addresses. >If a kernel debugger is available get the stack backtrace. >Arguments: >Arg1: fffff8000171ecce, memory referenced >Arg2: 0000000000000002, IRQL >Arg3: 0000000000000000, bitfield : > bit 0 : value 0 = read operation, 1 = write operation > bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) >Arg4: fffff800014aba52, address which referenced memory > >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!_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!_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 *** >*** *** >************************************************************************* > >ADDITIONAL_DEBUG_TEXT: >You can run '.symfix; .reload' to try to fix the symbol path and load symbols. > >FAULTING_MODULE: fffff80001401000 nt > >DEBUG_FLR_IMAGE_TIMESTAMP: 52cef720 > >READ_ADDRESS: unable to get nt!MmSpecialPoolStart >unable to get nt!MmSpecialPoolEnd >unable to get nt!MmPagedPoolEnd >unable to get nt!MmNonPagedPoolStart >unable to get nt!MmSizeOfNonPagedPoolInBytes > fffff8000171ecce > >CURRENT_IRQL: 0 > >FAULTING_IP: >nt!FsRtlDissectName+3b2 >fffff800`014aba52 410fb60c24 movzx ecx,byte ptr [r12] > >DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT > >BUGCHECK_STR: 0xA > >ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre > >LAST_CONTROL_TRANSFER: from fffff80001480be9 to fffff80001481640 > >STACK_TEXT: >fffff880`055fadb8 fffff800`01480be9 : 00000000`0000000a fffff800`0171ecce 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx >fffff880`055fadc0 fffff800`0147f860 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`0000005a : nt!KeSynchronizeExecution+0x3d59 >fffff880`055faf00 fffff800`014aba52 : fffff800`0171ecce fffff880`055fb0d8 fffff880`055fbf48 fffff880`0520e000 : nt!KeSynchronizeExecution+0x29d0 >fffff880`055fb090 fffff800`014bcdc1 : fffff880`055fbf48 fffff880`055fb7a0 fffff880`00000000 00000000`00000005 : nt!FsRtlDissectName+0x3b2 >fffff880`055fb770 fffff800`01480cc2 : fffff880`055fbf48 fffffa80`04c581a0 fffff880`055fbff0 fffffa80`059d48d0 : nt!IoGetPagingIoPriority+0x901 >fffff880`055fbe10 fffff800`0147f5ca : 00001f80`0010000f 0053002b`002b0010 00000202`0018002b 00000000`00000000 : nt!KeSynchronizeExecution+0x3e32 >fffff880`055fbff0 fffff800`0148b5d0 : fffff880`05293754 fffffa80`05a28c70 fffffa80`05a28c90 fffffa80`05a28c90 : nt!KeSynchronizeExecution+0x273a >fffff880`055fc188 fffff880`05293754 : fffffa80`05a28c70 fffffa80`05a28c90 fffffa80`05a28c90 fffff880`05338dd2 : nt!ExQueryDepthSList >fffff880`055fc190 fffff880`052fe98e : fffffa80`05a67c60 fffff880`00000020 fffffa80`05a28c74 fffff880`05320004 : ndprot62+0x85754 >fffff880`055fc1e0 fffff880`052f9d8d : fffffa80`05858580 fffffa80`05abbe90 fffffa80`05e20230 fffffa80`05a28c74 : ndprot62+0xf098e >fffff880`055fc220 fffff880`0532d5e7 : fffffa80`055fec90 fffffa80`05abbe90 fffffa80`05e20230 fffff880`055fc2b8 : ndprot62+0xebd8d >fffff880`055fc270 fffff880`0532d659 : fffffa80`05da63a0 fffffa80`05abbe90 fffffa80`05e20230 fffffa80`05b8ef01 : ndprot62+0x11f5e7 >fffff880`055fc2e0 fffff880`052bd084 : fffffa80`05da63a0 fffffa80`05abbe90 00000000`00000001 00000000`00000000 : ndprot62+0x11f659 >fffff880`055fc320 fffff880`0524eb8b : fffffa80`05bfc3c0 fffffa80`05abbe90 00000000`00000001 fffff800`014ad2a0 : ndprot62+0xaf084 >fffff880`055fc3a0 fffff880`05245852 : fffffa80`05a5a2e0 fffffa80`05abbe90 00000000`00000001 fffff800`0146933b : ndprot62+0x40b8b >fffff880`055fc3e0 fffff880`052623da : fffffa80`058bcb10 fffffa80`05abbe90 00000000`00000001 fffff800`014ad2a0 : ndprot62+0x37852 >fffff880`055fc440 fffff880`00f1036f : fffffa80`058bcb10 fffffa80`05abbe90 fffffa80`00000001 fffffa80`05ab0c10 : ndprot62+0x543da >fffff880`055fc480 fffff880`00f1021d : fffffa80`00000000 fffffa80`05abbe90 fffffa80`00000001 fffff880`00000000 : NDIS!NdisMSendNetBufferListsComplete+0x1bf >fffff880`055fc520 fffff880`0287efb1 : fffffa80`04d4ad10 fffff880`055fc5a9 fffffa80`04d4ad10 fffffa80`058a8f10 : NDIS!NdisMSendNetBufferListsComplete+0x6d >fffff880`055fc560 fffff880`0287f13b : fffffa80`03c5ed00 00000000`00000000 00000000`00000000 fffffa80`05abbe90 : netkvm+0x8fb1 >fffff880`055fc610 fffff880`0287f840 : 00000000`00000005 fffffa80`058a8e70 fffffa80`05ab0c00 fffffa80`058a8e70 : netkvm+0x913b >fffff880`055fc640 fffff800`019ef62f : 00000000`00000000 00000000`0000002a 00000000`000001f8 fffffa80`05b5f1e0 : netkvm+0x9840 >fffff880`055fc670 fffff880`00e53750 : fffffa80`05e53180 fffffa80`04d2ed00 00000000`00000000 4c4e4852`05b5f1e0 : hal!HalFreeCommonBuffer+0x35b >fffff880`055fc6e0 fffff880`0287f9de : fffffa80`04c581a0 fffff800`0146242a fffffa80`05c38630 fffffa80`05ca5320 : NDIS!NdisMAllocateNetBufferSGList+0x110 >fffff880`055fc780 fffff880`0287e476 : fffff880`028836d4 fffffa80`04ffd110 fffffa80`05e53180 fffffa80`05ca5320 : netkvm+0x99de >fffff880`055fc7c0 fffff880`0287feda : fffffa80`058a8e70 fffffa80`058a8e70 fffffa80`04d4ad10 fffffa80`05ca5320 : netkvm+0x8476 >fffff880`055fc7f0 fffff880`0287fae9 : fffffa80`058a8e70 fffffa80`04d4ad10 00000000`00000000 fffff800`016086c8 : netkvm+0x9eda >fffff880`055fc820 fffff880`00f104f1 : fffff880`05334900 00000000`00000801 fffffa80`04c581a0 206c644d`052fd231 : netkvm+0x9ae9 >fffff880`055fc920 fffff880`00e53624 : 00000000`00000000 fffffa80`04d85130 00000000`00000000 00000000`00000000 : NDIS!NdisMSendNetBufferListsComplete+0x341 >fffff880`055fc980 fffff880`013cc199 : 00000000`00000030 fffffa80`04c581a0 00000000`00000000 fffffa80`05a52df0 : NDIS!NdisFSendNetBufferLists+0x64 >fffff880`055fc9c0 fffff880`00e53569 : fffffa80`05c8f9b0 fffff880`05293a57 fffffa80`058cfcfc fffff880`05294723 : pacer+0x1199 >fffff880`055fcac0 fffff880`00f105d5 : fffffa80`05c8f9b0 00000000`00000000 fffffa80`04c581a0 fffffa80`057a7b20 : NDIS!NdisAdjustNetBufferCurrentMdl+0xa9 >fffff880`055fcb20 fffff880`0524ee35 : fffffa80`05c8f9b0 00000000`00000080 fffffa80`03cc89e0 00000000`00000000 : NDIS!NdisSendNetBufferLists+0x85 >fffff880`055fcb80 fffff880`052f8392 : fffffa80`05bfdc60 fffffa80`05d3c250 fffff880`00000000 fffff880`00000000 : ndprot62+0x40e35 >fffff880`055fcbd0 fffff880`052f7bc0 : fffffa80`05a50040 fffffa80`05d3c250 fffff880`0000000a fffff880`00000052 : ndprot62+0xea392 >fffff880`055fcc60 fffff880`05334983 : fffffa80`05a50040 fffff880`014fa9e0 fffff880`0146f384 00000000`00000000 : ndprot62+0xe9bc0 >fffff880`055fccf0 fffff800`0171ecce : fffffa80`05a50078 fffffa80`00000000 fffffa80`03cda680 fffff800`01479157 : ndprot62+0x126983 >fffff880`055fcd40 fffff800`01472fe6 : fffff880`01ece180 fffffa80`05c8f9b0 fffffa80`04f32b60 fffff880`0146f384 : nt!PsCreateSystemThread+0x1da >fffff880`055fcd80 00000000`00000000 : fffff880`055fd000 fffff880`055f7000 fffff880`055fc4e0 00000000`00000000 : nt!KeInitializeSemaphore+0x24a > > >STACK_COMMAND: kb > >FOLLOWUP_IP: >ndprot62+85754 >fffff880`05293754 0fb7c0 movzx eax,ax > >SYMBOL_STACK_INDEX: 8 > >SYMBOL_NAME: ndprot62+85754 > >FOLLOWUP_NAME: MachineOwner > >MODULE_NAME: ndprot62 > >IMAGE_NAME: ndprot62.sys > >BUCKET_ID: WRONG_SYMBOLS > >FAILURE_BUCKET_ID: WRONG_SYMBOLS > >ANALYSIS_SOURCE: KM > >FAILURE_ID_HASH_STRING: km:wrong_symbols > >FAILURE_ID_HASH: {70b057e8-2462-896f-28e7-ac72d4d365f8} > >Followup: MachineOwner >--------- >
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 1155891
: 949654