蓝屏 dmp提取的代码 英文看不懂 请教下是什么问题

zjl025

Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\110212-13135-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 \SystemRoot\system32\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 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Machine Name:
Kernel base = 0xfffff800`0480f000 PsLoadedModuleList = 0xfffff800`04a53670
Debug session time: Fri Nov  2 20:47:35.517 2012 (GMT+8)
System Uptime: 0 days 1:44:56.312
*********************************************************************
* 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 \SystemRoot\system32\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
....
The call to LoadLibrary(ext) failed, Win32 error 0n2
    "系统找不到指定的文件。"
Please check your debugger configuration and/or network access.
The call to LoadLibrary(exts) failed, Win32 error 0n2
    "系统找不到指定的文件。"
Please check your debugger configuration and/or network access.
The call to LoadLibrary(kext) failed, Win32 error 0n2
    "系统找不到指定的文件。"
Please check your debugger configuration and/or network access.
The call to LoadLibrary(kdexts) failed, Win32 error 0n2
    "系统找不到指定的文件。"
Please check your debugger configuration and/or network access.
The call to LoadLibrary(ext) failed, Win32 error 0n2
    "系统找不到指定的文件。"
Please check your debugger configuration and/or network access.
The call to LoadLibrary(exts) failed, Win32 error 0n2
    "系统找不到指定的文件。"
Please check your debugger configuration and/or network access.
The call to LoadLibrary(kext) failed, Win32 error 0n2
    "系统找不到指定的文件。"
Please check your debugger configuration and/or network access.
The call to LoadLibrary(kdexts) failed, Win32 error 0n2
    "系统找不到指定的文件。"
Please check your debugger configuration and/or network access.
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Bugcheck code 0000000A
Arguments 00000000`00000000 00000000`00000002 00000000`00000000 fffff800`04df9477

RetAddr           : Args to Child                                                           : Call Site
fffff800`0488d769 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt+0x7f1c0
00000000`0000000a : 00000000`00000000 00000000`00000002 00000000`00000000 fffff800`04df9477 : nt+0x7e769
00000000`00000000 : 00000000`00000002 00000000`00000000 fffff800`04df9477 fffffa80`06a1bd60 : 0xa
00000000`00000002 : 00000000`00000000 fffff800`04df9477 fffffa80`06a1bd60 fc377304`3dcbd5b2 : 0x0
00000000`00000000 : fffff800`04df9477 fffffa80`06a1bd60 fc377304`3dcbd5b2 71543a17`d78918d0 : 0x2
*** WARNING: Unable to verify timestamp for hal.dll
*** ERROR: Module load completed but symbols could not be loaded for hal.dll
fffff800`04df9477 : fffffa80`06a1bd60 fc377304`3dcbd5b2 71543a17`d78918d0 baacff72`c37bf032 : 0x0
fffffa80`06a1bd60 : fc377304`3dcbd5b2 71543a17`d78918d0 baacff72`c37bf032 0fb92db8`9ccffc97 : hal+0x2477
fc377304`3dcbd5b2 : 71543a17`d78918d0 baacff72`c37bf032 0fb92db8`9ccffc97 00000000`00000000 : 0xfffffa80`06a1bd60
71543a17`d78918d0 : baacff72`c37bf032 0fb92db8`9ccffc97 00000000`00000000 00000000`00000000 : 0xfc377304`3dcbd5b2
baacff72`c37bf032 : 0fb92db8`9ccffc97 00000000`00000000 00000000`00000000 00000000`00000000 : 0x71543a17`d78918d0
0fb92db8`9ccffc97 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xbaacff72`c37bf032
00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfb92db8`9ccffc97
00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0

lonelyarrow

从代码上看错误代码是
0x0000000A 错误表示在内核模式中存在以过高的进程内部请求级别（IRQL）访问其没有权限访问的内存地址。这个错误一般是因为硬件设备的驱动程序存在BUG，某些软件或硬件与Windows不兼容引起的。 如果遇到0x0000000A错误，建议尝试以“最后一次正确的配置”方式启动 Windows，并检查一下最近有没有安装或升级过任何系统更新、硬件设备的驱动程序、BIOS、Firmware及应用软件等。如果有的话，请将最近更新过的应用软件及硬件设备逐一卸载、恢复到之前可以稳定运行的版本，看看问题能否解决。

网络安全

上传DUMP。