That message indicates a problem with the NT File System (NTFS).
Since the message (and BSOD) are coming from Windows the OS is at least starting to load but then has a problem.
I can't imagine running a virus scan would cause a problem like that.
What I can imagine will cause a problem like that are things like a power failure, using the power button, using the reset button, plug pulling, battery removal, ungraceful shutdown, aborted restart, etc.
Have any of those events occurred?
Answer the following questions as best you can:
What is your system make and model?
If a Dell what is the Service Tag number?
If an HP what is the serial number?
Does the system have a working CD/DVD drive?
Do you have a genuine bootable Windows 7 SP1 installation CD/DVD?
What was the issue you were having that brought about this virus scan or was it just a routine scan?
What is the name of the virus scanning tool(s) you used?
Did the scan complete or did you stop it, how did you stop it, did the system restart during the scan?
I would start by running a chkdsk with error correction (chkdsk /r) on the afflicted drive volume but you are going to have to boot on something in order to do that.
You can run a chkdsk with error correction from a Command Prompt from the Windows System Recovery Options screen:
Running chkdsk is fine even if it doesn't find any problems. It will not hurt anything to run it.
Assuming your boot drive is C, run the following command:
chkdsk C: /r
Respond in the affirmative to any "are you sure" kinds of messages.
Let chkdsk finish and correct any problems it might find.
Depending on the size of the volume, the amount of data on the volume, the speed of your system and what the chkdsk finds to do It may take a long time for chkdsk to complete (several to many hours) or it may appear to be 'stuck'. Be patient. If the HDD light is still flashing, chkdsk is doing something. Keep an eye on the percentage amount to be sure it is still making progress. It may even appear to go backwards sometimes.
You should run chkdsk /r again until it finds no errors to correct.
Then see how things look.
Edited by joseibarra, 25 November 2017 - 05:13 PM.