New
#11
This one is inconclusive. It doesn't point to Kaspersky directly, but it could be triggered by the earlier Kaspersky problem.Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1A, {41284, afd4001, 665b, fffff70001080000} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4ad3 ) Followup: MachineOwner ---------
I understand your reluctance to abandon a paid product. Kaspersky isn't alone in triggering BSOD's - I have seen the same issue with AVG, Avast (very common here because its so widely used), Symantec (Norton), Bitdefender and even Avira. There are many systems that have one of these and never experience BSOD's - why that is, I cannot say.
I think because anti-malware products tend to be intrusive by nature, the Windows system files tend to be sensitive to that behaviour. Perhaps if 3rd party anti-malware products can be set-up less 'aggressively' they may not trigger BSOD's.
The only product that we have never seen cause BSOD's here, is MSE, but that makes sense because both it and the OS are products of the same company.