949
係統無故重啟 附dump文件分析
求分析下是什麼問題
Microsoft (R) Windows Debugger Version 10.0.15063.468 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\112817-83062-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 10240 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 10240.16384.amd64fre.th1.150709-1700
Machine Name:
Kernel base = 0xfffff802`ac011000 PsLoadedModuleList = 0xfffff802`ac335f30
Debug session time: Tue Nov 28 17:37:20.597 2017 (UTC + 1:00)
System Uptime: 0 days 3:02:13.591
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
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {ffffffffffffffa5, 2, 0, fffff802ac0f0e0a}
Probably caused by : ntkrnlmp.exe ( nt!KiFindReadyThread+5a )
Followup: MachineOwner
---------
0: kd> !abalyze -v
No export abalyze found
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: ffffffffffffffa5, 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: fffff802ac0f0e0a, address which referenced memory
Debugging Details:
------------------
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 10240.16384.amd64fre.th1.150709-1700
SYSTEM_MANUFACTURER: HP
SYSTEM_PRODUCT_NAME: HP Pavilion Notebook
SYSTEM_SKU: T1L76EA#ABE
SYSTEM_VERSION: Type1ProductConfigId
BIOS_VENDOR: Insyde
BIOS_VERSION: F.74
BIOS_DATE: 11/18/2015
BASEBOARD_MANUFACTURER: HP
BASEBOARD_PRODUCT: 80A4
BASEBOARD_VERSION: 91.1B
DUMP_TYPE: 2
BUGCHECK_P1: ffffffffffffffa5
BUGCHECK_P2: 2
BUGCHECK_P3: 0
BUGCHECK_P4: fffff802ac0f0e0a
READ_ADDRESS: fffff802ac3d5500: Unable to get MiVisibleState
ffffffffffffffa5
CURRENT_IRQL: 2
FAULTING_IP:
nt!KiFindReadyThread+5a
fffff802`ac0f0e0a 410fb649a5 movzx ecx,byte ptr [r9-5Bh]
CPU_COUNT: 4
CPU_MHZ: 960
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 4e
CPU_STEPPING: 3
CPU_MICROCODE: 6,4e,3,0 (F,M,S,R) SIG: 33'00000000 (cache) 33'00000000 (init)
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: AV
PROCESS_NAME: svchost.exe
ANALYSIS_SESSION_HOST: DESKTOP-3VFU3FD
ANALYSIS_SESSION_TIME: 12-14-2017 18:17:38.0441
ANALYSIS_VERSION: 10.0.15063.468 x86fre
TRAP_FRAME: ffffd00022f76cf0 -- (.trap 0xffffd00022f76cf0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000000000a rbx=0000000000000000 rcx=fffff802ac374180
rdx=ffffd000572b3180 rsi=0000000000000000 rdi=0000000000000000
rip=fffff802ac0f0e0a rsp=ffffd00022f76e80 rbp=0000000000000040
r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
r11=ffffd000572b3180 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
nt!KiFindReadyThread+0x5a:
fffff802`ac0f0e0a 410fb649a5 movzx ecx,byte ptr [r9-5Bh] ds:ffffffff`ffffffa5=??
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff802ac1685a9 to fffff802ac15dc20
STACK_TEXT:
ffffd000`22f76ba8 fffff802`ac1685a9 : 00000000`0000000a ffffffff`ffffffa5 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffd000`22f76bb0 fffff802`ac166dc8 : 00000002`f02f56e6 00000000`00000000 ffffe000`69cfa6d0 00000000`000008d0 : nt!KiBugCheckDispatch+0x69
ffffd000`22f76cf0 fffff802`ac0f0e0a : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x248
ffffd000`22f76e80 fffff802`ac056cc3 : ffffd000`572b3180 00000000`00000000 00000000`00000000 00000000`0000000a : nt!KiFindReadyThread+0x5a
ffffd000`22f76eb0 fffff802`ac0569ea : fffff802`ac374180 00000000`00000001 fffff802`ac3ea200 ffffe000`6ca53800 : nt!KiSearchForNewThreadOnProcessor+0x143
ffffd000`22f76ef0 fffff802`ac056159 : 00000000`00000000 00000000`00000001 00000000`00000000 ffffe000`6ca53900 : nt!KiSearchForNewThread+0x21a
ffffd000`22f76f40 fffff802`ac055be8 : 00000000`00000000 00000000`00000000 fffff801`63a1dcc0 ffffd000`22f77120 : nt!KiSwapThread+0xe9
ffffd000`22f76ff0 fffff802`ac057e35 : ffffe000`5f6ba180 00000000`00000000 ffffe000`6e828180 ffffd000`22f77120 : nt!KiCommitThreadWait+0x148
ffffd000`22f77080 fffff801`63a1e2a4 : ffffe000`6b565390 00000000`00000000 00000000`00000100 00000001`5f060000 : nt!KeWaitForSingleObject+0x385
ffffd000`22f77130 fffff801`63a8e3bb : ffffe000`6e828180 00000000`00000000 ffffe000`6e206b48 00000000`00000000 : NTFS!NtfsWaitOnIo+0x28
ffffd000`22f77170 fffff801`63a8d5ec : 00000000`00000001 fffff801`631091c9 00000000`00000000 ffffe000`00000000 : NTFS!NtfsDefragFileInternal+0xd7f
ffffd000`22f77400 fffff801`63ac8ac8 : 00000000`00000000 ffffe000`60cd4d60 ffffc000`678cb180 ffffe000`5f6ba180 : NTFS!NtfsDefragFile+0x1d0
ffffd000`22f774a0 fffff801`63ac864c : ffffe000`6e206b48 ffffe000`6e828180 ffffe000`6e828180 00000000`00000000 : NTFS!NtfsUserFsRequest+0x208
ffffd000`22f77510 fffff801`631051c4 : ffffe000`64255c80 ffffd000`22f776d0 ffffe000`6e828180 ffffe000`6e828568 : NTFS!NtfsFsdFileSystemControl+0x11c
ffffd000`22f77620 fffff801`63132d55 : 00000000`00000000 ffffffff`ffffffff 00000000`00000001 00000000`00000000 : FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x2a4
ffffd000`22f776a0 fffff802`ac43f17d : 00000000`00000001 ffffd000`22f77a80 ffffe000`6e828180 ffffe000`00000001 : FLTMGR!FltpFsControl+0x115
ffffd000`22f77700 fffff802`ac4906da : 00000000`00000000 ffffe000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x71d
ffffd000`22f77920 fffff802`ac168263 : ffffc000`5a455c00 fffff802`ac43205d ffff5c97`ec94d63a ffffd000`22f77a80 : nt!NtFsControlFile+0x56
ffffd000`22f77990 00007ffa`542738da : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
000000f3`8c49e1f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`542738da
STACK_COMMAND: kb
THREAD_SHA1_HASH_MOD_FUNC: c1795f669407b6ed9f82145875353188f1fa5ef1
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 444d96c0cf48ae63cd24de7d4a4725150faa70a3
THREAD_SHA1_HASH_MOD: 09468324ee29f64ace0e570d6fb070fbd0f2cca7
FOLLOWUP_IP:
nt!KiFindReadyThread+5a
fffff802`ac0f0e0a 410fb649a5 movzx ecx,byte ptr [r9-5Bh]
FAULT_INSTR_CODE: 49b60f41
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!KiFindReadyThread+5a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 559f3c1a
IMAGE_VERSION: 10.0.10240.16384
BUCKET_ID_FUNC_OFFSET: 5a
FAILURE_BUCKET_ID: AV_nt!KiFindReadyThread
BUCKET_ID: AV_nt!KiFindReadyThread
PRIMARY_PROBLEM_CLASS: AV_nt!KiFindReadyThread
TARGET_TIME: 2017-11-28T16:37:20.000Z
OSBUILD: 10240
OSSERVICEPACK: 16384
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: 2015-07-10 05:29:30
BUILDDATESTAMP_STR: 150709-1700
BUILDLAB_STR: th1
BUILDOSVER_STR: 10.0.10240.16384.amd64fre.th1.150709-1700
ANALYSIS_SESSION_ELAPSED_TIME: abe
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:av_nt!kifindreadythread
FAILURE_ID_HASH: {341c56c9-f4c9-259d-2aa4-c94d6f156edb}
Followup: MachineOwner
---------
最後更新：2017-12-15 02:04:40
上一篇：
Microsoft Visual C++ 2015不能安裝
下一篇： 應用商城錯誤的卸載了怎麼辦
- win10 應用商店
- Windows10 上軟件經常無響應
- 從昨天開始用易升更新我的win10，都提示0xc1900107
- WIN10係統多次在使用中或者啟動時藍屏，錯誤代碼0x0000000A,0x000000EF,0x0000007A
- 攝像頭打不開
- windows10 應用商店出現問題，無法打開！提示嚐試重新安裝解決問題！求助！
- WSUS同步到了過期的更新
- 沒有更新之前好好的，更新之後出現unauthorized wireless network card is plugged
- windows 7 旗艦版sp1 64位，通過MediaCreationTool工具升級出現 0xC1900101
- windows10裏的microsoft store無法打開
相關內容
- 你的設備已過期，並缺少重要的安全和質量更新，因此存在風險。讓我們帶你重回正軌，這樣
- 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 防病毒已關閉的問題