Closed Reboot Crash - System Service Exception - dxgmms.sys

Is anyone else running into this error?

• Windows 10 64bit
• Glad Giraffe, Update 3
• Using Normal launch or 64 bit launch.

This bug causes windows to crash and my system to reboot. It happens most often in the Outpost. It also leaves the last sound repeating in a stutter.

The error windows displays before it reboots is "System Service Exception: dxgmms.sys".

I updated to the latest Nvidia drivers and still had the same crash. This time it crashed while at the bottom of an ocean.

 

i too have ran into this mine happen on glad giraffe update 1

 

I have the same issue. I've checked my drivers, even going so far as to reinstall the nvidia driver. My crash always happens when I go to the desert planet in my starting solar system. It gets really laggy then BSODs. According to Windows, it's a driver issue.

I'm on Windows 10 64 bit
Glad Giraffe Update 3

 

Someone suggested renaming the "giraffe_storage" file in the starbound folder as anything else. HOWEVER, that only prompts the game to make a new one, and that's essentially wiping your characters and universe. So don't do that.

 

i found that it is only on windows 10 my friend is on windows 7 and he as no problems

 

I basically did a fresh install for this Glad Giraffe and thus started with a new character as well. So, this bug is happening with a clean fresh start.

 

This is an issue with your drivers rather than the game itself. If you've already reinstalled the latest version of your drivers, check to make sure they didn't install extra "utilities" that might interfere (example: ASUS (I think?) had a "utility" that would try to add overlay support or something like that to games and was causing the crash, you can search the Support forum here to find the details).

This is a common suggestion as it does give the game a fresh start (as if it was a new install) which helps narrow down the cause of an issue. Your saves are still there, just delete the new folder and rename your old one back (that's why it said rename, not delete, your folder initially).

 

Would the trend that it's on Windows 10 mean anything as far as the driver issue goes?

 

Same problem for me lately, Windows 10 64bit, Glad Giraffe Update 3 and always using the 64-bit version. I get blue screens for dxgmms2.sys that have been happening all week and got 3 in a row in the last hour.
Found a thread on reddit about it and someone mentioned that starting the game in OpenGL mode fixes it since DirectX is having problems.

Going to test that out with running it via 64-bit OpenGL.

Update edit: I can confirm so far OpenGL mode has not caused any BSOD so far.

 

I have the same issue, I randomly crash whenever I try and play the game. Sometimes I can play for up to an hour, sometimes I barely make it down to the surface of the planet. And every time I try and open the game in OpenGL mode I get stuck at the loading screen that immediately follows the chuckling fish. The game refuses to open in OpenGL mode, does anyone know what the hell is wrong?

 

Came back to confirm that OpenGL is working for me in place of DirectX. Maybe someone could explain why that would be?

 

In other forums theres description how to fix it!

http://nzgeek.org/blog/dxgmms1-sys-crash-blue-screen-of-death/

The problem is both is damaged the graca drives and direct x...

https://www.nvidia.com/content/global/global.php

http://www.amd.com/

https://www.microsoft.com/en-us/download/confirmation.aspx?id=17431

 

That post is from 2009 and includes fixes for Windows 7 and Server 2008. I'm running Win 10 with an Intel chip, not AMD. Also, this only happens in Starbound so far. Other games I've been playing recently that have never crashed the system include X-Com Enemy Within and Fallout 4 (yeah, amazing for a Bethesda game).

I've done a fresh install of nvidia drivers, updated my bios, and scanned for bad memory. I've now disabled the steam overlay to see if that does it. If that doesn't I'll give openGL a shot since others seem to be having success with that option. I'll report back later.[DOUBLEPOST=1451500614][/DOUBLEPOST]Disabling steam overlay didn't do it. I guess its openGL for me as well. Will report back on findings.

 

First and foremost, this looks to be a memory reference issue. I also recommend using the OpenGL option, if you can. Additional details below.

-

I get a similar error (with dxgmms2, as opposed to dxgmms). Happens pretty consistently when running the 64-bit version while playing a youtube video at the same time, may be just a coincidence.

Another thread also covers this issue, lazarus78 indicates it's a problem with windows and directX, so maybe it's not a problem directly with Starbound: http://community.playstarbound.com/threads/bluescreen-while-playing.103896/

Anyway, I happen to sort of know my way around windbg and was able to get some info for my crash dump, thought I'd share some additional info I found. if nothing else maybe it will help other people googling this issue catch this thread and get some answers. Maybe this will help a developer debug, who knows.

-

The long and short of it is, the DEFAULT_BUCKET_ID (Which I translate as being the overall problem) is WIN8_DRIVER_FAULT. It makes sense that this is causing issues, since I'm running windows 10 (build 10586).
More specific error message is the FAILURE_BUCKET_ID is 0x3B_dxgmms2!VIDMM_CPU_HOST_APERTURE::UnmapRange. This, paired with the exception code, "The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.", makes me think that this is a memory reference problem. At least, The percent signs make me think it's talking about registers, or maybe this is just how windbg represents memory references and so it's not really supposed to be obvious/human readable.

Anyway, also including the !analyze -v windbg command output of debugging the memory dump, I edited some bits that are specific to my machine, can't be too careful on the internet.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff800b0961fba, Address of the instruction which caused the bugcheck
Arg3: ffffd00021426d00, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Debugging Details:
------------------

Page 3f73 not present in the dump file. Type ".hh dbgerr004" for details
Page 48a8 not present in the dump file. Type ".hh dbgerr004" for details
Page 1f00 not present in the dump file. Type ".hh dbgerr004" for details
Page 1f00 not present in the dump file. Type ".hh dbgerr004" for details
Page 1f00 not present in the dump file. Type ".hh dbgerr004" for details
Page 1f00 not present in the dump file. Type ".hh dbgerr004" for details
Page 1f00 not present in the dump file. Type ".hh dbgerr004" for details
Page 1f00 not present in the dump file. Type ".hh dbgerr004" for details

DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING:  10586.17.amd64fre.th2_release.151121-2308

SYSTEM_MANUFACTURER:  System manufacturer

SYSTEM_PRODUCT_NAME:  System Product Name

SYSTEM_SKU:  SKU

SYSTEM_VERSION:  System Version

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  0502

BIOS_DATE:  08/31/2011

BASEBOARD_MANUFACTURER:  ASUSTeK Computer INC.

BASEBOARD_PRODUCT:  P8Z68-M PRO

BASEBOARD_VERSION:  Rev 1.xx

DUMP_TYPE:  1

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff800b0961fba

BUGCHECK_P3: ffffd00021426d00

BUGCHECK_P4: 0

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

FAULTING_IP:
dxgmms2!VIDMM_CPU_HOST_APERTURE::UnmapRange+3a
fffff800`b0961fba 488b0f          mov     rcx,qword ptr [rdi]

CONTEXT:  ffffd00021426d00 -- (.cxr 0xffffd00021426d00)
rax=ffffd00021427768 rbx=fffffffffffffe48 rcx=ffffc000af4a85b0
rdx=fffffffffffffe48 rsi=ffffc000af4a85b0 rdi=0000000000000000
rip=fffff800b0961fba rsp=ffffd00021427720 rbp=ffffc000bd4bea01
r8=ffffc000b1adb501  r9=00000000000007ff r10=ffffd000c1868260
r11=ffffc000b7be60a0 r12=ffffc000af4a8610 r13=ffffc000af4a85f8
r14=0000000000000000 r15=0000000000000002
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`b0961fba 488b0f          mov     rcx,qword ptr [rdi] ds:002b:00000000`00000000=????????????????
Resetting default scope

CPU_COUNT: 4

CPU_MHZ: c26

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 2a

CPU_STEPPING: 7

CPU_MICROCODE: 6,2a,7,0 (F,M,S,R)  SIG: 29'00000000 (cache) 29'00000000 (init)

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  starbound.exe

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  [REDACTED]

ANALYSIS_SESSION_TIME:  12-30-2015 22:02:16.0430

ANALYSIS_VERSION: 10.0.10586.567 amd64fre

LAST_CONTROL_TRANSFER:  from fffff800b09770f1 to fffff800b0961fba

STACK_TEXT: 
ffffd000`21427720 fffff800`b09770f1 : ffffffff`fffffe48 ffffc000`bd4beab0 00000000`00000000 ffffc000`af4a85b0 : dxgmms2!VIDMM_CPU_HOST_APERTURE::UnmapRange+0x3a
ffffd000`21427770 fffff800`b09c76e3 : 00000000`00010000 ffffc000`bd4beab0 ffffc000`af4a85b0 ffffc000`af4a85b0 : dxgmms2! ?? ::FNODOBFM::`string'+0x4b1
ffffd000`214277c0 fffff800`b09db176 : ffffc000`bd4beab0 ffffc000`b2045720 ffffc000`bd4beab0 ffffc000`b2045720 : dxgmms2!VIDMM_GLOBAL::BuildMdlForAllocInCpuHostAperture+0x3f
ffffd000`21427800 fffff800`b09d309c : ffffc000`bd4beab0 00000000`00000000 ffffe000`ec8f85d0 00000000`00000000 : dxgmms2!VIDMM_GLOBAL::LockAllocInCpuHostAperture+0x32
ffffd000`21427880 fffff800`b09adfc5 : ffffc000`b0da2970 ffffc000`b0da2970 ffffe000`ec8f85d0 ffffd000`21427a68 : dxgmms2! ?? ::NNGAKEGL::`string'+0x296c
ffffd000`21427910 fffff800`aedb0f39 : ffffd000`21427b80 ffffe000`ec8f85d0 ffffc000`b8d2a770 ffffe000`00000002 : dxgmms2!VIDMM_GLOBAL::Lock+0x345
ffffd000`214279d0 fffff800`aee2ac02 : ffffc000`bba8b010 ffffc000`bd440010 00000000`00000000 00000000`00000020 : dxgkrnl!VIDMM_EXPORT::VidMmLock+0x49
ffffd000`21427a10 fffff803`56558fa3 : 00000078`db99e590 00000000`00000837 ffffc000`b8d2a770 ffffc000`bd440010 : dxgkrnl!DxgkLock2+0x4d2
ffffd000`21427b00 00007ff8`c84140d4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000078`db99e568 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`c84140d4


THREAD_SHA1_HASH_MOD_FUNC:  69872e51025587be6030dc1777c1568a596058a3

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  e4cb736e11f28fee691da0e9e353734806bb4de0

THREAD_SHA1_HASH_MOD:  358fb887d3297987c4802221af23b590eede0916

FOLLOWUP_IP:
dxgmms2!VIDMM_CPU_HOST_APERTURE::UnmapRange+3a
fffff800`b0961fba 488b0f          mov     rcx,qword ptr [rdi]

FAULT_INSTR_CODE:  480f8b48

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  dxgmms2!VIDMM_CPU_HOST_APERTURE::UnmapRange+3a

FOLLOWUP_NAME:  [REDACTED]

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5632d236

IMAGE_VERSION:  10.0.10586.0

STACK_COMMAND:  .cxr 0xffffd00021426d00 ; kb

BUCKET_ID_FUNC_OFFSET:  3a

FAILURE_BUCKET_ID:  0x3B_dxgmms2!VIDMM_CPU_HOST_APERTURE::UnmapRange

BUCKET_ID:  0x3B_dxgmms2!VIDMM_CPU_HOST_APERTURE::UnmapRange

PRIMARY_PROBLEM_CLASS:  0x3B_dxgmms2!VIDMM_CPU_HOST_APERTURE::UnmapRange

TARGET_TIME:  2015-12-30T05:35:40.000Z

OSBUILD:  10586

OSSERVICEPACK:  0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE: 

USER_LCID:  0

OSBUILD_TIMESTAMP:  2015-11-22 01:24:24

BUILDDATESTAMP_STR:  151121-2308

BUILDLAB_STR:  th2_release

BUILDOSVER_STR:  10.0.10586.17.amd64fre.th2_release.151121-2308

ANALYSIS_SESSION_ELAPSED_TIME: 108c

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x3b_dxgmms2!vidmm_cpu_host_aperture::unmaprange

FAILURE_ID_HASH:  {137d5227-112d-13b6-b9e2-66eebf9d349f}

 

@irongamer
the Link for amd is the only way for ati graca drivers... send that all because you didn't send any info about your system until that point...
and it goes about the problem it self, and how others fixed that.
I'm just trying to help take it or leave it!

But running win10 says everything...
No crashes on games from "bigger" producers, yeah but only in the fact of having a lot
more resources to be prepared for MS's next travelling bug...
Starbound is still an indie project in beta phase...
think about that...

 

Hey InnocentForScratchers, nothing personal. Just mentioning that the link was for other specs. I did mention Windows 10 in my first post. Also, I'm not poo pooing on Starbound when I mention other titles. I'm just trying to give some more data points.

 

Well,the error is caused by starbound honestly,my first blue screen ever(then,the other followed,again,while playing starbound)
Also this crash can reset your universe,how fun,riiight?

edit:well,this time the thing deleted my char..aww.

 

Yeah, it did blow away the universe on one crash, but I haven't seen it do that since.

 

Yup first BSOD [SYSTEM_SERVICE_EXCEPTION: dxgmms2.sys] in a year, been playing CSGO, Trove, and many games daily and no BSOD until I started hosting a Starbound server. Specifically, I got the exact same BSOD about 4 times ever since I got the game 2 days ago.

P.S. Instead of using the normal 64-bit Launch, try the OPENGL 64-bit. I have not got BSOD all day which may suggest that there is something wrong between DirectX and Nvidia driver.

Update: 2 days of rigorous playing and no BSOD with OpenGL

 

Yes,using OpenGL 64 bit not only stop the crash,but,greatly increase the performance.Starbound probably have problem with the recent nvidia driver.