EldoS | Feel safer!

Software components for data protection, secure storage and transfer


Posted: 08/17/2011 02:20:42
by Pol R (Basic support level)
Joined: 06/22/2011
Posts: 10

We are performing testing with our system and get occasional blue screens

Is it a known problems?
When should it be solved?


[ Download ]
Posted: 08/17/2011 05:46:16
by Eugene Mayevski (Team)

Blue screen is a way of the OS to report about an error (and almost any error in kernel is fatal). So the question of "when will it be solved" is not applicable - nobody can say "now the system is free of errors".

Our developer will take a look at the particular report you've sent and will fix it for the pre-release version of CBFS. It's possible, that the error has already been fixed (if it's an issue of the cache that has been added in version 3.2).

But in general blue screen is just an error message, and it can happen due to many factors, from hardware failure to incorrect operation of some filter driver of some antivirus, firewall etc. . In some cases blue screens are just a coincidence with one's use of CBFS, i.e. the error happens elsewhere and is not related to CBFS or other our product.

Sincerely yours
Eugene Mayevski
Posted: 08/17/2011 05:54:35
by Volodymyr Zinin (Team)

Hello Pol,

The dumps show that a driver AVGIDSFilter.sys (which it seems belongs to one of AVG products) sent incorrect request to CallbackFS and that caused BSODs.
Update the AVG products installed on your machine and if the problem occurs again please send the dump to us.
Also we are going to make a new build (perhaps it will be today). So it would be better if that one was used.
Posted: 08/17/2011 11:14:43
by Eric Dahlvang (Standard support level)
Joined: 09/11/2009
Posts: 29

The dumps show that a driver AVGIDSFilter.sys (which it seems belongs to one of AVG products) sent incorrect request to CallbackFS and that caused BSODs.

Shouldn't the CallbackFS be resilient enough to allow applications to send incorrect requests without crashing the system? We cannot control every application installed on every client machine, and it is unreasonable to assume that every application is going to behave appropriately. I assume there are other file system drivers that AVG is calling incorrectly, that are not blue screening as a result.
Posted: 08/17/2011 11:27:05
by Eugene Mayevski (Team)

It's not our driver that crashed, but AVG's one ;)

Sincerely yours
Eugene Mayevski
Posted: 08/17/2011 12:03:32
by Volodymyr Zinin (Team)

We always try to support the CallbackFS driver to be maximally reliable and of course incorrect requests from user mode applications are handled without BSODs. But in this case it's a kernel mode driver which sends the requests, and usually Windows kernel mode code (i.e. drivers as well as Windows kernel) trusts and doesn't check for the requests from another kernel mode components. At least Microsoft recommends this in order to make the kernel as fast as possible and based on an assumption that the kernel components are well tested and don't contain bugs.
In the situation the BSOD occurs the AVG driver sends incorrect request which CallbackFS has been able to process without crash but then AVG itself causes a BSOD when postprocessing it.



Topic viewed 1818 times

Number of guests: 1, registered members: 0, in total hidden: 0


Back to top

As of July 15, 2016 EldoS business operates as a division of /n software, inc. For more information, please read the announcement.

Got it!