这是用windbg工具检测蓝屏原因后的分析结果
microsoft(r)windows debugger version 6.11.0001.404 x86
copyright(c)microsoft corporation.all rights reserved.
loading dump file[c:\windows\minidump\mini052709-06.dmp]
mini kernel dump file:only reg**ters and stack trace are **ailable
symbol search path **:*invalid*
symbol loading may be unreliable without a symbol search path.*
use.symfix to h**e the debugger choose a symbol path.*
after setting your symbol path,use.reload to refresh symbol locations.*
executable search path **:
symbols can not be loaded because symbol path ** 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 ntoskrnl.exe,win32 error 0n2
warning:unable to verify timestamp for ntoskrnl.exe
error:module load completed but symbols could not be loaded for ntoskrnl.exe
windows xp kernel version 2600(service pack 3)mp(2 procs)free x86 compatible
product:winnt,suite:terminalserver singleuserts
machine name:
kernel base=0x804d8000 psloadedmodulel**t=0x8055e720
debug session time:wed may 27 22:06:16.000 2009(gmt+8)
system uptime:0 days 0:13:54.740
symbols can not be loaded because symbol path ** 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 ntoskrnl.exe,win32 error 0n2
warning:unable to verify timestamp for ntoskrnl.exe
error:module load completed but symbols could not be loaded for ntoskrnl.exe
loading kernel symbols
loading user symbols
loading unloaded module l**t
bugcheck analys***
use!analyze-v to get detailed debugging **rmation.
bugcheck c2,{7,cd4,b**,b**7280c}
kernel symbols are wrong.please fix symbols to do analys**.
warning:unable to verify timestamp for eqsyssecure.sys
error:module load completed but symbols could not be loaded for eqsyssecure.sys
warning:unable to verify timestamp for safeboxkrnl.sys
error:module load completed but symbols could not be loaded for safeboxkrnl.sys
warning:unable to verify timestamp for swenum.sys
error:module load completed but symbols could not be loaded for swenum.sys
your debugger ** not using the correct symbols*
in order for th** command to work properly,your symbol path*
must point to.pdb files that h**e full type **rmation.*
certain.pdb files(such as the public os symbols)do not*
contain the required **rmation.contact the group that*
provided you with these symbols if you need th** command to*
work.*
type referenced:nt!kprcb*
your debugger ** not using the correct symbols*
in order for th** command to work properly,your symbol path*
must point to.pdb files that h**e full type **rmation.*
certain.pdb files(such as the public os symbols)do not*
contain the required **rmation.contact the group that*
provided you with these symbols if you need th** command to*
work.*
type referenced:nt!kprcb*
symbols can not be loaded because symbol path ** 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 ** 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:eqsyssecure.sys(eqsyssecure+6c2e)
followup:machineowner
1:kd>!analyze-v
bugcheck analys***
bad_pool_caller(c2)
the current thread ** making a bad pool request.typically th** ** at a bad irql level or double freeing the same allocation,etc.
arguments:
arg1:**,attempt to free pool which was already freed
arg2:00000cd4,(reserved)
arg3:b**,memory contents of the pool block
arg4:b**7280c,address of the block of pool being deallocated
debugging details:
kernel symbols are wrong.please fix symbols to do analys**.
your debugger ** not using the correct symbols*
in order for th** command to work properly,your symbol path*
must point to.pdb files that h**e full type **rmation.*
certain.pdb files(such as the public os symbols)do not*
contain the required **rmation.contact the group that*
provided you with these symbols if you need th** command to*
work.*
type referenced:nt!kprcb*
...