首页
社区
课程
招聘
[求助] 蓝屏故障如何分析出原因啊?
发表于: 2010-3-18 15:28 7339

[求助] 蓝屏故障如何分析出原因啊?

2010-3-18 15:28
7339
计算机已经从检测错误后重新启动。检测错误: 0x100000d1 (0xde076dfa, 0x000000ff, 0x00000001, 0xb75cf7fb)。 已将转储的数据保存在: C:\WINDOWS\Minidump\Mini031810-01.dmp。

C:\>dumpchk Mini031810-01.dmp
Loading dump file Mini031810-01.dmp
----- 32 bit Kernel Mini Dump Analysis

DUMP_HEADER32:
MajorVersion        0000000f
MinorVersion        00000a28
DirectoryTableBase  06bf8380
PfnDataBase         80e00000
PsLoadedModuleList  8055e720
PsActiveProcessHead 805648b8
MachineImageType    0000014c
NumberProcessors    00000002
BugCheckCode        100000d1
BugCheckParameter1  de076dfa
BugCheckParameter2  000000ff
BugCheckParameter3  00000001
BugCheckParameter4  b75cf7fb
PaeEnabled          00000001
KdDebuggerDataBlock 8054e2e0
MiniDumpFields      00000dff

TRIAGE_DUMP32:
ServicePackBuild      00000300
SizeOfDump            00010000
ValidOffset           0000fffc
ContextOffset         00000320
ExceptionOffset       000007d0
MmOffset              00001068
UnloadedDriversOffset 000010a0
PrcbOffset            00001878
ProcessOffset         000024c8
ThreadOffset          00002728
CallStackOffset       00002980
SizeOfCallStack       000006b8
DriverListOffset      000032c8
DriverCount           0000007e
StringPoolOffset      00005830
StringPoolSize        00001178
BrokenDriverOffset    00000000
TriageOptions         00000041
TopOfStack            b7845948
DebuggerDataOffset    00003038
DebuggerDataSize      00000290
DataBlocksOffset      000069a8
DataBlocksCount       00000002

Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible

Kernel base = 0x804d8000 PsLoadedModuleList = 0x8055e720
Debug session time: Thu Mar 18 13:17:06 2010
System Uptime: 0 days 0:09:21
start    end        module name
804d8000 806e5000   nt             Checksum: 001FD3A1  Timestamp: Tue Aug 04 22:
20:04 2009 (4A784394)

Unloaded modules:
b7942000 b79ed000   kmixer.sys    Timestamp: unavailable (00000000)
b83e5000 b8410000   kmixer.sys    Timestamp: unavailable (00000000)
f7ad6000 f7ad7000   drmkaud.sys    Timestamp: unavailable (00000000)
b8410000 b8433000   aec.sys     Timestamp: unavailable (00000000)
b861e000 b862b000   DMusic.sys    Timestamp: unavailable (00000000)
f7607000 f7615000   swmidi.sys    Timestamp: unavailable (00000000)
f79cb000 f79cd000   splitter.sys    Timestamp: unavailable (00000000)
f7657000 f7662000   imapi.sys    Timestamp: unavailable (00000000)
f7647000 f7655000   redbook.sys    Timestamp: unavailable (00000000)
f7637000 f7643000   p3.sys      Timestamp: unavailable (00000000)
f7877000 f787c000   Cdaudio.SYS    Timestamp: unavailable (00000000)
f7607000 f7617000   cdrom.sys    Timestamp: unavailable (00000000)
f7983000 f7986000   Sfloppy.SYS    Timestamp: unavailable (00000000)
f7867000 f786c000   Flpydisk.SYS    Timestamp: unavailable (00000000)

Finished dump check

还要一个工具(WindowsXP-KB838079-SupportTools-ENU.exe), 自已下载吧

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

上传的附件:
收藏
免费 0
支持
分享
最新回复 (6)
雪    币: 1272
活跃值: (5124)
能力值: ( LV3,RANK:20 )
在线值:
发帖
回帖
粉丝
2
在网上看了一下, 别人的好像都有下面的"ExceptionAddress", 我的为什么没有

MachineImageType i386
NumberProcessors 1
BugCheckCode 0xc000021a
BugCheckParameter1 0xe1270188
BugCheckParameter2 0x00000001
BugCheckParameter3 0x00000000
BugCheckParameter4 0x00000000

ExceptionCode 0x80000003
ExceptionFlags 0x00000001
ExceptionAddress 0x8014fb84

和我设的"小内存转存"无关吧?
上传的附件:
2010-3-18 15:33
0
雪    币: 234
活跃值: (10)
能力值: ( LV2,RANK:10 )
在线值:
发帖
回帖
粉丝
PAC
3
小内存转储也应该有异常地址啊
2010-3-18 17:15
0
雪    币: 1272
活跃值: (5124)
能力值: ( LV3,RANK:20 )
在线值:
发帖
回帖
粉丝
4
我找了成 6 吧机, 都找不到异常地址, 只有我上面的.....
2010-3-19 18:34
0
雪    币: 296
活跃值: (89)
能力值: ( LV15,RANK:340 )
在线值:
发帖
回帖
粉丝
5
大致看了一下,TesSafe.sys引起的蓝屏。注意红色标出的部分:

1: 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: de076dfa, memory referenced
Arg2: 000000ff, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: b75cf7fb, address which referenced memory

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



MODULE_NAME: TesSafe

FAULTING_MODULE: 804d8000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4b62962c

WRITE_ADDRESS: de076dfa

CURRENT_IRQL: ff

FAULTING_IP:
TesSafe+77fb
b75cf7fb 088946148326 or byte ptr [ecx+26831446h],cl

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

BUGCHECK_STR: 0xD1

LAST_CONTROL_TRANSFER: from b75cf854 to b75cf7fb

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
b78459bc b75cf854 b7845d9c 83e65340 00000000 TesSafe+0x77fb
b7845dc8 028f37df 0000001b 00000206 154cff08 TesSafe+0x7854
b7845dcc 00000000 00000206 154cff08 00000023 0x28f37df


STACK_COMMAND: kb

FOLLOWUP_IP:
TesSafe+77fb
b75cf7fb 088946148326 or byte ptr [ecx+26831446h],cl

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: TesSafe+77fb

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: TesSafe.sys

BUCKET_ID: WRONG_SYMBOLS

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

1: kd> lmvm TesSafe
start end module name
b75c8000 b7602000 TesSafe T (no symbols)
Loaded symbol image file: TesSafe.sys
Image path: TesSafe.sys
Image name: TesSafe.sys
Timestamp: Fri Jan 29 16:02:52 2010 (4B62962C)
CheckSum: 00041D84
ImageSize: 0003A000
Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0
2010-3-19 22:25
0
雪    币: 1491
活跃值: (985)
能力值: (RANK:860 )
在线值:
发帖
回帖
粉丝
6
一直都不怎么动调试DUMP文件
2010-3-19 22:59
0
雪    币: 1272
活跃值: (5124)
能力值: ( LV3,RANK:20 )
在线值:
发帖
回帖
粉丝
7
谢谢, 我明天回去按你的做一下!!!!
2010-3-20 05:02
0
游客
登录 | 注册 方可回帖
返回
//