Jump to content

4.03 dxgmms2.sys Blue Screen in win10


reverseclipse

Recommended Posts

Since the latest patch 12/8, I've been getting direct X blue screens in win10. This was not an issue before the patch. Looking online shows other games having similar problems with win10. A lot of people falsely accuse graphics drivers for this. Anyone have a fix? Known bug?
Link to comment
Share on other sites

  • Replies 244
  • Created
  • Last Reply

Top Posters In This Topic

I am having the exact same problem and have been searching for any info on how to fix this but cant find anything yet.

I tried the few suggestions I found like installing Direct X 9.0 and changing some specific graphics settings but none worked. What eliminated the problem for me was rolling back to the previous version of Windows 10 before the November Win 10 major patch.

Edited by Greywoulf
Update
Link to comment
Share on other sites

Got the same problem. Seems like we have to wait for microsoft to fix this I guess. For me, it appeared with the latestst patch. I am not familliar with DirectX Issues, so I cannot tell if it is windows fault or SWTOR. Maybe someone has a workaround until it is fixed?
Link to comment
Share on other sites

Same here, but only happens, if i use taxi on core worlds (the slow ones). I've tried Balmora and Alderaan so far and i got BSD using taxi there. For instance on Makeb its fine, since that taxi is more like quick travel.
Link to comment
Share on other sites

I've been having issues too, BSOD, crashing and freezing. Did a system restore, checked the disc, did a memory scan and they came back clear. Did sfc/scannow and it found some errors and fixed them, ran the SWTOR repair and it found 11-12 files and fixed them. Rolled back my driver to the older 353.62 one, installed DX 9.0c. Nothing has fixed it, can't go more than 2 hours without something happening.
Link to comment
Share on other sites

Windows 10 Pro 64 Bit - Build 11082 (Released Dec 17th, 2015)

Just installed this version. haven't tested it yet but logging into the game now

previous build, I had no issues.

 

Lenovo y510p Laptop - Modded

i7 4700mq (Stock Clock)

16 GB Samsung Ram @ 1600

M.2 SSD 256GB (OS and games)

Nvidia GT 755m x2 (SLI - 359.06 Drivers -

)

 

I was not aware this was an issue.

Link to comment
Share on other sites

Thank you, I'm glad I'm not the only one experiencing this.

 

I've only gotten one BSOD but Reshade/SweetFX has been randomly recompiling. This happens specifically every time my ship does the whole hyperjump thing.

 

And yes, it never happened before the Windows 10 patch -- the one before yesterday's, and yesterday's didn't fix it.

Link to comment
Share on other sites

Thank you, I'm glad I'm not the only one experiencing this.

 

I've only gotten one BSOD but Reshade/SweetFX has been randomly recompiling. This happens specifically every time my ship does the whole hyperjump thing.

 

And yes, it never happened before the Windows 10 patch -- the one before yesterday's, and yesterday's didn't fix it.

 

so third party software running in the background? does it still BSOD when this is OFF?

 

 

no issues today...(streaming a flashpoint) Tython

Hitbox.tv/VETTEswtor

SWTOR.tv

Link to comment
Share on other sites

so third party software running in the background? does it still BSOD when this is OFF?

 

Yes, it does. I mentioned Reshade because it gave me an easy way of telling me when the game wasn't working correctly.

 

By the way, Reshade/SweetFx does not interact with the game at all, therefore it is not third-party software that is forbidden in the ToS. It is post-processing software, just like what your graphics card does. It is simply another layer on top of how your graphics card reads the game information.

 

Because of this, at first I thought perhaps my graphics card was going, which is why I was relieved to find this thread.

Edited by Cedia
Link to comment
Share on other sites

I noticed that too, today, on Taris:

everytime I take a taxi between more than 2 points: BSOD dxgmms2.sys

Maybe it has been there for longer than one day, but I noticed it today, and it's really annoying (compared to a standard CTD)

I run the latest NVIDIA drivers and my system didnt have such problems 1-2 weeks ago (dont know when it really started)

Edited by Draksen
Link to comment
Share on other sites

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.

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

Link to comment
Share on other sites

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.

Edited by Azurac
Link to comment
Share on other sites

Guest
This topic is now closed to further replies.

×
×
  • Create New...