Dxgmms1.sys bluescreen and more...

Page 1 of 4 123 ... LastLast

  1. Posts : 20
    Windows 7 Ultimate x64
       #1

    Dxgmms1.sys bluescreen and more...


    Hi, I've had my computer for a year now with no problems until now. Recently, within the past month I had started getting strange bluescreens. They were not very common, but now it is just getting out of hand. I mostly encounter the dxgmms1 bluescreen when playing games (minecraft, battlefield), but things like NEITO.sys at other times. The bluescreens I have gotten are: dxgmms1.sys, NETO.sys, ndis.sys, and ntoskrnl.sys.

    System info
    -64 bit
    -full version
    -year old hardware
    -year old os

    Thanks
      My Computer


  2. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #2

    Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads
    You can use MagicDisc as an alternative.

    Remove TunUP Utilities since it could have messed up your system
    Windows 7 does not need any 'TuneUp' software or whatsoever related utilities
    Run SFC /SCANNOW Command - System File Checker

    Run a scan of Malwarebytes

    Run a RAM test RAM - Test with Memtest86+

    Remove EVGA Precision
    Code:
    sptd.sys        fffff880`010c5000    fffff880`011eb000    0x00126000    0x4ad24632    12/10/2009 00:55:14
    Code:
    TuneUpUtilitiesDriver64.sys        fffff880`09631000    fffff880`09639000    0x00008000    0x4ab2238c    17/09/2009 15:54:52
    Code:
    *******************************************************************************
    *                                                                             *
    *                        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: fffff880055bbfe8, The address that the exception occurred at
    Arg3: fffff88007eb4698, Exception Record Address
    Arg4: fffff88007eb3ef0, 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::ReferenceAllocationForSubmission+98
    fffff880`055bbfe8 48035020        add     rdx,qword ptr [rax+20h]
    
    EXCEPTION_RECORD:  fffff88007eb4698 -- (.exr 0xfffff88007eb4698)
    ExceptionAddress: fffff880055bbfe8 (dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0x0000000000000098)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: ffffffffffffffff
    Attempt to read from address ffffffffffffffff
    
    CONTEXT:  fffff88007eb3ef0 -- (.cxr 0xfffff88007eb3ef0)
    rax=7ffff8a0059e9880 rbx=fffff8a01e0d7e50 rcx=fffffa8006da7fc0
    rdx=0000000000000060 rsi=fffffa80071194d0 rdi=fffffa800a16f000
    rip=fffff880055bbfe8 rsp=fffff88007eb48d0 rbp=0000000000000000
     r8=fffffa8007119520  r9=fffff88007eb4901 r10=0000000000000000
    r11=fffffa800a149410 r12=0000000000000000 r13=0000000000000000
    r14=fffffa800ae7ebb0 r15=0000000000000027
    iopl=0         nv up ei pl nz ac po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010216
    dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0x98:
    fffff880`055bbfe8 48035020        add     rdx,qword ptr [rax+20h] ds:002b:7ffff8a0`059e98a0=????????????????
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_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:  0000000000000000
    
    EXCEPTION_PARAMETER2:  ffffffffffffffff
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003d11100
     ffffffffffffffff 
    
    FOLLOWUP_IP: 
    dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+98
    fffff880`055bbfe8 48035020        add     rdx,qword ptr [rax+20h]
    
    BUGCHECK_STR:  0x7E
    
    LAST_CONTROL_TRANSFER:  from fffff880055b9803 to fffff880055bbfe8
    
    STACK_TEXT:  
    fffff880`07eb48d0 fffff880`055b9803 : 00000000`00000000 fffffa80`10111000 00000000`00000010 fffff8a0`1e0d7e50 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0x98
    fffff880`07eb4910 fffff880`055d365d : 00000000`00000000 fffff8a0`059e9880 fffffa80`00000000 fffffa80`0ae7ebb0 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xd6f
    fffff880`07eb4ae0 fffff880`055d3398 : fffff880`036a8fc0 fffff880`055d2d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
    fffff880`07eb4cd0 fffff880`055d2e96 : 00000000`00000000 fffffa80`0cb57940 00000000`00000080 fffffa80`0a149410 : dxgmms1!VidSchiSubmitQueueCommand+0x50
    fffff880`07eb4d00 fffff800`03d7e32e : 00000000`0461fd69 fffffa80`0a03eb60 fffffa80`06a2b040 fffffa80`0a03eb60 : dxgmms1!VidSchiWorkerThread+0xd6
    fffff880`07eb4d40 fffff800`03ad3666 : fffff880`036a4180 fffffa80`0a03eb60 fffff880`036af040 fffff880`0141e384 : nt!PspSystemThreadStartup+0x5a
    fffff880`07eb4d80 00000000`00000000 : fffff880`07eb5000 fffff880`07eaf000 fffff880`07eb4680 00000000`00000000 : nt!KiStartSystemThread+0x16
    
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+98
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: dxgmms1
    
    IMAGE_NAME:  dxgmms1.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1
    
    STACK_COMMAND:  .cxr 0xfffff88007eb3ef0 ; kb
    
    FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+98
    
    BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+98
    
    Followup: MachineOwner
    ---------
      My Computer


  3. Posts : 20
    Windows 7 Ultimate x64
    Thread Starter
       #3

    Thank you for the reply.
    I removed my ISO mounting program, and I will install the one recommended. I have already ran memtest and got no errors. I also removed TuneUp, but I don't know what EVGA precision is? I will also be running system file checker overnight. By the way--no bluescreens so far.
      My Computer


  4. Posts : 20
    Windows 7 Ultimate x64
    Thread Starter
       #4

    I just got another dxgmms1.sys. Help is appreciated. My minidump is attached. Thanks.
      My Computer


  5. Posts : 20
    Windows 7 Ultimate x64
    Thread Starter
       #5

    Help is still needed please.
      My Computer


  6. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #6

    Do you use RivaTuner/MSI Afterburner? They have known issues with Windows 7
    Remove such software
      My Computer


  7. Posts : 20
    Windows 7 Ultimate x64
    Thread Starter
       #7

    I removed RivaTuner and MSI and now I am waiting to see if I get a bluescreen.
      My Computer


  8. Posts : 20
    Windows 7 Ultimate x64
    Thread Starter
       #8

    I just got another bluescreen dxgmms1.sys while playing Bad Company 2. This is happening pretty often. I also ran SFC and Memtest and they both seemed fine. Thanks.
      My Computer


  9. Posts : 20
    Windows 7 Ultimate x64
    Thread Starter
       #9

    I recently got a SYSTEM_SERVICE_EXCEPTION bluescreen that said ntoskrnl.exe was causing it. This is really a problem now, and I would really like some help. I also tried driver verifier, but it didn't seem to work right.
      My Computer


  10. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #10

    Sneerz said:
    I recently got a SYSTEM_SERVICE_EXCEPTION bluescreen that said ntoskrnl.exe was causing it. This is really a problem now, and I would really like some help. I also tried driver verifier, but it didn't seem to work right.
    Please upload these dumps
      My Computer


 
Page 1 of 4 123 ... LastLast

  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 04:17.
Find Us