BSOD with error FLTMGR_FILE_SYSTEM 0x000000F5

Does BSOD contain also name of buggy driver drivername.sys ?
If yes, write it please.

This is a bug in filter driver. I think you can to do only two things:

1. You can to to uninstall this driver from system. Probably it is some utility which encrypts/decrypts data on the disk ? Have you installed something like this ?
If yes, try to uninstall it.
Only vendor can fix driver bug and release new version, you can to do nothing with it.
2. Check if you have latest Service Pack in system - if not, install latest SP. Maybe this can help also.

Peter

No drivername !
I install Diskeeper which defragment file system, I will try to uninstall this.

Yes, possible reason, by info which I found it contains file system filter driver.
It probably makes some defragmentation activity in the morning
and it invokes described bug.

But Windows contains defragmentation utility which is part of system,
so why not to use it ?

Peter

check if there is a minidump, and post it for analysis here

Windows defrag utility and Diskeeper are two different things. Diskeeper say on own page: It prevents fragmentation before it can happen, creating a level of disk speed and efficiency previously unapproachable.

Where I can find minidump ? I found only Memory.dmp ?

c:\windows\minidump
Are you running Diskeeper at an elevated administratkive level - RIGHT-click on exe file, run as admin?

In attach.
Diskeeper are running as service, DK is resident in memory and manage Windows write to disk.
Mini122409-01.dmp

I agree - AlfaFF looks to be the cause.  Looking at the maker's site, this sounds suspiciously rootkit-like in what it can do!
http://www.alfasp.com/products.html
You need to find what app has installed it and see if there is an update.  Do you have anything using DRM or any form of security/copy protection?

http://forums.spybot.info/archive/index.php/t-46328.html
This person has both Diskeeper and Alfa File Protector installed (although a different DLL name).
If you look on the right here in the news section, you will see AlfaFF is the same company's doing:
http://www.alfasp.com/
So Diskeeper sounds a possibility.  Check for updates.  If no joy, you could try their official support channel and ask them if they use it, and if they do, that you're getting a BSoD that appears to be from it.

I'm check disk CHKDSK/r , and it seems that problem are gone. Maybe some file's are being corrupted and by night when Diskeeper are doing defrag are came to this file and cause BSOD !
I will report if problem are again repeat.