tcpip.sys is a driver from Windows related to the network, meaning either the network drivers or 3rd party drivers connecting to the network are causing issues.
The flagged drivers are Malwarebytes Web Access control and Acronis Storage Filter management.
Either update or reinstall Malwarebytes and Acronis.
Code:
*** WARNING: Unable to verify timestamp for mwac.sys
*** ERROR: Module load completed but symbols could not be loaded for mwac.sys
2: kd> lmvm mwac
start end module name
fffff880`0c8d9000 fffff880`0c8eb000 mwac T (no symbols)
Loaded symbol image file: mwac.sys
Image path: \??\C:\Windows\system32\drivers\mwac.sys
Image name: mwac.sys
Timestamp: [COLOR="Red"]Wed Jun 18 04:06:34 2014[/COLOR] (53A0F42A)
CheckSum: 00010FDD
ImageSize: 00012000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
*** WARNING: Unable to verify timestamp for fltsrv.sys
*** ERROR: Module load completed but symbols could not be loaded for fltsrv.sys
2: kd> lmvm fltsrv
start end module name
fffff880`01f51000 fffff880`01f6f000 fltsrv T (no symbols)
Loaded symbol image file: fltsrv.sys
Image path: \SystemRoot\system32\DRIVERS\fltsrv.sys
Image name: fltsrv.sys
Timestamp: [COLOR="red"]Mon May 13 11:40:09 2013[/COLOR] (5190B4F9)
CheckSum: 00021D3A
ImageSize: 0001E000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
A 0x3B(SYSTEM_SERVICE_EXCEPTION) could have a few options where I'll try to explain what happens according to what I understand.
In this case it is likely that Malwarebytes and Acronis are both trying to access the internet, so they give instructions to the related driver to request data from the internet. However the data is not in the correct way requested so the related driver gives a signal that it can't execute the data, an exception of a system service (part of a program or a program) which hasn't been catched (properly).
I hope I have made it a little bit clear of what could have happened with a really short explanation, there are quite a few scenario's of what could have happened.
Lastly Seikan340, you are running a Lenovo Product ID on an ASUS board.
This makes your installation counterfeit.
Troubleshooting a counterfeit installation is useless as it is not known what has been modified to your system.
A counterfeit installation contains heavily modified code which causes the system to behave in unexpected ways.
For this reason, analyzing counterfeit systems is unreliable and most analysts won't try it.
Code:
OS Manufacturer: Microsoft Corporation
OS Configuration: Standalone Workstation
OS Build Type: Multiprocessor Free
Registered Owner: Djalal
Registered Organization:
Product ID: [COLOR="Red"]00426-OEM-8992662-00497[/COLOR] <-- Lenovo PID on ASUS board
Original Install Date: 06/06/2014, 18:34:32
System Boot Time: 02/11/2015, 20:45:06
System Manufacturer: ASUS
I recommend to install a genuine copy of Windows.
If, after you have installed a genuine copy of Windows, you still get BSOD's we'll be happy to assist you.
