Login
[x]
Log in using an account from:
Fedora Account System
Red Hat Associate
Red Hat Customer
Or login using a Red Hat Bugzilla account
Forgot Password
Login:
Hide Forgot
Create an Account
Red Hat Bugzilla – Attachment 639057 Details for
Bug 873499
Win2008r2 64 bit guest BSOD when running
[?]
New
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.rh83 Release notes
FAQ
Guides index
User guide
Web Services
Contact
Legal
This site requires JavaScript to be enabled to function correctly, please enable it.
wdbg analysis result
wdbg.log (text/x-log), 27.47 KB, created by
Xu Tian
on 2012-11-06 02:47:04 UTC
(
hide
)
Description:
wdbg analysis result
Filename:
MIME Type:
Creator:
Xu Tian
Created:
2012-11-06 02:47:04 UTC
Size:
27.47 KB
patch
obsolete
> >Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64 >Copyright (c) Microsoft Corporation. All rights reserved. > > >Loading Dump File [C:\Windows\2012-11-03-09-55-47-Memory.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 (8 procs) Free x64 >Product: Server, suite: TerminalServer DataCenter SingleUserTS >Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850 >Machine Name: >Kernel base = 0xfffff800`0141b000 PsLoadedModuleList = 0xfffff800`01660e90 >Debug session time: Sat Nov 3 07:38:06.625 2012 (GMT-8) >System Uptime: 0 days 0:02:44.531 >********************************************************************* >* 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 >.... >******************************************************************************* >* * >* Bugcheck Analysis * >* * >******************************************************************************* > >Use !analyze -v to get detailed debugging information. > >BugCheck 101, {18, 0, fffff880020a4180, 7} > >*** ERROR: Symbol file could not be found. Defaulted to export symbols for hal.dll - >***** Kernel symbols are WRONG. Please fix symbols to do analysis. > >************************************************************************* >*** *** >*** *** >*** Your debugger is not using the correct symbols *** >*** *** >*** In order for this command 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 *** >*** *** >************************************************************************* >************************************************************************* >*** *** >*** *** >*** Your debugger is not using the correct symbols *** >*** *** >*** In order for this command 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 *** >*** *** >************************************************************************* >************************************************************************* >*** *** >*** *** >*** Your debugger is not using the correct symbols *** >*** *** >*** In order for this command 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 *** >*** *** >************************************************************************* >************************************************************************* >*** *** >*** *** >*** Your debugger is not using the correct symbols *** >*** *** >*** In order for this command 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 *** >*** *** >************************************************************************* >************************************************************************* >*** *** >*** *** >*** Your debugger is not using the correct symbols *** >*** *** >*** In order for this command 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 *** >*** *** >************************************************************************* >************************************************************************* >*** *** >*** *** >*** Your debugger is not using the correct symbols *** >*** *** >*** In order for this command 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 *** >*** *** >************************************************************************* >************************************************************************* >*** *** >*** *** >*** Your debugger is not using the correct symbols *** >*** *** >*** In order for this command 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 *** >*** *** >************************************************************************* >************************************************************************* >*** *** >*** *** >*** Your debugger is not using the correct symbols *** >*** *** >*** In order for this command 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 *** >*** *** >************************************************************************* >********************************************************************* >* 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+ * >********************************************************************* >********************************************************************* >* 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+ * >********************************************************************* >Probably caused by : ntkrnlmp.exe > >Followup: MachineOwner >--------- > >0: kd> !analyze -v >******************************************************************************* >* * >* Bugcheck Analysis * >* * >******************************************************************************* > >CLOCK_WATCHDOG_TIMEOUT (101) >An expected clock interrupt was not received on a secondary processor in an >MP system within the allocated interval. This indicates that the specified >processor is hung and not processing interrupts. >Arguments: >Arg1: 0000000000000018, Clock interrupt time out interval in nominal clock ticks. >Arg2: 0000000000000000, 0. >Arg3: fffff880020a4180, The PRCB address of the hung processor. >Arg4: 0000000000000007, 0. > >Debugging Details: >------------------ > >***** Kernel symbols are WRONG. Please fix symbols to do analysis. > >************************************************************************* >*** *** >*** *** >*** Your debugger is not using the correct symbols *** >*** *** >*** In order for this command 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 *** >*** *** >************************************************************************* >************************************************************************* >*** *** >*** *** >*** Your debugger is not using the correct symbols *** >*** *** >*** In order for this command 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 *** >*** *** >************************************************************************* >************************************************************************* >*** *** >*** *** >*** Your debugger is not using the correct symbols *** >*** *** >*** In order for this command 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 *** >*** *** >************************************************************************* >************************************************************************* >*** *** >*** *** >*** Your debugger is not using the correct symbols *** >*** *** >*** In order for this command 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 *** >*** *** >************************************************************************* >************************************************************************* >*** *** >*** *** >*** Your debugger is not using the correct symbols *** >*** *** >*** In order for this command 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 *** >*** *** >************************************************************************* >************************************************************************* >*** *** >*** *** >*** Your debugger is not using the correct symbols *** >*** *** >*** In order for this command 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 *** >*** *** >************************************************************************* >************************************************************************* >*** *** >*** *** >*** Your debugger is not using the correct symbols *** >*** *** >*** In order for this command 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 *** >*** *** >************************************************************************* >************************************************************************* >*** *** >*** *** >*** Your debugger is not using the correct symbols *** >*** *** >*** In order for this command 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 *** >*** *** >************************************************************************* >********************************************************************* >* 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+ * >********************************************************************* >********************************************************************* >* 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+ * >********************************************************************* > >ADDITIONAL_DEBUG_TEXT: >Use '!findthebuild' command to search for the target build information. >If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols. > >MODULE_NAME: nt > >FAULTING_MODULE: fffff8000141b000 nt > >DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7951a > >BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_8_PROC > >DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT > >CURRENT_IRQL: 0 > >STACK_TEXT: >fffff880`023475e8 fffff800`014f2a89 : 00000000`00000101 00000000`00000018 00000000`00000000 fffff880`020a4180 : nt!KeBugCheckEx >fffff880`023475f0 fffff800`014a5eb7 : fffff880`00000000 fffff800`00000007 00000000`0002625a 00000000`00000000 : nt!wcsncat_s+0x5c61 >fffff880`02347680 fffff800`01a191c0 : 00000000`00000000 fffff880`02347830 fffff800`01a353c0 fffff800`00000000 : nt!KeUpdateSystemTime+0x377 >fffff880`02347780 fffff800`01497b73 : 00000000`02fc61c0 fffff800`01a353c0 00000000`00000001 00000000`00000000 : hal!HalSendNMI+0xbd0 >fffff880`023477b0 fffff800`014a1200 : fffff800`0160de80 fffff800`00000001 00000000`00000000 fffff880`02347a48 : nt!KeSynchronizeExecution+0xce3 >fffff880`02347940 fffff800`014d232e : fffff880`00000783 fffff800`01648760 fffff800`0141b000 00000000`0000097b : nt!KeWaitForMultipleObjects+0x15c0 >fffff880`02347a10 fffff800`014a1444 : 00000000`0000003c fffff800`01648760 00000000`00000000 00000000`00000000 : nt!FsRtlLookupLastBaseMcbEntry+0xb16 >fffff880`02347b20 fffff800`015617ad : fffff800`01648fa8 00000000`00000100 00003c10`00008827 00000000`ffffffff : nt!KeWaitForMultipleObjects+0x1804 >fffff880`02347b70 fffff800`014635d4 : 00000000`00005400 00000000`00000010 00000000`00000000 00000000`00000003 : nt!KdEnableDebugger+0x4e5d >fffff880`02347c10 fffff800`01738cce : fffffa80`30a17b60 00000000`00000080 fffffa80`309afb30 00000000`00000000 : nt!RtlRemoveEntryHashTable+0xba4 >fffff880`02347d40 fffff800`0148cfe6 : fffff880`009b8180 fffffa80`30a17b60 fffff880`009c30c0 00000000`00000000 : nt!PsCreateSystemThread+0x1da >fffff880`02347d80 00000000`00000000 : fffff880`02348000 fffff880`02342000 fffff880`023477d0 00000000`00000000 : nt!KeInitializeSemaphore+0x24a > > >STACK_COMMAND: .bugcheck ; kb > >FOLLOWUP_NAME: MachineOwner > >IMAGE_NAME: ntkrnlmp.exe > >BUCKET_ID: WRONG_SYMBOLS > >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 873499
: 639057 |
639060