Windows XP hanging on aswrvrt.sys at startup

system · 2014-01-17T14:45:48.000Z

Windows XP system is hanging on aswrvrt.sys at startup. This also happens even when I try to load in safe mode. Attached please find my frst.txt file. Can you please help me? Thanks in advance.

essexboy · 2014-01-17T15:55:10.000Z

Download the attached fixlist.txt to the same location as FRST
Run FRST and press FIX

Once done try a reboot to normal mode

system · 2014-01-17T19:37:06.000Z

Thank you very much for your quick reply. Much appreciated. Managed to skip the avast drivers, but now hanging at Mup.sys. I guess you cannot help me further, it seems there are more problems on this pc.

system · 2014-01-17T19:44:31.000Z

ftanti post:3:

Thank you very much for your quick reply. Much appreciated. Managed to skip the avast drivers, but now hanging at Mup.sys. I guess you cannot help me further, it seems there are more problems on this pc.

Essexboy is on many Forums and expert…he will respond.
In mean time some reading:
http://www.aitechsolutions.net/mupdotsysXPhang.html
http://www.aitechsolutions.net/winxpnoboot.html
http://answers.microsoft.com/en-us/windows/forum/windows_xp-system/mupsys-error-on-windows-xp-pro/b1483aab-cc1c-4ab5-b7de-9a5ae9a10a40
http://www.bleepingcomputer.com/forums/t/393442/windows-xp-freezes-at-mupsys-in-safe-modeno-administrator-passowrd/
…but don’t try anything until he answers and gives advice on best next-steps…
…I’m sure he will ask…do you have a XP Windows O/S CD/DVD ?..in other words access to this CD/DVD for Repair Console ?

essexboy · 2014-01-17T19:54:08.000Z

A few things to check…

Enter the BIOS and see what the drive is set at i.e. SATA or AHCI
Once there change it to the other option and try a reboot
If it fails then return the BIOS to the initial state

system · 2014-01-17T20:44:46.000Z

No luck. It is currently set to SATA, could not find a way to switch it to AHCI. I have booted XP from a CD and entered the recovery console. Excecuted chkdsk and hard disk seems ok.

essexboy · 2014-01-17T20:49:43.000Z

Did you use chkdsk c: /r

system · 2014-01-17T21:49:33.000Z

I was doing just chkdsk /r, now doing chkdsk c: /r is taking a long time to complete. Seems something wrong with the disk…will let you know what happens when it finishes thanks for the support

essexboy · 2014-01-17T21:55:09.000Z

Aye you need to specify the main drive otherwise it will check the RAM drive where the recovery console is only

system · 2014-01-17T22:01:38.000Z

ftanti post:8:

doing chkdsk c: /r is taking a long time to complete.

Yes, it will…even if nothing is wrong depending on disk size and files could be 30min+.
If there are issues it could take hour+…
If there are TONS of issues longer but at that point who knows if works/solves.
…bottom line…let it run, be patient…go do something else.

essexboy · 2014-01-17T22:08:37.000Z

This error can be caused by corrupt data on the boot sector and chkdsk will repair that

If this reboots normally you will need to repair Avast

system · 2014-01-17T22:12:21.000Z

chkdsk just finished now. Rebooted but still hangs at Mup.sys and then reboots again on its own

essexboy · 2014-01-17T22:29:41.000Z

OK next trick

To start the Recovery Console directly from the Windows XP CD you would do the following:

[*]Insert the Windows XP cd in your computer.[*]Restart your computer so you are booting off of the CD.[*]When the Welcome to Setup screen appears, press the R button on your keyboard to start the Recovery Console.[*]The Recovery Console will start and ask you which Windows installation you would like to log on to. If you have multiple Windows installations, it will list each one, and you would enter the number associated with the installation you would like to work on and press enter. If you have just one Windows installation, type 1 and press enter.[*]It will then prompt you for the Administrator’s password. If there is no password, simply press enter. Otherwise type in the password and then press enter.[*]If you entered the correct password you will now be presented with a C:\Windows> prompt and you can start using the Recovery Console.

Type map and press enter.
It will give you the drive letters.
Note down the letter of you CD-ROM.
If it is a letter other than E you should replace the letter E with your CD drive letter when applying the expand command later on if the command is needed to be applied.

Type following commmands, pressing Enter after each one.

[*]ren c:\windows\system32\drivers\atapi.sys atapi.old
(It will returns to the prompt again without notification)[*]copy c:\windows\servicepackfiles\i386\atapi.sys c:\windows\system32\drivers
(If you get a notification “1 file(s) copied” you don’t need to do the next expand command and go to exit command. But if you get notification that the file doesn’t exist proceed with expand command)[*]expand e:\I386\atapi.sy_ c:\windows\system32\drivers
(You should be notified that the file expanded)[*]exit

    You may remove the CD or let Windows boot normally.

system · 2014-01-18T08:05:44.000Z

Followed these steps, rebooted and hangs at the same place.

essexboy · 2014-01-18T14:40:24.000Z

OK another trick is to restore the computer outside of windows in a Linux base

Download http://unetbootin.sourceforge.net/unetbootin-xpud-windows-latest.exe & http://noahdfear.net/downloads/bootable/xPUD/xpud-0.9.2.iso to the desktop of your clean computer
[*]Insert your USB drive
[*]Press Start > My Computer > right click your USB drive > choose Format > Quick format
[*]Double click the unetbootin-xpud-windows-387.exe that you just downloaded
[*]Press Run then OK
[*]Select the DiskImage option then click the browse button located on the right side of the textbox field.
[*]Browse to and select the xpud-0.9.2.iso file you downloaded
[]Verify the correct drive letter is selected for your USB device then click OK
[]It will install a little bootable OS on your USB device
[*]Once the files have been written to the device you will be prompted to reboot ~ do not reboot and instead just Exit the UNetbootin interface

Download http://noahdfear.net/downloads/rst.sh to the USB drive
[*]Boot the Sick computer to xPUD.
[*]Press File
[*]Expand mnt
[*]Expand your USB (sdb1)
[*]Confirm that you see rst.sh that you downloaded there
[*]Press Tool at the top
[*]Choose Open Terminal
[*]Type bash rst.sh
[*]Press Enter
[*]After it has finished a report will be located in the USB drive (sdb1) named enum.log
[]Plug that USB back into the clean computer and open it
[]Then post the contents here

system · 2014-01-18T20:36:14.000Z

Essexboy, how about a manual registry restore ?

essexboy · 2014-01-18T22:02:43.000Z

As it stands the registry does not appear damaged… But, lets give it a shot

From the recovery console command prompt type the following pressing enter after each line :

[b]CD C:\windows
md tmp
copy c:\windows\system32\config\system c:\windows\tmp\system.bak
copy c:\windows\system32\config\software c:\windows\tmp\software.bak
copy c:\windows\system32\config\sam c:\windows\tmp\sam.bak
copy c:\windows\system32\config\security c:\windows\tmp\security.bak
copy c:\windows\system32\config\default c:\windows\tmp\default.bak

delete c:\windows\system32\config\system
delete c:\windows\system32\config\software
delete c:\windows\system32\config\sam
delete c:\windows\system32\config\security
delete c:\windows\system32\config\default

copy c:\windows\repair\system c:\windows\system32\config\system
copy c:\windows\repair\software c:\windows\system32\config\software
copy c:\windows\repair\sam c:\windows\system32\config\sam
copy c:\windows\repair\security c:\windows\system32\config\security
copy c:\windows\repair\default c:\windows\system32\config\default [/b]

Then try a reboot

system · 2014-01-18T22:41:59.000Z

I will give it a try tomorrow. Seeing this message late in the day Will keep you updated with my progress and thank you again.

system · 2014-01-18T22:55:01.000Z

ftanti post:18:

I will give it a try tomorrow. Seeing this message late in the day Will keep you updated with my progress and thank you again.

First try what Essexboy outlined in last comment of page 1.

system · 2014-01-19T13:49:12.000Z

Ok. I did the steps and here is my result.

Announcements