帮忙看看这蓝屏代码是什么意思
帮忙看看这蓝屏代码是什么意思
这是我电脑蓝屏的代码
0xx804DD49F,0xF7B01E2C,0x
微软的答案:& 是机器翻译的.您可能会在基于 Windows 的计算机上收到一条错误消息：“STOP 0x”或“STOP 0x0000008e”察看本文应用于的产品文章编号 : 903251 最后修改 : 日 修订 : 4.0 本页症状注意原因解决方案症状在基于 Microsoft Windows Server 2003、Microsoft Windows XP 或 Microsoft Windows 2000 的计算机上，可能会遇到下列一种或多种症状： o 计算机自动重新启动。 o 登录后，您收到以下错误消息： Microsoft WindowsThe system has recovered from a serious error.A log of this error has been created.Please tell Microsoft about this problem.We have created an error report that you can send to help us improve Microsoft Windows.We will treat this report as confidential and anonymous.To see what data this error report contains, click here.要查看错误报告的内容，请单击“单击此处”。当您单击消息框底部的“单击此处”链接时，可能会看到类似下列数据样本之一的错误特征信息。数据样本 1BCCode : BCP1 :f8655000 BCP2 : BCP3 :fc7cc465& BCP4 : OSVer :5_1_2600 SP :0_0 Product :256_1数据样本 2BCCode :0000008e BCP1 :c0000005 BCP2 : BCP3 :fd28eaa4& BCP4 : OSVer :5_1_2600 SP :0_0 Product :256_1o 您会收到下列“Stop”错误消息之一。消息 1A problem has been detected and Windows has been shut down to prevent damage to your computer...Technical information:STOP:0xxfxxfc7cc465, 0x) PAGE_FAULT_IN_NONPAGED_AREA (50)消息 2A problem has been detected and Windows has been shut down to prevent damage to your computer...Technical information:STOP:0x0000008e (0xcxxfd28eaa4, 0x) KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e) o 系统事件日志中记录了类似如下的错误消息：日期:date来源:系统错误时间:time类别:(102) 类型:错误事件 ID:1003 用户:N/A计算机:COMPUTER描述:错误代码 、parameter1 f8655000、parameter2 、parameter3 fc7cc465、parameter4 。有关更多信息，请参阅在
的帮助和支持中心。数据: 73 74 65 6d 20 45 System E
6f 72 20 20 45 72 rror Er f 72 20 63 6f 64 65 ror code
30 30 30 30 30 35 0: 30 20 20 50 61 72 61 6d 0 Param
65 72 73 20 66 66 eters ff
66 66 64 31 2c日期:date来源:系统错误时间:time类别:(102) 类型:错误事件 ID:1003 用户:N/A计算机:COMPUTER描述:错误代码 0000008e、parameter1 c0000005、parameter2 、parameter3 fd28eaa4、parameter4 。有关更多信息，请参阅在
的帮助和支持中心。数据: 73 74 65 6d 20 45 System E
6f 72 20 20 45 72 rror Er f 72 20 63 6f 64 65 ror code
30 30 30 30 30 35 20:30 20 20 50 61 72 61 6d 0 Param
65 72 73 20 66 66 eters ff
66 66 64 31 2c回到顶端注意o “Stop”错误的症状因计算机的系统故障选项而异。 有关如何配置系统故障选项的更多信息，请单击下面的文章编号，以查看 Microsoft 知识库中相应的文章： 307973 ( ) 如何在 Windows 中配置系统故障和恢复选项o “Stop”错误消息的括号内的四个参数因计算机的配置而异。 回到顶端原因如果计算机感染了 HaxDoor 病毒的一个变种，就可能发生此问题。HaxDoor 病毒创建了一个隐藏进程。此外，该病毒还隐藏文件和注册表项。HaxDoor 病毒的可执行文件可能有多个名称，但通常是 Mszx23.exe。该病毒的很多变种会在计算机上安放一个名为 Vdmt16.sys 或 Vdnt32.sys 的驱动程序。该驱动程序用来隐藏病毒进程。如果删除这些文件，HaxDoor 病毒变种可以恢复它们。回到顶端解决方案重要说明：此部分、方法或任务包含有关如何修改注册表的步骤。但是，注册表修改不当可能会出现严重问题。因此，请一定严格按照下列步骤操作。为了获得进一步保护，请在修改注册表之前对其进行备份。这样就可以在出现问题时还原注册表。有关如何备份和还原注册表的更多信息，请单击下面的文章编号，以查看 Microsoft 知识库中相应的文章：322756 ( ) 如何在 Windows 中备份和还原注册表要解决此问题，请按照下列步骤操作：1. 打印下面的 Microsoft 知识库文章。参考该文章完成此过程。307654 ( ) 如何安装和使用 Windows XP 的恢复控制台2. 单击“开始”，单击“运行”，键入 regedit，然后单击“确定”。 3. 找到以下注册表子项：HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogin\Notify 4. 找到并删除注册表子项中任何引用“drct16”或“draw32”的项。例如，可能会看到类似如下的项： HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\Notify\drct16HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\Notify\draw32 5. 插入 Windows XP 安装 CD，然后从 CD 重新启动计算机。 6. 在“欢迎使用安装程序”屏幕上，按 R（修复）来启动 Windows 恢复控制台。 7. 选择与要修复的 Windows 安装对应的数字。该数字通常为 1。 8. 提示输入管理员密码时，请输入管理员密码。如果没有管理员密码，则按 Enter。 9. 在命令提示符处，移至 C:\Windows\System32 文件夹。例如，键入 cd C:\Windows\System32。 10. 使用 ren（重命名）命令将下列文件重命名为所示的名称。记住，每键入一个命令后都要按 Enter。如果出现“File not found”（找不到文件）消息，则移到列表中的下一个文件。ren 1.a3d 1.a3d.badren cm.dll cm.dll.badren cz.dll cz.dll.badren draw32.dll draw32.dll.badren drct16.dll drct16.dll.badren dt163.dt dt163.dt.badren fltr.a3d fltr.a3d.badren hm.sys hm.sys.badren hz.dll hz.dll.badren hz.sys hz.sys.badren i.a3d i.a3d.badren in.a3d in.a3d.badren klo5.sys klo5.sys.badren klogini.dll klogini.dll.badren memlow.sys memlow.sys.badren mszx23.exe mszx23.exe.badren p2.ini p2.ini.badren ps.a3d ps.a3d.badren redir.a3d redir.a3d.badren tnfl.a3d tnfl.a3d.badren vdmt16.sys vdmt16.sys.badren vdnt32.sys vdnt32.sys.badren w32tm.exe w32tm.exe.badren WD.SYS WD.SYS.badren winlow.sys winlow.sys.badren wmx.a3d wmx.a3d.badren wz.dll wz.dll.badren wz.sys wz.sys.bad要在完成后删除这些文件，请键入 del *.bad。 11. 取出 Windows XP 安装 CD，然后键入 Exit 以重新启动计算机。 12. 当计算机重新启动时，单击“开始”，单击“运行”，键入 regedit，然后单击“确定”。 13. 找到并删除下列注册表子项以及每个子项下可能存在的任何项。如果来自该列表的任何注册表子项都不存在，则移至列表中的下一个子项。HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\vdmt16HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\vdnt32HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\winlowHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\memlowHKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\vdmt16HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\vdnt32HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\winlowHKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\memlowHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ENUM\ROOT\LEGACY_VDMT16HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ENUM\ROOT\LEGACY_VDNT32HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ENUM\ROOT\LEGACY_WINLOWHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ENUM\ROOT\LEGACY_MEMLOW 14. 找到并删除下列注册表子项下包含 Mszx23.exe 文件名的任何项：HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\RunHKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\RunServicesHKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunHKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunServices 15. 退出注册表编辑器。 16. 确保已用最新的定义更新了防病毒和防间谍软件程序，然后执行一次完整的系统扫描。 下列恶意软件已被防病毒供应商识别。 Symantec： Backdoor.Haxdoor.D Trend Micro： BKDR_HAXDOOR.BC、BKDR_HAXDOOR.BN、BKDR_HAXDOOR.BA、BKDR_HAXDOOR.AL PandaLabs： HAXDOOR.AW F-Secure： Backdoor.Win32.Haxdoor、Backdoor.Win32.Haxdoor.al Sophos： Troj/Haxdoor-AF、Troj/Haxdoor-CN、Troj/Haxdoor-AE Kaspersky Lab： Backdoor.Win32.Haxdoor.bg McAfee： BackDoor-BAC
其他回答 (1)
应用程序发生异常 这一条在玩游戏时候经常出现.
相关知识等待您来回答
电脑常识领域专家蓝屏 哪位大侠给看看是怎么回事_百度知道
蓝屏 哪位大侠给看看是怎么回事
win32k;function that caused the problem.BugCheck 1000008E;image that contains this address!analyze -v to get detailed debugging information: Debugging Details., and thesystem is booted /:Arg1, Trap FrameArg4: (NTSTATUS) 0xc0000005 - 0x%08lxFAULTING_IP, 837ed898Bugcheck AnalysisUse .If this happens.: MachineOwnerBugcheck AnalysisKERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)This is a very common bugcheck, 8d478c2c, but .sys ( win32k.ANODEBUG, The address that the exception occurred atArg3:EXCEPTION_CODE.Some common problems are exception code 0x, make sure a debugger gets connected.
Usually the exception address pinpointsthe driver/, but this system was booted/: win32k;DEBUG, {c}Probably caused by .
Always note this addressas well as the link date of the driver/: 8d478c2c.
This means a hardcoded breakpoint or assertion was hit: c0000005.
This is not supposed to happen as developers should never havehardcoded breakpoints in retail code.
This will let us see why this breakpoint ishappening, The exception code that was not handledArg2: 837ed898!FindTimer+2c837ed898 394614
dword ptr [esi+14h]!FindTimer+2c )Followup
来自拓听网
//www。这个错误的可能原因较多.请参见、50这样的代码://www:KERNEL_MODE_EXCEPTION_NOT_HANDLED  .&/zhidao/wh%3D450%2C600/sign=62fd0d5e8ec0b8d3e57da/d6d55fb73caa20a4dd7d://b.com/zh-cn/search/R，如果在蓝屏故障提示中看到某应用软件或某硬件设备驱动程序的文件名.，一般遇到此错误时比较麻烦.com/zh-cn/search/Results:  ，但Windows错误处理器无法准确捕获错误类型.jpg" esrc="http.请点击我的回答下方【选为满意答案】按钮.hiphotos.主要如下可能.更多有关这个蓝屏的微软帮助和解决方法.蓝屏代码 Stop. ://b.不兼容的驱动程序5，问题一般与相应的应用软件或硬件设备有关.看看是否还会自检不过或蓝屏报错，那十有八九就是内存存在兼容性问题或彻底损坏了:.如果你认为我的解答对解决你的问题有帮助,看看有没有相应的记录.http:升级驱动程序或升级BIOS.硬件配置问题3.<img class="ikqb_img" src="0x0000008E. ◇解决方案;◆错误分析: 0x1000008E (等同于新式蓝屏表示代码 BCCode【◆】【哈搂】【◆】.hiphotos. .如果出现8E蓝屏重启之后还伴随着出现0A.蓝屏原因.;如果在蓝屏故障提示中没有显示引起错误的文件名: 造成这个蓝屏错误的原因较多.都不行就要弃用有问题的内存条或更换新的内存条、7E.microsoft?q=0x0000008e&错误名称 0x0000008E.建议关机.com/zhidao/wh%3D600%2C800/sign=0ade078e4836acaf59b59efa4ce9a128/d6d55fb73caa20a4dd7d.hiphotos.就交换位置插或只插单根内存条开机;故障分析 0x0000008E错误表示内核程序遇到了问题.com/zhidao/pic/item/d6d55fb73caa20a4dd7d.baidu.硬盘损坏2.baidu..aspx.还不行; ，看看有没有提到引起错误的具体是哪个文件.内存条不匹配或已损坏.然后把内存条插好开机;1：KERNEL_MODE_EXCEPTION_NOT_HANDLED  .baidu?q=0x0000008e ..jpg" />，建议检查一下完整的蓝屏故障提示:内核级应用程序产生了错误.操作系统内存在病毒6: 8e 或 1000008e).aspx
其他&1&条热心网友回答
XP系统吗？クイック アクセス
0x0000008E蓝屏
Microsoft (R) Windows Debugger& Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
Symbol search path is: F:\Windows\Symbols
Executable search path is:
Windows Vista Kernel Version 6002 (Service Pack 2) MP (4 procs) Free x86 compatible
Product: Server, suite: Enterprise TerminalServer SingleUserTS
Built by: .x86fre.lh_sp2rtm.0
Kernel base = 0x81c18000 PsLoadedModuleList = 0x81d2fc70
Debug session time: Sun Feb 13 02:48:04.675 2011 (GMT+8)
System Uptime: 0 days 3:53:09.086
WARNING: Unable to reset page directories
Loading Kernel Symbols
......................................Missing image name, possible paged-out or corrupt data.
.Unable to read KLDR_DATA_TABLE_ENTRY at
- NTSTATUS 0xC0000147
WARNING: .reload failed, module list may be incomplete
*******************************************************************************
*&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
*&&&&&&&&&&&&&&&&&&&&&&& Bugcheck Analysis&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
*&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 8E, {cc, a38a9c58, 0}
*** WARNING: Unable to verify timestamp for Unknown_Module_
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
Followup: MachineOwner
1: kd& !analyze -v
*******************************************************************************
*&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
*&&&&&&&&&&&&&&&&&&&&&&& Bugcheck Analysis&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
*&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED (8e)
This is a very common bugcheck.& Usually the exception address pinpoints
the driver/function that caused the problem.& Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x.& This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.& This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.& This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 0000012c, The address that the exception occurred at
Arg3: a38a9c58, Trap Frame
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - 0x%08lx
FAULTING_IP:
Unknown_Module_;12b
0000012c ??&&&&&&&&&&&&& ???
TRAP_FRAME:& a38a9c58 -- (.trap ffffffffa38a9c58)
Unable to read trap frame at a38a9c58
DEFAULT_BUCKET_ID:& VISTA_RC
BUGCHECK_STR:& 0x8E
CURRENT_IRQL:& 0
LAST_CONTROL_TRANSFER:& from
to 81ce5b0d
STACK_TEXT:&
a38a0 00 nt!KeBugCheckEx+0x1e
STACK_COMMAND:& .trap 0xffffffffa38a9c58 ; kb
SYMBOL_NAME:& ANALYSIS_INCONCLUSIVE
FOLLOWUP_NAME:& MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME:& Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP:& 0
BUCKET_ID:& ZEROED_STACK
Followup: MachineOwner
唉,有高手帮忙分析下么?用的是GT450的显卡,显卡驱动换了好多版本.硬盘是0阵列.
请您提供一份或几份MINIDUMP以供进一步的分析。此外，若蓝屏频发而对象不定，亦不妨关注硬件工作状态，典型如内存。对于内存，可执行内存诊断复查其可靠性。
回答の候補に設定
回答としてマーク
这回是内存管理错误，但不一定代表你的物理内存有毛病，故障原因可能与之前相同，还是主板芯片组驱动的问题。
Alexis Zhang
http://mvp./profile/jie
http://blogs.itecn.net/blogs/alexis
推荐以 NNTP Bridge 桥接新闻组方式访问论坛以获取最佳用户体验。
本帖是回复帖，原帖作者是楼上的 &abenlee123&
BugCheck 1A, {5003, c58f, }
Probably caused by : memory_corruption ( nt!MiAllocateWsle+7d )
回答の候補に設定
回答としてマーク
すべての返信
故障类型属于未知且无法确定引起故障的映像名称，可能是未知的硬件问题。
如果以前没有问题，是在最近修改过什么设置或添加删除过什么程序或设备驱动后出现的问题，请回忆一下引起故障前的最近操作或修改。
Alexis Zhang
http://mvp./profile/jie
http://blogs.itecn.net/blogs/alexis
推荐以 NNTP Bridge 桥接新闻组方式访问论坛以获取最佳用户体验。
本帖是回复帖，原帖作者是楼上的 &abenlee123&
Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.
电脑配置如下:
&CPU: AMD840T
内存: 12GB(4GB+4GB+2GB+2GB) DDR3宇瞻内存--我用MEMTEST跑过八个小时没发现问题;
硬盘: 希捷500GX2 0阵列;
显卡: 影驰GT450; 主板: 华硕M4A88TD-M
电源： Huntkey 350W;
windows2008的操作系统
以前出现过0x0000007E或8E蓝屏，发现是dxgkrnl.sys的问题，我就更新了显卡驱动.然后出现了上面的情况；现在WINDOWS下面的dmp文件有500多MB，一个正常的不可能这么大吧。
以前还出现过0x0000001---ndis.sys蓝屏； 以上是玩魔界二时蓝屏的，另外开的软件还有内存释放专家来释放内存，如果不释放，机子就太卡了，因为内存太小了。 到底是什么硬件问题呀。机子配回来一直这样。不是天天蓝，是开机一二天左右不定时的蓝。
Microsoft (R) Windows Debugger& Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
Symbol search path is: F:\Windows\Symbols
Executable search path is:
Windows Vista Kernel Version 6002 (Service Pack 2) MP (4 procs) Free x86 compatible
Product: Server, suite: Enterprise TerminalServer SingleUserTS
Built by: .x86fre.lh_sp2rtm.0
Kernel base = 0x81c0a000 PsLoadedModuleList = 0x81d21c70
Debug session time: Mon Feb 14 13:43:27.592 2011 (GMT+8)
System Uptime: 0 days 1:30:31.962
Loading Kernel Symbols
.....................................................................................................................................
Loading User Symbols
Loading unloaded module list
*******************************************************************************
*&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
*&&&&&&&&&&&&&&&&&&&&&&& Bugcheck Analysis&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
*&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {c, 8, c02030a8}
*** ERROR: Module load completed but symbols could not be loaded for ahcix86s.sys
*** ERROR: Module load completed but symbols could not be loaded for processr.sys
Probably caused by : ahcix86s.sys ( ahcix86s+21daa )
Followup: MachineOwner
3: kd& !analyze -v
*******************************************************************************
*&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
*&&&&&&&&&&&&&&&&&&&&&&& Bugcheck Analysis&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
*&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.& This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: c02030a8, memory referenced
Arg2: , IRQL
Arg3: , value 0 = read operation, 1 = write operation
Arg4: c02030a8, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS:& c02030a8
CURRENT_IRQL:& 9
FAULTING_IP:
+ffffffffc02030a8
c02030a8 ??&&&&&&&&&&&&& ???
DEFAULT_BUCKET_ID:& VISTA_RC
BUGCHECK_STR:& 0xD1
PROCESS_NAME:& System
TRAP_FRAME:& 91569b20 -- (.trap ffffffff91569b20)
eax=c02030a8 ebx= ecx=88ac28f4 edx=88c7bcc8 esi=88ac28ac edi=84c7be58
eip=c02030a8 esp=91569b94 ebp=91569bac iopl=0&&&&&&&& nv up ei ng nz na po nc
cs=0008& ss=0010& ds=0023& es=0023& fs=0030& gs=0000&&&&&&&&&&&& efl=
c02030a8 ??&&&&&&&&&&&&& ???
Resetting default scope
LAST_CONTROL_TRANSFER:& from c02030a8 to 81c57fb9
STACK_TEXT:&
030a8 badb0d00 88c7bcc8 91569b44 nt!KiTrap0E+0x2e1
WARNING: Frame IP not in any known module. Following frames may be wrong.
bd3daa 0c7be58 84c7be58 0xc02030a8
91569bac 90bd2f35 88acac 84c7be58 ahcix86s+0x21daa
9bd32b7 88ac25e4 ac2584 ahcix86s+0x20f35
bb84 88ac2c ahcix86s+0x212b7
14bab 88acc38
ahcix86s+0x3662
a28ac8 c50970 storport!RaCallMiniportInterrupt+0x1b
c00 88a28a10 89f1e020 storport!RaidpAdapterInterruptRoutine+0x26
c508e9 8aaa2 91569cf8 nt!KiChainedDispatch2ndLvl+0x44
a99d8 8aaa2 91569cf8 nt!KiChainedDispatch+0x29
9cbac94 ed78 processr+0x29d8
cb0 a3aa383 nt!PoIdle+0x2d1
0e 1a3aa383 01c85a60 nt!KiIdleLoop+0xd
STACK_COMMAND:& kb
FOLLOWUP_IP:
ahcix86s+21daa
90bd3daa 8b06&&&&&&&&&&& mov&&&& eax,dword ptr [esi]
SYMBOL_STACK_INDEX:& 2
SYMBOL_NAME:& ahcix86s+21daa
FOLLOWUP_NAME:& MachineOwner
MODULE_NAME: ahcix86s
IMAGE_NAME:& ahcix86s.sys
DEBUG_FLR_IMAGE_TIMESTAMP:& 4adf0eab
FAILURE_BUCKET_ID:& 0xD1_W_ahcix86s+21daa
BUCKET_ID:& 0xD1_W_ahcix86s+21daa
Followup: MachineOwner
今天又蓝了.代码如上,是什么原因呀,唉.
500MB 的是核心内存转储，在“启动与故障恢复”选项中修改为“小内存转储（64KB/128KB）”就可以减小了。
NDIS.SYS 驱动的问题可能与 ACPI 高级电源选项配置不当有关，或者是计算机部分硬件驱动程序有冲突。建议重新安装主板芯片组驱动以修复一下高级电源选项设置。
Alexis Zhang
http://mvp./profile/jie
http://blogs.itecn.net/blogs/alexis
推荐以 NNTP Bridge 桥接新闻组方式访问论坛以获取最佳用户体验。
本帖是回复帖，原帖作者是楼上的 &abenlee123&
现在WINDOWS下面的dmp文件有500多MB，一个正常的不可能这么大吧。
以前还出现过0x0000001---ndis.sys蓝屏； 以上是玩魔界二时蓝屏的，
最新的这次蓝屏是 ahcix86s.sys 驱动程序引起的，应该是主板芯片组提供的 AHCI 驱动。请重新安装一下主板芯片组驱动。
Alexis Zhang
http://mvp./profile/jie
http://blogs.itecn.net/blogs/alexis
推荐以 NNTP Bridge 桥接新闻组方式访问论坛以获取最佳用户体验。
本帖是回复帖，原帖作者是楼上的 &abenlee123&
Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.
Microsoft (R) Windows Debugger& Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
Symbol search path is: F:\Windows\Symbols
Executable search path is:
Windows Vista Kernel Version 6002 (Service Pack 2) MP (4 procs) Free x86 compatible
Product: Server, suite: Enterprise TerminalServer SingleUserTS
Built by: .x86fre.lh_sp2rtm.0
Kernel base = 0x81c37000 PsLoadedModuleList = 0x81d4ec70
Debug session time: Mon Feb 14 17:57:29.461 2011 (GMT+8)
System Uptime: 0 days 0:13:12.176
Loading Kernel Symbols
.....................................................................................................................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 7ffd400c).& Type &.hh dbgerr001& for details
Loading unloaded module list
*******************************************************************************
*&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
*&&&&&&&&&&&&&&&&&&&&&&& Bugcheck Analysis&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
*&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {5003, c58f, }
Probably caused by : memory_corruption ( nt!MiAllocateWsle+7d )
Followup: MachineOwner
2: kd& !analyze -v
*******************************************************************************
*&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
*&&&&&&&&&&&&&&&&&&&&&&& Bugcheck Analysis&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
*&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
*******************************************************************************
MEMORY_MANAGEMENT (1a)
&&& # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: , The subtype of the bugcheck.
Arg2: c0802000
Arg3: 0001558f
Debugging Details:
------------------
BUGCHECK_STR:& 0x1a_5003
DEFAULT_BUCKET_ID:& VISTA_RC
PROCESS_NAME:& mw2.exe
CURRENT_IRQL:& 0
LAST_CONTROL_TRANSFER:& from 81c96b48 to 81d04b0d
STACK_TEXT:&
b842dc4c 81c96b48 02000 nt!KeBugCheckEx+0x1e
b842dc84 81caf7f0 c122a0
nt!MiAllocateWsle+0x7d
b842dcd4 81cd0b7a d0 nt!MiResolveDemandZeroFault+0x681
b842dd4c 81c84db4 d1 nt!MmAccessFault+0x191a
b842dd4c 77ab9e05 d1 nt!KiTrap0E+0xdc
WARNING: Frame IP not in any known module. Following frames may be wrong.
STACK_COMMAND:& kb
FOLLOWUP_IP:
nt!MiAllocateWsle+7d
81c96b48 cc&&&&&&&&&&&&& int&&&& 3
SYMBOL_STACK_INDEX:& 1
SYMBOL_NAME:& nt!MiAllocateWsle+7d
FOLLOWUP_NAME:& MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP:& 49e0199e
IMAGE_NAME:& memory_corruption
FAILURE_BUCKET_ID:& 0x1a_5003_nt!MiAllocateWsle+7d
BUCKET_ID:& 0x1a_5003_nt!MiAllocateWsle+7d
Followup: MachineOwner
主板驱动升级了下, 现在又这样蓝了,请帮忙分析下. PROCESS_NAME:& mw2.exe是我正在玩的游戏魔界二.
请您提供一份或几份MINIDUMP以供进一步的分析。此外，若蓝屏频发而对象不定，亦不妨关注硬件工作状态，典型如内存。对于内存，可执行内存诊断复查其可靠性。
回答の候補に設定
回答としてマーク
这回是内存管理错误，但不一定代表你的物理内存有毛病，故障原因可能与之前相同，还是主板芯片组驱动的问题。
Alexis Zhang
http://mvp./profile/jie
http://blogs.itecn.net/blogs/alexis
推荐以 NNTP Bridge 桥接新闻组方式访问论坛以获取最佳用户体验。
本帖是回复帖，原帖作者是楼上的 &abenlee123&
BugCheck 1A, {5003, c58f, }
Probably caused by : memory_corruption ( nt!MiAllocateWsle+7d )
回答の候補に設定
回答としてマーク
Microsoft (R) Windows Debugger& Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
Symbol search path is: F:\Windows\Symbols
Executable search path is:
**************************************************************************
THIS DUMP FILE IS PARTIALLY CORRUPT.
KdDebuggerDataBlock is not present or unreadable.
**************************************************************************
Unable to read PsLoadedModuleList
**************************************************************************
THIS DUMP FILE IS PARTIALLY CORRUPT.
KdDebuggerDataBlock is not present or unreadable.
**************************************************************************
KdDebuggerData.KernBase & SystemRangeStart
Windows Vista Kernel Version 6002 MP (4 procs) Free x86 compatible
Product: Server, suite: Enterprise TerminalServer SingleUserTS
Kernel base = 0x PsLoadedModuleList = 0x81d2bc70
Debug session time: Sat Feb 19 20:27:07.875 2011 (GMT+8)
System Uptime: 2 days 17:52:40.108
**************************************************************************
THIS DUMP FILE IS PARTIALLY CORRUPT.
KdDebuggerDataBlock is not present or unreadable.
**************************************************************************
Unable to read PsLoadedModuleList
**************************************************************************
THIS DUMP FILE IS PARTIALLY CORRUPT.
KdDebuggerDataBlock is not present or unreadable.
**************************************************************************
KdDebuggerData.KernBase & SystemRangeStart
Loading Kernel Symbols
Unable to read PsLoadedModuleList
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
CS descriptor lookup failed
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get program counterGetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
*******************************************************************************
*&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
*&&&&&&&&&&&&&&&&&&&&&&& Bugcheck Analysis&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
*&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck F4, {3, 8aa08016c, 81e3a650}
***** Debugger could not find nt in module list, module list might be corrupt, error 0x.
GetContextState failed, 0xD0000147
Unable to read selector for PCR for processor 0
GetContextState failed, 0xD0000147
Unable to read selector for PCR for processor 0
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
Followup: MachineOwner
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
唉,怎么回事呀...
Microsoft (R) Windows Debugger& Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
Symbol search path is: F:\Windows\Symbols
Executable search path is:
**************************************************************************
THIS DUMP FILE IS PARTIALLY CORRUPT.
KdDebuggerDataBlock is not present or unreadable.
**************************************************************************
Unable to read PsLoadedModuleList
**************************************************************************
THIS DUMP FILE IS PARTIALLY CORRUPT.
KdDebuggerDataBlock is not present or unreadable.
**************************************************************************
KdDebuggerData.KernBase & SystemRangeStart
Windows Vista Kernel Version 6002 MP (4 procs) Free x86 compatible
Product: Server, suite: Enterprise TerminalServer SingleUserTS
Kernel base = 0x PsLoadedModuleList = 0x81d58c70
Debug session time: Sat Feb 19 22:33:36.974 2011 (GMT+8)
System Uptime: 0 days 0:04:36.057
**************************************************************************
THIS DUMP FILE IS PARTIALLY CORRUPT.
KdDebuggerDataBlock is not present or unreadable.
**************************************************************************
Unable to read PsLoadedModuleList
**************************************************************************
THIS DUMP FILE IS PARTIALLY CORRUPT.
KdDebuggerDataBlock is not present or unreadable.
**************************************************************************
KdDebuggerData.KernBase & SystemRangeStart
Loading Kernel Symbols
Unable to read PsLoadedModuleList
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
CS descriptor lookup failed
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get program counterGetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
*******************************************************************************
*&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
*&&&&&&&&&&&&&&&&&&&&&&& Exception Analysis&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
*&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
*******************************************************************************
Use !analyze -v to get detailed debugging information.
GetContextState failed, 0xD0000147
Unable to read selector for PCR for processor 0
WARNING: Unable to reset page directories
GetContextState failed, 0xD0000147
Unable to read selector for PCR for processor 0
WARNING: Unable to reset page directories
***** Debugger could not find ntdll in module list, module list might be corrupt, error 0x.
GetContextState failed, 0xD0000147
Unable to read selector for PCR for processor 0
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to read selector for PCR for processor 0
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
Followup: MachineOwner
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
这一次是 0x 错误，请参考一下这里：
/kb/330100/zh-cn
通常是硬盘及数据线引起的问题。
Alexis Zhang
http://mvp./profile/jie
http://blogs.itecn.net/blogs/alexis
推荐以 NNTP Bridge 桥接新闻组方式访问论坛以获取最佳用户体验。
本帖是回复帖，原帖作者是楼上的 &abenlee123&
Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.
Microsoft (R) Windows Debugger& Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
Symbol search path is: F:\Windows\Symbols
Executable search path is:
Windows Vista Kernel Version 6002 (Service Pack 2) MP (4 procs) Free x86 compatible
Product: Server, suite: Enterprise TerminalServer SingleUserTS
Built by: .x86fre.lh_sp2rtm.0
Kernel base = 0x81c51000 PsLoadedModuleList = 0x81d68c70
Debug session time: Sun Feb 20 16:51:41.501 2011 (GMT+8)
System Uptime: 0 days 18:10:39.312
Loading Kernel Symbols
.....................................................................................................................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 7ffdf00c).& Type &.hh dbgerr001& for details
Loading unloaded module list
*******************************************************************************
*&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
*&&&&&&&&&&&&&&&&&&&&&&& Bugcheck Analysis&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
*&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {5003, cf07, 422f8201}
Probably caused by : memory_corruption ( nt!MiAllocateWsle+7d )
Followup: MachineOwner
这个与上次相同，内存管理错误。
Alexis Zhang
http://mvp./profile/jie
http://blogs.itecn.net/blogs/alexis
推荐以 NNTP Bridge 桥接新闻组方式访问论坛以获取最佳用户体验。
本帖是回复帖，原帖作者是楼上的 &abenlee123&
Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.
Microsoft (R) Windows Debugger& Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
Symbol search path is: F:\Windows\Symbols
Executable search path is:
Windows Vista Kernel Version 6002 (Service Pack 2) MP (4 procs) Free x86 compatible
Product: Server, suite: Enterprise TerminalServer SingleUserTS
Built by: .x86fre.lh_sp2rtm.0
Kernel base = 0x PsLoadedModuleList = 0x8211bc70
Debug session time: Sat Feb 26 06:11:23.849 2011 (GMT+8)
System Uptime: 0 days 5:13:19.482
Loading Kernel Symbols
......................................................................................................................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 7ffda00c).& Type &.hh dbgerr001& for details
Loading unloaded module list
*******************************************************************************
*&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
*&&&&&&&&&&&&&&&&&&&&&&& Bugcheck Analysis&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
*&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 8E, {cefc3c68, 0}
Page 31e6c2 not present in the dump file. Type &.hh dbgerr004& for details
Probably caused by : win32k.sys ( win32k!TimersProc+75 )
Followup: MachineOwner
蓝屏后电脑无法启动,屏幕也不亮,拿掉两条单根4G的内存后, 才能开机. 难道M4A88TD-M主板不支持单条4G的内存? 可在MEMTEST下测试了一天也没事的.
请您尝试暂时安装较少的内存并进行进一步的观察，并可尝试对BIOS进行更新（最新版本似乎是1706）
华硕 M4A88TD-M 支持单条 4GB 内存，最大支持 16GB。
综合这么多次的蓝屏故障信息来看，可以认定主板有问题。如果可以自己刷新主板 BIOS 请试试重新刷一下。
Alexis Zhang
http://mvp./profile/jie
http://blogs.itecn.net/blogs/alexis
推荐以 NNTP Bridge 桥接新闻组方式访问论坛以获取最佳用户体验。
本帖是回复帖，原帖作者是楼上的 &abenlee123&
蓝屏后电脑无法启动,屏幕也不亮,拿掉两条单根4G的内存后, 才能开机. 难道M4A88TD-M主板不支持单条4G的内存? 可在MEMTEST下测试了一天也没事的.
