在卸载java 时 windows7 蓝屏 重启恢复正常 以后经常蓝屏 求解决方法

Posted 2023-03-21

java和系统蓝屏没有直接的联系。。。。，蓝屏一般与驱动程序有关，去找系统日志，然后看下错误代码追问

本人非专业怎样看错误代码 详细点 我重装了系统 就在重装刚结束又出现了一次 只要每次开机后都会有一次 蓝苹重起后恢复

追答

那就检查下你的硬件吧！还有把错误代码发上来

追问

0X0000001A（0X0000000000041790，0XFFFFFA80000A8570,0X000000000000FFF,0X0000000000000000)

追答

如果是台式机：检查下你的内存条和硬盘线（把内存条拔出来擦下金手指，检查下硬盘线是否插好）
把你的硬件信息贴出来，还有你安装的啥系统（官方原版WIN7还是ghost版的）

追问

与 itunes 有冲突 卸载了就好了

参考技术A 我和你的问题一模一样，安装一个程序然后需要升级JAva runtime， 于是卸载了之前的，然后安装了新的，然后就频繁蓝屏重启。我是Thinkpad E40，好像是Ghost系统 参考技术B 一楼不是等于没回答么？楼主这样问了，就说明他看不懂日志文了。 参考技术C 重装系统，一切ok。追问

我重装了 就在重装刚结束又出现了一次 只要每次开机后都会有一次 蓝苹重起后恢复

网络快捷键切换时，电脑直接蓝屏后重启。检测错误: 0x00000050

(0xfffff8e0047639bc, 0x0000000000000001, 0xfffff80004607fa2, 0x0000000000000005)。已将转储的数据保存在: C:\Windows\MEMORY.DMP。报告 ID: 052611-17768-01。” 我用windbg工具打开了 MEMORY.DMP文件 其中内容是 ：

(由于内容比较多 我因此放在回答中 ) 谢谢各位老师赐教哦
我的是dell N4010 468笔记本电脑问题来源于我由64位家庭普通版升级到64位旗舰版之后出现的哈 我想请的是懂WINDBG工具以及懂分析.DMP文件的老师 赐教哈 而不是从网上摘抄过来的哈

我用windbg工具打开了 MEMORY.DMP文件 其中内容是 ：

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

Loading Dump File [F:\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is 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+ *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Windows Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Kernel base = 0xfffff800`04a4d000 PsLoadedModuleList = 0xfffff800`04c92650
Debug session time: Fri May 27 20:17:42.027 2011 (GMT+8)
System Uptime: 0 days 2:14:32.635
*********************************************************************
* 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+ *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Loading Kernel Symbols
....................................................................................................................................................................
Loading User Symbols

Loading unloaded module list
...................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, 20, fffffa80019e8610, fffffa80019e8a50, 4440001

*** ERROR: Module load completed but symbols could not be loaded for btusbflt.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for bthport.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!PVOID ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 : btusbflt.sys ( btusbflt+2b17 )

Followup: MachineOwner
--------- 参考技术A 我们先从软件和硬件来了解电脑死机的原因：
硬件方面：
1.板卡接触不良或品质问题致设备运行不稳定
2.电脑散热不良致使CPU或显卡芯片温度过高而死机，其中有硬件设计缺陷，比如某些被召回的显卡或计算机部件

软件方面：
1用户遭到远程木马控制，电脑一切都在黑客的掌握之中。
2.病毒或恶意插件入侵，导致系统被破坏。
3.电脑安装的驱动不兼容，电脑运行一段时间就出现死机情况。
4.软件本身兼容性问题，软件不兼容严重冲突与系统冲突，出现电脑死机情况。

电脑死机解决办法
首先，下载金山毒霸2011并运行，选择全盘扫描清理电脑内木马病毒，再使用系统修改功能，修复被各种原因破坏的系统文件。如果您的电脑还出现蓝屏情况，我们需要分析dump文件之后，来确定原因，相信请点击浏览蓝屏后如何提取 dump 文件方法。采纳一下吧~~~~ 参考技术B 你好，电脑蓝屏，主要是：“内存有错误”或“软件不兼容”引起！

这是解决方法：（作者：力王历史）

1。试试开机，出完电脑品牌后，按F8，安全模式，光标选定：最后一次正确配置，

回车，回车，按下去！【关键一步】

2。再不行，进安全模式，回车，到桌面后，杀毒软件，全盘杀毒！

“隔离区”的东西，彻底删除！

3。再使用：360安全卫士，“功能大全”里的：“360系统急救箱”，

点：开始急救！重启后，点开“文件恢复区”，全选，彻底删除文件！

系统修复，全选，立即修复！【关键一步】

网络修复，开始修复，重启电脑！

360安全卫士，扫描插件，立即清理！360安全卫士，系统修复，一键修复！

【金山急救箱】，勾选：【扩展扫描】，立即扫描，立即处理，重启电脑！

4。再不行，拔下显卡和内存条，橡皮擦擦，再用毛刷，清理插槽灰尘和风扇，

更换内存插槽等！【台式机】

5。检查是否有同类功能的，多余类似软件，如：多款播放器，多款杀毒软件

等，卸载多余的，只留一款，因为同类软件，互不兼容！【关键一步】

6。再不行，下载“驱动人生”，升级：显卡驱动！

7。如果还是不行，需要“一键还原”或“重装系统”了！

8。硬件有问题，送修！