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 949684 Details for
Bug 1155910
[whql][netkvm]Job MPE failed while job was running on win2008R2 because of bsod (D1) on build 93 - 1 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.
guest_server_dump_analysis
MEMORY-2008R2-Server-single.txt (text/plain), 36.61 KB, created by
Min Deng
on 2014-10-23 07:13:51 UTC
(
hide
)
Description:
guest_server_dump_analysis
Filename:
MIME Type:
Creator:
Min Deng
Created:
2014-10-23 07:13:51 UTC
Size:
36.61 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\MEMORY-2008R2-Server-single.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`01453000 PsLoadedModuleList = 0xfffff800`01698e90 >Debug session time: Tue Oct 21 22:57:58.328 2014 (UTC + 8:00) >System Uptime: 0 days 7:45:24.296 >********************************************************************* >* 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 D1, {0, 2, 0, fffff88004f4ad6f} > >*** 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 >***** 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+ebd6f ) > >Followup: MachineOwner >--------- > >0: kd> !analyze -v >******************************************************************************* >* * >* Bugcheck Analysis * >* * >******************************************************************************* > >DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) >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 kernel debugger is available get stack backtrace. >Arguments: >Arg1: 0000000000000000, memory referenced >Arg2: 0000000000000002, IRQL >Arg3: 0000000000000000, value 0 = read operation, 1 = write operation >Arg4: fffff88004f4ad6f, 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: fffff80001453000 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 > 0000000000000000 > >CURRENT_IRQL: 0 > >FAULTING_IP: >ndprot62+ebd6f >fffff880`04f4ad6f 488b00 mov rax,qword ptr [rax] > >DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT > >BUGCHECK_STR: 0xD1 > >ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre > >LAST_CONTROL_TRANSFER: from fffff800014d2be9 to fffff800014d3640 > >STACK_TEXT: >fffff800`0131a4e8 fffff800`014d2be9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx >fffff800`0131a4f0 fffff800`014d1860 : fffff800`0131aba8 fffff800`0131abb0 3fd00000`00000000 fffffa80`042311a0 : nt!KeSynchronizeExecution+0x3d59 >fffff800`0131a630 fffff880`04f4ad6f : fffffa80`03cf7040 fffffa80`054c8a50 00000000`00000004 00000000`00000000 : nt!KeSynchronizeExecution+0x29d0 >fffff800`0131a7c0 fffff880`04f7e5e7 : fffffa80`043ad820 fffffa80`055b1a70 fffffa80`05519990 fffff800`0131a858 : ndprot62+0xebd6f >fffff800`0131a810 fffff880`04f7e659 : fffffa80`03cf7040 fffffa80`055b1a70 fffffa80`05519990 fffffa80`05666201 : ndprot62+0x11f5e7 >fffff800`0131a880 fffff880`04f4865c : fffffa80`03cf7040 fffffa80`055b1a70 fffffa80`054abc01 00000000`00000000 : ndprot62+0x11f659 >fffff800`0131a8c0 fffff880`04e9fb8b : fffffa80`054ef040 fffffa80`055b1a70 fffffa80`00000001 fffffa80`03ef3840 : ndprot62+0xe965c >fffff800`0131a930 fffff880`04e96852 : fffffa80`04d93730 fffffa80`055b1a70 3fd00000`00000001 00001f80`00000200 : ndprot62+0x40b8b >fffff800`0131a970 fffff880`04eb33da : fffffa80`054d3b10 fffffa80`055b1a70 fffffa80`00000001 00000000`000000c0 : ndprot62+0x37852 >fffff800`0131a9d0 fffff880`00f9336f : fffffa80`054d3b10 fffffa80`055b1a70 00000000`00000001 fffffa80`055b1a70 : ndprot62+0x543da >fffff800`0131aa10 fffff880`00f9321d : 00000000`00000000 fffffa80`055b1a70 fffffa80`00000001 fffff800`00000000 : NDIS!NdisMSendNetBufferListsComplete+0x1bf >fffff800`0131aab0 fffff880`02c5bfb1 : fffffa80`0432deb0 fffff800`0131ab39 00000000`00000000 fffffa80`0432b010 : NDIS!NdisMSendNetBufferListsComplete+0x6d >fffff800`0131aaf0 fffff880`02c56298 : fffffa80`0432dd00 00000000`00000301 00000000`00000000 fffffa80`055b1a70 : netkvm+0x8fb1 >fffff800`0131aba0 fffff880`02c60e0c : fffffa80`0432b010 fffffa80`000003e8 00000000`00000000 00000000`00000000 : netkvm+0x3298 >fffff800`0131abe0 fffff880`00ed5b51 : 00000000`00000010 00000000`00000246 fffff800`01645e80 00000000`00000000 : netkvm+0xde0c >fffff800`0131ac40 fffff800`014deb1c : fffffa80`0433d468 00000017`00000000 00000000`00000001 fffff800`01645e80 : NDIS!NdisGetSessionToCompartmentMappingEpochAndZero+0x161 >fffff800`0131acd0 fffff800`014cb36a : fffff800`01645e80 fffff800`01653cc0 00000000`00000000 fffff880`00ed5a00 : nt!KeReleaseMutant+0x5dc >fffff800`0131ad80 00000000`00000000 : fffff800`0131b000 fffff800`01315000 fffff800`0131ad40 00000000`00000000 : nt!KiCpuId+0x79a > > >STACK_COMMAND: kb > >FOLLOWUP_IP: >ndprot62+ebd6f >fffff880`04f4ad6f 488b00 mov rax,qword ptr [rax] > >SYMBOL_STACK_INDEX: 3 > >SYMBOL_NAME: ndprot62+ebd6f > >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 1155910
: 949684