Please upgrade your browser for the best possible experience.

Chrome Firefox Internet Explorer
×

4.03 dxgmms2.sys Blue Screen in win10


Helidoc's Avatar


Helidoc
12.20.2015 , 04:46 PM | #21
This seems to be happening with the latest TH2 update and NVidia drivers. In a nutshell a clean install to driver 347.88 Using DDU ( available on Guru3D dot com ) to clean your system of all the NVidia stuff and a fresh install of the 347.88 driver (available on NVidia's site) will get you going until MS and NVidia can get the DX12 stuff to play nice again. What is happening is dxgmms2 is tossing a VIDMM_CPU_HOST_APERTURE::UnmapRange+0x3a error out which is what is causing the Blue Screen for most systems that are getting it. For the technical minded or anyone who wants to see the partial dump, here it is.
Code:
Windows 10 Kernel Version 10586 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 10586.17.amd64fre.th2_release.151121-2308
Machine Name:
Kernel base = 0xfffff800`da888000 PsLoadedModuleList = 0xfffff800`dab66c70
Debug session time: Sun Dec 20 13:46:02.247 2015 (UTC - 7:00)
System Uptime: 0 days 1:12:07.929
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..
Loading User Symbols
Loading unloaded module list
.............................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff801e4651fba, ffffd0002740cd00, 0}

Probably caused by : dxgmms2.sys ( dxgmms2!VIDMM_CPU_HOST_APERTURE::UnmapRange+3a )

Followup:     MachineOwner
---------

7: kd> !thread
GetPointerFromAddress: unable to read from fffff800dac07200
THREAD ffffe001074f3840  Cid 2830.1138  Teb: 0000000001e2c000 Win32Thread: ffffe0010029b0f0 RUNNING on processor 7
Not impersonating
GetUlongFromAddress: unable to read from fffff800dab56ef8
Owning Process            ffffe001070cd140       Image:         swtor.exe
Attached Process          N/A            Image:         N/A
fffff78000000000: Unable to get shared data
Wait Start TickCount      276987       
Context Switch Count      118167         IdealProcessor: 7             
ReadMemory error: Cannot get nt!KeMaximumIncrement value.
UserTime                  00:00:00.000
KernelTime                00:00:00.000
Win32 Start Address 0x000000005a2b3e6f
Stack Init ffffd0002740dc90 Current ffffd0002740d710
Base ffffd0002740e000 Limit ffffd00027408000 Call 0
Priority 12 BasePriority 9 UnusualBoost 0 ForegroundBoost 2 IoPriority 2 PagePriority 5
Child-SP          RetAddr           : Args to Child                                                           : Call Site
ffffd000`2740c418 fffff800`da9d52e9 : 00000000`0000003b 00000000`c0000005 fffff801`e4651fba ffffd000`2740cd00 : nt!KeBugCheckEx
ffffd000`2740c420 fffff800`da9d4bfc : ffffd000`2740d4e8 ffffd000`2740cd00 fffff801`e3e8ac02 ffffd000`2740d4e8 : nt!KiBugCheckDispatch+0x69
ffffd000`2740c560 fffff800`da9d080d : fffff800`dabb9000 fffff800`da888000 0004c830`007cc000 fffff801`e65073e9 : nt!KiSystemServiceHandler+0x7c
ffffd000`2740c5a0 fffff800`da901f39 : 00000000`00000000 00000000`000004d2 ffffd000`2740cba0 ffffd000`2740c600 : nt!RtlpExecuteHandlerForException+0xd
ffffd000`2740c5d0 fffff800`da90034c : ffffd000`2740d4e8 ffffd000`2740d200 ffffd000`2740d4e8 fffff801`00000001 : nt!RtlDispatchException+0x429
ffffd000`2740ccd0 fffff800`da9d53c2 : 000003f0`1788ca38 000003f0`1788ca38 ffffc444`d0cb7e0a 00000000`00000001 : nt!KiDispatchException+0x144
ffffd000`2740d3b0 fffff800`da9d3aa1 : c1d00021`00000010 00000000`ff010000 00000000`00000001 00000000`00000000 : nt!KiExceptionDispatch+0xc2
ffffd000`2740d590 fffff801`e4651fba : ffffc001`3a089a30 ffffc001`32203501 ffffc001`204d69c0 fffff801`e465272e : nt!KiPageFault+0x221 (TrapFrame @ ffffd000`2740d590)
ffffd000`2740d720 fffff801`e46670f1 : ffffffff`fffffe48 ffffc001`322035e0 00000000`00000000 ffffc001`204d69c0 : dxgmms2!VIDMM_CPU_HOST_APERTURE::UnmapRange+0x3a
ffffd000`2740d770 fffff801`e46b76e3 : 00000000`00010000 ffffc001`322035e0 ffffc001`204d69c0 ffffc001`204d69c0 : dxgmms2! ?? ::FNODOBFM::`string'+0x4b1
ffffd000`2740d7c0 fffff801`e46cb176 : ffffc001`322035e0 ffffc001`379b2350 ffffc001`322035e0 ffffc001`379b2350 : dxgmms2!VIDMM_GLOBAL::BuildMdlForAllocInCpuHostAperture+0x3f
ffffd000`2740d800 fffff801`e46c309c : ffffc001`322035e0 00000000`00000000 ffffe001`0811cc00 00000000`00000000 : dxgmms2!VIDMM_GLOBAL::LockAllocInCpuHostAperture+0x32
ffffd000`2740d880 fffff801`e469dfc5 : ffffc001`319db410 ffffc001`319db410 ffffe001`0811cc00 ffffd000`2740da68 : dxgmms2! ?? ::NNGAKEGL::`string'+0x296c
ffffd000`2740d910 fffff801`e3e10f39 : ffffd000`2740db80 ffffe001`0811cc00 ffffc001`33eb33a0 ffffe000`00000002 : dxgmms2!VIDMM_GLOBAL::Lock+0x345
ffffd000`2740d9d0 fffff801`e3e8ac02 : ffffc001`2f5c12e0 ffffc001`3058d010 00000000`00000000 00000000`00000020 : dxgkrnl!VIDMM_EXPORT::VidMmLock+0x49
ffffd000`2740da10 fffff800`da9d4fa3 : 00000000`0e93e830 00000000`00000837 ffffc001`33eb33a0 ffffc001`3058d010 : dxgkrnl!DxgkLock2+0x4d2
ffffd000`2740db00 00000000`6b777324 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 (TrapFrame @ ffffd000`2740db00)
00000000`0e93e808 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x6b777324

Stutiguias's Avatar


Stutiguias
12.21.2015 , 08:30 AM | #22
same problem here.
0x3B_dxgmms2!VIDMM_CPU_HOST_APERTURE::AcquireRange
here from nvidia forum about that
https://forums.geforce.com/default/t...dxgmms2-sys/2/

MarkusPm's Avatar


MarkusPm
12.21.2015 , 02:05 PM | #23
I found this thread

https://forums.geforce.com/default/t...n-dxgmms2-sys/

that seems to solve the BSOD problem (at least for me). I uninstalled the most current drivers an reinstalled version 347.88. After that I had no problems anymore with the taxis on Alderaan.

HTH!

Azurac's Avatar


Azurac
12.21.2015 , 04:04 PM | #24
Maybe it will fix it for me too??

But the way I see it the problem for me was fixed after I uninstalled the update named KB3124200. All issues with BSOD occured AFTER that update was installed.

And issues disapeared after I uninstalled it.

BlueGlowie's Avatar


BlueGlowie
12.21.2015 , 06:38 PM | #25
Uninstall old drivers, Install 347.88

347.88 was the last release before they went to dxgmms2.sys

Enjoy

KaraPeters's Avatar


KaraPeters
12.23.2015 , 05:53 PM | #26
I'm crashing with this same error on average once every ten to fifteen minutes. Rolled back the driver to the version advised, but still crashing with the exact same error. This has only been happening since the most recent patch. I have the latest version of Windows.

mmarshall's Avatar


mmarshall
12.24.2015 , 03:50 PM | #27
I've gotten the same BSOD errors twice while riding a taxi. No issues any other time and no issues on any other games (WOW, Iracing, etc have no issues). Not sure what the problem is.

colorline's Avatar


colorline
12.24.2015 , 07:10 PM | #28
I hope Bioware and Nvidia work on it and make a patch and/or drivers for resolve this bugs :/
Retrouvez-moi sur console-toi.fr

colorline's Avatar


colorline
12.25.2015 , 04:15 AM | #29
A new driver is out http://www.nvidia.com/download/drive...px/96883/en-us i hope its resolve the pb
Retrouvez-moi sur console-toi.fr

KineticBlue's Avatar


KineticBlue
12.25.2015 , 03:39 PM | #30
Hi, i have the latest driver but the game still crash .. no issues fixed ?