Attachment 591434 Details for Bug 831570 – guest core dump

guest core dump

debug.info.txt (text/plain), 4.47 KB, created by Xu Tian on 2012-06-13 10:37:15 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Xu Tian

Created: 2012-06-13 10:37:15 UTC

Size: 4.47 KB

patch

obsolete

>
>Microsoft (R) Windows Debugger Version 6.10.0003.233 AMD64
>Copyright (c) Microsoft Corporation. All rights reserved.
>
>
>Loading Dump File [C:\Users\test\Desktop\061312-22687-01.dmp]
>Mini Kernel Dump File: Only registers and stack trace are available
>
>Symbol search path is: SRV*http://msdl.microsoft.com/download/symbols
>0: kd> !analyze -v
>*******************************************************************************
>*                                                                             *
>*                        Bugcheck Analysis                                    *
>*                                                                             *
>*******************************************************************************
>
>SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
>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 0x80000003.  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: ffffffffc0000005, The exception code that was not handled
>Arg2: fffff80002ad102f, The address that the exception occurred at
>Arg3: fffff88004606938, Exception Record Address
>Arg4: fffff88004606190, Context Record Address
>
>Debugging Details:
>------------------
>
>
>EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
>
>FAULTING_IP: 
>nt!PfpFlushBuffers+6f
>fffff800`02ad102f 4d8b1b          mov     r11,qword ptr [r11]
>
>EXCEPTION_RECORD:  fffff88004606938 -- (.exr 0xfffff88004606938)
>ExceptionAddress: fffff80002ad102f (nt!PfpFlushBuffers+0x000000000000006f)
>   ExceptionCode: c0000005 (Access violation)
>  ExceptionFlags: 00000000
>NumberParameters: 2
>   Parameter[0]: 0000000000000000
>   Parameter[1]: ffffffffffffffff
>Attempt to read from address ffffffffffffffff
>
>CONTEXT:  fffff88004606190 -- (.cxr 0xfffff88004606190)
>rax=3f3f3f3f3f3f3f3f rbx=000000000002d5b3 rcx=0000000000000001
>rdx=fffffa8003916001 rsi=0000000000000000 rdi=fffff8000280d568
>rip=fffff80002ad102f rsp=fffff88004606b70 rbp=0000000000000080
> r8=fffffa8003916000  r9=0000000000000000 r10=fffff8000280bc60
>r11=3f3f3f3f3f3f3f3f r12=0000000000000000 r13=0000000000000000
>r14=0000000000000000 r15=fffff880009e9ec0
>iopl=0         nv up ei pl nz na po nc
>cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
>nt!PfpFlushBuffers+0x6f:
>fffff800`02ad102f 4d8b1b          mov     r11,qword ptr [r11] ds:002b:3f3f3f3f`3f3f3f3f=????????????????
>Resetting default scope
>
>CUSTOMER_CRASH_COUNT:  1
>
>DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
>
>PROCESS_NAME:  System
>
>CURRENT_IRQL:  0
>
>ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
>
>EXCEPTION_PARAMETER1:  0000000000000000
>
>EXCEPTION_PARAMETER2:  ffffffffffffffff
>
>READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800028b70e0
> ffffffffffffffff 
>
>FOLLOWUP_IP: 
>nt!PfpFlushBuffers+6f
>fffff800`02ad102f 4d8b1b          mov     r11,qword ptr [r11]
>
>BUGCHECK_STR:  0x7E
>
>LAST_CONTROL_TRANSFER:  from fffff80002af2820 to fffff80002ad102f
>
>STACK_TEXT:  
>fffff880`04606b70 fffff800`02af2820 : fffffa80`048cd601 00000000`00000080 fffffa80`036f8040 fffff800`0280d568 : nt!PfpFlushBuffers+0x6f
>fffff880`04606c10 fffff800`02924166 : ffffffff`ff676980 fffffa80`048cd660 fffff880`04606db0 fffffa80`048cd660 : nt!PfTLoggingWorker+0xe0
>fffff880`04606d40 fffff800`0265f486 : fffff880`009e5180 fffffa80`048cd660 fffff880`009eff40 fffff880`0126ca90 : nt!PspSystemThreadStartup+0x5a
>fffff880`04606d80 00000000`00000000 : fffff880`04607000 fffff880`04601000 fffff880`04606750 00000000`00000000 : nt!KxStartSystemThread+0x16
>
>
>SYMBOL_STACK_INDEX:  0
>
>SYMBOL_NAME:  nt!PfpFlushBuffers+6f
>
>FOLLOWUP_NAME:  MachineOwner
>
>MODULE_NAME: nt
>
>IMAGE_NAME:  ntkrnlmp.exe
>
>DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600
>
>STACK_COMMAND:  .cxr 0xfffff88004606190 ; kb
>
>FAILURE_BUCKET_ID:  X64_0x7E_nt!PfpFlushBuffers+6f
>
>BUCKET_ID:  X64_0x7E_nt!PfpFlushBuffers+6f
>
>Followup: MachineOwner
>---------
>

Actions: View

Attachments on bug 831570: 591434