系统重装后总是重启解决

Posted 2020-07-06 行尸走肉

最近给恺鹏装了个系统，笔记本型号是 联想 Y430P， win8.1 专业版。

系统做好之后总是蓝屏重启。

报错是

 CRITICAL_STRUCTURE_CORRUPTION

 

这个错误其实并没有什么卵用，因为你并不能知道到底发生了什么问题。

这里如果你的计算机设置了打印蓝屏日志的话（默认情况下都是），可以用windbug软件查看。

http://pan.baidu.com/s/1c2x4qMs

到我的网盘里可以直接下载，用法的话自己百度吧。我说一下打开后有一个 open crash dmp ，然后选择蓝屏的日志文件，C:\Windows\Minidmp一般在这个文件夹下。

如果找不到，自行百度。。。

下面是我的一个蓝屏日志打开后的信息，ERROR: FindPlugIns 8007007b 这一条是关键的信息。

你多多查看几个蓝屏文件，看看错误信息是不是同一个错误导致的。

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\Admin\Desktop\Minidump\040416-4828-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 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 9600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff801`38e0a000 PsLoadedModuleList = 0xfffff801`390e3250
Debug session time: Mon Apr 4 22:15:12.692 2016 (GMT+8)
System Uptime: 0 days 1:10:56.686
*********************************************************************
* 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 109, {a3a01f59d72bb8ee, b3b72be029aaf07d, ffffe0013e3ff550, 1c}

***** 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 : ntoskrnl.exe ( nt+1509a0 )

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

 

http://pan.baidu.com/s/1pKZ1rwZ

这里一个文件是修复ntoskrnl.exe这个程序错误的文件，是国外的人弄的，我并没有试过，如果有人用感觉有用的话记得跟我说一下。

 

 

接着说恺鹏的电脑，看了好多dmp文件，我发现导致错误的都是这个插件导致的，那么我排除硬件问题。

由于是用驱动人生一键更新的驱动，所以考虑是驱动不兼容导致的。

把所有安装好的驱动卸载，到官网上下载重新安装。还是有问题。

后来发现官网上并没有给出键盘、鼠标、蓝牙声卡、这三个驱动，果断删除。

因为蓝屏并不是有规律的，所以没法考察有没有解决这个问题，看日志文件发现有一个内核的代码的全局变量无法正常加载，

所以用介质修复了一下。

方法：win+c->设置->电源->按住shift，同时点击重启。在高级选项中选择修复，然后插入介质，我用的是u盘，具体过程没有截图，但是挺简单的，之后系统重启

问题解决。

总结一下：重装系统后，到官网下载驱动。

          　　如果已经用驱动精灵安装了驱动，全部卸载，再到官网重新下载安装。

　　　　　　这样，一般情况下就解决了问题。

显卡的卸载安装要按照这个顺序：

右击计算机选择管理，打开后左侧有个设备管理器，点开里面的显示适配器，先右击NV开头的独立显卡驱动-卸载-删除设备驱动程序-确定，再右击Intel显卡驱动-卸载-删除设备驱动程序-确定，之后重启。

您好，卸载完两个显卡驱动后需要先重启电脑，然后先安装intel集成显卡驱动http://driverdl.lenovo.com.cn/lenovo/DriverFilesUploadFloder/40890/Y430p_IntelVGA_Win8.1_1.exe，再安装Nvidia独立显卡驱动http://driverdl.lenovo.com.cn/lenovo/DriverFilesUploadFloder/40891/Y430p_NV_VGA_Win8.1_1.exe，装完后重启电脑就安装完成了。
之后在按住windows（键盘左下角四个方块的按键）+X键→选择“命令提示符（管理员）”→在弹出的命令提示符窗口中输入sfc /scannow自动检测并修复系统文件后使用看是否正常。