BSOD trying to scan with MalwareBytes, error code 24.

[Hexagon12]

This thread is exactly in title. I am having a BSOD issue 0x00000024, while trying to scan with MalwareBytes. Dm Log is attached.

 

[essenbe]

The dump is giving me no information other than it is a third Party driver causing the problem. Do you have another anti Virus installed? If you do, put Malwarebythes folder in the scan exceptions, and stop the other program and run Malwarebytes again. See if that helps.

If not, uninstall Malwarebytes with their removal Utility and reinstall it. https://helpdesk.malwarebytes.org/h...-How-do-I-uninstall-Malwarebytes-Anti-Malware-

 

[Hexagon12]

So, here's a short backstory of my problem.
:ar: Those problems started, when I installed my computer with Windows 7.
1. Windows updates- can't install with error code 80070BC9
2. Firefox crashes when I launch it.
3. IE crashes when I click "Save file"
4. All of that felt strange to me, so I decided to install an AV.
5. Avast doesn't install- error code 0x00000002
6. Malwarebytes installed, but when I clicked in Threat Scan, It gave a BSOD 0x24 (NTFS_FILE_SYSTEM)

 

[essenbe]

I suggest you try these

as I told you before, uninstall and use the uninstall tool I linked to and reinstall after finished
http://www.sevenforums.com/tutorials/338716-malwarebytes-anti-malware-free.html

Also, http://www.sevenforums.com/tutorials/166445-windows-defender-offline.html

 

[essenbe]

Also, after you finished, open a elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.

 

[Hexagon12]

No luck at all!
I tried powering computer up, and then bam! BSOD 0x1E. What is now happening?

 

[essenbe]

If you installed any software or hardware uninstall it. Boot into safe mode.

Try a system restore from boot http://www.sevenforums.com/tutorials/700-system-restore.html

try all of these steps http://www.sevenforums.com/tutorials/219533-troubleshooting-windows-7-failure-boot.html

Run Windows Defender Offline linked above.

 

[Hexagon12]

So, the 0x1E was a first and the last issue at the startup. So, i did those things-
1. Ran sfc /scannow, Windows file protection found no integrity issues,
2. Uninstalled Malwarebytes
3. Ran Windows Defender Offline on a USB flash drive, ran full scan, no viruses.

Now it seems that I can't install any update- it gives the error code 80070BC9.

 

[essenbe]

try Manually installing the Update. You may need to disable your AV while doing it and re enable it afterwards. Also, try this, just be sure to use the right version for your installation. Fix Windows corruption errors by using the DISM or System Update Readiness tool

 

[essenbe]

The dump file is

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
[COLOR=red]BugCheck 24[/COLOR], {c08a5, 0, 0, 0}

That bug check and the windows update error code both usually indicate NTFS file system corruption. You need to run check disk http://www.sevenforums.com/tutorials/433-disk-check.html

 

[Hexagon12]

Tried to install SURT, it was nearly ended, and then BOOM! 0x24 again. The same one as the last. OK. This IS a disk problem. After failing updates, i tried restarting, and chkdsk popped up. It seems that it is doing some job.

 

[essenbe]

There are exceptions to everything, but a code 24 is usually the NTFS file system. Which many times is the hard drive, or corrupted files on it. As I recall, you have been having corrupted files it appears quite often. That is also one of ther reasons for the code for your failed Windows updates, windows update is corrupted.