Windows Vista BSOD in Vista

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


Loading Dump File [C:\Users\R600\Desktop\Mini041407-02.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: C:\Users\R600\Desktop;C:\Windows
Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6000.16386.x86fre.vista_rtm.061101-2205
Kernel base = 0x81c00000 PsLoadedModuleList = 0x81d11db0
Debug session time: Sat Apr 14 05:16:43.287 2007 (GMT-7)
System Uptime: 0 days 0:00:38.100
Loading Kernel Symbols
..............................................................................................................................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 924caaea, 94fa7ab0, 0}

Probably caused by : win32k.sys ( win32k!HMFreeObject+7d )

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

0: kd> .reload
Loading Kernel Symbols
..............................................................................................................................................
Loading User Symbols
Loading unloaded module list
.....
0: kd> .reload
Loading Kernel Symbols
..............................................................................................................................................
Loading User Symbols
Loading unloaded module list
.....
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: 924caaea, The address that the exception occurred at
Arg3: 94fa7ab0, 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!HMFreeObject+7d
924caaea ff7040 push dword ptr [eax+40h]

TRAP_FRAME: 94fa7ab0 -- (.trap ffffffff94fa7ab0)
ErrCode = 00000000
eax=00000000 ebx=00000039 ecx=00000000 edx=00000000 esi=ff910018 edi=ffac2400
eip=924caaea esp=94fa7b24 ebp=94fa7b34 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!HMFreeObject+0x7d:
924caaea ff7040 push dword ptr [eax+40h] ds:0023:00000040=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: VISTA_RC

BUGCHECK_STR: 0x8E

PROCESS_NAME: Ati2evxx.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 924891d2 to 924caaea

STACK_TEXT:
94fa7b34 924891d2 00000000 00000000 ffac2400 win32k!HMFreeObject+0x7d
94fa7b74 92489ab3 ffac2400 94fa7bb4 00000018 win32k!xxxFreeWindow+0x7d6
94fa7bc4 924bf5ef 00000000 94fa7c28 924bf17b win32k!xxxDestroyWindow+0x4cb
94fa7bd0 924bf17b ff910018 ffacede0 ffacc008 win32k!HMDestroyUnlockedObject+0x1b
94fa7be4 924bebfe 9468262f 8726e030 00000000 win32k!DestroyThreadsObjects+0x71
94fa7c28 924be37e 00000001 94fa7c50 924be314 win32k!xxxDestroyThreadInfo+0x254
94fa7c34 924be314 8726e030 00000001 8726e030 win32k!UserThreadCallout+0x4b
94fa7c50 81e1baec 8726e030 00000001 94fac7fc win32k!W32pThreadCallout+0x3a
94fa7cbc 81e1b58d 000000ff 8726e030 8726e001 nt!PspExitThread+0x46c
94fa7cd4 81cb1410 87306138 94fa7d00 94fa7d0c nt!PsExitSpecialApc+0x22
94fa7d2c 81c8ca16 00000001 00000000 94fa7d44 nt!KiDeliverApc+0x1dc
94fa7d2c 77b20f34 00000001 00000000 94fa7d44 nt!KiServiceExit+0x56
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012e454 00000000 00000000 00000000 00000000 0x77b20f34


STACK_COMMAND: kb

FOLLOWUP_IP:
win32k!HMFreeObject+7d
924caaea ff7040 push dword ptr [eax+40h]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: win32k!HMFreeObject+7d

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 45d3cc1d

FAILURE_BUCKET_ID: 0x8E_win32k!HMFreeObject+7d

BUCKET_ID: 0x8E_win32k!HMFreeObject+7d

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

Hi, can someone tell me if Ati2evxx.exe is the problem? I'm trying to see if this is the problem to my BSOD. It happens on starting my Vista PC, if I reset it a few times the problem sometimes disappear. I usually sometimes get this error on coldboot start up. I used to get 0x0000008E errors and did a memtest86 with 9 passes with no ram errors. I later found out one of my ramsticks was bad so I RMA'd it. I am using the latest ATI 7.3 drivers. So far this is my only problem and concern about my PC system. Ati2evxx.exe is used for hotkey correct? If it is, I'll just disable it in MSCONFIG.