Avast related BSOD

Hello! Today I experienced a BSOD right when PC started the Windows. A dump file was created and I used a Nirsoft utility to see into it and I saw that it was caused by aswSP.sys, but I’m no expert, so please tell me where can I send my dump file for analysis. Thank you! :slight_smile:

I PM pk and he will come and help you

Bellzemos: please send me (kurtin@avast.com) a couple of the latest minidumps from \Windows\Minidump folder. Thanks.

I only have two minidumps and I’ve sent them both to your email address. Thank you.

Thanks, this BSOD was already fixed - bad synchronization state in behavior shield.

You mean that you fixed it now, after seeing into my minidump and that it will be fixed with the next Avast update? Or that it was already fixed before today and that it (that BSOD) shouldn’t have happened to me? Thank you.

5.0.677 released: Sep 07
this synchronization bug was fixed on Sep 14

unfortunately you need to wait for the next program update

Yes, I have the 5.0.677 version of Avast so why do I have to wait untill the next update, what will be changed about it then, if it’s already fixed?

Can I do anything to prevent this BSOD to happen again? I tought that aswSP.sys is related to Avast’s self-protection, not behaviour shield.

If it means anything - yesterday I uninstalled my HDD to format an old HDD of mine and then installed the original one back into my PC. But yesterday the PC was working flawlessly, so I don’t know if that BSOD is in any way connected to my HDD changing…

Thank you. :slight_smile:

The bug was fixed in avast source code in some later build, because it was discovered after 677 release date.

A race condition is a situation in which two threads are working with some shared data, and the final result depends on the timing of how the threads are scheduled. This may or may not lead to unpredictable results or BSODs in kernel drivers. God only knows where you get next BSOD (well, you got it after one month).

Behavior shield is internally implemented in aswSP.sys driver.

OK, now I understand. We’ll have to wait for the next official update… And I’m happy it’s not related to my HDD changing. Thank you for your explanation. :slight_smile: