A strange issue is now found in Windows 10 laptops that crash down the OS without providing any kind of warning if repeatedly opened and closed. Apparently, Microsoft is working to fix this problem faced by users. A defect in Microsoft DirectX Video Memory Management (Dxgmms2.sys) component has been accepted by Microsoft. This flaw is capable enough for crashing down Windows 10 on continuous opening and closing of the laptop.
A couple of situations have already been listed by Microsoft that could be the possible reasons for the origination of the problem. The Dxgmms2.sys affects the responding of the Desktop Windows Manager (DWM.exe) and hence results in the crash.
Therefore, you can understand that to ensure the smooth and proper working of Windows 10, the DWM is really important. According to Microsoft, “The Desktop Window Manager runs as a Windows service. It can be enabled and disabled through the Administrative Tools Control Panel item, under Services, as Desktop Window Manager Session Manager”. Microsoft also adds, “This problem occurs because of an issue in the Microsoft DirectX Video Memory Management (Dxgmms2.sys) component. This is not a hardware issue”.
The various scenarios stated by Microsoft are:
SCENARIO 1-
- An HDMI (High Definition Multimedia Interface) monitor is plugged into a Windows 10 running laptop.
- The monitor is made to function at 4K resolution.
- Repeated playing of any 4K H264 video.
- Inside Control Panel, you open ‘Advanced settings’ from ‘Power Options’ item, thus setting ‘Lid close action’ as ‘Do nothing’.
- With the 4K video playing, you continuously open and close the lid.
SCENARIO 2-
- Two 4K monitors are connected to a Thunderbolt 3 docking station by you.
- A 4K solution monitor has been connected to the docking station by you and then you arrange a triple 4K display configuration in either ‘clone’ or ‘extend’ mode.
- The laptop is continuously opened and closed.
If all these things happened, then this could cause Windows 10 to crash. Apparently, these are prescribed ones by Microsoft and there, perhaps could be other scenarios as well. Microsoft is working on to fix this issue.