Well my proudest gaming moment was when I debugged and figured out why a game I was playing at the time, Sudden Attack, crashed my Windows machine every odd minute or so once started. I am a Software Engineer and so I debugged the memory dump to find out the cause.
Not sure if I am supposed to paste a link here to my blog where I detail what I did to solve it (If this is not allowed please remove my post>
https://rickteck.wordpress.com/2011/05/14/sudden-attack-bsod-dxgkrnl-sys-video_memory_management_internal-10e/
Raw Bugcheck analysis and solution>
*******************************************************************************
* *
* 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:
——————
PEB is paged out (Peb.Ldr = 7ffdf00c). Type “.hh dbgerr001” for details
PEB is paged out (Peb.Ldr = 7ffdf00c). Type “.hh dbgerr001” for details
BUGCHECK_STR: 0x10e_1e
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: dwm.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 8dcad230 to 820d80e3
STACK_TEXT:
a5e526cc 8dcad230 0000010e 0000001e 00000000 nt!KeBugCheckEx+0x1e
a5e526f4 8dc38beb 00000000 0000010e 0000001e watchdog!WdLogEvent5+0x130
a5e52734 8dc48557 b676cfd0 8925d848 b9fb5450 dxgkrnl!VIDMM_PROCESS_HEAP::Reset+0x39
a5e5276c 8dc41145 b9fb5450 8925d000 85419bd8 dxgkrnl!VIDMM_APERTURE_SEGMENT::ReleaseTemporaryResource+0x17b
a5e52788 8dc2f112 0000ff00 89220628 89272210 dxgkrnl!VIDMM_GLOBAL::EvictTemporaryAllocations+0x7b
a5e527e0 8dc30dd3 b46a9510 00000000 85419bd8 dxgkrnl!VIDMM_GLOBAL::PrepareDmaBuffer+0x345
a5e528e8 8dc2e930 89272210 89220628 a5e52928 dxgkrnl!VidSchiSubmitRenderCommand+0x126
a5e528f8 8dc109a1 89272210 89272210 89a1e660 dxgkrnl!VidSchiSubmitQueueCommand+0x61
a5e52928 8dc2e876 8923f000 a5e5294c 89a1e660 dxgkrnl!VidSchiSubmitQueueCommandDirect+0x1ae
a5e52950 8dc30a3d 01272210 8dcad100 b4a0e770 dxgkrnl!VidSchiSubmitCommandPacketToQueue+0x171
a5e52974 8dc3464a 89a1e660 a5e52a94 00000000 dxgkrnl!VidSchSubmitCommand+0x2bf
a5e52b90 8dc33f30 a5e52bac 28279e6f 0292f520 dxgkrnl!DXGCONTEXT::Render+0x513
a5e52d58 82062a1a 0292f520 0292f664 77479a94 dxgkrnl!DxgkRender+0x272
a5e52d58 77479a94 0292f520 0292f664 77479a94 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0292f664 00000000 00000000 00000000 00000000 0x77479a94
STACK_COMMAND: kb
FOLLOWUP_IP:
dxgkrnl!VIDMM_PROCESS_HEAP::Reset+39
8dc38beb 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: 4893b1df
FAILURE_BUCKET_ID: 0x10e_1e_dxgkrnl!VIDMM_PROCESS_HEAP::Reset+39
BUCKET_ID: 0x10e_1e_dxgkrnl!VIDMM_PROCESS_HEAP::Reset+39
Follow-up: MachineOwner
———
According to instructions in the Debugging Tools for Windows help file this bugcheck code 0x10E: VIDEO_MEMORY_MANAGEMENT_INTERNAL is usually caused by a video driver behaving improperly. Based on these instructions I updated my laptop video card (NVIDIA GeForce 8400M GS) drivers to the latest version of nVidia ForceWare 186.03. THIS DID NOT SOLVE THE PROBLEM THOUGH
SOLUTION!
IMAGE_NAME: dxgkrnl.sys
PROCESS_NAME: dwm.exe
Taking a closer look at the dump we have 2 clues: dxgkrnl.sys drawing out functions and dwm.exe (Desktop Window Manager – responsible for the graphics effects on Vista) being the owner process when the crash occurs. It seems that DirectX and the card drivers are drawing functions that the Desktop Windows Manager process cannot handle. The common denominator in this equation and all the subsequent MEMORY dumps generated is always the darn dwm process.
The Workaround is obvious, kill the dwm.exe process and configure Windows Vista to use the classic windows theme also to save system resources as this process eats Virtual Memory in my case 133MB.
Kill the svchost parent process above dwm or the Desktop Window Manager will respawn within it’s parent every time.