6,210
社区成员
发帖
与我相关
我的任务
分享求助！！ 有没有哪位遇到过虚拟机系统中 ping 宿主机 电脑就蓝屏了的情况？？？出现蓝屏上显示007f的错误
用windbg分析的结果
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+ *
*********************************************************************
Unable to load image \windows\system32\ntkrnlpa.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt
Kernel base = 0x804d8000 PsLoadedModuleList = 0x8055e720
Debug session time: Thu Jun 26 13:52:15.734 2014 (GMT+8)
System Uptime: 0 days 0:49:02.523
*********************************************************************
* 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+ *
*********************************************************************
Unable to load image \windows\system32\ntkrnlpa.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
.......................................................................................................................................................
Loading User Symbols
Loading unloaded module list
..................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007F, {8, 80042000, 0, 0}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*** WARNING: Unable to verify timestamp for afd.sys
*** ERROR: Module load completed but symbols could not be loaded for afd.sys
*** WARNING: Unable to verify timestamp for tcpip.sys
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
*** WARNING: Unable to verify timestamp for 360netmon.sys
*** ERROR: Module load completed but symbols could not be loaded for 360netmon.sys
*** WARNING: Unable to verify timestamp for 360LanProtect.sys
*** ERROR: Module load completed but symbols could not be loaded for 360LanProtect.sys
*** WARNING: Unable to verify timestamp for NDIS.sys
*** ERROR: Module load completed but symbols could not be loaded for NDIS.sys
*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
Probably caused by : 360netmon.sys ( 360netmon+43b9 )
Followup: MachineOwner
---------
0: kd> -v
^ Syntax error in '-v'
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 00000008, EXCEPTION_DOUBLE_FAULT
Arg2: 80042000
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
FAULTING_MODULE: 804d8000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 0
BUGCHECK_STR: 0x7f_8
CUSTOMER_CRASH_COUNT: 6
DEFAULT_BUCKET_ID: WRONG_SYMBOLS
LAST_CONTROL_TRANSFER: from 804fc38e to 80500c68
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
a4703ffc 804fc38e 00000002 804fc24e 00000000 nt+0x28c68
a4704024 8052499c 00000001 00000001 c0512de8 nt+0x2438e
a4704038 8054b353 a470405c 00000001 00000000 nt+0x4c99c
a47040f0 8054b6bb 00000011 00000000 00000000 nt+0x73353
a4704114 8050a247 00000011 00000000 88be5e18 nt+0x736bb
a470415c a8820c21 88cb42a8 00000000 00000001 nt+0x32247
a4704180 a882c431 88cb42a8 88be5d18 88f81500 afd+0xdc21
a47041a8 a882677c 88be5d18 88d8dd86 0000007e afd+0x19431
a47041f0 a88e9712 88d8dd9a 00000014 a88e9712 afd+0x1377c
a470429c a88d85fc 88f7b868 0101a8c0 88d8dd86 tcpip+0x3e712
a4704308 a88ca30e 8a42b1a8 1801a8c0 0101a8c0 tcpip+0x2d5fc
a4704368 a88ca6a3 00000020 8a42b1a8 a88ad592 tcpip+0x1f30e
a47043e4 a88ac836 00000000 8a42b1a8 88d8dd86 tcpip+0x1f6a3
a470449c a88ab928 8a42b1a8 88d8dd9a 0000006a tcpip+0x1836
a47044dc a88b06ef 00000000 88d8dce8 88d8dd78 tcpip+0x928
a470450c a89083b9 892a01f0 88d8dce8 88d8dd78 tcpip+0x56ef
a4704534 a868eda3 892a01f0 88d8dce8 88d8dd78 360netmon+0x43b9
a47045dc b7d2978e 892a01f0 88d8dce8 88d8dd78 360LanProtect+0x3da3
a4704644 b7d1bed4 01db32f0 a4704664 00000001 NDIS+0x2378e
a470466c b7d0699d 892a01f0 893172c8 00000000 NDIS+0x15ed4
a4704688 a88aed40 8a3e9260 893172c8 892a01f0 NDIS+0x99d
a47046b0 a88ae916 892a01f0 893172c8 88f34390 tcpip+0x3d40
a47046dc a88ae65a 892a01f0 a4704702 00000001 tcpip+0x3916
a470470c a88db763 8a436b70 1801a8c0 893172c8 tcpip+0x365a
a47047c8 a88dc1d4 893172c8 0000006a 00000000 tcpip+0x30763
a47047e4 a88cbcca 893172c8 00000000 0000006a tcpip+0x311d4
a470485c a88afe1b 8a42b1a8 88cd1dc6 00000014 tcpip+0x20cca
a47048e4 a88ac836 00000000 88cd1dc6 88cd1dc6 tcpip+0x4e1b
a470499c a88ab928 8a42b1a8 88cd1dda 0000006a tcpip+0x1836
a47049dc a88b06ef 00000000 88cd1d28 88cd1db8 tcpip+0x928
a4704a0c a89083b9 892a01f0 88cd1d28 88cd1db8 tcpip+0x56ef
a4704a34 a868eda3 892a01f0 88cd1d28 88cd1db8 360netmon+0x43b9
a4704adc b7d2978e 892a01f0 88cd1d28 88cd1db8 360LanProtect+0x3da3
a4704b44 b7d1bed4 01db9648 a4704b64 00000001 NDIS+0x2378e
a4704b6c b7d0699d 892a01f0 89317400 00000000 NDIS+0x15ed4
a4704b88 a88aed40 8a3e9260 89317400 892a01f0 NDIS+0x99d
a4704bb0 a88ae916 892a01f0 89317400 88f34390 tcpip+0x3d40
a4704bdc a88ae65a 892a01f0 a4704c02 00000001 tcpip+0x3916
a4704c0c a88db763 8a436b70 1801a8c0 89317400 tcpip+0x365a
a4704cc8 a88dc1d4 89317400 0000006a 00000000 tcpip+0x30763
a4704ce4 a88cbcca 89317400 00000000 0000006a tcpip+0x311d4
a4704d5c a88afe1b 8a42b1a8 88d4cf7e 00000014 tcpip+0x20cca
a4704de4 a88ac836 00000000 88d4cf7e 88d4cf7e tcpip+0x4e1b
a4704e9c a88ab928 8a42b1a8 88d4cf92 0000006a tcpip+0x1836
a4704edc a88b06ef 00000000 88d4cee0 88d4cf70 tcpip+0x928
a4704f0c a89083b9 892a01f0 88d4cee0 88d4cf70 tcpip+0x56ef
a4704f34 a868eda3 892a01f0 88d4cee0 88d4cf70 360netmon+0x43b9
a4704fdc b7d2978e 892a01f0 88d4cee0 88d4cf70 360LanProtect+0x3da3
a4705044 b7d1bed4 01dd8180 a4705064 00000001 NDIS+0x2378e
a470506c b7d0699d 892a01f0 89317538 00000000 NDIS+0x15ed4
a4705088 a88aed40 8a3e9260 89317538 892a01f0 NDIS+0x99d
a47050b0 a88ae916 892a01f0 89317538 88f34390 tcpip+0x3d40
a47050dc a88ae65a 892a01f0 a4705102 00000001 tcpip+0x3916
a470510c a88db763 8a436b70 1801a8c0 89317538 tcpip+0x365a
a47051c8 a88dc1d4 89317538 0000006a 00000000 tcpip+0x30763
a47051e4 a88cbcca 89317538 00000000 0000006a tcpip+0x311d4
a470525c a88afe1b 8a42b1a8 88da5496 00000014 tcpip+0x20cca
a47052e4 a88ac836 00000000 88da5496 88da5496 tcpip+0x4e1b
a470539c a88ab928 8a42b1a8 88da54aa 0000006a tcpip+0x1836
a47053dc a88b06ef 00000000 88da53f8 88da5488 tcpip+0x928
a470540c a89083b9 892a01f0 88da53f8 88da5488 tcpip+0x56ef
a4705434 a868eda3 892a01f0 88da53f8 88da5488 360netmon+0x43b9
a47054dc b7d2978e 892a01f0 88da53f8 88da5488 360LanProtect+0x3da3
STACK_COMMAND: kb
FOLLOWUP_IP:
360netmon+43b9
a89083b9 ?? ???
SYMBOL_STACK_INDEX: 10
SYMBOL_NAME: 360netmon+43b9
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: 360netmon
IMAGE_NAME: 360netmon.sys
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
那是分析的结果 哪位大神能帮忙解读分析下 非常感谢 这个问题困扰了很久
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+ *
*********************************************************************
Unable to load image \windows\system32\ntkrnlpa.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt
Kernel base = 0x804d8000 PsLoadedModuleList = 0x8055e720
Debug session time: Thu Jun 26 13:52:15.734 2014 (GMT+8)
System Uptime: 0 days 0:49:02.523
*********************************************************************
* 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+ *
*********************************************************************
Unable to load image \windows\system32\ntkrnlpa.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
.......................................................................................................................................................
Loading User Symbols
Loading unloaded module list
..................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007F, {8, 80042000, 0, 0}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*** WARNING: Unable to verify timestamp for afd.sys
*** ERROR: Module load completed but symbols could not be loaded for afd.sys
*** WARNING: Unable to verify timestamp for tcpip.sys
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
*** WARNING: Unable to verify timestamp for 360netmon.sys
*** ERROR: Module load completed but symbols could not be loaded for 360netmon.sys
*** WARNING: Unable to verify timestamp for 360LanProtect.sys
*** ERROR: Module load completed but symbols could not be loaded for 360LanProtect.sys
*** WARNING: Unable to verify timestamp for NDIS.sys
*** ERROR: Module load completed but symbols could not be loaded for NDIS.sys
*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
Probably caused by : 360netmon.sys ( 360netmon+43b9 )
Followup: MachineOwner
---------
0: kd> -v
^ Syntax error in '-v'
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 00000008, EXCEPTION_DOUBLE_FAULT
Arg2: 80042000
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
FAULTING_MODULE: 804d8000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 0
BUGCHECK_STR: 0x7f_8
CUSTOMER_CRASH_COUNT: 6
DEFAULT_BUCKET_ID: WRONG_SYMBOLS
LAST_CONTROL_TRANSFER: from 804fc38e to 80500c68
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
a4703ffc 804fc38e 00000002 804fc24e 00000000 nt+0x28c68
a4704024 8052499c 00000001 00000001 c0512de8 nt+0x2438e
a4704038 8054b353 a470405c 00000001 00000000 nt+0x4c99c
a47040f0 8054b6bb 00000011 00000000 00000000 nt+0x73353
a4704114 8050a247 00000011 00000000 88be5e18 nt+0x736bb
a470415c a8820c21 88cb42a8 00000000 00000001 nt+0x32247
a4704180 a882c431 88cb42a8 88be5d18 88f81500 afd+0xdc21
a47041a8 a882677c 88be5d18 88d8dd86 0000007e afd+0x19431
a47041f0 a88e9712 88d8dd9a 00000014 a88e9712 afd+0x1377c
a470429c a88d85fc 88f7b868 0101a8c0 88d8dd86 tcpip+0x3e712
a4704308 a88ca30e 8a42b1a8 1801a8c0 0101a8c0 tcpip+0x2d5fc
a4704368 a88ca6a3 00000020 8a42b1a8 a88ad592 tcpip+0x1f30e
a47043e4 a88ac836 00000000 8a42b1a8 88d8dd86 tcpip+0x1f6a3
a470449c a88ab928 8a42b1a8 88d8dd9a 0000006a tcpip+0x1836
a47044dc a88b06ef 00000000 88d8dce8 88d8dd78 tcpip+0x928
a470450c a89083b9 892a01f0 88d8dce8 88d8dd78 tcpip+0x56ef
a4704534 a868eda3 892a01f0 88d8dce8 88d8dd78 360netmon+0x43b9
a47045dc b7d2978e 892a01f0 88d8dce8 88d8dd78 360LanProtect+0x3da3
a4704644 b7d1bed4 01db32f0 a4704664 00000001 NDIS+0x2378e
a470466c b7d0699d 892a01f0 893172c8 00000000 NDIS+0x15ed4
a4704688 a88aed40 8a3e9260 893172c8 892a01f0 NDIS+0x99d
a47046b0 a88ae916 892a01f0 893172c8 88f34390 tcpip+0x3d40
a47046dc a88ae65a 892a01f0 a4704702 00000001 tcpip+0x3916
a470470c a88db763 8a436b70 1801a8c0 893172c8 tcpip+0x365a
a47047c8 a88dc1d4 893172c8 0000006a 00000000 tcpip+0x30763
a47047e4 a88cbcca 893172c8 00000000 0000006a tcpip+0x311d4
a470485c a88afe1b 8a42b1a8 88cd1dc6 00000014 tcpip+0x20cca
a47048e4 a88ac836 00000000 88cd1dc6 88cd1dc6 tcpip+0x4e1b
a470499c a88ab928 8a42b1a8 88cd1dda 0000006a tcpip+0x1836
a47049dc a88b06ef 00000000 88cd1d28 88cd1db8 tcpip+0x928
a4704a0c a89083b9 892a01f0 88cd1d28 88cd1db8 tcpip+0x56ef
a4704a34 a868eda3 892a01f0 88cd1d28 88cd1db8 360netmon+0x43b9
a4704adc b7d2978e 892a01f0 88cd1d28 88cd1db8 360LanProtect+0x3da3
a4704b44 b7d1bed4 01db9648 a4704b64 00000001 NDIS+0x2378e
a4704b6c b7d0699d 892a01f0 89317400 00000000 NDIS+0x15ed4
a4704b88 a88aed40 8a3e9260 89317400 892a01f0 NDIS+0x99d
a4704bb0 a88ae916 892a01f0 89317400 88f34390 tcpip+0x3d40
a4704bdc a88ae65a 892a01f0 a4704c02 00000001 tcpip+0x3916
a4704c0c a88db763 8a436b70 1801a8c0 89317400 tcpip+0x365a
a4704cc8 a88dc1d4 89317400 0000006a 00000000 tcpip+0x30763
a4704ce4 a88cbcca 89317400 00000000 0000006a tcpip+0x311d4
a4704d5c a88afe1b 8a42b1a8 88d4cf7e 00000014 tcpip+0x20cca
a4704de4 a88ac836 00000000 88d4cf7e 88d4cf7e tcpip+0x4e1b
a4704e9c a88ab928 8a42b1a8 88d4cf92 0000006a tcpip+0x1836
a4704edc a88b06ef 00000000 88d4cee0 88d4cf70 tcpip+0x928
a4704f0c a89083b9 892a01f0 88d4cee0 88d4cf70 tcpip+0x56ef
a4704f34 a868eda3 892a01f0 88d4cee0 88d4cf70 360netmon+0x43b9
a4704fdc b7d2978e 892a01f0 88d4cee0 88d4cf70 360LanProtect+0x3da3
a4705044 b7d1bed4 01dd8180 a4705064 00000001 NDIS+0x2378e
a470506c b7d0699d 892a01f0 89317538 00000000 NDIS+0x15ed4
a4705088 a88aed40 8a3e9260 89317538 892a01f0 NDIS+0x99d
a47050b0 a88ae916 892a01f0 89317538 88f34390 tcpip+0x3d40
a47050dc a88ae65a 892a01f0 a4705102 00000001 tcpip+0x3916
a470510c a88db763 8a436b70 1801a8c0 89317538 tcpip+0x365a
a47051c8 a88dc1d4 89317538 0000006a 00000000 tcpip+0x30763
a47051e4 a88cbcca 89317538 00000000 0000006a tcpip+0x311d4
a470525c a88afe1b 8a42b1a8 88da5496 00000014 tcpip+0x20cca
a47052e4 a88ac836 00000000 88da5496 88da5496 tcpip+0x4e1b
a470539c a88ab928 8a42b1a8 88da54aa 0000006a tcpip+0x1836
a47053dc a88b06ef 00000000 88da53f8 88da5488 tcpip+0x928
a470540c a89083b9 892a01f0 88da53f8 88da5488 tcpip+0x56ef
a4705434 a868eda3 892a01f0 88da53f8 88da5488 360netmon+0x43b9
a47054dc b7d2978e 892a01f0 88da53f8 88da5488 360LanProtect+0x3da3
STACK_COMMAND: kb
FOLLOWUP_IP:
360netmon+43b9
a89083b9 ?? ???
SYMBOL_STACK_INDEX: 10
SYMBOL_NAME: 360netmon+43b9
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: 360netmon
IMAGE_NAME: 360netmon.sys
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
那是分析的结果 哪位大神能帮忙解读分析下 非常感谢 这个问题困扰了很久
...全文
请发表友善的回复…
发表回复
