Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [c:\windows\minidump\Mini061108-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: c:\windows\symbols
Executable search path is: c:\windows\i386
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0
Debug session time: Wed Jun 11 13:05:27.593 2008 (GMT+3)
System Uptime: 0 days 0:55:12.187
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
.....................................................................................................................................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 10000050, {e3a90ffc, 1, 804dafed, 1}
Could not read faulting driver name
Probably caused by : ntoskrnl.exe ( nt!RtlPrefetchCopyMemory32+2f )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: e3a90ffc, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: 804dafed, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000001, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
WRITE_ADDRESS: e3a90ffc
FAULTING_IP:
nt!RtlPrefetchCopyMemory32+2f
804dafed f3a5 rep movs dword ptr es:[edi],dword ptr [esi]
MM_INTERNAL_CODE: 1
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: iPodService.exe
LAST_CONTROL_TRANSFER: from 8056d84a to 804dafed
STACK_TEXT:
b6197bcc 8056d84a e3a9102a e3a91014 0000003c nt!RtlPrefetchCopyMemory32+0x2f
b6197c2c 8056d03b e1713330 8a1af708 89e40a20 nt!HvpGetCellMap+0xc
b6197c40 00000000 b6197ce4 b6197c70 00000000 nt!NtQueryVolumeInformationFile+0x30
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!RtlPrefetchCopyMemory32+2f
804dafed f3a5 rep movs dword ptr es:[edi],dword ptr [esi]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!RtlPrefetchCopyMemory32+2f
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntoskrnl.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 48025de7
FAILURE_BUCKET_ID: 0x50_W_nt!RtlPrefetchCopyMemory32+2f
BUCKET_ID: 0x50_W_nt!RtlPrefetchCopyMemory32+2f
Followup: MachineOwner
---------
Friday, June 20, 2008
Probably caused by : ntoskrnl.exe ( nt!RtlPrefetchCopyMemory32+2f )
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment