阅读577 返回首页    go 微软 go windows

Surface Pro4 IRQ

自从某次系统自动更新更了一波驱动之后就遇到了这个问题。

现在几乎一天一次蓝屏。很烦人，严重影响工作。求助！！！！

Minidump文件

Onedrive: https://1drv.ms/u/s!At2BNClrA92Tugf78f3Vp2_SQ_JW

Baidu: https://pan.baidu.com/s/1gfeWG4j

使用windbg的信息：

Microsoft (R) Windows Debugger Version 10.0.17016.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Documents\Desktop\111217-9546-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are 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
Built by: 16299.15.amd64fre.rs3_release.170928-1534
Machine Name:
Kernel base = 0xfffff801`d7a08000 PsLoadedModuleList = 0xfffff801`d7d69fd0
Debug session time: Sun Nov 12 15:21:21.885 2017 (UTC + 8:00)
System Uptime: 0 days 23:18:05.891
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, 2, 0, fffff801d7a72588}

Probably caused by : ntkrnlmp.exe ( nt!KiTimerWaitTest+2f8 )

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

nt!KeBugCheckEx:
fffff801`d7b6b960 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffdc84`96c87360=000000000000000a
0: 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: fffff801d7a72588, address which referenced memory

Debugging Details:
------------------


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  10.0.16299.19 (WinBuild.160101.0800)

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:  2

BUGCHECK_P1: 0

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff801d7a72588

READ_ADDRESS: fffff801d7e00380: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
 0000000000000000 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiTimerWaitTest+2f8
fffff801`d7a72588 4d8b36          mov     r14,qword ptr [r14]

CPU_COUNT: 4

CPU_MHZ: 8a0

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)

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXPNP: 1 (!blackboxpnp)


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  AV

PROCESS_NAME:  System

ANALYSIS_SESSION_HOST:  DESKTOP-CLQ9BB5

ANALYSIS_SESSION_TIME:  11-12-2017 16:12:41.0822

ANALYSIS_VERSION: 10.0.17016.1000 amd64fre

TRAP_FRAME:  ffffdc8496c874a0 -- (.trap 0xffffdc8496c874a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=fffff801d5f97c08
rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff801d7a72588 rsp=ffffdc8496c87630 rbp=ffffc70bcd7e8788
 r8=0000000000000000  r9=fffff801d7a08000 r10=fffff801d5f94180
r11=ffffdc8496c876c8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz ac po cy
nt!KiTimerWaitTest+0x2f8:
fffff801`d7a72588 4d8b36          mov     r14,qword ptr [r14] ds:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff801d7b771e9 to fffff801d7b6b960

STACK_TEXT:  
ffffdc84`96c87358 fffff801`d7b771e9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffdc84`96c87360 fffff801`d7b7557d : 00000000`00000000 00000000`00000000 ffffc70b`c8ec1ae0 fffff801`d7ac7df9 : nt!KiBugCheckDispatch+0x69
ffffdc84`96c874a0 fffff801`d7a72588 : 0000084f`33a06bf0 ffffc70b`cd7e8780 ffffc70b`c8ec1700 00000000`00000000 : nt!KiPageFault+0x23d
ffffdc84`96c87630 fffff801`d7a3fc65 : 00000000`00000002 00000000`00000002 00000000`00000000 fffff801`d5f94180 : nt!KiTimerWaitTest+0x2f8
ffffdc84`96c876d0 fffff801`d7a3fa36 : ffffc70b`cd7e8780 ffffc70b`cd7e8780 ffffc70b`c8ec1700 00000000`00000000 : nt!KiSetTimerEx+0x195
ffffdc84`96c87750 fffff801`d7a17911 : 00000000`00000000 ffffc70b`bf751080 00000012`a05f2000 ffffc70b`c8ec1700 : nt!KeSetCoalescableTimer+0x56
ffffdc84`96c87790 fffff801`d7b95a3b : ffffc70b`bf751080 00000000`00000000 00000000`00000001 ffffc70b`bf751080 : nt!ExpTimerResume+0x59
ffffdc84`96c877d0 fffff801`d7f0ce2e : ffffc70b`bf751358 ffffc70b`bf751050 ffffc70b`bf751358 00000000`00000000 : nt!PspProcessDelete+0x14358b
ffffdc84`96c87870 fffff801`d7ac98c6 : 00000000`00000000 00000000`00000000 ffffc70b`bf751358 ffffc70b`bf751080 : nt!ObpRemoveObjectRoutine+0x7e
ffffdc84`96c878d0 fffff801`d7ed8802 : 00000000`00000000 ffffc70b`bf1d8da8 ffffc70b`bf1d8da8 00000000`00000000 : nt!ObfDereferenceObjectWithTag+0xc6
ffffdc84`96c87910 fffff801`d7f0ce2e : fffff801`d7f55e10 ffffc70b`bf1d86d0 fffff801`d7f55e10 ffffc70b`bf1d86d0 : nt!PspThreadDelete+0x1d2
ffffdc84`96c87980 fffff801`d7f55ead : 00000000`00000000 ffffc70b`bf1d86d0 fffff801`d7f55e10 ffffc70b`bdca1980 : nt!ObpRemoveObjectRoutine+0x7e
ffffdc84`96c879e0 fffff801`d7a62835 : ffffc70b`c8ec1700 fffff801`d7f55e10 ffffc70b`bdca1980 00000000`00000012 : nt!ObpProcessRemoveObjectQueue+0x9d
ffffdc84`96c87a80 fffff801`d7aeb4e7 : ffffd79b`454f2110 00000000`00000080 ffffc70b`bdcc3040 ffffc70b`c8ec1700 : nt!ExpWorkerThread+0xf5
ffffdc84`96c87b10 fffff801`d7b70ef6 : ffffa281`48140180 ffffc70b`c8ec1700 fffff801`d7aeb4a0 00000000`00000001 : nt!PspSystemThreadStartup+0x47
ffffdc84`96c87b60 00000000`00000000 : ffffdc84`96c88000 ffffdc84`96c81000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


THREAD_SHA1_HASH_MOD_FUNC:  cc24e4c0a8779558fb0d6361e72f812fc42ed5e0

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  ebab9b5f0de4ad7ff171b880ffa9f77c2e1db414

THREAD_SHA1_HASH_MOD:  9eef8c7ca0ce66f8b8b34848179f303828cff762

FOLLOWUP_IP: 
nt!KiTimerWaitTest+2f8
fffff801`d7a72588 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

IMAGE_VERSION:  10.0.16299.19

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-12T07:21:21.000Z

OSBUILD:  16299

OSSERVICEPACK:  19

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2017-10-10 13:23:07

BUILDDATESTAMP_STR:  160101.0800

BUILDLAB_STR:  WinBuild

BUILDOSVER_STR:  10.0.16299.19

ANALYSIS_SESSION_ELAPSED_TIME:  605

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:av_nt!kitimerwaittest

FAILURE_ID_HASH:  {8c029a8d-9f29-4bde-2664-6010a6365158}

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

最后更新：2017-11-12 17:04:16

  上一篇：go WIN10 蓝屏 求分析
  下一篇：go Edge浏览器出了问题