I am starting to think this ocmputer doesnt like to sit idle - i am also hoping that its not what it was last time cos i did as i was asked
anyway here`s the log thanks in advance
I had a look at a previous analysis, with your BSODs I'm wondering if there's something going on on your system.
I noticed I made a mistake in this one
It is an improper analysis, because the drivers are from McAfee, not from Malwarebytes. Given that its been months since I made the post I can't remember why and how I made this mistake.
I'm bringing this up because your 0xC2 crash looks really familiair with other(s) I've seen from your system.Please try a clean reinstallation of Malwarebytes, use the link for a clean removal.
NOTE: the license data will be removed too, note the license data somewhere BEFORE removing!
https://support.malwarebytes.org/cus...5311?b_id=6438
Code:*** WARNING: Unable to verify timestamp for mfencbdc.sys *** ERROR: Module load completed but symbols could not be loaded for mfencbdc.sys fffff880`02ffd6c8 fffff880`056316a9Unable to load image \SystemRoot\system32\drivers\mfeavfk.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for mfeavfk.sys *** ERROR: Module load completed but symbols could not be loaded for mfeavfk.sys mfeavfk+0x316a9
This time I'm not planning on making the same mistake again, my suggestion is to uninstall McAfee and install Microsoft Security Essentials
Uninstall tool for McAfee, with a small note can be found here
It is basically the case that Malwarebytes driver calls a driver from McAfee where the McAfee driver for unknown reasons fails to do what it needs to do. The dump doesn't provide a lot of intel on the issue.
Quote