Microsoft ® Windows Debugger Version 6.5.0003.7

Copyright © Microsoft Corporation. All rights reserved.

Loading Dump File [C:\WINDOWS\Minidump\Mini041606-01.dmp]

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

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols

Executable search path is:

Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 2600.xpsp_sp2_gdr.050301-1519

Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420

Debug session time: Sun Apr 16 01:43:30.984 2006 (GMT+2)

System Uptime: 0 days 5:27:30.569

Loading Kernel Symbols

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

Loading unloaded module list

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

Loading User Symbols

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

* *

* Bugcheck Analysis *

* *

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

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {e27a4ffc, 0, 804d9da8, 1}

Could not read faulting driver name

Probably caused by : win32k.sys ( win32k!vSrcCopyS32D32Identity+5b )

Followup: MachineOwner

---------

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

Arg2: 00000000, value 0 = read operation, 1 = write operation.

Arg3: 804d9da8, If non-zero, the instruction address which referenced the bad memory

address.

Arg4: 00000001, (reserved)

Debugging Details:

------------------

Could not read faulting driver name

READ_ADDRESS: e27a4ffc

FAULTING_IP:

nt!memmove+33

804d9da8 f3a5 rep movsd

MM_INTERNAL_CODE: 1

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x50

LAST_CONTROL_TRANSFER: from bf83a167 to 804d9da8

STACK_TEXT:

b953b24c bf83a167 139f9fd4 e27a4ffc 00000080 nt!memmove+0x33

b953b270 bf839e20 0001ff40 00000000 12a00054 win32k!vSrcCopyS32D32Identity+0x5b

b953b484 bf847c49 e28ba880 00000000 00000000 win32k!EngCopyBits+0x51a

b953b540 bf8482a4 00000000 e27ab000 00020020 win32k!GreGetDIBitsInternal+0x795

b953b5d8 804de7ec 080104a0 c1051c70 00000000 win32k!NtGdiGetDIBitsInternal+0x27e

b953b5d8 7c95eb94 080104a0 c1051c70 00000000 nt!KiFastCallEntry+0xf8

WARNING: Frame IP not in any known module. Following frames may be wrong.

013bf21c 00000000 00000000 00000000 00000000 0x7c95eb94

FOLLOWUP_IP:

win32k!vSrcCopyS32D32Identity+5b

bf83a167 83c40c add esp,0xc

SYMBOL_STACK_INDEX: 1

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: win32k!vSrcCopyS32D32Identity+5b

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 43446a58

STACK_COMMAND: kb

FAILURE_BUCKET_ID: 0x50_win32k!vSrcCopyS32D32Identity+5b

BUCKET_ID: 0x50_win32k!vSrcCopyS32D32Identity+5b

Followup: MachineOwner

---------

UP

מישהו?

תעיין פה ותעלה תקבצי דאמפ..

http://hwzone.co.il/community/index.php?topic=124642.0