The WriteFile and ReadFile functions return ERROR_NOT_ENOUGH_MEMORY - where can there be a rake?

Question

C++ / C#

Such a question - there is a computer (restored from the image by acronis). Win7 32-bit SP1. After the customer rolled on it security patches (required by the company's policy), the desktop application began to spontaneously throw ERROR_NOT_ENOUGH_MEMORY when reading and writing files. It can work ten days without failures, and it can throw ten failures a day. The industrial system is running 24x7, so this is pretty critical. Memory consumption - the first thing we checked, everything is fine there. Moreover, OutOfMemory can be caught from time to time, even just copying small files in the explorer.
The tutorial says this:
The WriteFile function may fail with ERROR_INVALID_USER_BUFFER or ERROR_NOT_ENOUGH_MEMORYwhenever there are too many outstanding asynchronous I/O requests.
I strongly sin on Symantec Endpoint Protection and Acronis.
I have the image in my hands and there the problem is reproduced by a simple test program that simply writes and reads files through fwrite and fread.
Of course, we will rearrange everything from scratch and most likely it will take off, but I want to figure it out, because I'm meticulous. The seven 32 bits cannot be changed - there is a tricky piece of iron and there is a driver only for this OS. I read Russinovich , ran through the Process Explorer processes and did not see any anomalies. "too many outstanding asynchronous I/O requests" confuses me a lot. Nowhere is there any information "too many" - is it generally how much and with what counter can I look at this matter?

Answer 1

Well, if you sin against the antivirus, put the files that the program uses into exceptions for AV.