又一次蓝屏,麻烦懂的帮忙看看,谢谢帮助!

Question

又一次蓝屏,麻烦懂的帮忙看看,谢谢帮助!

匿名

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64

Loading Dump File [C:\Windows\Minidump\032010-37393-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at end of path element

Symbol search path is: SRV*C:\Users\冼则明\Desktop\sss*http://msdl.microsoft.com/download/symbols

Executable search path is:

Windows 7 Kernel Version 7600 MP (4 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255

Machine Name:

Kernel base = 0xfffff80004402000 PsLoadedModuleList = 0xfffff8000463fe50

Debug session time: Sat Mar 20 20:04:01.147 2010 (GMT+8)

System Uptime: 0 days 3:15:28.083

Loading Kernel Symbols

.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.

Run !sym noisy before .reload to track down problems loading symbols.

..............................................................

................................................................

............................................

Loading User Symbols

Loading unloaded module list

.......

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {28, 2, 0, fffff800044b6090}

Probably caused by : memory_corruption ( nt!MiFindNodeOrParent+0 )

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: 0000000000000028, memory referenced

Arg2: 0000000000000002, IRQL

Arg3: 0000000000000000, 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: fffff800044b6090, address which referenced memory

Debugging Details:

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800046aa0e0

0000000000000028

CURRENT_IRQL: 2

FAULTING_IP:

nt!MiFindNodeOrParent+0

fffff800`044b6090 48f7412800ffffff test qword ptr [rcx+28h],0FFFFFFFFFFFFFF00h

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: foobar2000.exe

TRAP_FRAME: fffff88009f27700 -- (.trap 0xfffff88009f27700)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000

rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000

rip=fffff800044b6090 rsp=fffff88009f27898 rbp=0000000000000000

r8=fffff88009f278e0 r9=0000000000000000 r10=fffffa8005961010

r11=fffffa8005952630 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0 nv up ei ng nz na po nc

nt!MiFindNodeOrParent:

fffff800044b6090 48f7412800ffffff test qword ptr [rcx+28h],0FFFFFFFFFFFFFF00h ds:0000000000000028=????????????????

Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80004473469 to fffff80004473f00

STACK_TEXT:

fffff88009f275b8 fffff80004473469 : 000000000000000a 0000000000000028 0000000000000002 0000000000000000 : nt!KeBugCheckEx

fffff88009f275c0 fffff800044720e0 : 0000000000000000 fffffa8005961058 0000000000000000 0000000063416d4d : nt!KiBugCheckDispatch+0x69

fffff88009f27700 fffff800044b6090 : fffff800044b9e17 fffff68000017a80 fffff70001080000 0000000000000000 : nt!KiPageFault+0x260

fffff88009f27898 fffff800044b9e17 : fffff68000017a80 fffff70001080000 0000000000000000 0000000000000002 : nt!MiFindNodeOrParent

fffff88009f278a0 fffff800044b9d9d : 0000000000000000 0000000000000000 0000000000000000 fffff8a002a57918 : nt!MiLocateAddressInTree+0x17

fffff88009f278d0 fffff800044b9ea8 : 0000000000000000 0000000000000000 fffffa800548d0e8 fffffa80059610c8 : nt!MiGetSharedProtosAtDpcLevel+0xbd

fffff88009f27920 fffff8000441019b : 8000000049fac882 0000000000000000 0000000000000001 0000000000000001 : nt!MiGetSharedProtos+0x18

fffff88009f27950 fffff80004578810 : fffff8a002a57918 fffffa8005961050 fffffa8001bd0680 0000007c500152b8 : nt! ?? ::FNODOBFM::`string'+0x92bb

fffff88009f27980 fffff800044eab8b : fffffa80060ac1e0 0000000300000000 fffffa8005961010 fffffa80059610c8 : nt!MiEmptyPageAccessLog+0x160

fffff88009f279f0 fffff80004789e50 : fffffa8005bf6010 0007ffff00000000 0000000000000000 0000000000000000 : nt! ?? ::FNODOBFM::`string'+0x388b6

fffff88009f27b10 fffff8000478a25b : 0000098000000000 0000000002f50000 fffffa8000000001 00000000069ae901 : nt!MiUnmapViewOfSection+0x1b0

fffff88009f27bd0 fffff80004473153 : 0000000000000000 00000000764a1a75 fffffa80060ac1e0 fffffa80045ae960 : nt!NtUnmapViewOfSection+0x5f

fffff88009f27c20 00000000778b015a : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x13

00000000069ae038 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x778b015a

STACK_COMMAND: kb

FOLLOWUP_IP:

nt!MiFindNodeOrParent+0

fffff800`044b6090 48f7412800ffffff test qword ptr [rcx+28h],0FFFFFFFFFFFFFF00h

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!MiFindNodeOrParent+0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: X64_0xA_nt!MiFindNodeOrParent+0

BUCKET_ID: X64_0xA_nt!MiFindNodeOrParent+0

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: 0000000000000028, memory referenced

Arg2: 0000000000000002, IRQL

Arg3: 0000000000000000, 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: fffff800044b6090, address which referenced memory

Debugging Details:

READ_ADDRESS: 0000000000000028