Surface pro 4,Windows蓝屏报告,Probably caused by :
这两天遇到两次蓝屏,都是在打游戏的时候遇到的,找到dmp文件,结果如下,请问有人知道是什么原因造成的吗?谢谢!
Microsoft (R) Windows Debugger Version 10.0.16299.15 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Chen\Desktop\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 16299 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 16299.15.amd64fre.rs3_release.170928-1534
Machine Name:
Kernel base = 0xfffff800`e1a99000 PsLoadedModuleList = 0xfffff800`e1dfafd0
Debug session time: Fri Nov 3 11:37:04.629 2017 (UTC + 8:00)
System Uptime: 0 days 21:00:42.566
Loading Kernel Symbols
...............................................................
................................................................
................................................................
........................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000009`8ad35018). Type ".hh dbgerr001" for details
Loading unloaded module list
..................................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {0, 2, 0, fffff800e1b03588}
Probably caused by : ntkrnlmp.exe ( nt!KiTimerWaitTest+2f8 )
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800e1b03588, address which referenced memory
Debugging Details:
------------------
DUMP_CLASS: 1
DUMP_QUALIFIER: 401
BUILD_VERSION_STRING: 16299.15.amd64fre.rs3_release.170928-1534
SYSTEM_MANUFACTURER: Microsoft Corporation
SYSTEM_PRODUCT_NAME: Surface Pro 4
SYSTEM_SKU: Surface_Pro_4
SYSTEM_VERSION: D:0B:08F:1C:03P:38
BIOS_VENDOR: Microsoft Corporation
BIOS_VERSION: 107.1741.768
BIOS_DATE: 06/13/2017
BASEBOARD_MANUFACTURER: Microsoft Corporation
BASEBOARD_PRODUCT: Surface Pro 4
DUMP_TYPE: 1
BUGCHECK_P1: 0
BUGCHECK_P2: 2
BUGCHECK_P3: 0
BUGCHECK_P4: fffff800e1b03588
READ_ADDRESS: 0000000000000000
CURRENT_IRQL: 2
FAULTING_IP:
nt!KiTimerWaitTest+2f8
fffff800`e1b03588 4d8b36 mov r14,qword ptr [r14]
CPU_COUNT: 4
CPU_MHZ: 9c0
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 4e
CPU_STEPPING: 3
CPU_MICROCODE: 6,4e,3,0 (F,M,S,R) SIG: BA'00000000 (cache) BA'00000000 (init)
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: AV
PROCESS_NAME: SearchIndexer.exe
ANALYSIS_SESSION_HOST: SURFACE-CHENCHE
ANALYSIS_SESSION_TIME: 11-03-2017 14:36:56.0045
ANALYSIS_VERSION: 10.0.16299.15 amd64fre
TRAP_FRAME: ffffa184b27bf3f0 -- (.trap 0xffffa184b27bf3f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=fffff800e1eadbc0
rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800e1b03588 rsp=ffffa184b27bf580 rbp=ffffd68a6a043a38
r8=0000000000000000 r9=fffff800e1a99000 r10=ffffe681fd9d2180
r11=ffffa184b27bf618 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz ac pe cy
nt!KiTimerWaitTest+0x2f8:
fffff800`e1b03588 4d8b36 mov r14,qword ptr [r14] ds:00000000`00000000=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800e1c081e9 to fffff800e1bfc960
STACK_TEXT:
ffffa184`b27bf2a8 fffff800`e1c081e9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffa184`b27bf2b0 fffff800`e1c0657d : 00000004`00000008 00000000`00000004 ffffd68a`6a3205f0 00000000`00000004 : nt!KiBugCheckDispatch+0x69
ffffa184`b27bf3f0 fffff800`e1b03588 : 00000259`137bdef0 ffffd68a`6a043a30 ffffd68a`625b85c0 00000000`00000000 : nt!KiPageFault+0x23d
ffffa184`b27bf580 fffff800`e1ad0c65 : 00000000`00000002 00000000`00000002 00000000`00000000 ffffe681`fd9d2180 : nt!KiTimerWaitTest+0x2f8
ffffa184`b27bf620 fffff800`e1ad0a36 : ffffd68a`6a043a30 ffffd68a`6a043a30 ffffd68a`625b85c0 00000000`00000000 : nt!KiSetTimerEx+0x195
ffffa184`b27bf6a0 fffff800`e1aa8911 : 00000000`00000000 ffffbc81`6ee8b000 00000000`00000001 ffffd68a`62357080 : nt!KeSetCoalescableTimer+0x56
ffffa184`b27bf6e0 fffff800`e1c26a3b : ffffd68a`6a3205c0 00000000`00000000 ffffd68a`00000001 ffffd68a`6a3205c0 : nt!ExpTimerResume+0x59
ffffa184`b27bf720 fffff800`e1f9de2e : 00000000`00000000 ffffd68a`6a320590 00000000`00000000 00000000`00000000 : nt!PspProcessDelete+0x14358b
ffffa184`b27bf7c0 fffff800`e1b5a8c6 : 00000000`00000000 00000000`00000000 00000000`00000000 ffffd68a`6a3205c0 : nt!ObpRemoveObjectRoutine+0x7e
ffffa184`b27bf820 fffff800`e1fc781b : 00000000`ffff8010 ffffd68a`5cc9eb90 ffffd68a`5cc9eb90 ffffd68a`6a320590 : nt!ObfDereferenceObjectWithTag+0xc6
ffffa184`b27bf860 fffff800`e1fc9beb : ffffa184`b27bf9c0 ffffbc81`00000000 00000000`00000000 fffff800`e200e7af : nt!ObCloseHandleTableEntry+0x25b
ffffa184`b27bf9a0 fffff800`e1c07d53 : ffffd68a`625b85c0 ffffd68a`624acac0 ffffd68a`625b85c0 00000198`d0b29b68 : nt!NtClose+0xcb
ffffa184`b27bfa00 00007ffb`79fa0024 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000009`8b4f95d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`79fa0024
THREAD_SHA1_HASH_MOD_FUNC: 56bbda43058b319b941139b7fcbf39f4218c27fb
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 45e071311fbef8bdd572f39b636da9f1ed5dda9b
THREAD_SHA1_HASH_MOD: fe34192f63d13620a8987d294372ee74d699cfee
FOLLOWUP_IP:
nt!KiTimerWaitTest+2f8
fffff800`e1b03588 4d8b36 mov r14,qword ptr [r14]
FAULT_INSTR_CODE: 48368b4d
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!KiTimerWaitTest+2f8
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 59dc593b
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 2f8
FAILURE_BUCKET_ID: AV_nt!KiTimerWaitTest
BUCKET_ID: AV_nt!KiTimerWaitTest
PRIMARY_PROBLEM_CLASS: AV_nt!KiTimerWaitTest
TARGET_TIME: 2017-11-03T03:37:04.000Z
OSBUILD: 16299
OSSERVICEPACK: 0
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 784
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2017-10-10 13:23:07
BUILDDATESTAMP_STR: 170928-1534
BUILDLAB_STR: rs3_release
BUILDOSVER_STR: 10.0.16299.15.amd64fre.rs3_release.170928-1534
ANALYSIS_SESSION_ELAPSED_TIME: 570
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:av_nt!kitimerwaittest
FAILURE_ID_HASH: {8c029a8d-9f29-4bde-2664-6010a6365158}
Followup: MachineOwner
最后更新:2017-11-03 18:03:45
上一篇:
win10 1709 微软拼音输入法 触控键盘大写锁定紊乱
下一篇:
说你的组织使用了 Windows Defender应用程序控制来组织此应用。怎么办
你的设备已过期,并缺少重要的安全和质量更新,因此存在风险。让我们带你重回正轨,这样
Microsoft store 无法联网,显示Microsoft Store需要联网,你似乎没有联网
设备以迁移 由于仅部分匹配或匹配不明确,因此无法迁移设备
由于在创建转储期间出错,创建转储文件失败。
发生临时 DNS 错误
应用商店,在我们这边发生问题,无法使你登陆,错误代码: 0xD000000D
照相机不可用,错误代码:0xA00F4244(0xC00DABE0)
应用商店打开异常提示“清单中指定了未知的布局”
自定义扫描Windows defender里面的设备性能和运行状况 黄色感叹号问题
windows预口体验成员内口版本遇到问题需要重启
热门内容
windows10 点开此电脑后,有两个显示硬盘盘符的目录是怎么回事?
windows 10 专业版无法下载中文语言包
KB4056892
win10不能共享文件夹
在Surfacebook上用Windows to go 1703版本,更新后重启蓝屏,无法进入系统
windows10 1709版本更新失败,错误0x8007001f
microdoft visual c++ 2015 redistributable
WIN10 Insider Preview 17025更新失败,错误代码0x80096004
计算机管理服务 出现一个内部错误(INVALID
关于控制面板中的安全和维护内提示Windows defender 防病毒已关闭的问题