BSOD dxgmms1.sys randomly


  1. Posts : 5
    Windows 7 Pro 32bits
       #1

    BSOD dxgmms1.sys randomly


    My DELL M1330 is randomly crashing (always BSOD)
    I changed the wifi card, the battery, and the RAM Module (I've just bought crucial 4Gb kit).
    I reinstalled Windows 7, and I installed the minimal drivers :
    - gpu drivers from the nvidia website
    - Rocoh drivers from a website on the net (the drivers on dell pages is just for windows XP)
    - Synaptics from their website
    - Logitech drivers
    And that's all.

    I uploaded the file as suggested

    Please help me
      My Computer

  2.    #2

    Code:
    BugCheck 1000007E, {c0000005, 927acec6, 903329f0, 903325d0}
    
    Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::StartPreparation+c )
    Code:
    Usual causes:  Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control
    Code:
    EXCEPTION_RECORD:  903329f0 -- (.exr 0xffffffff903329f0)
    ExceptionAddress: 927acec6 (dxgmms1!VIDMM_GLOBAL::StartPreparation+0x0000000c)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 00000001
       Parameter[1]: 112a2c51
    Attempt to write to address 112a2c51
    It appears that a device driver has attempted to access and write to a invalid memory address.

    Code:
    1: kd> lmvm nvlddmkm
    start    end        module name
    91e10000 926e3000   nvlddmkm T (no symbols)           
        Loaded symbol image file: nvlddmkm.sys
        Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
        Image name: nvlddmkm.sys
        Timestamp:        Fri Jun 21 10:03:10 2013 (51C416CE)
        CheckSum:         008A7D0D
        ImageSize:        008D3000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    I would roll back to a older WHQL driver, which is available to download from here - NVIDIA Driver Downloads - Advanced Search

    Remove:

    Code:
    Start Menu\Programs\DAEMON Tools Lite
    Arc said:
    Download SPTD standalone installer from Disk-Tools.com, and execute the downloaded file as guided below :
    • Double click to open it.
    • Click this button only:
    • If it is grayed out, as in the picture, there is no more SPTD in your system, and you just close the window.
    Daemon Tools uses a driver called sptd.sys, which is known to cause BSODs with Windows 7. It is recommend you remove this program, and use Windows own in-built features or ImgBurn.

    Where did you download the drivers from?
      My Computer


  3. Posts : 5
    Windows 7 Pro 32bits
    Thread Starter
       #3

    Thanks for your fast answer, I will do what you suggest and come back here very soon to tell if bsod happened again or not
      My Computer

  4.    #4

    I will look forward to your results :)
      My Computer


  5. Posts : 5
    Windows 7 Pro 32bits
    Thread Starter
       #5

    I did what you did but I had a new BSOD screen (not same error).
    I had also an other one just before.

    Hope you will find my problem

    Thanks in advance for that
      My Computer

  6.    #6

    BSOD Analysis:

    Code:
    BugCheck E3, {88ba13b0, 85874030, 899844f0, 3}
    
    Probably caused by : win32k.sys ( win32k!GreReleaseSemaphoreInternal+a )
    Code:
    Usual causes:  Device driver
    A thread has attempted to release a lock on a resource in which it didn't own. The blue text highlights the address of the resource, and the green text indicates the thread which attempted to release the resource which it didn't rightfully own. The resource seems to be protected a Semaphore object, which only allows a certain number of threads to have access.

    Code:
    1: kd> k
    ChildEBP RetAddr  
    ae051c84 82ab496e nt!ExpReleaseResourceForThreadLite+0x23e
    ae051c8c 82ac5454 nt!ExReleaseResourceLite+0xf
    ae051c90 9b644377 nt!ExReleaseResourceAndLeaveCriticalRegion+0x5
    ae051c94 9b654ea9 win32k!GreReleaseSemaphoreInternal+0xa
    ae051ce4 9b65520d win32k!GreCreateDisplayDC+0x359
    ae051d04 9b6550cd win32k!UserGetDesktopDC+0xf4
    ae051d28 82a788a6 win32k!GreCreateCompatibleDC+0x61
    ae051d28 77617094 nt!KiSystemServicePostCall
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    00183a34 00000000 0x77617094
    Code:
    1: kd> dt nt!_ERESOURCE 88ba13b0
       +0x000 SystemResourcesList : _LIST_ENTRY [ 0x88ba1360 - 0x88ba1400 ]
       +0x008 OwnerTable       : 0x899844f0 _OWNER_ENTRY
       +0x00c ActiveCount      : 0n0
       +0x00e Flag             : 0
       +0x010 SharedWaiters    : 0x899b1b10 _KSEMAPHORE
       +0x014 ExclusiveWaiters : 0x89b29188 _KEVENT
       +0x018 OwnerEntry       : _OWNER_ENTRY
       +0x020 ActiveEntries    : 0
       +0x024 ContentionCount  : 0x48
       +0x028 NumberOfSharedWaiters : 0
       +0x02c NumberOfExclusiveWaiters : 0
       +0x030 Address          : (null) 
       +0x030 CreatorBackTraceIndex : 0
       +0x034 SpinLock         : 0xae051c74
    Code:
    1: kd> dt nt!_OWNER_ENTRY 0x899844f0
       +0x000 OwnerThread      : 0 <-- No owner?
       +0x004 IoPriorityBoosted : 0y1
       +0x004 OwnerReferenced  : 0y1
       +0x004 OwnerCount       : 0y000000000000000000000000000000 (0)
       +0x004 TableSize        : 3
    I was attempting to find the owning thread, but I couldn't seem to getting anywhere, since the !locks extension won't work with a Minidump. Or maybe, there was no owning thread, and the current thread attempted to release a resource it didn't even acquire.

    --------------------------------------------------------------------------

    Code:
    1: kd> lmvm nvlddmkm
    start    end        module name
    9500b000 959fa000   nvlddmkm T (no symbols)           
        Loaded symbol image file: nvlddmkm.sys
        Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
        Image name: nvlddmkm.sys
        Timestamp:        Sat Oct 15 07:34:27 2011 (4E992973)
        CheckSum:         009DBCBF
        ImageSize:        009EF000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Is this a WHQL driver? The driver still seems to be causing problems, I believe there's a WHQL driver around January 2013 for nVidia.

    Run Driver Verifier to scan for any corrupted drivers which may be causing problems, this program works by running various stress tests on drivers, in order to produce a BSOD which will locate the driver; run for least 24 hours:

       Information
      My Computer


  7. Posts : 5
    Windows 7 Pro 32bits
    Thread Starter
       #7

    I did what you asked :
    - Installed a driver WHQL from january for my graphic card
    - Run verifier.exe and totally uninstall daemon tools because the driver was crashing the computer
    - Run verifier.exe again and I had only one BSOD and my graphic card driver hang some time...

    Hope you will find the problem
      My Computer

  8.    #8

    Code:
    BugCheck C9, {23e, 85ed0310, 9eafaf68, 0}
    
    *** WARNING: Unable to verify timestamp for GEARAspiWDM.sys
    *** ERROR: Module load completed but symbols could not be loaded for GEARAspiWDM.sys
    *** WARNING: Unable to verify timestamp for dtsoftbus01.sys
    *** ERROR: Module load completed but symbols could not be loaded for dtsoftbus01.sys
    Probably caused by : dtsoftbus01.sys ( dtsoftbus01+1310 )
    This bugcheck indicates that Driver Verifier has found a I/O violation, more specifically, we can see that the that device driver has marked a IRP pending but didn't return the STATUS_PENDING flag. More Information - The NT Insider:Properly Pending IRPs - IRP Handling for the Rest of Us

    --------------------------------------------------------------------------------

    Okay, I see you removed Daemon Tools which is good.

    Code:
    0: kd> lmvm GEARAspiWDM
    start    end        module name
    931a0000 931a5300   GEARAspiWDM T (no symbols)           
        Loaded symbol image file: GEARAspiWDM.sys
        Image path: \SystemRoot\system32\DRIVERS\GEARAspiWDM.sys
        Image name: GEARAspiWDM.sys
        Timestamp:        Thu May 03 20:55:59 2012 (4FA2E2CF)
        CheckSum:         0001012F
        ImageSize:        00005300
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    This driver belongs to either iTunes or something related to a CD-ROM driver by Gear Software - GEAR Software - DVD Mastering Software & CD Burning Software & GEAR PRO Mastering

    I would update the driver/program if possible.

    Stop 0x7E:

    Code:
    0: kd> lmvm nvlddmkm
    start    end        module name
    8e03d000 8e8da000   nvlddmkm T (no symbols)           
        Loaded symbol image file: nvlddmkm.sys
        Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
        Image name: nvlddmkm.sys
        Timestamp:        Sat Dec 29 06:49:51 2012 (50DE928F)
        CheckSum:         00881536
        ImageSize:        0089D000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Please update your nVidia graphics card driver to the latest WHQL version, which is now the 1st of July:

    Version: 320.49
    Release Date for Desktops and Notebooks : July 1st 2013
    In Device Manager: 9.18.13.2049
    1. Start Type: Device Manager
    2. Expand Display Adapters
    3. Right-Click Driver Name, Uninstall
    4. Reboot
    5. Run Driver Sweeper
    6. Reboot
    7. Install Downloaded Driver

    Driver Sweeper will scan for any left over files from the old driver, old driver files can cause conflicts with new driver installations. Create a System Restore point beforehand, in case any problems or issues arise.

    Driver Sweeper:
      My Computer


  9. Posts : 5
    Windows 7 Pro 32bits
    Thread Starter
       #9

    Ok I did what you suggest, the system seems to be stable (for now), I will come back in 2 weeks to tell you if a BSOD happened again

    Thanks for your help !
      My Computer

  10.    #10

    Welcome, glad to be able to help :)
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 06:35.
Find Us