Een grondige analyse levert het volgende op (probleem te wijten aan dxgkrnl.sys in combinatie met msnmsgr.exe (MSN Messenger)):
In 9/10 gevallen gaat het om hardware problemen met deze error, in jouw geval twijfel ik. Herinstalleren van de Video drivers en MSN. Give it a try I would say..
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18484.x86fre.vistasp2_gdr.110617-0336
Machine Name:
Kernel base = 0x8240c000 PsLoadedModuleList = 0x82519930
Debug session time: Sat Aug 13 15:33:27.510 2011 (UTC + 2:00)
System Uptime: 0 days 5:16:34.585
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 10E, {1e, 0, 0, 0}
Probably caused by :
dxgkrnl.sys ( dxgkrnl!VIDMM_PROCESS_HEAP::Reset+39 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e)
The video memory manager encountered a condition that it can't recover from. By crashing,
the video memory manager is attempting to get enough information into the minidump such that
somebody can pinpoint what lead to this condition.
Arguments:
Arg1: 0000001e, The subtype of the bugcheck:
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------
BUGCHECK_STR: 0x10e_1e
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME:
msnmsgr.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 90e99230 to 824c789f
STACK_TEXT:
8ac256ac 90e99230 0000010e 0000001e 00000000 nt!KeBugCheckEx+0x1e
8ac256d4 90e24498 00000000 0000010e 0000001e watchdog!WdLogEvent5+0x130
8ac25714 90e346ee 98e5e8c8 88839848 ab52eee0 dxgkrnl!VIDMM_PROCESS_HEAP::Reset+0x39
8ac2574c 90e283ce ab52eee0 88839000 8824a750 dxgkrnl!VIDMM_APERTURE_SEGMENT::ReleaseTemporaryResource+0x17b
8ac25768 90e1bf07 0000ff00 88834008 856622e0 dxgkrnl!VIDMM_GLOBAL::EvictTemporaryAllocations+0x7b
8ac257c0 90e1b6ae a17e6250 00000000 8824a750 dxgkrnl!VIDMM_GLOBAL:
repareDmaBuffer+0x345
8ac258c8 90e1ab87 856622e0 88834008 8ac25908 dxgkrnl!VidSchiSubmitRenderCommand+0x126
8ac258d8 90dfb768 856622e0 856622e0 88ab4848 dxgkrnl!VidSchiSubmitQueueCommand+0x61
8ac25908 90e1aaaa 88823000 8ac2592c 88ab4848 dxgkrnl!VidSchiSubmitQueueCommandDirect+0x1ae
8ac25930 90e1a73c 016622e0 90e99100 8a4a8968 dxgkrnl!VidSchiSubmitCommandPacketToQueue+0x171
8ac25954 90e1edb8 88ab4848 8ac25a74 00000000 dxgkrnl!VidSchSubmitCommand+0x2bf
8ac25b70 90e1e69e 8ac25b8c 1a233c35 0010f1f0 dxgkrnl!DXGCONTEXT::Render+0x513
8ac25d38 8246396a 0010f1f0 0010f330 77d75ca4 dxgkrnl!DxgkRender+0x272
8ac25d38 77d75ca4 0010f1f0 0010f330 77d75ca4 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0010f330 00000000 00000000 00000000 00000000 0x77d75ca4
STACK_COMMAND: kb
FOLLOWUP_IP:
dxgkrnl!VIDMM_PROCESS_HEAP::Reset+39
90e24498 c745f005fcffff mov dword ptr [ebp-10h],0FFFFFC05h
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: dxgkrnl!VIDMM_PROCESS_HEAP::Reset+39
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgkrnl
IMAGE_NAME: dxgkrnl.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4d383dc1
FAILURE_BUCKET_ID: 0x10e_1e_dxgkrnl!VIDMM_PROCESS_HEAP::Reset+39
BUCKET_ID: 0x10e_1e_dxgkrnl!VIDMM_PROCESS_HEAP::Reset+39
Followup: MachineOwner
