积极答复者
Windows7蓝屏0x0000000a求分析

问题
-
以下是MEMORY.DMP分析内容,求高手分析,谢谢
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [E:\新建文件夹\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is availableSymbol search path is: SRV*d:\temp*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`04417000 PsLoadedModuleList = 0xfffff800`0465c670
Debug session time: Sat Mar 10 00:55:37.003 2012 (GMT+8)
System Uptime: 0 days 0:32:20.517
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`fffdf018). Type ".hh dbgerr001" for details
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************Use !analyze -v to get detailed debugging information.
BugCheck A, {f4, 2, 1, fffff8000449bd24}
PEB is paged out (Peb.Ldr = 00000000`fffdf018). Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 00000000`fffdf018). Type ".hh dbgerr001" for details
Probably caused by : hardware ( nt!KeRemoveQueueEx+b4 )Followup: MachineOwner
---------2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000000000000f4, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8000449bd24, address which referenced memoryDebugging Details:
------------------PEB is paged out (Peb.Ldr = 00000000`fffdf018). Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 00000000`fffdf018). Type ".hh dbgerr001" for detailsWRITE_ADDRESS: 00000000000000f4
CURRENT_IRQL: 2
FAULTING_IP:
nt!KeRemoveQueueEx+b4
fffff800`0449bd24 0000 add byte ptr [rax],alDEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: Wow.exe
TRAP_FRAME: fffff88004793600 -- (.trap 0xfffff88004793600)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000000000f4 rbx=0000000000000000 rcx=fffffa8008fc6340
rdx=0000000000000102 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000449bd24 rsp=fffff88004793790 rbp=fffffa8008fc6368
r8=fffff88004766301 r9=0000000000000004 r10=00000000000000e7
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz ac pe cy
nt!KeRemoveQueueEx+0xb4:
fffff800`0449bd24 0000 add byte ptr [rax],al ds:4690:00f4=??
Resetting default scopeMISALIGNED_IP:
nt!KeRemoveQueueEx+b4
fffff800`0449bd24 0000 add byte ptr [rax],alLAST_CONTROL_TRANSFER: from fffff800044931e9 to fffff80004493c40
STACK_TEXT:
fffff880`047934b8 fffff800`044931e9 : 00000000`0000000a 00000000`000000f4 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`047934c0 fffff800`04491e60 : fffffa80`ffffd9af fffff880`04793740 00000000`00000000 00000000`38000000 : nt!KiBugCheckDispatch+0x69
fffff880`04793600 fffff800`0449bd24 : fffff880`047d5180 fffffa80`073854e0 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
fffff880`04793790 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000202 fffff800`04499fda : nt!KeRemoveQueueEx+0xb4
STACK_COMMAND: kbFOLLOWUP_IP:
nt!KeRemoveQueueEx+b4
fffff800`0449bd24 0000 add byte ptr [rax],alSYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!KeRemoveQueueEx+b4
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: hardware
FAILURE_BUCKET_ID: X64_IP_MISALIGNED
BUCKET_ID: X64_IP_MISALIGNED
Followup: MachineOwner
---------2012年3月9日 18:09
答案
-
你是在 64 位 Windows 7 中运行 32 位的《魔兽世界》游戏客户端么?建议运行 WOW64.EXE 的 64 位客户端。--Alexis Zhanghttp://mvp.support.microsoft.com/profile/jiehttp://blogs.itecn.net/blogs/alexis推荐以 NNTP Bridge 桥接新闻组方式访问论坛以获取最佳用户体验。本帖是回复帖,原帖作者是楼上的 "Mikado陛下様"FAILURE_BUCKET_ID: X64_IP_MISALIGNEDBUCKET_ID: X64_IP_MISALIGNED
- 已建议为答案 Arthur Xie 2012年3月13日 2:56
- 已标记为答案 Arthur Xie 2012年3月16日 7:51
2012年3月9日 23:46
全部回复
-
你是在 64 位 Windows 7 中运行 32 位的《魔兽世界》游戏客户端么?建议运行 WOW64.EXE 的 64 位客户端。--Alexis Zhanghttp://mvp.support.microsoft.com/profile/jiehttp://blogs.itecn.net/blogs/alexis推荐以 NNTP Bridge 桥接新闻组方式访问论坛以获取最佳用户体验。本帖是回复帖,原帖作者是楼上的 "Mikado陛下様"FAILURE_BUCKET_ID: X64_IP_MISALIGNEDBUCKET_ID: X64_IP_MISALIGNED
- 已建议为答案 Arthur Xie 2012年3月13日 2:56
- 已标记为答案 Arthur Xie 2012年3月16日 7:51
2012年3月9日 23:46