开始新对话

未解决

此帖子已超过 5 年

A

5 Practitioner

 • 

274.2K 消息

2216

2014年3月3日 23:00

dell 6850 系统win2000 server 出现蓝屏

dell 6850 系统win2000 server 出现蓝屏,显示如下信息.该如何解决?????

Microsoft (R) Windows Debugger  Version 6.6.0007.5

Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\WINNT\MEMORY.DMP]

Kernel Summary Dump File: Only kernel address space is available

************************************************************************

WARNING: Dump file has inconsistent set-bit count.  Data may be missing.

************************************************************************

Symbol search path is: SRV*c:\temp*msdl.microsoft.com/.../symbols

Executable search path is:

Windows 2000 Kernel Version 2195 (Service Pack 4) MP (8 procs) Free x86 compatible

Product: Server, suite: Enterprise TerminalServer SingleUserTS

Kernel base = 0x80400000 PsLoadedModuleList = 0x80484520

Debug session time: Tue Mar  4 15:18:55.468 2014 (GMT+8)

System Uptime: 0 days 0:28:05.468

Loading Kernel Symbols

.....................................Page ca36 not present in the dump file. Type ".hh dbgerr004" for details

...................................................................

Loading User Symbols

PEB address is NULL !

Loading unloaded module list

........

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {80000003, 804564c4, 0, be386be0}

Probably caused by : afd.sys ( afd!AfdIssueDeviceControl+129 )

Followup: MachineOwner

---------

5: kd> !analyze -v

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)

This is a very common bugcheck.  Usually the exception address pinpoints

the driver/function that caused the problem.  Always note this address

as well as the link date of the driver/image that contains this address.

Arguments:

Arg1: 80000003, The exception code that was not handled

Arg2: 804564c4, The address that the exception occurred at

Arg3: 00000000, Parameter 0 of the exception

Arg4: be386be0, Parameter 1 of the exception

Debugging Details:

------------------

EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) -

FAULTING_IP:

nt!DbgBreakPoint+0

804564c4 cc              int     3

EXCEPTION_PARAMETER1:  00000000

EXCEPTION_PARAMETER2:  be386be0

DEFAULT_BUCKET_ID:  INTEL_CPU_MICROCODE_ZERO

BUGCHECK_STR:  0x1E

PROCESS_NAME:  System

EXCEPTION_RECORD:  f6087c10 -- (.exr fffffffff6087c10)

ExceptionAddress: 804564c4 (nt!DbgBreakPoint)

  ExceptionCode: 80000003 (Break instruction exception)

 ExceptionFlags: 00000000

NumberParameters: 3

  Parameter[0]: 00000000

  Parameter[1]: be386be0

  Parameter[2]: 00000000

CONTEXT:  f6087868 -- (.cxr fffffffff6087868)

eax=00000001 ebx=875eaf68 ecx=be386be0 edx=00000000 esi=00000000 edi=00000000

eip=804564c4 esp=f6087cd8 ebp=f6087d04 iopl=0         nv up ei pl nz ac po cy

cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00000213

nt!DbgBreakPoint:

804564c4 cc              int     3

Resetting default scope

LAST_CONTROL_TRANSFER:  from be386d3b to 804564c4

STACK_TEXT:  

f6087cd4 be386d3b be38433a 8755ca08 00000000 nt!DbgBreakPoint

f6087d04 be386b4b 875194c8 f6087d24 0000000c afd!AfdIssueDeviceControl+0x129

f6087d30 be384154 875194c8 00000001 00000000 afd!AfdSetEventHandler+0x2c

f6087d54 be38434b 8755ca08 be374234 be371d03 afd!AfdFreeEndpointResources+0xb8

f6087d60 be371d03 8755cac0 be374190 8047747c afd!AfdFreeEndpoint+0x11

f6087d78 80417481 00000000 00000000 00000000 afd!AfdDoWork+0x4b

f6087da8 80455a82 00000000 00000000 00000000 nt!ExpWorkerThread+0xaf

f6087ddc 8046b012 804173d2 00000001 00000000 nt!PspSystemThreadStartup+0x54

00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

FOLLOWUP_IP:

afd!AfdIssueDeviceControl+129

be386d3b 3bf7            cmp     esi,edi

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  afd!AfdIssueDeviceControl+129

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: afd

IMAGE_NAME:  afd.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  3eaf8d29

STACK_COMMAND:  .cxr 0xfffffffff6087868 ; kb

FAILURE_BUCKET_ID:  0x1E_afd!AfdIssueDeviceControl+129

BUCKET_ID:  0x1E_afd!AfdIssueDeviceControl+129

Followup: MachineOwner

5 Practitioner

 • 

274.2K 消息

2014年3月4日 00:00

上面的信息是分析C:\WINNT\MEMORY.DMP 文件显示的信息.

蓝屏时: 显示ntoskrnl.exe 与 afd.sys 文件错误.

求高手帮助该如何解决此问题.

122 消息

2014年3月4日 19:00

使用过程中出现的蓝屏还是做过什么操作之后出现的?

蓝屏比较复杂,应该从硬件和软件2个方面去分析原因

5 Practitioner

 • 

274.2K 消息

2014年3月4日 20:00

运行报关用电子账册软件中的综合维护工具后引起的. 运行后几秒钟就重启了, 不知是哪个硬件驱动造成的,还是其它原因.系统是刚装的.

找不到事件!

Top