The other day i applied a bunch of windows updates to my PC (don’t remember which, i hadn’t been updating in a while).
Everything looked ok, but when i tried to turn the pc on the following morning, Win7 stopped booting. It just hangs on the windows logo and never moves from there.
I tried booting in safe mode and noticed the same thing happens and Win7 stops loading when it reaches driver aswrvrt.sys.
After some research i gathered that this is something avast-related…can anyone help me?
What should i provide to make it easier to troubleshoot the issue?
On a side note: i tried a system restore to the day the updates were installed, but it was no help.
Insert the USB into the sick computer and start the computer. First ensuring that the system is set to boot from USB
Note: If you are not sure how to do that follow the instructions Here
Windows 7 and Vista screenshots
When you reboot you will see this. Click repair my computer
notepad and press Enter.
The notepad opens. Under File menu select Open.
Select “Computer” and find your flash drive letter and close the notepad.
In the command window type e:\frst64.exe or e:\frst.exe dependant on system
and press Enter Note: Replace letter e with the drive letter of your flash drive.
The tool will start to run.
When the tool opens click Yes to disclaimer.
How long should FRST take to launch? I downloaded the 64 bit version as my OS, but whenever i launch it it never starts. Checking with the task manager it’s stuck on not responding.
I made the mistake of trying again but not being fast enough with the boot selection, and for some reason there was a disk check scheduled for the C drive which i wasn’t able to skip no matter how much i pressed ‘any’ key.
It’s slowly advancing and finding a shitload of errors, which surely doesn’t make me happy.
I’ll be back once it’s completed, and try again to get the log from FRST.
I agree…especially depending on the errors/fixes you are getting…bad sectors ? file system corruption ?
I’d let it finish no matter how long it takes and hopefully you can boot.
If not, perhaps the FRST log will allow Essexboy to tweak and get to boot.
Alright, here’s the situation after yesterday: i came home to a windows login screen. Everything appeared to be working, i was able to log in and the pc looked ok.
I turned the pc off and went to bed. Now i’m back from work and i turned the pc on again and again it’s going through the checkdisk, and again it’s moving very slowly (it’s at 6% now and it started again with the “File record segment x is unreadable”. I’m wondering if this was caused by the system restore, as nothing of this happened before i tried that.
I’ll wait some more and see if it completes the check again and if it does, if it gets me to the login screen again.
If that happens i’ll try the HDD integrity utils and the OS reload.
The disk itself is only a few months old, it didn’t got hit or anything so i hope there’s no HW failure incoming. If i lose those 3tb of data i’m going to be very, very sad, lol.
I’ll keep you posted. Thank you very much for the help
Once this chkdsk has finished and you get into windows
Run an elevated command prompt to stop any loop that is currently set by using the following command :
If it was me and the PC booted and I got into Windows I’d hook a USB HDD up to it and pull/copy all my important data off.
I would do this prior to any other efforts…
HDDs drives are known to crash in my experience in four main scenarios…
Old and just too much wear over time…this can be many years though.
A hard drop…usually from dropping PC.
Heat…HDD running at 55C+ will die fairly quickly.
Infant Mortality…which is what I think you have…basically a bad HDD that exhibits early in life cycle.
Ok, new situation.
The scan stopped with a “an unknown error occurred” after running for two days.
Good news is that at least i was able to run FRST and scan for the log which i’m attaching.
At this point i’ll just be happy if i manage to get to windows and backup all my stuff before sending this disk for an RMA and getting a new one.
No luck - it stayed on the starting windows screen for a couple of minutes then diskcheck.
I had run the command you suggested through the prompt earlier though.
I tried cancelling it before it started but then the screen got stuck there.
In hindsight i shouldn’t have turned the pc off that one time it had booted
Ok, i’m a blind dumbass. I just noticed the disk check was being triggered on a different drive which had the same name (old installation of windows on another disk). I disconnected said disk and tried to boot again and voila!, it appears it’s more or less working now.
