aswRvrt.sys problem - won't boot, win7

system · 2014-07-22T16:38:24.000Z

Hi
Didn’t see any ref, BSOD was only momentarily on screen before system rebooted.
I ran chkdsk c: /r earlier (took hours!) - there was a message about having to stop current process to do it and handles not being valid before it ran. It ran through but still no joy booting…

Anything else I can try?

Thanks

essexboy · 2014-07-22T17:14:47.000Z

Does not look like it from what I can see. Have you tried a system restore ?

system · 2014-07-22T18:59:59.000Z

Hi
Hell, really? I didn’t think this would be so serious… haven’t done a system restore - will that lose any data? I don’t have any recent images for the machine - a comodo backup from March. That would mean I lose loads of data.

Are there any other options?

Thanks

system · 2014-07-22T19:08:56.000Z

Another (non-tech head) thought - is it possible to delete the aswRvrt.sys from the command prompt or would that be too easy

essexboy · 2014-07-22T19:29:23.000Z

All avast and comodo drivers/services are disabled.

You will lose some data using system restore but if you use this one it will be minimal :

Restore point made on: 2014-07-21 07:15:14

system · 2014-07-22T19:57:31.000Z

just tried restore to one from 18 july - failed and gave same error code as earlier BSOD (0x80070057). Will try more recent one, but not looking hopeful…arrgghhh!

essexboy · 2014-07-22T20:13:16.000Z

If that files then the final shot is SFC

Again from the recovery console command prompt enter the following command :

sfc /scannow /offbootdir=c:\ /offwindir=c:\windows

Once done try two startup repairs

system · 2014-07-22T20:19:18.000Z

Hi
Tried that and two other restore points - no joy. 0x80070057 error. Tried normal boot a few times to see if I could see BSOD for long enough to read it - there’s a long string of ASCII and something about corruption to something but it flies past too quickly to read.

Is there any other possible option that a clean install as I really am going to lose a lot?

Thanks

system · 2014-07-22T20:22:26.000Z

Sorry, missed your last post re sfc /scannow /offbootdir=c:\ /offwindir=c:\windows

will try that now, thanks

system · 2014-07-22T22:09:58.000Z

Hi essexboy,
Thanks for your support on this - much appreciated.
I ran sfc /scannow, which reported that WRP had found and repaired corrupt files and saved details to CBS.log. The two start up repairs found no problems so I tried a normal boot - momentary BSOD again, into restart. Start up repair then offered system restore and attempted repairs… but failed.
Will try to find CBS.log files if you think its worth it?

system · 2014-07-23T08:13:03.000Z

Hi
I disabled auto restart on system fail and got the BSOD info:
Technical information - STOP: 0x0000007B (0xFFFFF880009A97E8, 0XFFFFFFFFC0000034, 0X0000000000000000, 0X0000000000000000).

Is there anything else you can suggest trying?

Thanks again
Andy

system · 2014-07-23T08:25:04.000Z

The startup repair diagnostic details: Boot critical file c:\windows\system32\drivers\aswrvrt.sys is corrupt. Repair action: file repair. Result: Failed. Error code 0x2

system · 2014-07-23T12:01:49.000Z

Hi - some more details of the problem… please let me know if there’s anything else I can try.

Startup repair problem details:
Problem Event Name: StartupRepairOffline
Problem Signature01: 6.1.7600.16385
PS02: 6.1.7600.16385
PS03: unknown
PS04: 21200285
PS05: Autofailover
PS06: 3
PS07: NoRootCause
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033

system · 2014-07-23T12:19:32.000Z

Also, not sure if its relevant or not, but HD is partitioned - When running system recovery, Windows drive letter changes from C: to D: If I open Notepad from command prompt, the system has 3 HDDs listed - RECOVERY (C:) 6.37GB free of 14.6GB; OS (D:) 104GB free of 451GB and Boot (X:) 28.9MB free of 31.3MB

If I open the C: drive, there is a folder called Recovery, with no visible files in it, and an XML file called ADRInfos (4kB size on disk).

I’ve also attached the CBS.log from the SFC scan

essexboy · 2014-07-23T13:18:00.000Z

Aswvrt service is no longer active

C drive in your case is the system drive where all the boot data is

The error code is related to inaccessible boot device. Now there is a possibility that the BIOS has reset to IDE from SATA or vice versa

Step 1 Restart or turn on the PC, and look for a message such as "Press [X] to Go to Setup" or "Press [X] to Enter BIOS." Step 2 Follow the instructions on the boot screen to go to setup. Press "Ctrl-Alt-Del" to restart if the computer begins loading Windows before you can enter the BIOS. Step 3 Use the arrow pad to select an option such as "Advanced," "Integrated Peripherals" or "Main." Press "Enter." Step 4 Select "Storage Configuration," "Drive Configuration," "IDE Configuration" or a similar option, if available. Press "Enter." Step 5 Check setup for an option such as "Configure SATA As," "SATA Mode," "SATA Configuration" or "On-Chip SATA." Step 6 Press "Enter." Choose "IDE," "Compatible" or "ATA" from the menu and press "Enter" again. If pressing "Enter" doesn't bring up a menu, press "+" or "-" to change the parameters of the option. Step 7 Press "Esc" to return to the main menu, or select the "Exit" tab. Select the option to quit the BIOS and save changes. Step 8 Press "Enter" to restart the computer and boot the SATA drive as an IDE device.

system · 2014-07-23T13:35:46.000Z

Hi essexboy
Thanks for responding again. The BIOS allowed me to change the SATA from AHCI to ATA as only option. I did this and tried a reboot and got the BSOD.

essexboy · 2014-07-23T13:41:51.000Z

Could you now switch it back please … I will have another thunk

system · 2014-07-23T14:57:19.000Z

Ok, thanks - I’m praying you come up with something!

essexboy · 2014-07-23T15:49:52.000Z

OK could you run startup repair
Then reboot the computer
Repeat three times with a bootup between each repair

system · 2014-07-23T16:48:48.000Z

Hi

Ok, tried that - startup repair x3,normal boot to BSOD x3. Note, I ran startup repair from the system, not the USB/recovery disk - is this ok. Nothing unusual seemed to happen - system hung at BSOD as before, and restarted to Windows error recovery screen (from where I ran startup repair)…

Announcements