没有被BugCheck记录？这个。。。也不是太意外。。。有dump就好。。。
我的帖子不知道看过没：
http://bbs.kafan.cn/thread-1850008-1-1.html
根据我那帖子初步得到的结论：
错误名称 0x0000001E：KMODE_EXCEPTION_NOT_HANDLED
故障分析 0x0000001E 错误表示Windows检测到一个非法的或未知的进程指令。这个错误一般是因为内存发生故障引起的，或者与0x0000000A错误相似，表示在内核模式中存在以过高的进程内部请求级别（IRQL）访问其没有权限访问的内存地址。 如果遇到0x0000001E错误，建议首先检查一下软件及硬件兼容性，看看最近有没有安装过新的应用软件、硬件设备或驱动程序。如果有的话，请将最近安装过的软件及硬件逐一卸载，看看问题能否解决；其次，请检查一下蓝屏故障提示中是否提到问题是由WIN32K.SYS文件引起的，如果是的话，那么很可能是远程控制类软件引起的故障。
参考资料 关于0x0000001E错误，可以参考Microsoft知识库文章KB275678：
http://support.microsoft.com/kb/275678/zh-cn
总之，先查一下内存。
接下来上Debug报告：
Windows 8.1 Kernel Version 9600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9600.17936.amd64fre.winblue_ltsb.150715-0840
Machine Name:
Kernel base = 0xfffff800`78480000 PsLoadedModuleList = 0xfffff800`787557b0
Debug session time: Sat Sep 26 16:01:19.457 2015 (UTC + 8:00)
System Uptime: 0 days 23:34:30.508
Loading Kernel Symbols
.
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
..............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
..........................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000005, fffff800784e99c0, 0, ffffffffffffffff}
Probably caused by : memory_corruption ( nt!MiIssueHardFault+264 )
Followup: MachineOwner
---------
3: 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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff800784e99c0, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception
Debugging Details:
------------------
SYSTEM_SKU: ASUS-NotebookSKU
SYSTEM_VERSION: 1.0
BIOS_DATE: 08/30/2013
BASEBOARD_PRODUCT: X450JF
BASEBOARD_VERSION: 1.0
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff800784e99c0
BUGCHECK_P3: 0
BUGCHECK_P4: ffffffffffffffff
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800787df138
GetUlongPtrFromAddress: unable to read from fffff800787df298
GetUlongPtrFromAddress: unable to read from fffff800787df520
ffffffffffffffff
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - 0x%p
FAULTING_IP:
nt!MiIssueHardFault+264
fffff800`784e99c0 0fbf8fe4010000 movsx ecx,word ptr [rdi+1E4h]
EXCEPTION_PARAMETER2: ffffffffffffffff
BUGCHECK_STR: 0x1E_c0000005_R
CPU_COUNT: 4
CPU_MHZ: aea
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 3c
CPU_STEPPING: 3
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: winlogon.exe
CURRENT_IRQL: 0
ANALYSIS_VERSION: 10.0.10240.9 x86fre
LAST_CONTROL_TRANSFER: from fffff800785fd141 to fffff800785cf9a0
STACK_TEXT:
ffffd000`21a53e18 fffff800`785fd141 : 00000000`0000001e ffffffff`c0000005 fffff800`784e99c0 00000000`00000000 : nt!KeBugCheckEx
ffffd000`21a53e20 fffff800`785db5c2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x1d281
ffffd000`21a54510 fffff800`785d9afe : ffff630f`7edcb331 00000000`00000001 00000000`00000000 ffffe001`7e531690 : nt!KiExceptionDispatch+0xc2
ffffd000`21a546f0 fffff800`784e99c0 : 00000000`00000002 ffffd000`21a548f8 ffffe001`8022ed98 ffffd000`00000000 : nt!KiGeneralProtectionFault+0xfe
ffffd000`21a54880 fffff800`784d335a : ffffe001`8022ed98 ffffe001`8037c880 00000000`00000000 fffff960`002ff378 : nt!MiIssueHardFault+0x264
ffffd000`21a54940 fffff800`785d9c2f : 00000000`00000000 00000000`00000000 ffffd000`21a54a01 ffffe001`7ffb0710 : nt!MmAccessFault+0x5ba
ffffd000`21a54b00 00007ffb`82fdd466 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x12f
0000009f`4650f830 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`82fdd466
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiIssueHardFault+264
fffff800`784e99c0 0fbf8fe4010000 movsx ecx,word ptr [rdi+1E4h]
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: nt!MiIssueHardFault+264
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 55a68c66
IMAGE_VERSION: 6.3.9600.17936
IMAGE_NAME: memory_corruption
BUCKET_ID_FUNC_OFFSET: 264
FAILURE_BUCKET_ID: 0x1E_c0000005_R_nt!MiIssueHardFault
BUCKET_ID: 0x1E_c0000005_R_nt!MiIssueHardFault
PRIMARY_PROBLEM_CLASS: 0x1E_c0000005_R_nt!MiIssueHardFault
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x1e_c0000005_r_nt!miissuehardfault
FAILURE_ID_HASH: {0ad38ab7-f47d-7b82-c129-d9948639b890}
Followup: MachineOwner
---------
根据：https://msdn.microsoft.com/en-us ... s/hardware/ff557408(v=vs.85).aspx
0xC0000005: STATUS_ACCESS_VIOLATION
A memory access violation occurred. (Parameter 4 of the bug check is the address that the driver attempted to access.)
看看是不是哪个软件冲突了
|
发表于 2015-9-26 17:03:29
楼主