ubuysa
The BSOD Doctor
The 120420-9296-01.dmp dump is a VIDEO_MEMORY_MANAGEMENT_INTERNAL error and they're typically graphics driver errors. In this case the desktop windows manager (dwm.exe) was the process in control and the driver that failed was dxgmms2.sys, and that's part of the DirectX Graphics rendering engine.
In the stack trace the driver was accessing the graphics card (the module call is a dxgmms2!VIDMM_PROCESS_ADAPTER_INFO::~VIDMM_PROCESS_ADAPTER_INFO+0x27799) immediately prior to the bug check, so on the face of it this looks like a graphics driver problem.
But...a closer look at the drivers in use by the executing thread shows several failures for components of Avast security...
Code:
fffffe09`b778e738 fffff806`9493efa2 Unable to load image \SystemRoot\system32\drivers\aswStm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswStm.sys
aswStm+0x1efa2
fffffe09`b778e718 fffff806`91b96c68Unable to load image \SystemRoot\system32\drivers\aswSP.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswSP.sys
aswSP+0x66c68
fffffe09`b778e698 fffff806`9216caa1Unable to load image \SystemRoot\system32\drivers\aswNetHub.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswNetHub.sys
aswNetHub+0xcaa1The 120720-7687-01.dmp dump is a CRITICAL_PROCESS_DIED error, which (as the name suggests) means that a critical Windows process failed and halted the system. The process that failed was svchost.exe, the svc hosting process - I'm not able to determine what dll the process was hosting. The failure reason is a memory corruption - so it looks like we're back to RAM again.
However, investigating the drivers in use more deeply also shows that DirectX graphics was involved again (the module fffff806`946a7a05 dxgmms2!VIDMM_PROCESS_ADAPTER_INFO::~VIDMM_PROCESS_ADAPTER_INFO+0x27799 is seen - as it was in the first BSOD).
Again, a closer examination of the drivers in use by the executing thread shows problems with Avast...
Code:
fffffe09`b778e698 fffff806`9216caa1 Unable to load image \SystemRoot\system32\drivers\aswNetHub.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswNetHub.sys
aswNetHub+0xcaa1The root cause of both BSODs would thus appear to be Avast security. I would strongly suggest that you fully uninstall Avast using whatever removal tool Avast supplies (a simple uninstall is often not good enough for security packages). You really don't need anything other than Windows Defender in any case, and it's clear that Avast is causing your current issues.
