Hello, help please. Having a spot of bother with XP, which died with BSOD when I plugged an sd card in full of photos.
I presume avast tried to scan it causing BSOD. managed to re-boot into safe mode once, but now hangs on aswrvrt.sys like several others have experienced.
Ah, I’m not sure this is going to work, as I’ve got a RAID 0 as my system disk.
Please see the attached frst.txt file, but I suspect the relevant info is missing as the RAID driver probably hasn’t loaded
Have you tried a chkdsk /r from the recovery console ?
Thanks for the reply I was hoping you’d be along.
Up to press I’ve been struggling to get any of my boot CDs to recognise my hard drive due to the RAID 0 problem.
BART CD wasn’t working (In that it can’r see the C drive, even after F6 to load RAID drivers, similarly OTLPENet.exe
Even tried letting it boot to the HD and then F10 to interrupt and to get to the RAID console and trying to continue from there, using the HD RAID drivers that it had clearly seen (It tells me that the array is healthy, so the HD looks to be OK).
It appears to be a corruption of the MFT and I am not sure how that affects a raid drive
The thing is I cannot even invoke a restore point as FRST cannot read that data
Thankyou for the reply.Finally managed to get into XP recovery console as I remembered a made an XPSP3 slipstream disk earlier on in the year. My XP SP 1 & 2 disks wouldn’t boot as they recognised the XP SP3 installation and just defaulted t that, and the endless re-boot BSOD cuycle.
Now running CHKDSK /r to see if that does anything.
Failing that, any ideas of the easiest way to prevent Windows invoking the aswrvrt.exe driver from recovery console?
If all else fails, I did manage to boot to an old Paragon 10 Partition Manager CD, which recognised the C drive, so I must have included the RAID drivers when I made it.
I can then clear off a spare partion which I originally intended to keep free for a dual boot system with Linux, but never got round to it. I’ve just picked up a ligit copy of Windows 7, with the intention of making a dual boot system with that for some new photo developing software that doesn’t run under XP.
looks like it might be sooner rather than later.
Could I run FRST from a floppy under recovery Console and then upload it to this board from there?
If that should fail, I will remove all services and drivers for Avast but it may well then fail on the next driver. Yes run FRST from recovery console
Cheers, up to 70% and progressing very slowly, so I suspect it must be quite busy mending stuff.
This is the second time lately that Avast has caused a crash, but last time I was able to get into Safe Mode & msconfig to disable it on startup. I thought it was commodo to start with so binned that and went back to Windows firewall
The thing to bear in mind is that windows always stops on the last successfully loaded driver, not the one causing the problem
Ah, hadn’t realised that 
Also tried copying FRST to a floppy, changing to A: under recovery console, but on typing frst.exe I get “the command is not recognised”
CHKDSK finally finished, so lets see what happens on a re-boot unless you’ve any other ideas on running FRST from here first
Rats, BSOD on re-boot locks on aswrvrt.exe in safe mode.
Unfortunately as it stands I am unable to remove anything due to the hives being inaccessible
From the recovery console are you able to run Chkdsk c: /r
Yes that ran fine and I can access the various partitions on the RAID 0 disk from recovery console after booting from XPSP3 and RAID drivers on floppy.
Trouble is, that none of my other windows boot disks are working even though I’m loading the RAID drivers.
even XPSP2 doesn’t load, it just defaults to the faulty HDD installation.
Just contemplating using the Paragon boot disk to clear off a spare partition for Windows 7
I do have a ghost copy of a fairly recent backup, but the Ghost CD can’t see it at the moment.
Sounds as though one of the raid drivers may be corrupt… But as I say I know little about raid drives
pretty sure RAID drivers OK as they work with XPSP3 boot disk
Just booting into Paragon, which I think will let me re-name files if I know what to rename to prevent it running
Also RAID drivers on HDD are OK as they recognise the HDD on boot up. I probably just need to find a way to disable Avast from trying to boot on startup
Just an addendum, still struggling, but misinfoirmed you earlier. I’m actually on a RAID 1 array, i.e.duplicated not striped
Thanks, I will do some research on that
Hi,
peak4, if your Raid 1 is enable on the adapter, and you can see the correct partitions under OS (not duplicated partitions), your Raid is just fine. Deal with it has a regular drive.
I’m also getting a BSoD at aswRvrt.sys no matter what option I choose to boot, with ex code
Can anybody please advice?
Thanks
Thanksyou, Yes Raid is OK on HDD, but when drivers loaded from floppy during otlpenet.exe or BARTCD, the subsequently booted environment doesn’t show the drive.
Also I’ve an ancient backup of the drive using Parotion manager, whose boot cd does display the RAID partitions correctly. Last resort is to break the RAID 1 by unplugging a disk, restoring the PM backup and from there using Ghost to pull back a recent image from within the very old windows environment rather than trying to boot from the Ghost CD which doesn’t see the HDD
However the floppy with drivers must be OK as XPSP3 (only not xpSP1 or2) works OK sometimes.
I’ve currently got it up and running in Recovery Console after repeated attempts.
Can anyone supply a comprehensive list of drivers to disable? Do the all begin with ASW?
I’m hoping to use LISTSVC & DISABLE commands if I know which ones to kill.
LISTSVC seems to point to the following 8 drivers
aswFsBLK
aswMonFlt
AswRdr
aswRvrt
aswSnx
aswSP
aswTdi
aswVmm
Anything else I should be disabling please?