BSoD during scanning File System

[jeffers]

I was recently trying to run a scan when I encounter the BSoD during this phase of the scan process. I rebooted, and tried to scan again. I got the same issue. I used the repair tool and tried it again, and BSoD once more. I'm currently running the 20H2 version of Windows 10. Any way to fix this? 

[Malwarebytes]

***This is an automated reply***

Hi,

Thanks for posting in the Malwarebytes for Windows Help forum.

If you are having technical issues with our Windows product, please do the following:

Malwarebytes Support Tool - Advanced Options

This feature is designed for the following reasons:

• For use when you are on the forums and need to provide logs for assistance
• For use when you don't need or want to create a ticket with Malwarebytes
• For use when you want to perform local troubleshooting on your own

How to use the Advanced Options:

Spoiler

1. Download Malwarebytes Support Tool
2. Double-click mb-support-X.X.X.XXXX.exe to run the program
   • You may be prompted by User Account Control (UAC) to allow changes to be made to your computer. Click Yes to consent.
3. Place a checkmark next to Accept License Agreement and click Next
4. Navigate to the Advanced tab
5. The Advanced menu page contains four categories:
   • Gather Logs: Collects troubleshooting information from the computer. As part of this process, Farbar Recovery Scan Tool (FRST) is run to perform a complete diagnosis. The information is saved to a file on the Desktop named mbst-grab-results.zip and can be added as an email attachment or uploaded to a forum post to assist with troubleshooting the issue at hand.
   • Clean: Performs an automated uninstallation of all Malwarebytes products installed to the computer and prompts to install the latest version of Malwarebytes for Windows afterwards. The Premium license key is backed up and reinstated. All user configurations and other data are removed. This process requires a reboot.
   •  Repair System: Includes various system-related repairs in case a Windows service is not functioning correctly that Malwarebytes for Windows is dependent on. It is not recommended to use any Repair System options unless instructed by a Malwarebytes Support agent.
   • Anonymously help the community by providing usage and threat statistics: Unchecking this option will prevent Malwarebytes Support Tool from sending anonymous telemetry data on usage of the program.
6. To provide logs for review click the Gather Logs button
7. Upon completion, click OK
8. A file named mbst-grab-results.zip will be saved to your Desktop
9. Please attach the file in your next reply.
10. To uninstall all Malwarebytes Products, click the Clean button.
11. Click the Yes button to proceed. 
12. Save all your work and click OK when you are ready to reboot.
13. After the reboot, you will have the option to re-install the latest version of Malwarebytes for Windows.
14. Select Yes to install Malwarebytes.
15. Malwarebytes for Windows will open once the installation completes successfully.

Screenshots:

Spoiler

 

 

 

 

Spoiler

 

 

 

 

If you are having licensing issues, please do the following: 

Spoiler

For any of these issues:

• Renewals
• Refunds (including double billing)
• Cancellations
• Update Billing Info
• Multiple Transactions
• Consumer Purchases
• Transaction Receipt

Please contact our support team at https://support.malwarebytes.com/hc/en-us/requests/new to get help

If you need help looking up your license details, please head here: Find my premium license key

 

 

Thanks in advance for your patience.

-The Malwarebytes Forum Team

[Porthos]

2 hours ago, jeffers said:

I was recently trying to run a scan when I encounter the BSoD during this phase of the scan process. I rebooted, and tried to scan again. I got the same issue. I used the repair tool and tried it again, and BSoD once more. I'm currently running the 20H2 version of Windows 10. Any way to fix this? 

Can you please collect and upload as an attachment the diagnostic data using our MBST?

• Download and run the Malwarebytes Support Tool
• Accept the EULA and click Advanced tab on the left (not Start Repair)
• Click the Gather Logs button, and once it completes, attach the zip file it creates on your desktop to your next reply

[jeffers]

9 hours ago, Porthos said:

Can you please collect and upload as an attachment the diagnostic data using our MBST?

• Download and run the Malwarebytes Support Tool
• Accept the EULA and click Advanced tab on the left (not Start Repair)
• Click the Gather Logs button, and once it completes, attach the zip file it creates on your desktop to your next reply

Ok, here it is 

mbst-grab-results.zip

[Porthos]

43 minutes ago, jeffers said:

Ok, here it is 

Seems your disk has an issue. I will ask @AdvancedSetup to address your issue.

Quote

System errors:
=============
Error: (02/16/2021 12:22:37 PM) (Source: disk) (EventID: 7) (User: )
Description: The device, \Device\Harddisk1\DR1, has a bad block.

 

[AdvancedSetup]

We probably need to do a disk check of both drives to rule that out as a cause of the issue. However, if you're getting a bad block message showing up in your logs that's a pretty good indicator the hard drive is probably on the way out.
Normally hard drives have an internal table to mark bad sectors and thus prevent writes to those sectors. Blocks are a group of sectors and thus potentially more damage that can no longer be handled by the drive firmware.

There is no way to reliably determine if the hard drive will fail tomorrow or five years from now, but one should not simply ignore it. You should make sure your data is fully backed up. Then it's up to you, you can keep trying to use the hard drive and hope it doesn't get any worse and it might not but then again you could wake up next week and try to start the computer and the hard drive is now dead.

 

You can open an Elevated Admin command prompt and issue the following command to test and repair both drives. If it finds a bad block it will try to fix what it can and then mark the block or region as non usable going forward.

CHKDSK C: /F

CHKDSK D: /F

It will say it cannot lock the drive in most cases and ask if you want to run the check on restart. Press the Y key to tell it yes. Then restart the computer and let the disk check run.

If you need further help on how to do this please let us know

Thank you @jeffers

 

[jeffers]

41 minutes ago, AdvancedSetup said:

We probably need to do a disk check of both drives to rule that out as a cause of the issue. However, if you're getting a bad block message showing up in your logs that's a pretty good indicator the hard drive is probably on the way out.
Normally hard drives have an internal table to mark bad sectors and thus prevent writes to those sectors. Blocks are a group of sectors and thus potentially more damage that can no longer be handled by the drive firmware.

There is no way to reliably determine if the hard drive will fail tomorrow or five years from now, but one should not simply ignore it. You should make sure your data is fully backed up. Then it's up to you, you can keep trying to use the hard drive and hope it doesn't get any worse and it might not but then again you could wake up next week and try to start the computer and the hard drive is now dead.

 

You can open an Elevated Admin command prompt and issue the following command to test and repair both drives. If it finds a bad block it will try to fix what it can and then mark the block or region as non usable going forward.

CHKDSK C: /F

CHKDSK D: /F

It will say it cannot lock the drive in most cases and ask if you want to run the check on restart. Press the Y key to tell it yes. Then restart the computer and let the disk check run.

If you need further help on how to do this please let us know

Thank you @jeffers

 

I did that, restarted, and it ran a repair on both the C and D drive on startup. I'm not sure it that actually did anything or not? 

I should mention that a few months back I actually got a black screen of death. Nothing would work to solve the problem so I had to do a reinstall of Windows. Everything seemed fine until a few days ago when I got the black screen AGAIN. And again I had to reinstall Windows. Both times I reinstalled Malwarebytes but this last one was the first time it crashed to the BSoD. After the last install it also did a file check and repair. 

[AdvancedSetup]

To me it does sound like you should really consider replacing the hard drive. If you just reinstalled Windows and you're having a new bad block message that's not a good thing and might be there reason you're having so many issues.

We can try looking at more things if the issue continues but I would highly suggest looking at replacing the drive.