Avast's aswJsFlt.dll keeps crashing Firefox

Hello forum,

since about 1 or 2 weeks, my Firefox keeps crashing very often. That Firefox crash is also quite often, but not always, followed by a Windows Bluescreen (always with a different error code). Now when I look at Firefox’ crash logs, every single time it says that Avast’s aswJsFlt.dll crashed it, as you can see here: http://www.bilder-upload.eu/show.php?file=459271-1518224501.png

What exactly causes this problem? It’s incredibly annoying and makes normal PC usage almost impossible. I really hope you can help me.

I have a similar problem, but the crashing module is snxhk64.dll. Firefox is fully patched to version 58.0.2. Windows 10 1709 x64 fully patched.

It causes Firefox to fail to start, to spawn blank and broken tabs, and to crash outright in the middle of rendering a page.

I do not have the Firefox Avast add-on installed, and I do not have mail shield installed. Just File Shield, Web Shield, and Behavior Shield.

I’m tracking this problem on Bugzilla, but before I report my findings, I wanted to ping the forums and see if anyone else is having this problem.

https://bugzilla.mozilla.org/show_bug.cgi?id=1420963

Uninstalling Avast and reverting to Windows Defender clears up all the problems listed in that thread. I would really rather use Avast, but Firefox crashes or fails to start so often I will have to leave it uninstalled if I can’t fix it.

I have two other machines, a laptop and a desktop, that are running Firefox with Avast and not having any problems. The problem seems to be specific to this one machine.

Any help?

Yeah, a reply would be nice, don’t just leave us alone with this problem :confused:

@R. Hansen
Do those Firefox crashes caused by Avast also occasionally give you bluescreens or is that just me?

It’s the weekend. I’ve reported this on the Developers channel.

No. I don’t get blue screens. I suspect we have different problems. I probably should have started a different thread.

Is it okay if we keep both problems in this thread, or should I start a separate one for my problem?

http://i1376.photobucket.com/albums/ah32/rjhansen075/Crash%20reporter%20faulting%20module_zpsmy4btc2v.jpg

Hello can you provide us a dump of firefox.exe ?

  1. Download procdump tools from : https://docs.microsoft.com/en-us/sysinternals/downloads/procdump
  2. Register procdump as post mortem debugger : procdump -ma -i c:\dumps
  3. Try to induce the crash
  4. There should be a new dump of firefox in c:\dumps folder (you can set another folder)

System BSOD mini dump should be stored at :
%SystemRoot%\MEMORY.DMP

Please provide us with both dump files to analyze the issue.
Thank you

@ kwiq,
Your email address doesn’t list you as an Avast employee ???

Hello Weiku
I tried to decode the stack from attached image which points to aswjsflt.dll :

ntdl!tWaitForMultipleObjects
KERNELBASE.dllRtlAnsiStringToUnicodeString
kernel32.dllWaitForMultipleObjects
aswJsFlt.dll@0x2bb36 aswJsFlt64!WaitForAnyConnection
aswJsFlt.dll@0x2c21e aswJsFlt64!PipeServerThreadProcedureImpl

this thread is waiting in waitformultipleobjects and cant cause any issue.

To confirm that aswjsflt.dll causes the crash please close all instances of firefo, disable avast self protection for a while and rename aswjsflt.dll to aswjsflt.dll.org
the file should be stored at “c:\Program Files\AVAST Software\Avast\x64\aswJsFlt.dll”.
Start new firefox instance

Thank you.

To keep the customer safe, a reply to my question would be nice. :slight_smile:

I’m breaking my problem out to a second thread. It’s definitely a different issue. Good luck resolving your issue.

@kwiq
Who the hell are you? You’re clearly not from Avast, stop asking for my dumps, or for anything, you creep.

Hello,
believe or not i’m avast’s employee. I will ask forum moderators to add me to avast group.

The reason why you see avasts dll marked as red is because during crash mozzila takes a dump of the browser process and displays all threads with stacks and unknown libraries are marked with red color !
That is why you see aswjsflt and snx - but they didnt cause the crash. The crash occured it thread 0 with stack :

js::XDRAtom<1>(js::XDRState<1> *,JS::MutableHandle<JSAtom *>)
js::XDRScript<1>(js::XDRState<1> *,JS::Handle<js::Scope *>,JS::Handle<js::ScriptSourceObject *>,JS::Handle<JSFunction *>,JS::MutableHandle<JSScript *>)
js::XDRInterpretedFunction<1>(js::XDRState<1> *,JS::Handle<js::Scope *>,JS::Handle<js::ScriptSourceObject *>,JS::MutableHandle<JSFunction *>)
js::XDRScript<1>(js::XDRState<1> *,JS::Handle<js::Scope *>,JS::Handle<js::ScriptSourceObject *>,JS::Handle<JSFunction *>,JS::MutableHandle<JSScript *>)
js::XDRState<1>::codeScript(JS::MutableHandle<JSScript *>)
js::MultiScriptsDecodeTask::parse(JSContext *)
js::HelperThread::handleParseWorkload(js::AutoLockHelperThreadState &)
js::detail::ThreadTrampoline<void (&)(void *),js::HelperThread *>::Start(void *)

To confirm it please send us dumps and try to rename aswjsflt.dll for a while - it might help.
There is avast ftp server where you can upload dump files for analysis. (ftp://ftp.avast.com/incoming ) Zip all your data into aswJsFlt_keeps_crashing_firefox_12_02_2018.zip and upload them.
Thank you

@Weiku: kwiq is OK, you can trust him. :slight_smile:

PS: You can upload your minidump(s) here: ftp://ftp.avast.com/incoming/

Thanks kwiq,
Verified. :slight_smile:

Hello,
are you able to upload the zip file ? If you will have any issue plase let me know.
Thank you

Update:

It may not have been Avast’s .dll after all. I just found out yesterday that one of my 2 RAM modules was defective; it’s possible, I’d even say highly likely, that that caused all those browser crashes and Bluescreens. I removed it yesterday and so far I haven’t had any more crashes. It’s only been a day so far, so I can’t be 100% sure, but I’ll let you know if my browser starts crashing again.

It may be worth looking at a suggestion made by a user:
https://forum.avast.com/index.php?topic=215328.msg1447976#msg1447976

@bob3160
It’s still running normally since I removed the defective RAM, haven’t had another crash yet, it seems almost certain now that the broken RAM caused it. But like I said, should I experience any new issues I’ll let you know right away.