Hi. . .
5 of the 6 BSOD dumps named mwac.sys
as the probable cause/ offending driver of the BSODs and belongs to Malwarebytes.
Your MBAM driver version is recent, but make sure that you do have the most recent version of Malwarebytes installed -
mwac.sys Wed May 16 09:52:40 2018 (5AFC37A8)https://www.bleepingcomputer.com/download/malwarebytes-anti-malware/
The process running at the time of the BSODs was Malwarebytes service -
It is possible that MBAM was "phoning home" at the time of the BSODs; hence the reason that the Microsoft networking related driver netio.sys
was listed on the stack. Not really sure about this - just a theory, so make sure that your networking drivers (both wifi + Ethernet) are updated.
I don't know exactly what networking device you are using as systeminfo
(one of the apps executed by the BSOD Posting Instructions Sysnative app) lists your network device as -
Remote NDIS based Internet Sharing Device
I don't know if that is a wifi or Ethernet device.
Lastly, can you please explain your prior post? I honestly don't understand what you are trying to tell me -
my pc bluescreen only because of this web
that web is for fix the subtitle that not sync with the movie, usually im fix my subs there and doesn't have problem
but from june everytime upload the subtitle from my pc always bluescreen ( so i never open this web again )
1hours ago suddenly my pc bluescreen, only browsing with firefox
from bluescreenview idmwfp.sys , netio.sys , ntoskrnl.exe
is a driver belonging to an Internet Download Manager developed by Tonec. The information that I found out about it says the latest version was developed for Vista. Be sure that you have the most recent version installed. If you do and it was named in a BSOD, then you must uninstall it and find a new Internet Download Manager that is compatible with Windows 7 or newer.netio.sys
- I explained aboventoskrnl.exe
is the Windows kernel and is definitely not the cause of any of your BSODs. It is listed in BSOD dumps as the probable cause as a default of sorts as the real culprit could not be identified or unknown hardware failure is the actual cause.
Regards. . .