首页
社区
课程
招聘
[蓝屏求助]XP无问题,2003过一会就蓝屏..
发表于: 2011-1-12 14:16 3947

[蓝屏求助]XP无问题,2003过一会就蓝屏..

2011-1-12 14:16
3947
Use !analyze -v to get detailed debugging information.

BugCheck 1000007F, {8, 80042000, 0, 0}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Followup: MachineOwner
---------

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:
------------------

BUGCHECK_STR:  0x7f_8

CUSTOMER_CRASH_COUNT:  4

DEFAULT_BUCKET_ID:  DRIVER_FAULT_SERVER_MINIDUMP

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

UNALIGNED_STACK_POINTER:  c0000002

LAST_CONTROL_TRANSFER:  from 00000000 to 80a51e40

STACK_TEXT:  
c0000006 00000000 00000000 00000000 00000000 hal!KfRaiseIrql+0x6

STACK_COMMAND:  kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

BUCKET_ID:  BAD_STACK

Followup: MachineOwner

[注意]传递专业知识、拓宽行业人脉——看雪讲师团队等你加入!

收藏
免费 0
支持
分享
最新回复 (2)
雪    币: 30
活跃值: (10)
能力值: ( LV2,RANK:10 )
在线值:
发帖
回帖
粉丝
2
不知道什么问题,呵呵 帮你顶一下  
由楼下的大牛回答
2011-1-12 15:57
0
雪    币: 601
活跃值: (256)
能力值: ( LV11,RANK:190 )
在线值:
发帖
回帖
粉丝
3
这个陷阱可能是一个绑定的陷阱,不允许内核陷阱捕捉或处理一个较早的故障,始终会导致系统故障时出现的故障的双重故障,当内核堆栈溢出,函数类型不匹配,有故障或不匹配的内存可能导致此错误检查
2011-1-12 18:05
0
游客
登录 | 注册 方可回帖
返回
//