Loading Dump File [C:\WINDOWS\Minidump\Mini082410-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:/Symbole*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp3_gdr.100216-1514
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Tue Aug 24 11:02:22.671 2010 (GMT+2)
System Uptime: 0 days 0:02:16.396
Loading Kernel Symbols
...............................................................
.........................................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {ce6aa2fc, 1, bf80116a, 0}


Could not read faulting driver name
Probably caused by : memory_corruption

Followup: memory_corruption
---------

0: 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: ce6aa2fc, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: bf80116a, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 00000000, (reserved)

Debugging Details:
------------------


Could not read faulting driver name

WRITE_ADDRESS:  ce6aa2fc 

FAULTING_IP: 
win32k!ThreadUnlock1+26
bf80116a 008d0c498d14    add     byte ptr [ebp+148D490Ch],cl

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  2

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x50

PROCESS_NAME:  csrss.exe

LAST_CONTROL_TRANSFER:  from bf83c4ff to bf80116a

STACK_TEXT:  
b9dd5988 bf83c4ff e16a9268 b9dd5aa4 00000000 win32k!ThreadUnlock1+0x26
b9dd59f0 bf83c541 036894d8 00000000 00000001 win32k!xxxCallHook2+0x2ae
b9dd5a0c bf801ac9 00000000 00000001 00000000 win32k!xxxCallHook+0x26
b9dd5a54 bf88c0c4 b9dd5aa4 000025ff 00000000 win32k!xxxRealInternalGetMessage+0x264
b9dd5d30 bf87507d bf9ac0e0 00000001 b9dd5d54 win32k!xxxDesktopThread+0x3fc
b9dd5d40 bf8010fd bf9ac0e0 b9dd5d64 0077fff4 win32k!xxxCreateSystemThreads+0x6a
b9dd5d54 8054163c 00000000 00000022 00000000 win32k!NtUserCallOneParam+0x23
b9dd5d54 7c90e514 00000000 00000022 00000000 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
00000000 00000000 00000000 00000000 00000000 0x7c90e514


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !win32k
    bf80115f - win32k!ThreadUnlock1+1b
	[ 8b:83 ]
1 error : !win32k (bf80115f)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  ONE_BIT

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT

BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT

Followup: memory_corruption
---------