CTMFLT.SYS BSODs 0x000000F7 with 175 Beta

It’s here again.
Did you manage how to solve it? Version 178 is still giving BSODs…

Please, give me support.

Hi Tech,
Thank you for your feedback.This problem has been fixed, but you need to wait for the next release.

Was is a problem in the CTM driver or, on contrary, on avast sandbox driver?
I could ask them for support.
Many thanks.

Thank you very much. It is a bug of CTM driver. We has reproduced and fixed it.
Regards

Perfect… Many thanks.

Brad007, did you really make any specific change to correct this error?
You’ve said it was a problem in your driver and it will be corrected in the next CTM version
But you don’t release a new version and the problems disappears with avast 5.0.668 beta ([Reopen] BSOD of AIS Sandbox)

So, did you correct this error or it was avast team who did it?

No, it does not disappear :cry:
It’s back again: [Reopen] BSOD of AIS Sandbox
aswSnx.sys
0x00000050 (0xCAADC70C, 0x00000000, 0x8BAD052A, 0x00000000).
Seems I need urgently the next CTM version…

No, you DID NOT FIX IT! >:(
This BSOD come again…

0x00000050 (0xC9190634, 0x00000000, 0x8FE28EF9, 0x00000000)
aswSnx.sys
PAGE_FAULT_IN_NONPAGED_AREA

Hi Tech,
I am so sorry. My fault ,I don’t read clearly this post at that time. There maybe a conflict between ctm and avast.

Regards

For sure it has… between CTM and avast sandbox.
Strange that version 2.8 does not seem to have it with the last version of avast 5.0.677. At least, I’ve tested today all day long.

Hi Tech, thank you for your feedbacks. We have some clues for this confliction, and have made improment in new engine. We will continue to work on this issue.

Regards
Haibo

Can’t you get in contact with avast sandbox developer?

Seems avast team was faster on troubleshooting and acknowledging it.