蓝屏报表提示0X00000109用WIN7的自带的内存分析软件检查没有问题,!!!系
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\Symbols*https://msdl.microsoft.com/download/symbols
Executable search path is:
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.23807.amd64fre.win7sp1_ldr.170512-0600
Machine Name:
Kernel base = 0xfffff800`04013000 PsLoadedModuleList = 0xfffff800`04255750
Debug session time: Tue Jul 4 19:11:27.683 2017 (UTC + 8:00)
System Uptime: 0 days 0:24:56.464
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 109, {a3a039d89f1c26ea, 0, 8ce67e3e23e86e40, 101}
***** 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 ***
*** ***
*************************************************************************
Unable to open image file: C:\ProgramData\dbg\sym\ntoskrnl.exe\5915F59A5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\ProgramData\dbg\sym\ntoskrnl.exe\5915F59A5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\ProgramData\dbg\sym\ntoskrnl.exe\5915F59A5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\ProgramData\dbg\sym\ntoskrnl.exe\5915F59A5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\ProgramData\dbg\sym\ntoskrnl.exe\5915F59A5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\ProgramData\dbg\sym\ntoskrnl.exe\5915F59A5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\ProgramData\dbg\sym\ntoskrnl.exe\5915F59A5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\ProgramData\dbg\sym\ntoskrnl.exe\5915F59A5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\ProgramData\dbg\sym\ntoskrnl.exe\5915F59A5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\ProgramData\dbg\sym\ntoskrnl.exe\5915F59A5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\ProgramData\dbg\sym\ntoskrnl.exe\5915F59A5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\ProgramData\dbg\sym\ntoskrnl.exe\5915F59A5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\ProgramData\dbg\sym\ntoskrnl.exe\5915F59A5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\ProgramData\dbg\sym\ntoskrnl.exe\5915F59A5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\ProgramData\dbg\sym\ntoskrnl.exe\5915F59A5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\ProgramData\dbg\sym\ntoskrnl.exe\5915F59A5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\ProgramData\dbg\sym\ntoskrnl.exe\5915F59A5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\ProgramData\dbg\sym\ntoskrnl.exe\5915F59A5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\ProgramData\dbg\sym\ntoskrnl.exe\5915F59A5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
Probably caused by : ntoskrnl.exe ( nt+70e40 )
Followup: MachineOwner
---------
4: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
or data. See https://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
debugger that was not attached when the system was booted. Normal breakpoints,
"bp", can only be set if the debugger is attached at boot time. Hardware
breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a3a039d89f1c26ea, Reserved
Arg2: 0000000000000000, Reserved
Arg3: 8ce67e3e23e86e40, Failure type dependent information
Arg4: 0000000000000101, Type of corrupted region, can be
0 : A generic data region
1 : Modification of a function or .pdata
2 : A processor IDT
3 : A processor GDT
4 : Type 1 process list corruption
5 : Type 2 process list corruption
6 : Debug routine modification
7 : Critical MSR modification
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 ***
*** ***
*************************************************************************
Unable to open image file: C:\ProgramData\dbg\sym\ntoskrnl.exe\5915F59A5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\ProgramData\dbg\sym\ntoskrnl.exe\5915F59A5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\ProgramData\dbg\sym\ntoskrnl.exe\5915F59A5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\ProgramData\dbg\sym\ntoskrnl.exe\5915F59A5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\ProgramData\dbg\sym\ntoskrnl.exe\5915F59A5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\ProgramData\dbg\sym\ntoskrnl.exe\5915F59A5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\ProgramData\dbg\sym\ntoskrnl.exe\5915F59A5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\ProgramData\dbg\sym\ntoskrnl.exe\5915F59A5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\ProgramData\dbg\sym\ntoskrnl.exe\5915F59A5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\ProgramData\dbg\sym\ntoskrnl.exe\5915F59A5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\ProgramData\dbg\sym\ntoskrnl.exe\5915F59A5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\ProgramData\dbg\sym\ntoskrnl.exe\5915F59A5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\ProgramData\dbg\sym\ntoskrnl.exe\5915F59A5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\ProgramData\dbg\sym\ntoskrnl.exe\5915F59A5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\ProgramData\dbg\sym\ntoskrnl.exe\5915F59A5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\ProgramData\dbg\sym\ntoskrnl.exe\5915F59A5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\ProgramData\dbg\sym\ntoskrnl.exe\5915F59A5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\ProgramData\dbg\sym\ntoskrnl.exe\5915F59A5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\ProgramData\dbg\sym\ntoskrnl.exe\5915F59A5e6000\ntoskrnl.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
*************************************************************************
*** ***
*** ***
*** 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.
MODULE_NAME: nt
FAULTING_MODULE: fffff80004013000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 5915f59a
BUGCHECK_STR: 0x109
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff80004083e40
STACK_TEXT:
fffff880`049e1498 00000000`00000000 : 00000000`00000109 a3a039d8`9f1c26ea 00000000`00000000 8ce67e3e`23e86e40 : nt+0x70e40
STACK_COMMAND: kb
FOLLOWUP_IP:
nt+70e40
fffff800`04083e40 48894c2408 mov qword ptr [rsp+8],rcx
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt+70e40
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: ntoskrnl.exe
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
最后更新:2017-07-04 20:02:34
上一篇:
win10 home版本开始菜单卡死
下一篇:
将这台电脑设为可以检测到
你的设备已过期,并缺少重要的安全和质量更新,因此存在风险。让我们带你重回正轨,这样
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 防病毒已关闭的问题