Windows 7 - BSOD in Windows 7 Ultimate since a while

*******************************************************************************
*                                                                             *
*                        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: 97f936bc, The address that the exception occurred at
Arg3: 987a5b00, 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: 
dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+116
97f936bc 894804          mov     dword ptr [eax+4],ecx

TRAP_FRAME:  987a5b00 -- (.trap 0xffffffff987a5b00)
ErrCode = 00000002
eax=00000000 ebx=87a43000 ecx=b39ee0a8 edx=00000001 esi=85d96ab0 edi=b38e2610
eip=97f936bc esp=987a5b74 ebp=987a5ba8 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+0x116:
97f936bc 894804          mov     dword ptr [eax+4],ecx ds:0023:00000004=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  firefox.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 97f93f53 to 97f936bc

STACK_TEXT:  
987a5ba8 97f93f53 00000000 00000000 b3f2e5b0 dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+0x116
987a5bc8 97f7732b b1c7d270 00000000 987a5c54 dxgmms1!VIDMM_GLOBAL::CloseAllocation+0x37
987a5bd8 97ee34aa 87a43000 b1c7d270 00000000 dxgmms1!VidMmCloseAllocation+0x13
987a5c54 97ee1481 00000000 00000000 a45090e8 dxgkrnl!DXGDEVICE::DestroyAllocations+0x19a
987a5c7c 97ee6ee8 00000001 00000000 00000000 dxgkrnl!DXGDEVICE::ProcessTerminationList+0x89
987a5d28 82c9742a 001f95a4 001f94c0 770f64f4 dxgkrnl!DxgkCreateAllocation+0x28c
987a5d28 770f64f4 001f95a4 001f94c0 770f64f4 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
001f94c0 00000000 00000000 00000000 00000000 0x770f64f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+116
97f936bc 894804          mov     dword ptr [eax+4],ecx

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+116

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc265

FAILURE_BUCKET_ID:  0x8E_dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+116

BUCKET_ID:  0x8E_dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+116

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