Skip to main content

ATIH 2016 BSOD Fastfat.SYS with all new USB device

Thread needs solution

Hi everybody,

Just to report , that i have BSOD Fastfat.SYS error, just if i connect a new usb device (usb harddisk,usb key or memorycard) and if my computer have never detect this device before.

All the old device work perfectly without error but if is a new device (first time connected to computer) BSOD each time.

I can boot in safe mode with the new device connected the device manager detect it i restart the computer in classic boot and the new device work without the BSOD.

If i remove ATIH2016 all work done without the Fastfat.sys BSOD Error , if i download and install the last ATIH2016 the BSOD error return for each new device .

My computer is on windows 8.1 Pro with all updates, Ram 4Go ,SSD256 + 1To Hard Drive

Does somebody have a answer or a idea ?

Thanks, (sorry for my poor english i'am French)

0 Users found this helpful

Hi Renaud,

My best guess that this is only happening when Acronis is installed and not when it has been removed is a driver incompatibility.  Acronis installs a couple of drivers by default (snapman.sys is one).  When you uninstall, it should clean those out.  You may have some leftover stuff from Acronis when uninstalling (registry or leftover folders).

I would suggest, uninistalling Acronis again from control panel.  Then run the clean tool from my signature.  Then reboot.  After rebooting, check to see if any of these still remain and delete them if they do:

C:\Program Files (x86)\Acronis         C:\Program Files\Acronis        C:\Program Files (x86)\Common Files\Acronis        C:\Program Files\Common Files\Acronis     C:\ProgramData\Acronis

If you do have them and manually delete them, then reboot again.

Log back in with an account that has admin access to the system.  Log into your Acronis account and download the latest version of your Acronis Installer.  Once downloaded, right-click on it and "run as administrator" (even though logged in as administrator already) to ensure the highest credentials possible for the installer.  Then launch the application and register it reboot again and see if the BSOD is still there or not.

 

 

Hello Renaud, from searching in Google there can be many causes of BSOD associated with FastFAT.sys that have nothing in common with having ATIH 2016 installed, and there very few similar reports suggesting that the problem is caused by ATIH.

See https://forum.acronis.com/forum/110248 for suggestions given to another user with BSOD's.

See http://www.eightforums.com/bsod-crashes-debugging/ for help in solving issues with BSOD and Windows 8.1.

Have you tested booting normally into Windows 8.1 and disabling / closing all Acronis Services and Processes/Programs before inserting one of the new USB devices that trigger a BSOD on your system?  This will give a better indication of whether the issue has any relation to ATIH 2016.

There is a free utility called Who Crashed which can do a quick analysis of Windows crash dumps that the BSOD will create, this will give a better pointer to the potential cause.

 

Looks like it could even be bad/corrupt memory...  The following Microsoft KB article is for an older OS, but may apply regarding checking memory and or an additional recommendation for repairing the Fastfat.sys file.

 

Error Message Occurs with Damaged RAM or if the Fastfat.sys File Is Damaged or Missing

This article has been archived. It is offered "as is" and will no longer be updated.

Symptoms

When you start your computer, you may receive the following error message:

Windows could not start because the following file is missing or corrupt: System32\Drivers\FastFAT.sys

Cause

This issue may occur if either of the following conditions exist:

  • The Fastfat.sys file is damaged or missing.
  • The RAM in your computer is damaged or is not installed correctly.

Resolution

To resolve this issue:

  1. Make sure that the RAM in your computer is not damaged and is installed correctly:

    Warning In the following procedure, you will remove RAM from your computer. Do not complete this procedure unless you are very familiar with the correct precautions to use when you remove internal computer hardware components. The internal components of some computers may be damaged by static electricity discharge, use of too much force for removal or insertion, or the use of inappropriate tools. Microsoft recommends that you contact a qualified technician for repair of internal computer components. For information about the correct handling of computer components, contact your computer manufacturer. 

    For information about how to contact your computer manufacturer, visit the following Web site:

    http://support.microsoft.com/gp/vendors/en-us

    1. Turn off your computer.
    2. Remove the memory modules that are installed in your computer, but leave enough RAM for your computer to start and run Windows. For more information about the Windows RAM requirements, click the following article number to view the article in the Microsoft Knowledge Base:

      304297 System requirements for Microsoft Windows 2000 operating systems

    3. Start your computer. If you still receive the error message that is described in the "Symptoms" section of this article, remove a different memory module. You may have to restart your computer several times to identify the specific memory module that is not working correctly.
    4. If you determine that one or more memory modules are damaged, replace the damaged RAM, and then test to determine if the issue is resolved. If the issue is resolved, do not complete the remaining steps. If the issue is not resolved or you determine that none of your memory modules are damaged, go to step 2.
  2. Important If your computer is using the NTFS file system, you cannot use the following procedure to expand the Fastfat.sys file. Instead, you must create a parallel installation of Windows 2000. For additional information about how to create a parallel installation of Windows 2000, click the following article number to view the article in the Microsoft Knowledge Base:

    266465 HOW TO: Perform a Parallel Installation of Windows 2000

    Start your computer by using a startup disk that contains drivers for your CD-ROM drive. For example, you can use a startup disk from a computer that is running Microsoft Windows 98 or Microsoft Windows Millennium Edition.

  3. At the command prompt, type cd c:\winnt\system32\drivers, and then press ENTER.
  4. Type dir fastfat.sys, and then press ENTER. If you receive a "File not found" message, go to step 6. If you do not receive a "File not found" message, go to the next step.
  5. Type ren fastfat.sys fastfat.old, and then press ENTER.
  6. Type CD-ROM drive letter:, and then press ENTER.
  7. Type cd i386, and then press ENTER.
  8. Type expand.exe fastfat.sy_ c:\winnt\system32\drivers\fastfat.sys, and then press ENTER.
  9. Type c:, and then press ENTER.
  10. Restart your computer.

for : Bobbo_3C0X1

I have make a fresh of ATIH 2016 run in adminitrator mode with the cleaning with the utility before  , same issue always BSOD with new device.

Is not a memory hardware issue dont't forget no BSOD if i remove ATIH2016  

for : Steve Smith

Concerning the another user with the BSOD is not the same issue (hardware interrupt)

I have already tested with closing many service , remove all software startup same issue

Thank for Who Crashed i didn't know but is the same as Blue Screen viewer and they say the same FastFat.sys exception no more ...

I'am agree with Steve Smith is drivers compatility issue , if i remove the upperfilter fltsrv of diskdrive filters i'am no more BSOD with a new device but ATIH2016 not working ...

if i add fltsrv in upperfilter after Partmgr the BSOD is back with a new device .

I'm sure the culprit is fltsrv.sys (156Ko) my version is 1.3.0.2227 signed

If someone can say me is the correct version or not ?

Thanks All

Renaud, your version of fltsrv.sys is the same as that installed on my Windows 10 system.

Do you see any errors in the Windows Event Logs for the time of the BSOD that might show more information?

Attachment Size
334905-126304.png 10.91 KB

Run a repair on your Windows installation if you are using Windows 8 or above.  Open an Admin command prompt and type DISM.exe/Online/Cleanup-image/Restorehealth

Opening a command prompt with "run as administrator" and running
 

sfc /scannow

 

wouldn't hurt either. 

sfc /scannow

found no integrity file error

DISM.exe /Online /Cleanup-image/Scanhealth

DISM.exe /Online /Cleanup-image/Restorehealth

always a BSOD with any device, i attempt to update all drivers of my asus laptop but no more result.

If i réinstall my os i can check if the problem is here or not but a réinstall just for one software ...

I give up for the time I would spend to windows 10 soon (in some months it would be most mature ) .

By cons I really regret not having support directly with acronis and I'd remember it !

Thank you all for your time and advice.

 

Hi Renaud,

I believe you would have a valid recovery case that should not require PPI and with technical support. I might be wrong though, but it would not hurt to reach out to them to start one.  I will post your thread in the MVP forum to have the support engineers take a look and hopefully they will get back directly to you.  Im the mean time, please try to open a support case directly and see how it goes:

18623: How to get Technical Support: Tips, Tricks and Useful Information

5.    Recovery issue
- Related to recovery issues with the full version of the product
- Free of charge
- 24x7
- Not limited (Assistance with the recovery issue can be requested any time, even if you’re out of 30 days free support and don’t have PPI)
- Provided with e-mail and chat
Response time:
-  3 business days via e-mail
 - immediate via chat

There are a good number of things that could be the source of the problem.  Given the posts so far it is I think obviuos a driver corruption error or a hardware issue.  It also could be Malware but using a good scanner should find and fix it if so.

I have read that tseting your RAM for a fauly module is a recommended practice for such errors. 

Troubleshooting system file errors often take a long time and from my experience it's always the very last thing you try when you've pulled out all your hair that utimately fixes the problem.