This is from MEMORY.DMP
Code:
0x0000000A: IRQL_NOT_LESS_OR_EQUAL (7.07.2017 11:31:13) [Windows 10]
CAUSED BY: ntoskrnl
MBAMChameleon.sys [27.06.2017] * Malwarebytes Chameleon Protection Driver * => https://www.malwarebytes.org/chameleon/ If using this
nvlddmkm.sys [27.06.2017] * nVidia Video drivers * => http://www.nvidia.com/Download/index.aspx
PROCESS: chrome.exe
Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility
Theres the driver for Malwarebytes shown as cause. Please uninstall for testing purposes:
Your should also remove McAffee and use Windows Defender instead for a while:
There are a lot of errors in windows eventlog which show that theres a problem with McAffee:
Code:
2017-07-05 16:32:49 Error: The password notification DLL "C:\Program Files\TrueKey\McAfeeTrueKeyPasswordFilter" failed to load with error 126. Please verify that the notification DLL path defined in the registry, HKLM\System\CurrentControlSet\Control\Lsa\Notification Packages, refers to a correct and absolute path (<drive>:\<path>\<filename>.<ext>) and not a relative or invalid path. If the DLL path is correct, please validate that any supporting files are located in the same directory, and that the system account has read access to both the DLL path and any supporting files. Contact the provider of the notification DLL for additional support. Further details can be found on the web at http://go.microsoft.com/fwlink/?LinkId=245898.
2017-07-05 16:48:39 Error: The password notification DLL "C:\Program Files\TrueKey\McAfeeTrueKeyPasswordFilter" failed to load with error 126. Please verify that the notification DLL path defined in the registry, HKLM\System\CurrentControlSet\Control\Lsa\Notification Packages, refers to a correct and absolute path (<drive>:\<path>\<filename>.<ext>) and not a relative or invalid path. If the DLL path is correct, please validate that any supporting files are located in the same directory, and that the system account has read access to both the DLL path and any supporting files. Contact the provider of the notification DLL for additional support. Further details can be found on the web at http://go.microsoft.com/fwlink/?LinkId=245898.
2017-07-05 17:12:25 Error: The password notification DLL "C:\Program Files\TrueKey\McAfeeTrueKeyPasswordFilter" failed to load with error 126. Please verify that the notification DLL path defined in the registry, HKLM\System\CurrentControlSet\Control\Lsa\Notification Packages, refers to a correct and absolute path (<drive>:\<path>\<filename>.<ext>) and not a relative or invalid path. If the DLL path is correct, please validate that any supporting files are located in the same directory, and that the system account has read access to both the DLL path and any supporting files. Contact the provider of the notification DLL for additional support. Further details can be found on the web at http://go.microsoft.com/fwlink/?LinkId=245898.
There are also "bad blocks" on your hard disks / file system found:
Code:
2017-06-27 19:18:39 Error: The device, \Device\Harddisk0\DR0, has a bad block.
2017-06-27 19:18:46 Error: The device, \Device\Harddisk0\DR0, has a bad block.
2017-07-03 11:40:14 Error: The device, \Device\Harddisk0\DR0, has a bad block.
2017-07-03 13:44:29 Error: The device, \Device\Harddisk1\DR1, has a bad block.
2017-07-03 13:45:08 Error: The device, \Device\Harddisk1\DR1, has a bad block.
Two things u should do now. First one should be checking your SSD / hard disks. Second one should be repairing windows file system. All this can be done with those steps below:
Diagnostic Test
HDD TESTS
Run HDTune to check health and scan for errors.
Note
It may take some time, but look for signs of any errors or failure.
You can also run a disk or health check using
CrystalDiskInfo or
chkdsk. Refer to the tutorial for details of how to do this.
Take Screenshots of it and post it here.
Repair Windows Filesystem:
1. Open an elevated command prompt.
2. In the elevated command prompt, type these five commands below, and press Enter:
dism /Online /NoRestart /Cleanup-Image /RestoreHealth
dism /Online /NoRestart /Cleanup-Image /StartComponentCleanup
sfc /scannow
chkdsk C: /F /R /X
fsutil dirty set C:
SFC:
The SFC command scans the integrity of all protected system files and replaces incorrect versions with correct Microsoft versions.
DISM:
If a Windows image becomes unserviceable, you can use the Deployment Imaging and Servicing Management (DISM) tool to update the files and correct the problem.
For example, you would use DISM to fix Windows component store corruption when a sfc /scannow command is unable to repair corrupted or modified system files because the component store (source) is corrupted.
CHKDSK:
Checking your drives for errors every once in a while can help fix some performance issues. Drive errors can usually be caused by bad sectors, improper shutdowns, bad software, corruption, physical damage, etc...
Quote