As a founder it's time to let this game go the way of SWG if this keeps up, bad enough that I had to rename a toon I had for a while. Granted I reroll toons when I get bored with them so this one did not have the play time on it but I have had the name for a while. Been a sub since release and I'm beginning to rethink that since I'm now having to sit in a queue at 4am after getting bounced out of the game just by switching toons. /rant off

I literally feel your pain... had to do my imitrex injection earlier to curb mine.

Hoarders!!

Microsoft yesterday patched their DirectX core files for Win10. Was in game this morning with the latest NVidia Drivers 361.91 and am once again able to play the game with full settings and no BSOD's if you didn't get MS's Update you may want to check it for version 10586.122 which is where the core files are updated.

Go into your graphics settings and turn the grass setting to 0 and see if that helps. A lot of discussion about this issue here http://www.swtor.com/community/showthread.php?t=859343

Later on tonight when time permits I might break out some tools to fiddle with some of the advanced driver settings that can be only adjusted with things such as NVidia inspector etc. Since the only adjustment so far to make the game stable for most end users is the grass at 0 setting for now that should work for most. One thing that concerns me in the NVidia advance settings for this game in the latest driver is a 0x704D456E flag in the undefined area which is stating "Some objects render at the wrong depth" which may be why we need to turn grass down to 0 to correct this bug and prevent the BSOD. With WDDM v2 being pushed out by MS in this last update to Win 10 I do think once the dust settles MS, NVidia and several other companies will get it right. It is a huge transition from DX9-11 to DX12 with WDDM v2 and bad timing not just in the gaming community but in other applications that use memory management as well.

This here seems to fix the dxgmms2.sys BSOD for this title I had a few spots in game that I could get it to crash with this 100 percent of the time and after reinstalling the new drivers and making this adjustment in the graphics settings no more crashes. Thanks for pointing this out BG I'm running an SLI setup myself at least now we can look to which part of the programming is messing with the GPU virtual addressing in WDDM v2 as this is happening in both DX 9 and 11 titles and not just SWTOR.

For those of you getting the BSOD that have yet to roll back to the 347.88 driver. On the new driver 359.06 or 361.43 do you have an SLI set up and have you tried running the game on the new driver with SLI disabled? If so does it still crash with SLI disabled? I know this defeats the purpose of having SLI but looking at my debug logs and some of the memory errors that's being tossed out it looks to be an issue. I've compiled a report for MS and NVidia both and would just like to get further feed back to add to it if possible. Thanks

http://www.swtor.com/community/showthread.php?p=8707680 See my post on page 3 for details I found that a fresh install of 347.88 fixes it for now.

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

Tiridian, I run both unleashed and the game with Windows 7 64bit, never have run it in xp compatibility mode. I have an Core i7-2700k running at 3.9Ghz with 16GB of memory with a GTX 660 vid card. My Settings for unleashed are as follows. Add DiskCacheArena Add LocalApps Select FX Select Dynamic Add extra 100mb to the ram drive size (under additional options) Also because I have an Nvidia card I've made the following adjustments in my Nvidia control panel under manage 3d settings and it has helped this game as well. These Settings should be made under the program settings tab and select Star Wars the old rep for the program, if your system has not detected it you may have to add it to the list with the add button, be sure to add the program and not the launcher, again this is for Nvidia cards. Set Multi Display to Single Display Performance Mode Set Power Management to Prefer Max Performance Set Max Pre Rendered Frames to 2 or 3 Hope this helps...

Run unleashed and select the remove and quit option. Try running your game from the normal launcher icon. If that works you should be good from there. If it doesn't run the game from the normal launcher icon but don't select play, instead, once logged into the launcher select the cog and select the repair option and allow the game to repair itself. You should be golden after that. Don't forget to delete your unleashed xml file before launching unleashed again and reselecting your options for unleashed.