76
Living Room / Re: Malwarebytes self-start problem
« on: July 15, 2014, 08:48 AM »
I've used the Event viewer and BlueScreenView, along with "Who Crashed" and several diagnostic utilities. Unfortunately they usually cannot point out the actual driver causing the problem that led to the crash - only the Windows system driver that ultimately shut down the system. E.g., this phrase, or a similar version of it, is used in most of the diagnostics I have tried: "This problem is most likely caused by another driver on your system which cannot be identified at this time."
I have identified 22 separate drivers that have initiated BSODs, plus several others supposedly caused by the kernel, ntoskrnl.exe, though all checks and tests state that another 3rd party driver is actually causing the kernel to shut down. I tried sussing this out by myself long enough and I'm officially throwing in the towel and letting Puget Systems figure it out!
Thank you.
Jim
I have identified 22 separate drivers that have initiated BSODs, plus several others supposedly caused by the kernel, ntoskrnl.exe, though all checks and tests state that another 3rd party driver is actually causing the kernel to shut down. I tried sussing this out by myself long enough and I'm officially throwing in the towel and letting Puget Systems figure it out!
Thank you.
Jim