求助！windows 7 x86 运行一些小程序时蓝屏！

Posted 2023-02-14

蓝屏现象一般发生在偶然之中，比如浏览IE，清空回收站，玩网易泡泡游戏的斗地主等等；但在运行大型3D游戏时从未发生过蓝屏，乃至多线运行很费硬件的操作也是如此。还有需要说明的是超频前后都有蓝屏现象的发生。在此，希望能有高手给予解答，万分感激！！

操作系统: Windows 7 旗舰版 ( 32位 / DirectX 11 )

硬件
处理器: 英特尔 酷睿2 双核 E7400 @ oc 3.3GHz
主板: 微星 P43 Neo-F (MS-7519)
芯片组: 英特尔 4 Series Chipset
内存: 2 GB ( 威刚 DDR2 800MHz )
主硬盘: 500G (日立)+40G(旧硬盘，牌子忘了)
显卡: Nvidia GeForce GTX 260 ( 896 MB / 耕升 )
声卡: 瑞昱 ALC888 @ 英特尔 ICH10 高保真音频
网卡: 瑞昱 RTL8168C(P)/8111C(P) PCI-E Gigabit Ethernet NIC / 微星

蓝屏代码*** STOP:0X0000007F(0X00000008,0X807CF7500,0X00000000,0X00000000)
首先感谢“a12a21a12”及“力王历史”的回答。
对于“a12a21a12”给出的解答我也考虑过，但是内存如果跟主板不兼容，在运行大型3D类比较占系统资源的情况下首先体现出来不稳定性，但我这里从来没有发生过类似于蓝屏或花屏等事件，还有超频前后都有蓝屏发生，而且蓝屏发生的偶然性、不可测性着实让人头疼，基本上很久才发生一次；
而对于“力王历史”所给出的解答，首先恕我自大的认为我的系统很安全，至于播放器，因为用腻了暴风等播放器软件，所以用的是win7自带的wmp12+视频解码器；聊天的只有官方下载的qq；浏览器是IE8。最后我想说可能是因为您时间的关系，所以没有细看我描述的关于蓝屏的相关信息而把电脑中预先保存的“完美答案”复制于此，对于您所说的“原创”我深信不疑。

最后，我还是希望能有高手从dump文件信息中给出蓝屏的原因！再次表示感谢！！

非常感谢“cnhhwwj”的回答。但是我另有一笔记本，使用过程中从未发生过蓝屏。其系统和我台式机用的是一个安装包，只是台式机使用的是软件破解，笔记本是刷的bios成预装系统，不知道跟这个有没有关系。还有就是不知道跟双硬盘有没有关系，系统在新硬盘里，旧硬盘用来下载东西。蓝屏好像多发生在下载时。

以下是dump文件显示的信息

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

Loading Dump File [C:\Windows\Minidump\032610-24991-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 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x84009000 PsLoadedModuleList = 0x84151810
Debug session time: Fri Mar 26 14:48:46.393 2010 (GMT+8)
System Uptime: 0 days 4:25:53.079
*********************************************************************
* 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
.........
Unable to load image nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007F, 8, 807cf750, 0, 0

*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.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 : nvlddmkm.sys ( nvlddmkm+19753c )

Followup: MachineOwner
--------- 参考技术A 朋友，这是你下载的“软件”和电脑中的“内存”有冲突了，（答案原创，严禁其他网友复制）
我给你6种方法调试,快试试吧：
1.下载个“360急救箱”，原名：“360顽固木马专杀”，急救系统！
2.电脑里有木马或病毒干扰，下载“360安全卫士”和“360杀毒双引擎版”，建议“全盘扫描”病毒和木马，修补电脑上的漏洞！
3.你下载的“播放器”，或“聊天软件”，或“IE浏览器”的程序不稳定，或者“版本太旧”！建议卸掉，下载新的，或将其升级为“最新版本”。
4.就是你安装了两款或两款以上的同类软件（如：两款播放器，两款qq，或多款浏览器，多款杀毒软件等等）！它们在一起不“兼容”，卸掉“多余”的那一款！
5.你在电脑左下角“开始”菜单里找到“强力卸载电脑上的软件”，找到多余的那款卸掉！ 卸完了再“强力清扫”（看准了再卸，别把有用的卸了）。
6.实在不行就“还原系统”或“重装系统”！ 参考技术B 我也是用的WIN7旗舰版，这种现象也是经常发生，360扫描、打补丁、安装程序之类的都会蓝屏，后来我就尽量避免这些的动作，我查过很长时间了，最后我认为是这么个原因：windows7的安全性太高，致使系统在内存读写发出命令无法返回的时候蓝屏，具体原因我也不懂。反正就是系统与内存不怎么兼容，你也不用换内存，好像现在的内存基本都达不到windows7的标准，过段时间再出新内存的时候再换吧 参考技术C http://shower-thunder.spaces.live.com/blog/cns!250DE47BD119587C!131.entry?sa=855462087

按照这上面方法做 参考技术D 内存.换一条内存试一下.
再不行就有可能是主板问题了..
(前提是不超频..) 第5个回答  2019-07-11 以下是dump文件显示的信息
Microsoft
(R)
Windows
Debugger
Version
6.11.0001.402
X86
Copyright
(c)
Microsoft
Corporation.
All
rights
reserved.
Loading
Dump
File
[C:\Windows\Minidump\032610-24991-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
7600
MP
(2
procs)
Free
x86
compatible
Product:
WinNt,
suite:
TerminalServer
SingleUserTS
Machine
Name:
Kernel
base
=
0x84009000
PsLoadedModuleList
=
0x84151810
Debug
session
time:
Fri
Mar
26
14:48:46.393
2010
(GMT+8)
System
Uptime:
0
days
4:25:53.079
*********************************************************************
*
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
.........
Unable
to
load
image
nvlddmkm.sys,
Win32
error
0n2
***
WARNING:
Unable
to
verify
timestamp
for
nvlddmkm.sys
***
ERROR:
Module
load
completed
but
symbols
could
not
be
loaded
for
nvlddmkm.sys
*******************************************************************************
*
*
*
Bugcheck
Analysis
*
*
*
*******************************************************************************
Use
!analyze
-v
to
get
detailed
debugging
information.
BugCheck
1000007F,
8,
807cf750,
0,
0
***
WARNING:
Unable
to
verify
timestamp
for
dxgkrnl.sys
***
ERROR:
Module
load
completed
but
symbols
could
not
be
loaded
for
dxgkrnl.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
:
nvlddmkm.sys
(
nvlddmkm+19753c
)
Followup:
MachineOwner
---------