It started about 10 days ago.
Now the computers will produce a D1 Blue Screen randomly.
Reloaded Network Card drivers on all machines.
Uninstalled and reinstalled Avast (paid) on one machine.
Still getting Blue Screens.
Can you advise?
Is this how you re-installed Avast ???
Clean Install of Avast:
https://goo.gl/4Ptzkf
If you need additional help with the Clean Install, watch this:
https://youtu.be/p-h3myRD51A
Hi ralfm54
please upload your minidump into avast ftp server.
Windows memory dump are usually located at %SystemRoot%\Memory.dmp (https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/automatic-memory-dump)
Zip the dump file and name it as ralfm54_bsod_26_7_2018.zip.
Thank you
you find it here
http://www2.SRC4ALL.COM/Downloads/ralf/ralfm54_bsod_26_7_2018-01.zip
Hi ralfm54,
Your link wants name and password !
Can you use ftp://ftp.avast.com/incoming
Thank you
I hope the file transferred.
If it’s the same file, I hope you supplied Avast with the password, etc. 
File should be on your ftp
NETIO!CalloutStreamDataInit+0x1d tried to dereference memory address 0 which is invalid.
STACK_TEXT:
fffff8800add3858 fffff800054b6529 : 000000000000000a 0000000000000008 0000000000000002 0000000000000000 : nt!KeBugCheckEx
fffff8800add3860 fffff800054b3a7c : 0000000000000000 0000000000000008 0000000000000000 fffff8800add3d50 : nt!KiBugCheckDispatch+0x69
fffff8800add39a0 fffff8800178fafd : fffffa80168d0968 fffffa80168d0960 fffffa801149acd0 fffff880017a3973 : nt!KiPageFault+0x53c
fffff8800add3b30 fffff880017991c4 : fffff8800add3d50 fffff8800add3d50 fffff8800add3f60 fffff8800add3f60 : NETIO!CalloutStreamDataInit+0x1d
fffff8800add3b70 fffff880017a4f88 : 0000000000000000 fffff8800add3f60 fffff8800add3d00 fffff8800add3d88 : NETIO!StreamInvokeCalloutAndNormalizeAction+0x54
fffff8800add3c10 fffff880017a5f81 : fffffa801149ad80 fffff8800add3f60 fffff8800add3d50 fffff8800add43b0 : NETIO!StreamCalloutProcessData+0x48
fffff8800add3c60 fffff880017a7056 : fffff8800add3d50 fffff8800add43b0 fffff8800add3f01 fffffa801149ad80 : NETIO!StreamCalloutProcessingLoop+0xa1
fffff8800add3cf0 fffff88001787b12 : fffff8800add3f60 fffff8800451ac00 0000000000000000 fffffa800d3e0014 : NETIO!StreamProcessCallout+0x1e6
fffff8800add3de0 fffff8800176f1d8 : fffffa801a6c0014 fffffa8015ab9800 fffffa8015ba4e08 fffff8800add43b0 : NETIO! ?? ::FNODOBFM::string'+0x71f2 fffff8800add3f10 fffff88001770832 : fffff8800add0014 fffffa8015ab9800 fffffa800d3efe40 0000000000000000 : NETIO!ArbitrateAndEnforce+0x238 fffff8800add3fe0 fffff880017a9703 : fffff8800add4484 fffffa8015ab9800 ffff000000000001 fffff8800add43b0 : NETIO!KfdClassify+0x902 fffff8800add4350 fffff880017a9d3d : 0000000000000000 0000000000198924 0000000000010000 fffffa800d3efd80 : NETIO!StreamInternalClassify+0xf3 fffff8800add4420 fffff880017aa13e : 0000000000000014 fffffa800d3efcd0 0000000000000000 fffffa8014fc42f0 : NETIO!StreamInject+0x21d fffff8800add44f0 fffff88001609df3 : fffffa800d3efcd0 0000000000000153 fffffa8011a74a20 0000000000000700 : NETIO!FwppStreamInject+0x12e fffff8800add4580 fffff8800a44ad73 : fffffa800d7376d0 fffff8800a454840 fffffa8016952800 fffffa800d737760 : fwpkclnt!FwpsStreamInjectAsync0+0xcf fffff8800add45e0 fffffa800d7376d0 : fffff8800a454840 fffffa8016952800 fffffa800d737760 0000000000000153 : mwac+0x8d73 fffff8800add45e8 fffff8800a454840 : fffffa8016952800 fffffa800d737760 0000000000000153 0000000000000014 : 0xfffffa800d7376d0
fffff8800add45f0 fffffa8016952800 : fffffa800d737760 0000000000000153 0000000000000014 fffffa8000010000 : mwac+0x12840
fffff8800add45f8 fffffa800d737760 : 0000000000000153 0000000000000014 fffffa8000010000 fffffa8011a74a20 : 0xfffffa8016952800 fffff8800add4600 0000000000000153 : 0000000000000014 fffffa8000010000 fffffa8011a74a20 000000000000010c : 0xfffffa800d737760
fffff8800add4608 0000000000000014 : fffffa8000010000 fffffa8011a74a20 000000000000010c fffff8800a44afac : 0x153
fffff8800add4610 fffffa8000010000 : fffffa8011a74a20 000000000000010c fffff8800a44afac 0000000000000000 : 0x14
fffff8800add4618 fffffa8011a74a20 : 000000000000010c fffff8800a44afac 0000000000000000 fffff8800add4688 : 0xfffffa8000010000 fffff8800add4620 000000000000010c : fffff8800a44afac 0000000000000000 fffff8800add4688 0000000000000000 : 0xfffffa8011a74a20
fffff8800add4628 fffff8800a44afac : 0000000000000000 fffff8800add4688 0000000000000000 fffffa800d737760 : 0x10c
fffff8800add4630 0000000000000000 : fffff8800add4688 0000000000000000 fffffa800d737760 0000000000000100 : mwac+0x8fac
I found one foreing driver on stack mwac+0x8fac which points to malware bytes (https://www.file.net/process/mwac.sys.html)
I would try to remove or disable MBAMWebAccessControl.
Please let me know if it helped.
Thank you
one computer had a Blue Screen twice within 24 hours without anything running. An other has not done this after using the Avast Clean utility and reloading (2 days running now).
Malwarebytes and Avast have been running for years side by side.
How come that just 3 weeks ago the blue screens started?
Malwarebytes did not have any updates then there definitions, but Avast did. So, I assume something changes from your end. Can I revert to an older version or should I look for a new Antivirus?
Regarding Avast & Malwarebytes, see: https://forums.malwarebytes.com/topic/200324-exclusions-for-avast-users/
It might be good if you realized exactly how much your Antivirus does.
I personally no longer bother with MBAM since it really doesn’t do very much that isn’t already covered by Avast.
There was a time when you needed both. IMHO, that time has long since gone.
I now occasionally run a scan with AdwCleaner. https://www.malwarebytes.com/adwcleaner/
Just to add, on my systems, neither Malwarebytes or ADW ever found anything.
Thank you Asyn, I will give this a try.
It’s common in the Software Industry to ignore the Competition.
I would add the Scan Exclusions to my Software in the first place, but that’s me. I like Avast, but if I have to tell all our customers to switch to an other VS than I will if Avast does not change the way the treat competition.
You’re welcome.