1. Welcome to the Starbound support forums. Please check the support FAQs before posting: http://playstarbound.com/support

Closed Bluescreen while playing

Discussion in 'Starbound Support' started by Invidia1990, Dec 19, 2015.

Thread Status:
Not open for further replies.
  1. Invidia1990

    Invidia1990 Orbital Explorer

    Hello,

    starbound crashes a lot if I launch Starbound (not the OPEN-GL) Version. It doesn't matter if 32bit or 64bit.
    When it happens I am in the game playing. Don't doing any specific. The crashdump tells me that it seems to be a memory issue?

    Here the crashdump:
    Code:
    Debugging Details:
    ------------------
    
    TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
    
    FAULTING_IP:
    dxgmms2!VIDMM_CPU_HOST_APERTURE::UnmapRange+3a
    fffff800`65211fba 488b0f          mov     rcx,qword ptr [rdi]
    
    CONTEXT:  ffffd0002704ed00 -- (.cxr 0xffffd0002704ed00)
    rax=ffffd0002704f768 rbx=fffffffffffffe48 rcx=ffffc000be29a420
    rdx=fffffffffffffe48 rsi=ffffc000be29a420 rdi=0000000000000000
    rip=fffff80065211fba rsp=ffffd0002704f720 rbp=ffffc000c8ceb001
    r8=ffffc000c9aa9c01  r9=00000000000007ff r10=ffffd000204af260
    r11=ffffc000bcaadc90 r12=ffffc000be29a480 r13=ffffc000be29a468
    r14=0000000000000000 r15=0000000000000004
    iopl=0         nv up ei pl nz na pe nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
    dxgmms2!VIDMM_CPU_HOST_APERTURE::UnmapRange+0x3a:
    fffff800`65211fba 488b0f          mov     rcx,qword ptr [rdi] ds:002b:00000000`00000000=0000000000007974
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    BUGCHECK_STR:  0x3B
    
    PROCESS_NAME:  starbound.exe
    
    CURRENT_IRQL:  0
    
    BAD_PAGES_DETECTED: 7974
    
    LAST_CONTROL_TRANSFER:  from fffff800652270f1 to fffff80065211fba
    
    STACK_TEXT: 
    ffffd000`2704f720 fffff800`652270f1 : ffffffff`fffffe48 ffffc000`c8ceb0e0 00000000`00000000 ffffc000`be29a420 : dxgmms2!VIDMM_CPU_HOST_APERTURE::UnmapRange+0x3a
    ffffd000`2704f770 fffff800`652776e3 : 00000000`00010000 ffffc000`c8ceb0e0 ffffc000`be29a420 ffffc000`be29a420 : dxgmms2! ?? ::FNODOBFM::`string'+0x4b1
    ffffd000`2704f7c0 fffff800`6528b176 : ffffc000`c8ceb0e0 ffffc000`c6611010 ffffc000`c8ceb0e0 ffffc000`c6611010 : dxgmms2!VIDMM_GLOBAL::BuildMdlForAllocInCpuHostAperture+0x3f
    ffffd000`2704f800 fffff800`6528309c : ffffc000`c8ceb0e0 00000000`00000000 ffffe000`c7448ac0 00000000`00000000 : dxgmms2!VIDMM_GLOBAL::LockAllocInCpuHostAperture+0x32
    ffffd000`2704f880 fffff800`6525dfc5 : ffffc000`c955da10 ffffc000`c955da10 ffffe000`c7448ac0 ffffd000`2704fa68 : dxgmms2! ?? ::NNGAKEGL::`string'+0x296c
    ffffd000`2704f910 fffff800`664a0f39 : ffffd000`2704fb80 ffffe000`c7448ac0 ffffc000`c8506180 ffffe000`00000002 : dxgmms2!VIDMM_GLOBAL::Lock+0x345
    ffffd000`2704f9d0 fffff800`6651ac02 : ffffc000`c5a94660 ffffc000`c9d0c010 00000000`00000000 00000000`00000020 : dxgkrnl!VIDMM_EXPORT::VidMmLock+0x49
    ffffd000`2704fa10 fffff800`6cddcfa3 : 000000fa`6abee8f0 00000000`00000837 ffffc000`c8506180 ffffc000`c9d0c010 : dxgkrnl!DxgkLock2+0x4d2
    ffffd000`2704fb00 00007ff9`cb4840d4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    000000fa`6abee8c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7ff9`cb4840d4
    
    
    SYMBOL_NAME:  PAGE_NOT_ZERO
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: Unknown_Module
    
    IMAGE_NAME:  Unknown_Image
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    STACK_COMMAND:  .cxr 0xffffd0002704ed00 ; kb
    
    BUCKET_ID:  PAGE_NOT_ZERO
    
    Followup: MachineOwner
    ---------
    
    *** Memory manager detected 31092 instance(s) of page corruption, target is likely to have memory corruption.
    No other games are having issues, so I am pretty sure that it's not related to my machine. (Battlefield 4, Fallout 4, Skyrim).

    My computer:

    Windows 10 Professional 64bit
    Intel Core i5 4690k (not OCed)
    2x GTX 770
    16GB RAM

    If more information is needed tell me. Problems dont occur if I use OPEN-GL Version so far.
     
  2. sesharim

    sesharim Space Hobo

    hi there , have the same problem bluesrceen while playing , win 10 64 home. it happens most the time when i enter a portal or klick on a shop . when im wlking on the planets everything is fine. only when i interact with portal or shop this happens, but not everytime total random.
     
  3. lazarus78

    lazarus78 The Waste of Time

    Windows 10 has a known issue with DirectX. This issue can be triggered by Starbound but is not the fault of Starbound. It is a Windows issue.

    If in doubt, as per your crash log, google dxgmms2.dll crash.
     
  4. irongamer

    irongamer Scruffy Nerf-Herder

    Is there more specific information about this issue? I have not had this error on any other title. The error triggers fairly reliably: load the outpost about 4 times and/or play for ~10-15 minutes and Starbound crashes.

    • New bios driver
    • Clean install of new nvidia driver
    • Tried with and without Steam overlay
    • No memory error reported by Windows Memory Diagnostic
    Win 10 64bit
    i5-4690
    GTX 760
    8GB Ram
     
    Last edited: Dec 31, 2015
  5. lazarus78

    lazarus78 The Waste of Time

    It depends on what exactly dxgmms2.dll does. It may not be called up by many other games. This crash issue does appear in other games such as World of Warcraft.
     
Thread Status:
Not open for further replies.

Share This Page