想请问下大神这个蓝屏是怎么原因

于 2023-08-22 10:13:32 发布
阅读量166 收藏
点赞数
文章标签： windows
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/V0o54bra/article/details/132422173
版权

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


Loading Dump File [C:\Windows\Minidump\082123-9890-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path.           *
* Use .symfix to have the debugger choose a symbol path.                   *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
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 22621 MP (20 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 22621.1928.amd64fre.ni_release_svc_prod3.230622-0951
Machine Name:
Kernel base = 0xfffff807`1a400000 PsLoadedModuleList = 0xfffff807`1b0130e0
Debug session time: Mon Aug 21 19:53:44.121 2023 (UTC + 8:00)
System Uptime: 0 days 6:37:09.781
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
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 101, {a, 0, ffff910009dbe180, e}

***** 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                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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

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

16: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 000000000000000a, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffff910009dbe180, The PRCB address of the hung processor.
Arg4: 000000000000000e, 0.

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                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: fffff8071a400000 nt

DEBUG_FLR_IMAGE_TIMESTAMP:  69a46399

BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_14_PROC

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  0

STACK_TEXT:  
ffff9100`09f4ba28 fffff807`1a885c38 : 00000000`00000101 00000000`0000000a 00000000`00000000 ffff9100`09dbe180 : nt+0x431250
ffff9100`09f4ba30 00000000`00000101 : 00000000`0000000a 00000000`00000000 ffff9100`09dbe180 00000000`0000000e : nt+0x485c38
ffff9100`09f4ba38 00000000`0000000a : 00000000`00000000 ffff9100`09dbe180 00000000`0000000e 00000000`000fffff : 0x101
ffff9100`09f4ba40 00000000`00000000 : ffff9100`09dbe180 00000000`0000000e 00000000`000fffff 00000000`00000000 : 0xa


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  ntoskrnl.exe

BUCKET_ID:  WRONG_SYMBOLS

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

V0o54bra
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
Win10 1903过TP的双机调试
被遗弃的庸才博客
11-16 4688
了解内核知识已经有一段时间了，想双机调试一下XP，网上也找了不少资料。https://bbs.pediy.com/thread-248912.htm https://blog.csdn.net/kingswb/article/details/51194105差不多我用到的大部分代码都是从上面cv（Ctrl+c---->Ctrl+v）下来的1、首先解决The context is parti...
解决Windows系统崩溃Linux系统却没有任何问题的错误
weixin_34403693的博客
11-07 472
背景： 朋友有一台联想的Z460，系统为Windows 7 Home Basic正版系统（SP1），最近经常死机，用电脑出厂时自带的系统还原工具还原重装了多次都是相同的结果--死机依然。由于朋友不是很懂这方面，所以就交给了我处理。 信息收集： 操作系统名称 Microsoft Windows 7 家庭普通版 版本 6.1.7600 版本 7...
电脑蓝屏 求各位大佬帮助分析一下原因
m0_64931011的博客
11-13 2779
装了一块新硬盘 和罗技的驱动就开始蓝屏了 打游戏打一半就蓝屏 求求各位大佬帮帮孩子吧
一个蓝屏的分析-The caller is unlocking a pageable section that is not currently locked.
T76230169的专栏
04-06 1147
同事，给了一个蓝屏文件，说是不知道操作什么了引起了系统蓝屏，使用自定义分析可看到 MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: Arg1: 0000000000001010, The caller is unlocking a pageable section that is not currently locked. (This sectio
PCB文件 有哪位大神能打开这个文件么
最新发布
06-07
PCB文件 路由器
请问有哪位大神能破解这个DLL？
06-11
请问有哪位大神能破解这个DLL？
大神是如何总结这一月的？——ppt设计师创意类月度总结模板.zip
09-10
这种总结方式有助于提高工作效率，识别工作中的问题，并为下个月制定更好的计划。 这个模板的设计思路融合了日常办公元素，如铅笔、记事本、纸张和咖啡，这些象征着创意与专注的工作氛围。通过这样的视觉呈现，设计...
俄罗斯大神系统集合
03-12
2、因为大神的系统镜像是做成种子发布的，而且是国外的，有些种子使用的人少，下载没速度也正常，这种情况下请使用下载人数多的，或者请别人分享已下载好的 3、因为大神是在俄文网站上发布的，而且非注册会员是下载...
玩不转JTAG接口，就别想炼就为嵌入式开发大神？
01-19
一般支持的CPU内都包含了这两个模块。　一个含有 Debug接口模块的CPU，只要时钟正常，就可以通过JTAG接口访问CPU的内部寄存器和挂在CPU总线上的设备，如FLASH，RAM，SOC(比如4510B，44Box，AT91M系列)内置模块的...
lapack_win32.dll
03-04
IT++安装文件lapack_win32.dll
Windows Server 2008 R2 ntoskrnl.exe 引起蓝屏故障，重新启动
weixin_30681615的博客
05-24 1745
前不久在HP ProLiant DL360 G6的服务器上面安装了Windows Server 2008 R2，系统一到晚上凌晨就出现蓝屏、重启现象，并且在 C:\Windows\Minidump 目录下面产生一些Dump文件，如下图所示： 后面我用微软的Windbg程序查看了一下系统产生的Dump文件内容，分析一下文件日志，发现内容如下： Microsoft (R) Win...
Windbg内核调试之五: 一次利用Dump文件调试Deadlock的实战
wowolook的专栏
06-08 5743
http://www.cnblogs.com/Sonic2007/archive/2010/09/01/1541988.html 最近遇到项目的一个bug，安装产品之后系统hang住。大致的现象是系统logon之后，Taskbar显示，然后hang住，Ctrl+Alt+Del不能调出TaskManager，Mouse不能移动，硬盘LED不闪烁。由于机器不在手边，远程调试又极其慢(实际
服务器蓝屏
qq_42504125的博客
05-15 842
关于windows sever2012 R2电脑蓝屏 Microsoft ® Windows Debugger Version 6.12.0002.633 X86 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Administrator\Desktop\051519-21765...
请大神们帮忙分析一下蓝屏
weixin_42172349的博客
03-03 570
WARNING Unable to verify timestamp for Unknown_Module_00000000`00000000 ERROR Module load completed but symbols could not be loaded for Unknown_Module_00000000`00000000
中国移动网站控件引发的蓝屏问题分析
weixin_30546189的博客
02-26 648
本周四（2月23日），我接到了我们同事的一个奇怪的蓝屏case，据他回忆，他最近没有安装任何软件和驱动，也没有更改计算机的硬件配置，除了Windows后台进行的自动更新之外，他实在想不起来到底对计算机有什么额外的改变。可是突然，就从前一天23日周三晚上起，他的计算机就开始蓝屏，重启之后，进系统之前就会蓝屏，或者进了系统用不到一会儿也会蓝屏。因此，他怀疑是硬件（如内存）故障导致的，或者是 Windo...
Windows Vista蓝屏代码含义和解决方案
网络 人生 学习 进步
06-04 1690
　　1、0x0000000A:IRQL_NOT_LESS_OR_EQUAL　　错误分析:主要是由问题的驱动程序、有缺陷或不兼容的硬件与软件造成的. 从技术角度讲. 表明在内核模式中存在以太高的进程内部请求级别(IRQL)访问其没有权限访问的内存地址.◇解决方案:请用前面介绍的解决方案中的2、3、5、8、9方案尝试排除.　　2、0x00000012:TRAP_CAUSE_UNKNOWN　
安装VMWare Player后立即显示具有INTERNAL_POWER_ERROR的Vista 64位蓝屏
cunfuxiao7305的博客
10-03 1508
I hope this helps someone because it totally freaked me out this evening. I rebooted this evening, the first reboot since March, in fact, and blue-screened (BSOD) upon startup. At this point I was in ...
java 设计一个geometricobject类,求java大神解决这个题啊、、、、
06-13
好的，我可以帮你解决这个问题。 首先，我们需要定义一个GeometricObject类，它应该包含以下属性： - color：表示几何对象的颜色 - filled：表示几何对象是否被填充 - dateCreated：表示几何对象的创建日期 接下来，我们需要为这些属性定义相应的getter和setter方法。同时，我们还需要定义一个toString方法，用于返回该对象的字符串表示形式。 最后，我们需要定义两个抽象方法，分别为getArea和getPerimeter，用于计算几何对象的面积和周长。 下面是GeometricObject类的代码示例： ```java public abstract class GeometricObject { private String color; private boolean filled; private Date dateCreated; public GeometricObject() { dateCreated = new Date(); } public GeometricObject(String color, boolean filled) { this.color = color; this.filled = filled; dateCreated = new Date(); } public String getColor() { return color; } public void setColor(String color) { this.color = color; } public boolean isFilled() { return filled; } public void setFilled(boolean filled) { this.filled = filled; } public Date getDateCreated() { return dateCreated; } public abstract double getArea(); public abstract double getPerimeter(); @Override public String toString() { return "created on " + dateCreated + "\ncolor: " + color + " and filled: " + filled; } } ``` 请注意，这里我们使用了Java中的抽象类和抽象方法。由于我们无法计算一个通用的几何对象的面积和周长，所以我们需要将这两个方法定义为抽象方法，具体的实现则由子类来完成。 你可以在子类中扩展GeometricObject类，以创建具体的几何对象，例如圆形、矩形等等。

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值