Tweet
We have had a few reports of crashes in the Microsoft dxgmms2.sys device driver.
The full name of the the dxgmms2.sys file is the, DirectX Graphics MMS. We suspect MMS = Microsoft Media Server.
The crash is a blue screen of death with the error cause, System service exception.
Looking into the crash dump shows this additional detail.
dxgmms2!VIDMM_CPU_HOST_APERTURE::UnmapRange+3a
fffff801`47b81fba 488b0f mov rcx,qword ptr [rdi]
Speculation: An aperture is probably a reference to a PCIe memory mapped address range, used to transfer data from the CPU to the video card. Memory ranges might be being mapped and unmapped to perform data transfers. The software bug might be related to unmapping a memory range that wasn't currently mapped.
It only seems to be a problem with nVidia video cards and only in the latest patch releases of Win10.
To date the problem has been reported with only this specific combination of software / hardware.
A search on Google reveals this problem with dxgmms2.sys is very widespread. Causing similar crashes in a number of different games.
Some people have reported that cleaning out old video card drivers and installing them again might fix the problem. But we are a bit dubious of this. More likely it is a bug in the new dxgmms2.sys device driver that is provoked by some behaviour in nVidia's drivers.
Other people has reported that reverting to an older nVidia driver package (Version 347.88 for Window 8.1) will fix it, but this also means that the new DirectX12 functionality in Win10 will be lost. Further Windows will auto-update the driver when you aren't looking and break your system again.
Rolling back to early Win10 releases should also fix it.
The full name of the the dxgmms2.sys file is the, DirectX Graphics MMS. We suspect MMS = Microsoft Media Server.
The crash is a blue screen of death with the error cause, System service exception.
Looking into the crash dump shows this additional detail.
dxgmms2!VIDMM_CPU_HOST_APERTURE::UnmapRange+3a
fffff801`47b81fba 488b0f mov rcx,qword ptr [rdi]
Speculation: An aperture is probably a reference to a PCIe memory mapped address range, used to transfer data from the CPU to the video card. Memory ranges might be being mapped and unmapped to perform data transfers. The software bug might be related to unmapping a memory range that wasn't currently mapped.
It only seems to be a problem with nVidia video cards and only in the latest patch releases of Win10.
To date the problem has been reported with only this specific combination of software / hardware.
- Win10 build 10586 64bit (Threshold 2, Nov 2015 update)
- Geforce GT740 and GTX Titan. (but many other DirectX12 nVidia cards have problems if you search Google)
- nVidia Video drivers 353.30 until 359.06
- BurnInTest V8 while running the video test (and many games)
A search on Google reveals this problem with dxgmms2.sys is very widespread. Causing similar crashes in a number of different games.
Some people have reported that cleaning out old video card drivers and installing them again might fix the problem. But we are a bit dubious of this. More likely it is a bug in the new dxgmms2.sys device driver that is provoked by some behaviour in nVidia's drivers.
Other people has reported that reverting to an older nVidia driver package (Version 347.88 for Window 8.1) will fix it, but this also means that the new DirectX12 functionality in Win10 will be lost. Further Windows will auto-update the driver when you aren't looking and break your system again.
Rolling back to early Win10 releases should also fix it.
Comment