Yes we have a machine with McAfee removed to see if it eliminates issue but
because it only happens about once a week might be some time for it to
reoccur. McAfee 8.8 Update 1 was known to cause this issue but is supposed
to be fixed in this latest version we’re using.
In the old version when McAfee caused the 0x27 BSOD we saw mcafee driver in
the stack trace, this time we don’t though
Thanks
Malcolm
On Wednesday, October 26, 2016, Tim Roberts wrote:
> Malcolm McCaffery wrote:
> > Have seen this across an environment Win7/8.1/Win10. It is not high
> > frequency but does happen. Machines are running 64-bit OS with at
> > least 4-8GB ram typically.
> > …
> > Is there any further good diagnostic options for further narrowing
> > down if a 3rd party component is responsible before logging case with
> > Microsoft?
>
> Are these machines you control? Have you tried killing McAfee
> altogether to see whether the problem goes away?
>
> –
> Tim Roberts, xxxxx@probo.com <javascript:>
> Providenza & Boekelheide, Inc.
>
>
> —
> WINDBG is sponsored by OSR
>
> OSR is hiring!! Info at http://www.osr.com/careers
>
>
> MONTHLY seminars on crash dump analysis, WDF, Windows internals and
> software drivers!
> Details at http:
>
> To unsubscribe, visit the List Server section of OSR Online at <
> http://www.osronline.com/page.cfm?name=ListServer>
></http:></javascript:>