Done with Bad Sector checking also. Returned same results. No problem found in the drive or disk. Btw, in a separate para something more is written like if you have removed the disk before all files were written copy them or something like that. Is it important?
I would imagine that's to do with trying to remove the disk before the disk check has completed.
In view of the fact you've found nothing untoward, have you considered my earlier suggestion to remove Kaspersky?
It seems more than coincidence the this problem occurred after you were prompted about your renewal.
SFC/ SCANNOW is showing that there are two ways of doing it. From within the windows and when booting it. Which one do I need to choose? I am a bit wary about booting again as I don't know if it will start or just hang again.
Try Option 1 first, and if it won't play nicely try Option 2.
Did the SFC/verifyonly. It showed no violation of System integrity found. Does that mean there is nothing wrong with my system files? I am not keen on uninstalling Kaspersky. Last time I did it, my PC was infected within a day and had to reinstall the whole thing.
If SFC found nothing, chances are your system files are OK.
I don't know where you're going to have your computer infected so quickly, but in 20 years of using a personal computer I've never had a virus of any sort.
I would still recommend uninstalling Kaspersky as it seems the problem only occurred when you were prompted about renewing your subscription - Kasperky's way of encouraging you to renew? Perish the thought! :)
If you do uninstall it and it solves your problem I'd advise ditching Kaspersky altogether and use Microsoft's freebie, Microsoft Security Essentials.
http://www.microsoft.com/en-gb/secur...urity/mse.aspx
I have already bought a newer version of Kaspersky. Was just waiting for this license to expire. I have been using Kaspersky for 3 years, never had any problem. Don't really know if it's because of the license thing.Will reinstall within a few days. In the meanwhile, can the problem be resulting from any faulty hardware? Other than the HDD I mean, since I have already checked that yesterday.
It can be hardware. Hardware issues could include: failing hardware, hardware that is not seated properly, damaged hardware due to electrostatic discharge, etc.
WarningBefore you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer.WARNING: The steps that follow can void your warranty!!!
Strip down your system to run only the bare essentials: one RAM module, the CPU, motherboard, one hard disk, one graphics card (or use onboard graphics if you have it), keyboard, mouse, and one monitor. See how the system behaves. If it is stable, add one piece of hardware back at a time until you get crashes/freezes again. Take notes of what hardware you add and how the system responds to the hardware changes.
As you add and remove hardware, follow these steps for ESD safety:
- Shut down and turn off your computer.
- Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
- Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
- Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working. If you do not have an anti-static workbench, desk, or pad, you can use your computer tower/case by finding a metal hold in it, such as a drive bay.
Once these steps have been followed, it is safe to remove and replace components within your computer.
It could also be software that causes conflicts with the system.
Could be viruses/malware.
- Download and install Malwarebytes, update it, do not start the free trial, and then run a full scan. Also run a full scan with your antivirus software installed on your system. If you do not have antivirus software installed, see the Good and Free system security combination. for better security steps and scanning tools. Make sure to update the security software before running the full scan.
Could be a corrupted operating system.
Check Windows for corruption. Run SFC /SCANNOW Command - System File Checker up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations. Use OPTION THREE of SFC /SCANNOW Command - System File Checker to provide us with the sfcdetails.txt file if errors occur.
You may also have a corrupted Windows registry that SFC will not pick up.
- This would require a Repair Install of Windows. See steps 1-3 of Clean Reinstall - Factory OEM Windows 7 if you need installation media and steps for backing up important data prior to the repair install.
I usually recommend backing up important data prior to a repair install in case it is unsuccessful. Very rarely is it unsuccessful, but it is best to be safe.
May be corrupted, conflicting, or outdated drivers on the system.
- An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:
a. Backup your system and user filesThe idea with Verifier is to cause the system to crash, so do the things you normally do that cause crashes. After you have a few crashes, upload the crash reports for us to take a look and try to find patterns.
b. Create a system restore point
c. If you do not have a Windows 7 DVD, Create a system repair disc
d. In Windows 7:
- Click the Start Menu
- Type verifier in Search programs and files (do not hit enter)
- Right click verifier and click Run as administrator
- Put a tick in Create custom settings (for code developers) and click next
- Put a tick in Select individual settings from a full list and click next
- Set up the individual settings as in the image and click next
Attachment 212027- Put a tick in Select driver names from a list
- Put a tick next to all non-Microsoft drivers.
- Click Finish.
- Restart your computer.
If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using System Restore OPTION TWO.
Thanks to zigzag3143 for contributing to the Verifier steps.
If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.
When you are ready to disable Verifier: Start Menu -> All Programs -> Accessories -> Right click Command Prompt -> Run as administrator -> Type the following command and then Enter:verifier /reset-> Restart your computer.
Had a BSOD couple of hours back. But can't upload minidump file since it was not created. It just froze in the BSOD screen showing starting minidump process, so I restarted manually. There it showed that the BSOD is caused by some driver that ought not to be there or something like that. Talked about freed memory or some such stuff. Question is how do I determine which driver it is?
Verify the non-Microsoft drivers 5 at a time. Sometimes, having all non-Microsoft drivers verified results in the .dmp files not being created. Verify each set for 36 hours, or until you get a crash, whichever comes first.
Quote