BSOD Memory Management (poss. iastor.sys)

axe0 said:

Revo will not find anything about Acronis and IRST without them installed.

I don't have source for IRST -- it appears to be a Dell driver and there is nothing on the Dell site indicating an update for it for this particular computer. I have researched this driver (iastor.sys) for this machine and found nothing as an update or installation for it.

Acronis hosed my computer so badly that I don't want it near my computer. I understand the logic, but I'd like to find another way to remove it other than re-installing it.

If the computer would run for longer than three or four minutes I'd look in the registry for it.

thanks,
Tom

axe0 said:

Move the drivers somwhere else.
If moving them doesn't give problems, then delete them.

Update & FYI:

Attempt to install Acronis TrueImage 2012 fails with message "this software doesn't work with Windows 10"

Removing all Acronis / TrueImage registry entries does not stop BSOD

The Acronis drivers, according to what I've read, are inserted in between system drivers and can't be easily removed (though that's what I'm going to work on now).

WRT Intel driver iastor.sys -- the registry entries are protected and can't be deleted. It can be found under:
Device Manager > IDE ATA/ATAPI controllers > Intel 7 Series Chipset Family SATA AHCI Controller > iastor.sys
(my laptop uses iastorA.sys)

I tried to update the driver but it is current. Then, uninstalled it and rebooted and it came back. Then, uninstalled it and removed the software (iastor.sys) and rebooted -- crashed saying couldn't find boot device.

So -- apparently the iastor.sys is not a RAID controller in this circumstance but the SATA AHCI controller and I'm stuck with it.

I'm going to work on the Acronis angle, but wonder if there is something else that is being overlooked.

thanks again,
Tom

axe0 said:

Indeed, I forgot the iastor.sys doesn't have to be RAID.

If you would give me an updated zip file created by the DM Log Collector tool, I'll take another extra good look.

I have removed all vestiges of Acronis from the registry and renamed the drivers -- vsflt53.sys, vsflt61.sys and snapman.sys -- and everything seems to be working OK.

I remembered I had PerfectDisk 12 installed and there is a notice on their site that it requires special handling to remove it once Windows 10 is installed. I will work on removing it and then see if BSOD remains and will get back with you one way or the other.

thanks

I posted the note similar to what is below but it didn't show up ... will try again.

I believe the problem is resolved -- and that PerfectDisk 12.5 was the cause of BSOD Memory Management error.

The Acronis drivers surely didn't help, but apparently PerfectDisk was the primary cause of the crash. It makes sense now -- I could use the computer for 3 to 5 minutes before it crashed, just enough time for PerfectDisk to begin background defragmentation. Now that PD is removed, the computer has been running over 4 hours without a hitch.

It was not possible to remove PerfectDisk through the control panel > programs interface. It had to be removed with a tool they provide for that purpose. For the record -- PerfectDisk is a good product. I just didn't upgrade from ver. 12.5 as it worked okay on Win-7 (they are on v. 14 now).
Removal tool for PD -- Tools Utilities | Raxco Software

I removed all references to Acronis from the registry and everything appeared to be okay until I tried to access a USB device. It turns out that Acronis' snapman.sys was one of the drivers. Once I'd removed that, the USB worked again. FWIW, the information for removing Acronis TrueImage from the registry came from:
Leftover Drivers? | Acronis Forum

I have marked this thread as solved.