谢谢,目测我已经找到问题原因了,开始的时候就一直怀疑是ACHI驱动导致的,但是我无论如何也卸载不了ACHI驱动,因为驱动是后装的,也就是说装系统的时候我用的是ATA模式,装完系统以后我在装的INTEL C216的SATA ACHI驱动,然后重启的时候改为ACHI模式,可惜的是一旦安装了无论怎么弄都回不到未安装前的状态,最后我只好重装了系统,把除了ACHI驱动以外的驱动全装了,放了几天几夜也没蓝屏,刚开始我还怀疑过是显卡驱动的问题,装了好几个版本的都是一样,现在找到问题所在了,但是我一直不明白,为什么一定要等十几个小时才蓝屏,这十几个小时电脑是没有操作的,我曾怀疑是休眼导致的,但是直接启用休眠过段时间再唤醒,结果是不蓝屏的,那到底是ACHI驱动干了什么事情导致的十几个小时会自已蓝屏,如果有人在使用,机器是不会蓝屏的,求指教
附上更正命令后的内容,我试过发附件,但是发不出来
2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * *******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e) 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. Some common problems are exception code 0x80000003. This means a hard coded breakpoint or assertion was hit, but this system was booted /NODEBUG. This is not supposed to happen as developers should never have hardcoded breakpoints in retail code, but ... If this happens, make sure a debugger gets connected, and the system is booted /DEBUG. This will let us see why this breakpoint is happening. Arguments: Arg1: c0000005, The exception code that was not handled Arg2: 8053b658, The address that the exception occurred at Arg3: a76c8194, Trap Frame Arg4: 00000000
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 *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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 *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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 *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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 *** *** *** *************************************************************************
ADDITIONAL_DEBUG_TEXT: Use '!findthebuild' command to search for the target build information. If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
FAULTING_MODULE: 804d8000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 52302721
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - 0x%08lx
FAULTING_IP: nt+63658 8053b658 89448fe8 mov dword ptr [edi+ecx*4-18h],eax
TRAP_FRAME: a76c8194 -- (.trap 0xffffffffa76c8194) ErrCode = 00000002 eax=575c3a43 ebx=00000000 ecx=00000006 edx=00000001 esi=f67f20e0 edi=00000000 eip=8053b658 esp=a76c8208 ebp=a76c8210 iopl=0 nv up ei ng nz ac po cy cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010293 nt+0x63658: 8053b658 89448fe8 mov dword ptr [edi+ecx*4-18h],eax ds:0023:00000000=???????? Resetting default scope
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
LAST_CONTROL_TRANSFER: from a7493ba0 to 8053b658
STACK_TEXT: WARNING: Stack unwind information not available. Following frames may be wrong. a76c8210 a7493ba0 00000000 f67f20e0 00000019 nt+0x63658 a76c8a5c 804f018f 85c23880 85c969a0 85c969a0 EtFilemon+0x1ba0 a76c8b4c 805c0444 8ab47600 00000000 86b61328 nt+0x1818f a76c8bc4 805bc9d0 00000000 a76c8c04 00000040 nt+0xe8444 a76c8c18 80577033 00000000 00000000 00000001 nt+0xe49d0 a76c8c94 805779aa 0108fac8 80100080 0108fa68 nt+0x9f033 a76c8cf0 8057a0b4 0108fac8 80100080 0108fa68 nt+0x9f9aa a76c8d30 8054261c 0108fac8 80100080 0108fa68 nt+0xa20b4 a76c8d64 7c92e4f4 badb0d00 0108fa30 a736dd98 nt+0x6a61c a76c8d68 badb0d00 0108fa30 a736dd98 a736ddcc 0x7c92e4f4 a76c8d6c 0108fa30 a736dd98 a736ddcc 00000000 0xbadb0d00 a76c8d70 a736dd98 a736ddcc 00000000 00000000 0x108fa30 a76c8d74 a736ddcc 00000000 00000000 00000000 0xa736dd98 a76c8d78 00000000 00000000 00000000 00000000 0xa736ddcc
STACK_COMMAND: kb
FOLLOWUP_IP: EtFilemon+1ba0 a7493ba0 ?? ???
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: EtFilemon+1ba0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: EtFilemon
IMAGE_NAME: EtFilemon.sys
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner ---------
|