Unable to install Malwarebytes, or others

Update: mrvlpcie8897

Code:

Event[12750]:  Log Name: System  Source: Microsoft-Windows-Kernel-PnP  Date: 2017-12-27T18:26:17.245  Event ID: 219  Task: N/A  Level: Warning  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: TheBook  Description: The driver \Driver\mrvlpcie8897 failed to load for the device PCI\VEN_11AB&DEV_2B38&SUBSYS_045E0004&REV_00\4&1a5036a5&0&00EB.

mrvlpcie8897.sys

Marvell LE Driver for the WiFiCLass Driver

OEM or http://www.marvell.com/support/downloads/search.do

cannot open it.......security risk......post in different format so it can be viewed.

Uninstall ESET:

Code:

Event[10142]:  Log Name: System  Source: Service Control Manager  Date: 2017-12-21T18:02:45.213  Event ID: 7000  Task: N/A  Level: Error  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: TheBook  Description: The eapihdrv service failed to start due to the following error: This driver has been blocked from loading

Uninstall ESET manually using the ESET uninstaller toolESET Knowledgebase

these are the txt files produces

These were problem events noted in the event logs:

Code:

Event[9211]:  Log Name: System  Source: BTHUSB  Date: 2017-12-21T12:05:57.352  Event ID: 17  Task: N/A  Level: Error  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: TheBook  Description: The local Bluetooth adapter has failed in an undetermined manner and will not be used. The driver has been unloaded.

Code:

Event[8608]:  Log Name: System  Source: volmgr  Date: 2017-12-19T09:34:37.349  Event ID: 49  Task: N/A  Level: Error  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: TheBook  Description: Configuring the Page file for crash dump failed. Make sure there is a page file on the boot partition and that is large enough to contain all physical memory.

Code:

Event[8567]:  Log Name: System  Source: Service Control Manager  Date: 2017-12-19T09:22:08.040  Event ID: 7000  Task: N/A  Level: Error  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: TheBook  Description: The 963270ca63e0e72611d598be60b38345 service failed to start due to the following error: Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.

Code:

Event[8563]:  Log Name: System  Source: Service Control Manager  Date: 2017-12-19T09:22:04.370  Event ID: 7000  Task: N/A  Level: Error  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: TheBook  Description: The 963270ca63e0e72611d598be60b38345 service failed to start due to the following error: Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.

Code:

Event[8561]:  Log Name: System  Source: Service Control Manager  Date: 2017-12-19T09:22:04.228  Event ID: 7045  Task: N/A  Level: Information  Opcode: N/A  Keyword: Classic  User: S-1-5-21-2133594979-3002416721-123404935-1001  User Name: THEBOOK\PC  Computer: TheBook  Description: A service was installed in the system.Service Name:  963270ca63e0e72611d598be60b38345Service File Name:  C:\WINDOWS\system32\drivers\963270ca63e0e72611d598be60b38345.sysService Type:  kernel mode driverService Start Type:  system startService Account:

Code:

Event[8554]:  Log Name: System  Source: Microsoft-Windows-NDIS  Date: 2017-12-19T09:20:42.126  Event ID: 10317  Task: PnP  Level: Error  Opcode: Info  Keyword: N/A  User: N/A  User Name: N/A  Computer: TheBook  Description: Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {BE0A89E4-0500-4AF7-B1D1-AD0570C1A136}, had event Fatal error: The miniport has failed a power transition to operational power

Code:

Event[6090]:  Log Name: System  Source: Microsoft-Windows-USB-USBHUB3  Date: 2017-12-03T22:33:52.240  Event ID: 196  Task: Surprise Removal  Level: Warning  Opcode: Warning  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: TheBook  Description: USB device draining system power when system is idle.                          USB Device: VID: 0x1286 PID: 0x204C REV: 0x3201             Removal action failed: SkippedAsAlreadyMarkedForRemoval (Device vetoed previous attempt)

Code:

Event[5638]:  Log Name: System  Source: MTConfig  Date: 2017-12-02T18:26:53.107  Event ID: 1  Task: N/A  Level: Error  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: TheBook  Description: An attempt to configure the input mode of a multitouch device failed.

Code:

Event[5517]:  Log Name: System  Source: BTHUSB  Date: 2017-12-01T16:06:49.621  Event ID: 17  Task: N/A  Level: Error  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: TheBook  Description: The local Bluetooth adapter has failed in an undetermined manner and will not be used. The driver has been unloaded.

Code:

Event[9523]:  Log Name: System  Source: Display  Date: 2017-12-21T12:48:39.088  Event ID: 4101  Task: N/A  Level: Warning  Opcode: Info  Keyword: Classic  User: N/A  User Name: N/A  Computer: TheBook  Description: Display driver nvlddmkm stopped responding and has successfully recovered.

Code:

Event[12747]:  Log Name: System  Source: Microsoft-Windows-BitLocker-Driver  Date: 2017-12-27T18:26:15.978  Event ID: 24652  Task: N/A  Level: Warning  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: TheBook  Description: A recovery password was used to start Windows.Protector ID: {CD0CAED7-B8D8-446F-B4BE-1396C75F8C1C}.

Code:

Event[12746]:  Log Name: System  Source: Microsoft-Windows-BitLocker-Driver  Date: 2017-12-27T18:26:15.978  Event ID: 24636  Task: N/A  Level: Error  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: TheBook  Description: Bootmgr failed to obtain the BitLocker volume master key from the TPM.

Code:

Event[9408]:  Log Name: System  Source: Disk  Date: 2017-12-21T12:25:58.932  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: TheBook  Description: An error was detected on device \Device\Harddisk1\DR3 during a paging operation.Event[9409]:  Log Name: System  Source: Disk  Date: 2017-12-21T12:25:58.932  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: TheBook  Description: An error was detected on device \Device\Harddisk1\DR3 during a paging operation.Event[9410]:  Log Name: System  Source: Disk  Date: 2017-12-21T12:25:58.932  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: TheBook  Description: An error was detected on device \Device\Harddisk1\DR3 during a paging operation.Event[9411]:  Log Name: System  Source: Disk  Date: 2017-12-21T12:25:58.932  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: TheBook  Description: An error was detected on device \Device\Harddisk1\DR3 during a paging operation.Event[9412]:  Log Name: System  Source: Disk  Date: 2017-12-21T12:25:58.932  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: TheBook  Description: An error was detected on device \Device\Harddisk1\DR3 during a paging operation.Event[9413]:  Log Name: System  Source: Disk  Date: 2017-12-21T12:25:58.932  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: TheBook  Description: An error was detected on device \Device\Harddisk1\DR3 during a paging operation.Event[9414]:  Log Name: System  Source: Disk  Date: 2017-12-21T12:25:58.932  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: TheBook  Description: An error was detected on device \Device\Harddisk1\DR3 during a paging operation.Event[9415]:  Log Name: System  Source: Disk  Date: 2017-12-21T12:25:58.932  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: TheBook  Description: An error was detected on device \Device\Harddisk1\DR3 during a paging operation.Event[9416]:  Log Name: System  Source: Disk  Date: 2017-12-21T12:25:58.932  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: TheBook  Description: An error was detected on device \Device\Harddisk1\DR3 during a paging operation.Event[9417]:  Log Name: System  Source: Disk  Date: 2017-12-21T12:25:58.932  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: TheBook  Description: An error was detected on device \Device\Harddisk1\DR3 during a paging operation.Event[9418]:  Log Name: System  Source: Disk  Date: 2017-12-21T12:25:58.932  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: TheBook  Description: An error was detected on device \Device\Harddisk1\DR3 during a paging operation.Event[9419]:  Log Name: System  Source: Disk  Date: 2017-12-21T12:25:58.932  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: TheBook  Description: An error was detected on device \Device\Harddisk1\DR3 during a paging operation.Event[9420]:  Log Name: System  Source: Disk  Date: 2017-12-21T12:25:58.932  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: TheBook  Description: An error was detected on device \Device\Harddisk1\DR3 during a paging operation.Event[9421]:  Log Name: System  Source: Disk  Date: 2017-12-21T12:25:59.068  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: TheBook  Description: An error was detected on device \Device\Harddisk1\DR3 during a paging operation.Event[9422]:  Log Name: System  Source: Disk  Date: 2017-12-21T12:25:59.068  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: TheBook  Description: An error was detected on device \Device\Harddisk1\DR3 during a paging operation.

Code:

Event[522]:  Log Name: System  Source: mrvlpcie8897  Date: 2017-10-24T11:26:05.958  Event ID: 5002  Task: N/A  Level: Error  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: TheBook  Description: Marvell AVASTAR Wireless-AC Network Controller : Has determined that the network adapter is not functioning properly.

Code:

Event[1166]:  Log Name: System  Source: Disk  Date: 2017-10-31T17:37:11.727  Event ID: 11  Task: N/A  Level: Error  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: TheBook  Description: The driver detected a controller error on \Device\Harddisk1\DR5.

Code:

Event[11241]:  Log Name: System  Source: Disk  Date: 2017-12-22T10:19:51.301  Event ID: 11  Task: N/A  Level: Error  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: TheBook  Description: The driver detected a controller error on \Device\Harddisk1\DR1.

Code:

Event[1270]:  Log Name: System  Source: Microsoft-Windows-WER-SystemErrorReporting  Date: 2017-10-31T20:33:02.897  Event ID: 1001  Task: N/A  Level: Error  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: TheBook  Description: The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000000a (0x0000000000000002, 0x0000000000000002, 0x0000000000000000, 0xfffff803bd2fc588). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 4028a42b-2aab-47c1-ac71-6d300decac7c.

Code:

Event[8608]:  Log Name: System  Source: volmgr  Date: 2017-12-19T09:34:37.349  Event ID: 49  Task: N/A  Level: Error  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: TheBook  Description: Configuring the Page file for crash dump failed. Make sure there is a page file on the boot partition and that is large enough to contain all physical memory.

Code:

Event[12768]:  Log Name: System  Source: Win32k  Date: 2017-12-27T18:26:19.937  Event ID: 263  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: TheBook  Description: A pointer device has no information about the monitor it is attached to.

Code:

Event[12950]:  Log Name: System  Source: Volsnap  Date: 2017-12-27T21:04:43.394  Event ID: 33  Task: N/A  Level: Information  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: TheBook  Description: The oldest shadow copy of volume C: was deleted to keep disk space usage for shadow copies of volume C: below the user defined limit.

Afraid I just couldn't go through all that again, so have reinstalled Windows while keeping my data.
Is there anything I should do now, whilst I reinstall all the apps?

Choose 1 always on and 1 manual AV product to use on the computer.
Anything more can reduce the malware protection as the software can compete with each other creating gaps for the malware.

Run the AV software in full mode scanning all files.

Then make a backup image and restore point once you have restored applications and files.

The drive and drive files system should be checked so that you have a baseline.
Most of the tests can be done overnight (chkdsk /x /f /r and HD Tune full error scan).

Well Defender is always on, so what other AV product do you recommend to run manually?

Then ... Is it just those 2 you recommend to run - chkdsk /x /f /r and HD Tune full error scan?
Have just about got the applications re-installed so will run the full Defender and off line virus check next.

The most important things that can be done for malware is being careful about the email that is opened and what you click on on the websites. The AV products are rated and the results vary. There is no one product that is always better than the next.

Find one AV product that you like. The manual product is a backup option in case you want to double check.

On the computer's that I use it's the default Windows defender. Malwarebytes is the backup. Each of the products has its strengths and weaknesses.

Earlier in the thread you had run scannow and restorehealth. Those can be run any time to check the integrity of the operating system.

The CPU, GPU, MB etc. can be tested if you have any problems.

For routine maintenance:
1) AV scanning
2) checking the OS with scannnow and restorhealth
3) check the drive once a year or more frequently if you have discovered problems. The health testing (SMART) is predictive testing. For detecting current problems use surface (error scanning) and Sea Tools long generic testing.
4) backup files in case there are unexpected problems
5) make a backup image in case there are unexpected problems
6) perform in place upgrade repairs as needed with a windows 10 iso.