Microsoft ® Windows Debugger Version 6.9.0003.113 X86

Copyright © Microsoft Corporation. All rights reserved.

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

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

Symbol search path is: C:\WINDOWS\Symbols

Executable search path is:

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 (2 procs) Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS

Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0

Debug session time: Fri Nov 14 00:22:17.437 2008 (GMT+2)

System Uptime: 0 days 15:32:02.067

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

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

Unable to load image win32k.sys, Win32 error 0n2

*** WARNING: Unable to verify timestamp for win32k.sys

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

* *

* Bugcheck Analysis *

* *

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

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, bf8016ca, b688dfdc, 0}

Probably caused by : win32k.sys ( win32k!ValidateHwnd+103 )

Followup: MachineOwner

---------

0: kd> !analyze -v

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

* *

* Bugcheck Analysis *

* *

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)

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: c0000005, The exception code that was not handled

Arg2: bf8016ca, The address that the exception occurred at

Arg3: b688dfdc, Trap Frame

Arg4: 00000000

Debugging Details:

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

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP:

win32k!ValidateHwnd+103

bf8016ca 66095806 or word ptr [eax+6],bx

TRAP_FRAME: b688dfdc -- (.trap 0xffffffffb688dfdc)

ErrCode = 00000003

eax=00630069 ebx=00000200 ecx=00000000 edx=00000002 esi=e3d38eb0 edi=00000002

eip=bf8016ca esp=b688e050 ebp=b688e058 iopl=0 nv up ei pl zr na pe nc

cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246

win32k!ValidateHwnd+0x103:

bf8016ca 66095806 or word ptr [eax+6],bx ds:0023:0063006f=????

Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: steam.exe

LAST_CONTROL_TRANSFER: from bf841833 to bf8016ca

STACK_TEXT:

b688e058 bf841833 e3d38eb0 00000200 00000240 win32k!ValidateHwnd+0x103

b688e0b4 bf802ce9 e2b87008 e2b87008 00000000 win32k!xxxReceiveMessage+0x18c

b688e0e0 bf841222 00000200 00000000 00000000 win32k!HeavyAllocPool+0x126

b688e17c bf81413f bc6999f0 0000036e 00000000 win32k!xxxInterSendMsgEx+0x718

b688e1c8 bf836277 bc6999f0 0000036e 00000000 win32k!xxxSendMessageTimeout+0x1e7

b688e1ec bf8209e7 bc6999f0 0000036e 00000000 win32k!MapClientNeuterToClientPfn+0x24

b688e208 bf80ee53 bc6999f0 0000036e 00000000 win32k!TransferWakeBit+0x7

b688e240 804dd99f 000202f8 0000036e 00000000 win32k!NtUserMessageCall+0x23

b688e260 0012ce3c 7c90e4f4 badb0d00 0012ce0c nt!ZwSetSystemPowerState+0xf

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

b688e264 7c90e4f4 badb0d00 0012ce0c 00e10000 0x12ce3c

b688e268 badb0d00 0012ce0c 00e10000 1003f6ec 0x7c90e4f4

b688e26c 0012ce0c 00e10000 1003f6ec 89202444 0xbadb0d00

b688e270 00e10000 1003f6ec 89202444 89242474 0x12ce0c

b688e274 1003f6ec 89202444 89242474 89282474 0xe10000

b688e278 89202444 89242474 89282474 00001fa0 0x1003f6ec

b688e27c 89242474 89282474 00001fa0 bb38247c 0x89202444

b688e280 89282474 00001fa0 bb38247c 00000000 0x89242474

b688e284 00000000 bb38247c 00000000 55e8cf8b 0x89282474

STACK_COMMAND: kb

FOLLOWUP_IP:

win32k!ValidateHwnd+103

bf8016ca 66095806 or word ptr [eax+6],bx

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: win32k!ValidateHwnd+103

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 48ce513a

FAILURE_BUCKET_ID: 0x8E_win32k!ValidateHwnd+103

BUCKET_ID: 0x8E_win32k!ValidateHwnd+103

Followup: MachineOwner

---------

זה הכל , תעזרו לי בבקשה ...

אגב , יש לי חלון ווינדוס : "The system has recovered from a serious error." , אני לא מצליח להפתר ממנו , אני עושה dont send והוא ממשיך להפתח .

תודה .

זה יכול להיגרם ע"י VIRTUAL MEMORY

קליק ימני על המחשב שלי , מאפיינים , מתקדם , PERFORMANCE הגדרות , מתקדם , VIRTUAL MEMORY , תקליק על CHANGE

ותסמן כל כונן ותבחר NO PAGING FILE

ותראה אם הבעיה חוזרת על עצמה

מועבר לפורום תמיכה טכנית בבעיות חומרה.