Laptop crashes...BSOD during game


  1. Posts : 1
    Windows 7 Home Premium x64
       #1

    Laptop crashes...BSOD during game


    Hi! My laptop randomly crashes when i play games. Bugcheck says it is probably caused
    by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+17f ). I get BSOD sometimes after 5-10 mins or sometimes after hour/s of gameplay. Games are Cabal Online and DotA. Please help. I dont get this BSOD when i play this games on my desktop PC.

    Laptop Specs:
    TOSHIBA Satellite L510
    Intel i3 M 330 2.13GHZ
    Windows 7 Home Premium x64
    2048MB RAM
    ATI Mobility Radeon HD 5145
    Last edited by OdaNobunaga; 08 Apr 2011 at 15:27.
      My Computer


  2. Posts : 28,845
    Win 8 Release candidate 8400
       #2

    OdaNobunaga said:
    Hi! My laptop randomly crashes when i play games. Bugcheck says it is probably caused
    by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+17f ). I get BSOD sometimes after 5-10 mins or sometimes after hour/s of gameplay. Games are Cabal Online and DotA. Please help. I dont get this BSOD when i play this games on my desktop PC.

    Laptop Specs:
    TOSHIBA Satellite L510
    Intel i3 M 330 2.13GHZ
    Windows 7 Home Premium x64
    2048MB RAM
    ATI Mobility Radeon HD 5145
    You are accurate this one was caused by your video driver. remove and replace using these

    When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper

    When it is removed then download and install the fresh copy.


    Code:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\040911-29187-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;srv*e:\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.17514.amd64fre.win7sp1_rtm.101119-1850
    Machine Name:
    Kernel base = 0xfffff800`03658000 PsLoadedModuleList = 0xfffff800`0389de90
    Debug session time: Fri Apr  8 12:58:08.656 2011 (GMT-4)
    System Uptime: 0 days 0:18:34.248
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .....................................
    Loading User Symbols
    Loading unloaded module list
    .....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 50, {fffffaa00a5e3218, 1, fffff88004a1b507, 5}
    
    
    Could not read faulting driver name
    Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+17f )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced.  This cannot be protected by try-except,
    it must be protected by a Probe.  Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: fffffaa00a5e3218, memory referenced.
    Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
    Arg3: fffff88004a1b507, If non-zero, the instruction address which referenced the bad memory
        address.
    Arg4: 0000000000000005, (reserved)
    
    Debugging Details:
    ------------------
    
    
    Could not read faulting driver name
    
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800039090e8
     fffffaa00a5e3218 
    
    FAULTING_IP: 
    dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+17f
    fffff880`04a1b507 488908          mov     qword ptr [rax],rcx
    
    MM_INTERNAL_CODE:  5
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x50
    
    PROCESS_NAME:  cabalmain.exe
    
    CURRENT_IRQL:  0
    
    TRAP_FRAME:  fffff88008f1c480 -- (.trap 0xfffff88008f1c480)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffffaa00a5e3218 rbx=0000000000000000 rcx=fffffaa00a5e3218
    rdx=fffffa8005ccb000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff88004a1b507 rsp=fffff88008f1c610 rbp=0000000000000001
     r8=fffffa8005d3b3c0  r9=0000000000000001 r10=0000000000000018
    r11=fffff88008f1c5e0 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na po nc
    dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+0x17f:
    fffff880`04a1b507 488908          mov     qword ptr [rax],rcx ds:d000:fffffaa0`0a5e3218=????????????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80003682c6f to fffff800036d8640
    
    STACK_TEXT:  
    fffff880`08f1c318 fffff800`03682c6f : 00000000`00000050 fffffaa0`0a5e3218 00000000`00000001 fffff880`08f1c480 : nt!KeBugCheckEx
    fffff880`08f1c320 fffff800`036d676e : 00000000`00000001 fffffaa0`0a5e3218 fffff880`00000000 fffffa80`01871e10 : nt! ?? ::FNODOBFM::`string'+0x44891
    fffff880`08f1c480 fffff880`04a1b507 : fffffa80`01871e10 fffffa80`01871e10 fffff8a0`042a1010 00000000`00000001 : nt!KiPageFault+0x16e
    fffff880`08f1c610 fffff880`04a01ecc : 00000000`00000000 00000000`00000000 fffffa80`05841950 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+0x17f
    fffff880`08f1c6e0 fffff880`0510cccc : 00000000`00000000 fffff8a0`038d4000 fffff8a0`038d4000 00000000`00000001 : dxgmms1!VidMmCloseAllocation+0x44
    fffff880`08f1c710 fffff880`0510c65f : fffff8a0`038d4000 fffff8a0`038d5300 fffff8a0`00000000 00000000`00000000 : dxgkrnl!DXGDEVICE::DestroyAllocations+0x248
    fffff880`08f1c800 fffff880`0510c8e1 : fffff8a0`038d4000 fffff8a0`038d4000 00000000`00000001 00000000`00000000 : dxgkrnl!DXGDEVICE::ProcessTerminationList+0xa3
    fffff880`08f1c850 fffff880`0511079c : fffff8a0`0b01a600 fffff880`08f1cca0 fffffa80`05c76000 fffff880`050d73af : dxgkrnl!DXGDEVICE::TerminateAllocations+0xb9
    fffff880`08f1c8a0 fffff880`05112e57 : fffff8a0`038d4000 fffff880`08f1c9b0 00000000`7efdb001 fffff880`050d8001 : dxgkrnl!DXGDEVICE::DestroyAllocation+0x448
    fffff880`08f1c930 fffff960`0023c882 : 00000000`0008fd20 fffffa80`06f4c550 00000000`00000020 00000000`73775f08 : dxgkrnl!DxgkDestroyAllocation+0x9bf
    fffff880`08f1cbf0 fffff800`036d78d3 : 00000000`00000001 00000000`2bc35bdf 00000000`2f282701 00000000`2bc35be0 : win32k!NtGdiDdDDIDestroyAllocation+0x12
    fffff880`08f1cc20 00000000`7379120a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`0008e2f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7379120a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+17f
    fffff880`04a1b507 488908          mov     qword ptr [rax],rcx
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+17f
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: dxgmms1
    
    IMAGE_NAME:  dxgmms1.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1
    
    FAILURE_BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+17f
    
    BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+17f
    
    Followup: MachineOwner
    ---------
    
    0: kd> lmvm dxgmms1
    start             end                 module name
    fffff880`04a00000 fffff880`04a46000   dxgmms1    (pdb symbols)          c:\symbols\dxgmms1.pdb\0901C357E9E846EE8C2FBCC8107163201\dxgmms1.pdb
        Loaded symbol image file: dxgmms1.sys
        Mapped memory image file: C:\Symbols\dxgmms1.sys\4CE799C146000\dxgmms1.sys
        Image path: \SystemRoot\System32\drivers\dxgmms1.sys
        Image name: dxgmms1.sys
        Timestamp:        Sat Nov 20 04:49:53 2010 (4CE799C1)
        CheckSum:         00047A89
        ImageSize:        00046000
        File version:     6.1.7601.17514
        Product version:  6.1.7601.17514
        File flags:       0 (Mask 3F)
        File OS:          40004 NT Win32
        File type:        3.7 Driver
        File date:        00000000.00000000
        Translations:     0409.04b0
        CompanyName:      Microsoft Corporation
        ProductName:      Microsoft® Windows® Operating System
        InternalName:     dxgmms1.sys
        OriginalFilename: dxgmms1.sys
        ProductVersion:   6.1.7601.17514
        FileVersion:      6.1.7601.17514 (win7sp1_rtm.101119-1850)
        FileDescription:  DirectX Graphics MMS
        LegalCopyright:   © Microsoft Corporation. All rights reserved.
      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 00:48.
Find Us