Install Acronis True Image 2014 without the mount facility
On my Windows 8.1 system I've recently experienced sporadic BSODs which were apparently caused by CLFS.SYS.
According to the techie on the Windows 8 Forum this may be due to SPTD and/or Acronis True Image 2014.
He has suggested that I remove SPTD and True Image.
Is there any way to install True Image without the Image Mount feature?


- Log in to post comments

Might be worth checking the integrity of the clfs files. See this http://www.ehow.com/how_12151499_fix-clfssys-software.html . Note the error in step 3. You need to replace System32 with System32\Drivers. I did the check from within Windows by opening a command prompt as Administrator. Look at the attached jpg.
Attachment | Size |
---|---|
172505-112165.jpg | 32.5 KB |
- Log in to post comments

The problem has occurred once or twice in the past 4 months and does not appear to be related to any driver updates.
SPTD is SCSI Pass Through Direct. It provides a Virtual Drive facility enabling the mounting of disk image files; this facility is part of Windows 8 so it would seem that SPTD is redundant in Windows 8 systems.
I do have the latest version.
- Log in to post comments

- Log in to post comments

You entered the wrong location for clfs.sys. It is at C:\Windows\System32\Drivers\clfs.sys.
- Log in to post comments

OK
Now get this:-
C:\WINDOWS\system32>SFC /ScanFile=C:\Windows\System32\Drivers\clfs.sys
Windows Resource Protection did not find any integrity violations.
C:\WINDOWS\system32>SFC /ScanFile=C:\Windows\System32\clfsw32.dll
Windows Resource Protection did not find any integrity violations.
C:\WINDOWS\system32>
- Log in to post comments

Now you know your files are good.
Acronis uses two services for image mounting (tib and tib_mounter). I looked at both of them in Dependency Walker. They both depend on the clfs.sys service. I don't think that either one would be calling clfs if you weren't trying to mount an image. TI also uses TibMounterMonitor.exe. I looked at that in Dependency Walker and didn't see any calls for clsf.sys. I don't think TI is causing the problem, but you never know. You could always uninstall TI and see what happens. If you do uninstall TI, make sure the tib and tib_mounter services are gone. Do this by entering net start tib and net start tib_mounter in an Administator command prompt. You should see that the service names are invalid.
- Log in to post comments

Agree with Mustang here, could not find where clfs.sys was used unless called by TI. Can you. recall what processes or apps you were or had used immediately before or at the time of BSOD? If you can recall might help narrow it down.
- Log in to post comments