dxgmms1.sys bsod

I got a bsod i used bluescreen view and tracked it down to dxgmms1.sys

i believe it may be a bad driver but non under device manager are showing as broken or damaged any advice would be most helpful. i got lucky i didnt have anything important up but i would like to prevent this in the future

here is the log (see attachment)

ps: I have also been having slight issue with random power downs but i had attributed them to overheating, dont know if they may be related

 

What is your display adapter, driver version & date?

 

here is the specs for the laptop i am using http://www.laptop-software.com/acer-software/acer-aspiacer-aspire-5742-specs-review/

as for driver version and date:

version: 8.15.10.2622
date: 1/10/2012

 

It's very difficult to be sure of anything from 1 minidump, especially if we don't know what the computer was doing when it crashed.

Given that the BSOD implicates graphics, it's a laptop and you already suspect it to be heat-related, giving the internals a thorough, careful clean, check the fan is working and that there's plenty of air throughtput and space around the running laptop (laptop cooler/thick chopstick under the back of the laptop).

There are a number of older 3rd party drivers installed, BlueScreenView allows you to see all the drivers loaded and list them by date; Options > Lower pane mode > Show all drivers. You can check the drivers makers at Sysnative.com to enable you to check for updates.

LogMeIn is something I'd uninstall during testing, yours looks particularly old - Vista vintage perhaps.

Try to update all older hardware drivers so you have nothing 3rd party that pre-dates early 2011. Get the drivers from Acer or the hardware chip makers, use Windows/MSFT Update or the update drivers facility in Device Manager only as a last resort.

Give us some detail on what the computer was doing immediately before the crash. Upload any further minidumps if you get them.

Code:

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


Loading Dump File [C:\Windows\Minidump\040712-17503-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`02e50000 PsLoadedModuleList = 0xfffff800`03094650
Debug session time: Sat Apr  7 08:37:04.822 2012 (UTC + 1:00)
System Uptime: 1 days 2:02:12.289
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff880047cd13b, fffff880030fe978, fffff880030fe1d0}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::StartPreparation+f )

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff880047cd13b, The address that the exception occurred at
Arg3: fffff880030fe978, Exception Record Address
Arg4: fffff880030fe1d0, Context Record Address

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::StartPreparation+f
fffff880`047cd13b 48ff81900f0000  inc     qword ptr [rcx+0F90h]

EXCEPTION_RECORD:  fffff880030fe978 -- (.exr 0xfffff880030fe978)
ExceptionAddress: fffff880047cd13b (dxgmms1!VIDMM_GLOBAL::StartPreparation+0x000000000000000f)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000001
   Parameter[1]: 0000000000000f94
Attempt to write to address 0000000000000f94

CONTEXT:  fffff880030fe1d0 -- (.cxr 0xfffff880030fe1d0)
rax=fffffa80061d2d50 rbx=0000000000000000 rcx=0000000000000004
rdx=0000000000000000 rsi=00000000c0000001 rdi=0000000000000004
rip=fffff880047cd13b rsp=fffff880030febb0 rbp=0000000000000080
 r8=0000000000000000  r9=0000000000000000 r10=fffff880047b32b4
r11=fffffa8005b42850 r12=fffffa8004ec6410 r13=fffff88007eec1e8
r14=0000000000000000 r15=fffff880031d7f40
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00210282
dxgmms1!VIDMM_GLOBAL::StartPreparation+0xf:
fffff880`047cd13b 48ff81900f0000  inc     qword ptr [rcx+0F90h] ds:002b:00000000`00000f94=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000001

EXCEPTION_PARAMETER2:  0000000000000f94

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030fe100
GetUlongFromAddress: unable to read from fffff800030fe1c0
 0000000000000f94 Nonpaged pool

FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::StartPreparation+f
fffff880`047cd13b 48ff81900f0000  inc     qword ptr [rcx+0F90h]

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff880047c6575 to fffff880047cd13b

STACK_TEXT:  
fffff880`030febb0 fffff880`047c6575 : 00000000`00000000 00000000`c0000001 fffffa80`04ec6410 fffffa80`061d2d50 : dxgmms1!VIDMM_GLOBAL::StartPreparation+0xf
fffff880`030febe0 fffff880`047c63b3 : fffff880`07eec1e8 fffff880`047b5251 00000000`0000000f fffff880`031d7f40 : dxgmms1!VIDMM_GLOBAL::ProcessSystemCommand+0x31
fffff880`030fec70 fffff880`047e0231 : fffffa80`04ec6410 fffffa80`073e5010 00000000`0000000f fffff880`047e1f09 : dxgmms1!VidMmiProcessSystemCommand+0x47
fffff880`030feca0 fffff880`047df3bc : fffff880`031d7f40 fffffa80`061d2d50 00000000`00000000 fffffa80`04ec6410 : dxgmms1!VidSchiSubmitSystemCommand+0x39
fffff880`030fecd0 fffff880`047dee96 : 00000000`0000c2dd fffffa80`073e5010 00000000`00000080 fffffa80`04ec6410 : dxgmms1!VidSchiSubmitQueueCommand+0x74
fffff880`030fed00 fffff800`03166f7a : 00000000`021da62f fffffa80`05b4db60 fffffa80`01bf8840 fffffa80`05b4db60 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`030fed40 fffff800`02ebd9c6 : fffff880`031d3180 fffffa80`05b4db60 fffff880`031ddfc0 fffff880`01438384 : nt!PspSystemThreadStartup+0x5a
fffff880`030fed80 00000000`00000000 : fffff880`030ff000 fffff880`030f9000 fffff880`030fe7c0 00000000`00000000 : nt!KiStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::StartPreparation+f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1

STACK_COMMAND:  .cxr 0xfffff880030fe1d0 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::StartPreparation+f

BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::StartPreparation+f

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

 

before the crash i was streaming video in the background while playing runescape and had left open eclipse and foxit reader for homework purposes, as for the log me in i installed it last semester, if i get any other mini's ill be sure to upload them, I will check the drivers later tonight or tommarrow once i have time i have to get the java homework i was doing in eclipse done.

 

It is a directx file, so you can be reasonably certain its gpu related. If it persists, you may want to try rolling back the driver. It is an Intel integrated gpu, and Windows Update LOVES to suggest those drivers. The problem is, laptops work better with drivers from the OEM.

You could also try the Acer or Intel site and try reinstalling the drivers. If worse comes to worst, you could disable the graphics card in Device Manager and use the UGA drivers provided by Windows. The downside is that you can kiss any sort of hardware acceleration goodbye.

It is interesting that an Intel integrated GPU is giving you issues. My laptop runs an AMD radeon and Intel gpu on switchable graphics. Whenever I want stability, I switch to Intel. It also improves battery but thats not relevant.

 

i checked on 12/13/11 there was a intel display driver update run i will roll it back when i get back from dinner im leaving in like 2 mins

 

Or you could go the other way and install the latest Intel driver (8.15.10.2656) from http://downloadcenter.intel.com/Sea...+Graphics&ProdId=3231&LineId=1101&FamilyId=39