Windows Vista need help on BSOD when using live messenger (with dump file)

encountered intermittent BSOD when chatting on live messenger

below is the info from the dump file

appreciate any help rendered

cheers



Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\Mini071408-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\windows\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6000.16584.x86fre.vista_gdr.071023-1545
Kernel base = 0x82000000 PsLoadedModuleList = 0x82111e10
Debug session time: Mon Jul 14 00:30:54.990 2008 (GMT+8)
System Uptime: 0 days 1:48:42.232
Loading Kernel Symbols
.........................................................................................................................................
Loading User Symbols
Loading unloaded module list
...............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c000001d, 8209aa70, 974cba74, 0}



Probably caused by : win32k.sys ( win32k!xxxHkCallHook+302 )

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: c000001d, The exception code that was not handled
Arg2: 8209aa70, The address that the exception occurred at
Arg3: 974cba74, Trap Frame
Arg4: 00000000

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




EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.

FAULTING_IP:
nt! ?? ::FNODOBFM::`string'+5ad0
8209aa70 fe ???

TRAP_FRAME: 974cba74 -- (.trap 0xffffffff974cba74)
ErrCode = 00000000
eax=974cbb1c ebx=974cbd14 ecx=00000000 edx=00000000 esi=974cbd30 edi=974cbb48
eip=8209aa70 esp=974cbae8 ebp=974cbb78 iopl=0 nv up ei pl nz ac po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010212
nt! ?? ::FNODOBFM::`string'+0x5ad0:
8209aa70 fe ???
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: msnmsgr.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 9209b4a5 to 8209aa70

FAILED_INSTRUCTION_ADDRESS:
nt! ?? ::FNODOBFM::`string'+5ad0
8209aa70 fe ???

STACK_TEXT:
974cbb78 9209b4a5 00030000 00000001 974cbd14 nt! ?? ::FNODOBFM::`string'+0x5ad0
974cbbd4 920b4a50 004058c1 00000000 00000001 win32k!xxxHkCallHook+0x302
974cbc6c 920b4777 03031780 00000000 00000001 win32k!xxxCallHook2+0x2d0
974cbc88 920d9830 00000000 00000001 00000000 win32k!xxxCallHook+0x26
974cbce4 920de450 974cbd14 000025ff 00000000 win32k!xxxRealInternalGetMessage+0x39e
974cbd48 8208caaa 0006febc 00000000 00000000 win32k!NtUserPeekMessage+0x3f
974cbd48 76fa0f34 0006febc 00000000 00000000 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0006fe1c 00000000 00000000 00000000 00000000 0x76fa0f34


STACK_COMMAND: kb

FOLLOWUP_IP:
win32k!xxxHkCallHook+302
9209b4a5 e9ca000000 jmp win32k!xxxHkCallHook+0x3d1 (9209b574)

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: win32k!xxxHkCallHook+302

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 47c78718

FAILURE_BUCKET_ID: 0x8E_BAD_IP_win32k!xxxHkCallHook+302

BUCKET_ID: 0x8E_BAD_IP_win32k!xxxHkCallHook+302

Followup: MachineOwner
---------