求助!windows 7 x86 运行一些小程序时蓝屏!
发布网友
发布时间：2022-04-26 01:54
共6个回答
热心网友
时间：2022-04-12 11:59
Microsoft (R) Windows Debugger Version 6.11.0001.402 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minimp\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: Mole load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Proct: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x84009000 PsLoadedMoleList = 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: Mole load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
......................................
Loading User Symbols
Loading unloaded mole list
.........
Unable to load image nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Mole 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: Mole 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
---------
热心网友
时间：2022-04-12 13:17
我给你6种方法调试,快试试吧：
1.下载个“360急救箱”，原名：“360顽固木马专杀”，急救系统！
2.电脑里有木马或病毒干扰，下载“360安全卫士”和“360杀毒双引擎版”，建议“全盘扫描”病毒和木马，修补电脑上的漏洞！
3.你下载的“播放器”，或“聊天软件”，或“IE浏览器”的程序不稳定，或者“版本太旧”！建议卸掉，下载新的，或将其升级为“最新版本”。
4.就是你安装了两款或两款以上的同类软件（如：两款播放器，两款qq，或多款浏览器，多款杀毒软件等等）！它们在一起不“兼容”，卸掉“多余”的那一款！
5.你在电脑左下角“开始”菜单里找到“强力卸载电脑上的软件”，找到多余的那款卸掉！ 卸完了再“强力清扫”（看准了再卸，别把有用的卸了）。
6.实在不行就“还原系统”或“重装系统”！
热心网友
时间：2022-04-12 14:52
热心网友
时间：2022-04-12 16:43
按照这上面方法做
热心网友
时间：2022-04-12 18:51
再不行就有可能是主板问题了..
(前提是不超频..)
热心网友
时间：2022-04-12 21:16
Microsoft
(R)
Windows
Debugger
Version
6.11.0001.402
X86
Copyright
(c)
Microsoft
Corporation.
All
rights
reserved.
Loading
Dump
File
[C:\Windows\Minimp\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:
Mole
load
completed
but
symbols
could
not
be
loaded
for
ntoskrnl.exe
Windows
7
Kernel
Version
7600
MP
(2
procs)
Free
x86
compatible
Proct:
WinNt,
suite:
TerminalServer
SingleUserTS
Machine
Name:
Kernel
base
=
0x84009000
PsLoadedMoleList
=
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:
Mole
load
completed
but
symbols
could
not
be
loaded
for
ntoskrnl.exe
Loading
Kernel
Symbols
...............................................................
................................................................
......................................
Loading
User
Symbols
Loading
unloaded
mole
list
.........
Unable
to
load
image
nvlddmkm.sys,
Win32
error
0n2
***
WARNING:
Unable
to
verify
timestamp
for
nvlddmkm.sys
***
ERROR:
Mole
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:
Mole
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
---------
