4.03 dxgmms2.sys Blue Screen in win10

OwenBrooks · January 19, 2016

There is a thread here has become the defacto swtor thread , only post recently from NVidia was a week ago and is cant reproduce "cough" but given that was from the hotfix thread it is the best place for it to be flagged

close read of that thread and others, can see more programs then just swtor affected.

I hope they sort this soon its an annoyance at best

Edited January 19, 2016 by OwenBrooks

Plantface · January 19, 2016

I have had some success alleviating the problem by running SWTOR in full-screen windowed mode (in settings somewhere) and minimizing the game when traveling in taxi.

Plantface · January 19, 2016

I have had some success alleviating the problem by running SWTOR in full-screen windowed mode (in settings somewhere) and minimizing the game when traveling in taxi.

Nevermind, no success was had.

Eommer · January 19, 2016

this game already have graphics that looks old, special texture. disabling the grass just make me feel worse about this.

its weird how bioware, nvidia, ms dont fix this or even talk about it.

Grimaur · January 20, 2016

Credit to Rosettax on reddit, but they posted a link for for downloading Directx 9.0c from the microsoft site. Installed it a few days ago, maxed out grass quality and haven't crashed since.

Hopefully it helps a few others.

oscuran · January 20, 2016

I thought my card was going bad. Glad to know I am not the only one. Grass to 0 it is!

SpoonKB · January 20, 2016

Thanks for the help I just started playing SWTOR after a really long break and was worried about my machine only had the blue screen crash when I used the whale taxi on Alderan, hopfully this will be fixed soon! But in the meantime guess no grass for me.

OwenBrooks · January 20, 2016

Credit to Rosettax on reddit, but they posted a link for for downloading Directx 9.0c from the microsoft site. Installed it a few days ago, maxed out grass quality and haven't crashed since.

Hopefully it helps a few others.

That is interesting has anyone else tried reapplying the directx redist , that particular redist contains the dx9ex files , be interested if this helps others ?

Edited January 20, 2016 by OwenBrooks

betaku · January 20, 2016

That is interesting has anyone else tried reapplying the directx redist , that particular redist contains the dx9ex files , be interested if this helps others ?

Not really helping...

*******************************************************************************
*                                                                             *
*                        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: fffff800bc7a1fba, Address of the instruction which caused the bugcheck
Arg3: ffffd000232e9d00, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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

Page 1080 not present in the dump file. Type ".hh dbgerr004" for details
Page 1080 not present in the dump file. Type ".hh dbgerr004" for details
Page 1080 not present in the dump file. Type ".hh dbgerr004" for details
Page 1080 not present in the dump file. Type ".hh dbgerr004" for details

DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING:  10586.63.amd64fre.th2_release.160104-1513

SYSTEM_MANUFACTURER:  MSI

SYSTEM_PRODUCT_NAME:  MS-7751

SYSTEM_SKU:  To be filled by O.E.M.

SYSTEM_VERSION:  4.0

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  V17.12

BIOS_DATE:  10/30/2013

BASEBOARD_MANUFACTURER:  MSI

BASEBOARD_PRODUCT:  Z77 MPower (MS-7751)

BASEBOARD_VERSION:  4.0

DUMP_TYPE:  1

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff800bc7a1fba

BUGCHECK_P3: ffffd000232e9d00

BUGCHECK_P4: 0

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - L'instruction   0x%p emploie l'adresse m moire 0x%p. L' tat de la m moire ne peut pas  tre %s.

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

CONTEXT:  ffffd000232e9d00 -- (.cxr 0xffffd000232e9d00)
rax=ffffd000232ea768 rbx=fffffffffffffe48 rcx=ffffc0001e962970
rdx=fffffffffffffe48 rsi=ffffc0001e962970 rdi=0000000000000000
rip=fffff800bc7a1fba rsp=ffffd000232ea720 rbp=ffffc0002b7c0501
r8=ffffc00024fc2901  r9=00000000000007ff r10=ffffd000e1334260
r11=ffffc00024a37620 r12=ffffc0001e9629d0 r13=ffffc0001e9629b8
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`bc7a1fba 488b0f          mov     rcx,qword ptr [rdi] ds:002b:00000000`00000000=????????????????
Resetting default scope

CPU_COUNT: 8

CPU_MHZ: dac

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3a

CPU_STEPPING: 9

CPU_MICROCODE: 6,3a,9,0 (F,M,S,R)  SIG: 1B'00000000 (cache) 1B'00000000 (init)

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  swtor.exe

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  DESKTOP-3TNK862

ANALYSIS_SESSION_TIME:  01-20-2016 11:12:32.0314

ANALYSIS_VERSION: 10.0.10586.567 amd64fre

LAST_CONTROL_TRANSFER:  from fffff800bc7b70f1 to fffff800bc7a1fba

STACK_TEXT:  
ffffd000`232ea720 fffff800`bc7b70f1 : ffffffff`fffffe48 ffffc000`2b7c05c0 00000000`00000000 ffffc000`1e962970 : dxgmms2!VIDMM_CPU_HOST_APERTURE::UnmapRange+0x3a
ffffd000`232ea770 fffff800`bc8076e3 : 00000000`00010000 ffffc000`2b7c05c0 ffffc000`1e962970 ffffc000`1e962970 : dxgmms2! ?? ::FNODOBFM::`string'+0x4b1
ffffd000`232ea7c0 fffff800`bc81b176 : ffffc000`2b7c05c0 ffffc000`2adcb730 ffffc000`2b7c05c0 ffffc000`2adcb730 : dxgmms2!VIDMM_GLOBAL::BuildMdlForAllocInCpuHostAperture+0x3f
ffffd000`232ea800 fffff800`bc81309c : ffffc000`2b7c05c0 00000000`00000000 ffffe000`e4ab2980 00000000`00000000 : dxgmms2!VIDMM_GLOBAL::LockAllocInCpuHostAperture+0x32
ffffd000`232ea880 fffff800`bc7edfc5 : ffffc000`241daa40 ffffc000`241daa40 ffffe000`e4ab2980 ffffd000`232eaa68 : dxgmms2! ?? ::NNGAKEGL::`string'+0x296c
ffffd000`232ea910 fffff800`badf0f39 : ffffd000`232eab80 ffffe000`e4ab2980 ffffc000`23cb2690 ffffe000`00000002 : dxgmms2!VIDMM_GLOBAL::Lock+0x345
ffffd000`232ea9d0 fffff800`bae6ac02 : ffffc000`29cea7d0 ffffc000`2abff010 00000000`00000000 00000000`00000020 : dxgkrnl!VIDMM_EXPORT::VidMmLock+0x49
ffffd000`232eaa10 fffff800`f8dd2fa3 : 00000000`1a91e530 00000000`00000837 ffffc000`23cb2690 ffffc000`2abff010 : dxgkrnl!DxgkLock2+0x4d2
ffffd000`232eab00 00000000`6e397324 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`1a91e508 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x6e397324


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`bc7a1fba 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:  MachineOwner

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5632d236

IMAGE_VERSION:  10.0.10586.0

STACK_COMMAND:  .cxr 0xffffd000232e9d00 ; 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:  2016-01-20T09:55:11.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:  2016-01-05 02:28:56

BUILDDATESTAMP_STR:  160104-1513

BUILDLAB_STR:  th2_release

BUILDOSVER_STR:  10.0.10586.63.amd64fre.th2_release.160104-1513

ANALYSIS_SESSION_ELAPSED_TIME: 1900

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x3b_dxgmms2!vidmm_cpu_host_aperture::unmaprange

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

Always at the same spot in Belsavis...

OwenBrooks · January 20, 2016

Well at least we know now

dmajerus · January 21, 2016

Just adding my name to the mix of this is still happening to me but only since the latest patch. The link you gave to Direct X 9 doesn't specify where to place it in Windows 10 and the few places I've tried so far it says it can't, like Windows>system32

betaku · January 21, 2016

Just adding my name to the mix of this is still happening to me but only since the latest patch. The link you gave to Direct X 9 doesn't specify where to place it in Windows 10 and the few places I've tried so far it says it can't, like Windows>system32

You need to extract the package where you want and launch DXSETUP.

basbaker · January 21, 2016

I just wanted to thank everyone who's been working to pinpoint the problem and possible workarounds for everyone. I've turned my grass down to 0 and so far, so good. Keeping my fingers crossed for a permanent fix!

b-morgan · January 21, 2016

I'm not sure how to make SWTOR use the DX9 files after they have been downloaded and installed. Anyone know?

Terandas · January 23, 2016

Signed, happening to me to while taxiing, belsavis is real bad, happened twice at the same spot.

LilWhyWhy · January 23, 2016

It's good to know this may be a software driver issues and not my hardware. So it's pretty clear that this BSOD is happening on Windows 10 with Nvidia GPUs. I had my BSODs in these places: Balsavis, Coruscant, the Agent's ship. I lowered some settings a little, and haven't gotten a BSOD in 10 days, but last night it came back on Balsavis while riding my speeder around.

On Sat 1/23/2016 10:39:41 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\012316-5906-01.dmp
This was probably caused by the following module: dxgmms2.sys (dxgmms2!VIDMM_CPU_HOST_APERTURE::UnmapRange+0x3A) 
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80063521FBA, 0xFFFFD00027663D00, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\drivers\dxgmms2.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. 
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

My System:

GPU: EVGA GTX 670 2GB

CPU: Intel i5 2400 3.1GHz

RAM: 2x4 8 GB

OS: Windows 10 64x Education Edition

Motherboard: ASRock z75 pro3

I have a feeling this issue won't be resolved and I'll have to roll back to Windows 8.1

OwenBrooks · January 23, 2016

Grass needs to be set to 0 or roll the driver back to 347.88

Fleurdelis · January 24, 2016

Grass set to 0 works so far for me but I don't have a good system to have the grass at 0. I wants muh graz back.

LilWhyWhy · January 24, 2016

Grass set to 0 works so far for me but I don't have a good system to have the grass at 0. I wants muh graz back.

Seems to be working for me as well, but those repeating ground textures, god damn...I hope Nvidia fixes their problems with Windows 10, because BSODs are unacceptable.

JustinLeB · January 25, 2016

Adding my name to this thread so far i've been able to fix the issue by rolling back Windows 10 to Build 10.0.10240 as Im running Pro but that only means i've delayed the issue until July at max when win 10 forces me to update.

JohnLindsay · January 25, 2016

Adding my name to this. Voss is almost unplayable with the grass enabled.

Newyankalt · January 25, 2016

Yup having this as well, something with Windows 10 it seems. I suspected it was an issue with the grass as I have had crashes on Tython, Taris, and Alderaan so far on the Jedi knight I am leveling... The other planets like Coruscant and Tatooine haven't had issues. Guess grass is going to 0.

Newyankalt · January 25, 2016

Actually I just rolled back to 347.88 and turned auto updates off (important), hopefully all is well

vafran · January 25, 2016

Adding my name to this! Very annoying issue, specially having a very good rig.

Fleurdelis · January 25, 2016

Wonder when we will get a dev response? Their silence is crazy. This may have to be fixed in a windows update but them recognizing the problem officially would be nice.

4.03 dxgmms2.sys Blue Screen in win10

Recommended Posts

Link to comment

Share on other sites

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Announcements