The system that cried wolf: I've written a long, detailed, important article about a BSOD occurence during a MBAM scan and the subsequent investigation into the root case, with a careful use of strict problem solving methodologies, including errors, concepts, programs and tools like ataport.sys, Event ID 11, IDE Port, controller error, SMART info, disk diagnostic scan, TrueCrypt, BlueScreenView, Intel Rapid Storage Technology (RST), system stability, performance, additional checks, other tips and tricks, and more. Enjoy. Also, remember, remember, the sixth of September, Windows, MBAM and BSOD! Enjoy, again. https://www.dedoimedo.com/computers/windows-bsod-ataport-mbam.html Cheers, Mrk
The first thing to do when you suspect a software issue is to check the vendor's forums and see if other users report the same issue. If they do, its likely a bug fix will be forthcoming. Apply it and the error should go away. The lesson being even good software won't run perfectly under all conditions and every now and then something will go wrong. That's why software never stays at the same version as there are always bugs needing to be fixed. People can usually live with bugs but when a bug degrades or interferes with computer performance, they're rated critical. And upgrading it are an inevitable part of life.
What I wanted to highlight here is how to separate problems and how to work with symptoms. Once you know where the issue is, it's easier to search for fixes. Mrk
I'm running ALL sorts of operating systems, which is evident from any which review I do. This includes production win7/8, ubuntu 14.04 flavors, and then a billion tests. Mrk
