电脑蓝屏啊啊啊啊啊，一天三次，文档还好时时保存！！！
2024-05-25 02:43:27
某天下班电脑没关，第二天早上上班就发现我的电脑出现了蓝屏，小case好吧，直接重启。
重点!!!!一天给我蓝屏三次！！！不能忍！
第二天，下载了一个叫debugging tools的工具，就是下面这玩意：
完了以后安装，安装完以后在菜单处所有运行可以找到哈：
右键管理员运行。
运行后，点击file，文件路径如图，一般会有蓝屏系统日志都在这~打开最新的日志就可以查看了~~
文件日志如下，自己也不明白，如果还出现问题，就钻研一下，哪位大神也可以给看看:
Microsoft (R) Windows Debugger Version 6.10.0003.233 X86
Copyright (c) Microsoft Corporation. All rights reserved.Loading Dump File [C:\Windows\Minidump\021919-5366-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are availableSymbol 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 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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff800`0465a000 PsLoadedModuleList = 0xfffff800`0489e650
Debug session time: Tue Feb 19 15:16:33.454 2019 (GMT+8)
System Uptime: 0 days 1:42:09.594
*********************************************************************
* 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 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
......
ERROR: FindPlugIns 8007007b
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************Use !analyze -v to get detailed debugging information.BugCheck D1, {11000, 2, 0, fffff88001409dac}Unable to load image NETIO.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for NETIO.SYS
*** ERROR: Module load completed but symbols could not be loaded for NETIO.SYS
Unable to load image tcpip.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for tcpip.sys
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
***** 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 ***
*** ***
*************************************************************************
*********************************************************************
* 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+ *
*********************************************************************
*********************************************************************
* 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+ *
*********************************************************************
Probably caused by : NETIO.SYS ( NETIO+9dac )Followup: MachineOwner
---------所以问题相当于没解决！！再出现来更新!
电脑蓝屏啊啊啊啊啊，一天三次，文档还好时时保存！！！相关推荐
- 电脑开机一会就蓝屏怎么回事_常见的电脑蓝屏是怎么回事？学会三种解决方法，远离电脑维修店...
电脑蓝屏是我们常见的一种故障现象,它是系统无法从操作系统错误中恢复过来时表现的画面,有的是硬件问题引起,有的是软件问题引起,当我们遇到这种故障的时候,我们常常会通过关机重启的办法进行故障排除与解决,如 ...
- 我新买的计算机为什么是英语,新买的电脑蓝屏一直显示英文处理方法大全
电脑蓝屏,又叫蓝屏死机,是微软的 Windows 系列操作系统在无法从一个系统错误中恢复过来时,为保护电脑数据文件不被破坏而强制显示的屏幕图像,而最近有小伙伴反映新买的电脑蓝屏一直显示英文,遇到这种情 ...
- xp系统蓝屏代码7b_电脑蓝屏重启不求人！学会这个方法，自己就能轻松解决！...
在重装win10系统的过程中,我们需要多次等待电脑的重启,直到最后一次重启进入win10系统桌面,win10重装才算结束. 但如果在安装win10系统时,屏幕显示蓝屏,且无限重启,该怎么办呢? 下面马 ...
- 电脑蓝屏问题检查、解决、
蓝屏问题 1检查 在开始-->:运行中输入:EventVwr.msc ,回车出现"事件查看器",注意检查其中的"系统日志"和"应用程序日志&qu ...
- 揪出“凶手”——实战WinDbg分析电脑蓝屏原因
http://www.appinn.com/blue-screen-search-code/ 蓝屏代码查询器 – 找出蓝屏的元凶 11 文章标签: windows / 系统 / 蓝屏. 蓝屏代码查询器 ...
- Android——电脑蓝屏重启后，studio无法认出Android环境 setup JDK（缓存！缓存！缓存）...
电脑蓝屏重启后,studio无法认出Android环境 setup JDK 问题重现:因为工作问题,需要用到模拟器,然后创建了模拟器后开启了漫长的等待之旅,两三分钟之后win8蓝屏,重启,再次打开,依 ...
- 电脑蓝屏终止代码irql_电脑蓝屏代码浅析
你不一定要点蓝字关注我的 01 什么是蓝屏 蓝屏 BSOD 蓝屏,英文名BSOD,Blue Screen of Death,即蓝屏死机,微软操作系统的经典死机提示屏幕. 蓝屏其实是一种保护措施和一种调 ...
- vsc系统是什么意思_电脑蓝屏是什么意思？蓝屏就一定要重装系统吗？你可不要弄错了...
电脑的常见故障有电脑黑屏.电脑蓝屏.电脑死机.开机进BIOS.加载程序无响应等等,这些故障多数都是软件问题引起的,我们充其量做个系统就能解决!但是有些电脑故障现象并不一定就是系统坏了,比如电脑蓝屏,电 ...
- 计算机弹出错误字,电脑蓝屏，并且屏幕上出现这样的文字该怎么解决？
电脑蓝屏,并且屏幕上出现这样的文字该怎么解决? a problem has been detected and windows has been shut down to prevent damage ...
最新文章
- 报名 | 赢取20万美金！Call For Code编程马拉松北京站来袭！
- linux 查看硬件信息
- InnoDB存储引擎对MVCC的实现
- RabbitMQ消息的确认模式
- 写一个易于维护使用方便性能可靠的Hybrid框架（一）—— 思路构建
- mysql数据库用户的创建_mysql创建用户及数据库
- window.opener.location.reload() and href()的区别
- python中如何判断输入的是否是数字_python如何判断输入是不是数字
- 实际开发中的问题积累【积累】
- 新旧时代的更替——Turbo码/TCM码
- 软件工程课程设计小组人员分工
- 华为认证怎么考？华为认证考试费用是多少？
- HDU 5745 La Vie en rose（DP+bitset优化）
- 联想微型计算机B3O5,联想B3一体电脑
- 写口算用计算机作文600字,口算考试作文600字
- 【数字】求特定三位数
- 清晰理解precision(精确度)和recall(召回度)
- win7计算机睡眠后无法唤醒,win7系统待机后打不开怎么办|win7待机无法唤醒的解决方法...
- ubuntu14.10+QT4编写ARM9（mini2440）应用的配置与安装
- 张振民北京计算机专修学院,工行甘肃省分行张振民一行来校考察交流