While performing Windows Logo Kit (WLK) testing for Display devices on Vista SP2 x64, a bug check 0x10E may be encountered. The specific test this is encountered with is the Display 'CRASH' test. This is a stress-oriented test designed to simulate heavy and high-performance graphics load. The bug check has been reported to affect 1 in 4 'CRASH' test runs during logo testing. It is possible this problem may also be rarely encountered by users of graphics-intensive applications.
For this specific issue, the bug check information will show a value of 0x2 for the first argument (eg: "BugCheck 10E, {2, 1, 0, 0}"). This parameter signifies that the process heap was not empty (there is a memory leak) while the process was exiting. This can be seen in output of “!analyze –v” as follows:
Arg1: 0000000000000002, Process heap being destroyed isn't empty.
For this specific issue, the bug check information will show a value of 0x2 for the first argument (eg: "BugCheck 10E, {2, 1, 0, 0}"). This parameter signifies that the process heap was not empty (there is a memory leak) while the process was exiting. This can be seen in output of “!analyze –v” as follows:
Arg1: 0000000000000002, Process heap being destroyed isn't empty.