Chkdsk on boot in a new Acer Extensa 5635ZG laptop.

Good to know it's not only in my case and pundits are behind to fix it.

Interesting read, it has shed some light in my understanding of the issue. My main worry of a bad manufactured HDD is now out.

On the matter, do you think the Reliability monitor information messages I reported here some post above which seem to state, if I understand it correctly, that a hard disk driver has been successfully reinstalled, also has something to do with this issue?

I don't have the intention to change Avira AntiVir for another one. I'm now paying for a complete McAfee suit that I ruled out in my old laptop because it was quite slowed down by that antivirus. Well, probably with my new notebook it was not going to be that a problem but now I'm very happy with Avira and actually considering to pay for its complete suit instead of for McAfee's.

I didn't know Avira, neither heard of it before but I had the need to use an antivirus with a lesser memory impact and searching on the web I came across a poll about best free antivirus of the year and Avira was ahead of the standing (by then) along with Avast.

Many, many thanks, ickymay.

ickymay said:

juandiego said:

On the matter, do you think the Reliability monitor information messages I reported here some post above which seem to state, if I understand it correctly, that a hard disk driver has been successfully reinstalled, also has something to do with this issue?

No , because you are still getting the 5038 error

Well, I meant that those messages seemed to state that the same HDD-related driver was installed successfully EVERY day despite I did nothing; by itself. On the other hand, this issue seems to have stopped since I installed the proper HDD and chipset drivers for Win7Pro32bits, at least the message in question has not appeared yesterday nor today.

I've programmed the task -through its Windows security logs option- to warn me when a 5038 error takes place. They keep happening with avgntflt.sys and cpuz132_x32.sys when upon/right after booting (not at random times as I thought before), and with mbamswissarmy.sys when Malwarebytes is run.

However, I have not had an auto check disk process upon boot again since I made the proper HDD and Chipset drivers installation. Perhaps this has also helped.

I'm now confident that, as/because they say, must be a adaptation problem between the new Win.7 NTFS system and some programmes which will be gradually fixed by those programmes updates.

Cheers, ickymay.

Hi again.

Just to report that I have had a new check disk upon boot. This time with no error detected by the event viewer/windows logs/security. I installed the hotfix Avira sent me which seems to work out because it's no longer causing security error messages. I uninstalled CPU_Z. And finally I have not run MBAM again.

Now I don't know how to track evidences or hints of its origin.

Any idea?

Thanks in advance.