鬼子进村
新手上路
积分 10
发帖 10
注册 2009-8-27
|
#1 开机蓝屏？帮忙看下 谢谢！
百度上搜索mp110010.sys 有提到微点 不知道是不是 这么解决？？？
昨天的报告10/06
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini100610-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 XP Kernel Version 2600 (Service Pack 3) MP (2 procs)
Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d8000 PsLoadedModuleList = 0x8055e720
Debug session time: Wed Oct 6 19:05:54.906 2010 (GMT+8)
System Uptime: 0 days 0:00:39.640
*************************************************************
********
* 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 Ntfs.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Ntfs.SYS
*** ERROR: Module load completed but symbols could not be
loaded for Ntfs.SYS
*************************************************************
******************
*
*
* Bugcheck Analysis
*
*
*
*************************************************************
******************
Use !analyze -v to get detailed debugging information.
BugCheck 10000050, {b656003a, 1, 8054c96b, 0}
*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be
loaded for mssmbios.sys
***** Kernel symbols are WRONG. Please fix symbols to do
analysis.
*** WARNING: Unable to verify timestamp for mp110010.sys
*** ERROR: Module load completed but symbols could not be
loaded for mp110010.sys
*** WARNING: Unable to verify timestamp for diskpt.sys
*** ERROR: Module load completed but symbols could not be
loaded for diskpt.sys
*** WARNING: Unable to verify timestamp for mp110011.sys
*** ERROR: Module load completed but symbols could not be
loaded for mp110011.sys
*** WARNING: Unable to verify timestamp for fltMgr.sys
*** ERROR: Module load completed but symbols could not be
loaded for fltMgr.sys
*** WARNING: Unable to verify timestamp for bdfsfltr.sys
*** ERROR: Module load completed but symbols could not be
loaded for bdfsfltr.sys
*** WARNING: Unable to verify timestamp for Hookport.sys
*** ERROR: Module load completed but symbols could not be
loaded for Hookport.sys
*************************************************************
************
***
***
***
***
*** 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 : mp110010.sys ( mp110010+1f09 )
Followup: MachineOwner
| |
※ ※ ※ 本文纯属【鬼子进村】个人意见，与【 微点交流论坛 】立场无关※ ※ ※
|
 |
|
2010-10-7 12:29 |
|
鬼子进村
新手上路
积分 10
发帖 10
注册 2009-8-27
|
#2
今天的报告10/07
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini100710-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 XP Kernel Version 2600 (Service Pack 3) MP (2 procs)
Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d8000 PsLoadedModuleList = 0x8055e720
Debug session time: Thu Oct 7 11:45:58.093 2010 (GMT+8)
System Uptime: 0 days 0:00:38.843
*************************************************************
********
* 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
.......
*************************************************************
******************
*
*
* Bugcheck Analysis
*
*
*
*************************************************************
******************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 8054c96b, b656132c, 0}
*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be
loaded for mssmbios.sys
***** Kernel symbols are WRONG. Please fix symbols to do
analysis.
*** WARNING: Unable to verify timestamp for fltMgr.sys
*** ERROR: Module load completed but symbols could not be
loaded for fltMgr.sys
*** WARNING: Unable to verify timestamp for bdfsfltr.sys
*** ERROR: Module load completed but symbols could not be
loaded for bdfsfltr.sys
*** WARNING: Unable to verify timestamp for Hookport.sys
*** ERROR: Module load completed but symbols could not be
loaded for Hookport.sys
*************************************************************
************
***
***
***
***
*** 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 : bdfsfltr.sys ( bdfsfltr+98da )
Followup: MachineOwner
| |
※ ※ ※ 本文纯属【鬼子进村】个人意见，与【 微点交流论坛 】立场无关※ ※ ※
|
|
|
|
2010-10-7 12:30 |
|
Legend
超级版主
超级版主
积分 77171
发帖 70170
注册 2005-10-29
|
#3
感谢楼主的反馈，请问楼主机器中安装是什么操作系统？系统中还有其他安全产品吗？微点主动防御的版本是多少（微点主界面--辅助功能--关于）
请楼主到C盘windows中搜索看下是否有蓝屏文件（minidump或者memory）
如果有，请楼主联系微点在线管理员qq：383154254或466248167 在线传输一下。
| |
※文章所有权归【Legend】与【东方微点论坛】共同所有，转载请注明出处！※
|
微点官方认证新浪微博：欢迎进入 微点新浪微博
微点技术支持邮箱: support@micropoint.com.cn
给Legend发短消息 |
|
|
|
2010-10-7 12:33 |
|
鬼子进村
新手上路
积分 10
发帖 10
注册 2009-8-27
|
#4
操作系统：windows xp sp3
其他安全产品：360
微点主动防御软件 家庭版
程序版本： 1.2.10581.0296
特征版本： 1.6.1641.101006
更新时间： 2010-10-06 16:55:58
蓝屏文件（minidump）有
开机要么蓝屏要么死机多次了 重启就没事？？
玩着还会突然死机
都是这两天才有 之前都没碰到过
| |
※ ※ ※ 本文纯属【鬼子进村】个人意见，与【 微点交流论坛 】立场无关※ ※ ※
|
|
|
|
2010-10-7 12:48 |
|
Legend
超级版主
超级版主
积分 77171
发帖 70170
注册 2005-10-29
|
#5
楼主提供的文件我们已经分析 未发现异常 如果楼主方便，请您进行以下设置：
具体设置如下：
设置成功的要求：
1.虚拟内存的保存空间要设置在系统盘
2.虚拟内存的空间大小要大于物理内存
1) 设置生产蓝屏文件：我的电脑-〉右键属性-〉高级-〉启动和故障恢复-〉将\"写入调试信息\"改为“核心内存转储”，并勾掉\"系统失败\"中的“自动重新启动”。
2) 在出现蓝屏时请等待蓝屏文件写入100%完成后重启，将c:\windows\MEMORY.DMP压缩发给我们。
3)需要发送时，请您通过论坛短消息联系我们索要具体的发送方式。或者直接联系微点技术交流QQ群的管理员(383154254、466248167)在线传输，请您在联系管理员时附上本帖链接。（如果楼主对以上设置不是很清楚 您可以按照上面的方式联系微点在线管理员 由他们协助您进行具体的设置即可）
| |
※文章所有权归【Legend】与【东方微点论坛】共同所有，转载请注明出处！※
|
微点官方认证新浪微博：欢迎进入 微点新浪微博
微点技术支持邮箱: support@micropoint.com.cn
给Legend发短消息 |
|
|
|
2010-10-8 16:25 |
|
Legend
超级版主
超级版主
积分 77171
发帖 70170
注册 2005-10-29
|
#6
对于楼主反馈的问题我们已经进行处理，请楼主升级到微点最新版本后测试，看看是否还有此问题发生。
本主题关闭，如楼主反馈的问题在升级到微点最新版本后没有解决或还有其他关于微点的问题需要我们协助，请您另开新帖继续讨论，感谢您对微点软件的支持。
| |
※文章所有权归【Legend】与【东方微点论坛】共同所有，转载请注明出处！※
|
微点官方认证新浪微博：欢迎进入 微点新浪微博
微点技术支持邮箱: support@micropoint.com.cn
给Legend发短消息 |
|
|
|
2010-10-12 11:57 |
|
