Skip navigation
McAfee Secure sites help keep you safe from identity theft, credit card fraud, spyware, spam, viruses and online scams
900 Views 6 Replies Latest reply: Sep 5, 2013 12:52 PM by gow75 RSS
gow75 Newcomer 6 posts since
Sep 5, 2013
Currently Being Moderated

Sep 5, 2013 10:46 AM

VSE 8.8 patch 2 issue  maybe?

i have a server that does a Baseline on deman scan on a sunday during non production hours.  the scan lasted 20 mins we then receieved an alert saying that 97% cpu utilization occured on this server.  PAtch2 is appplied to this server.   i also checked event viewer since this is server 2008 and it showed this at the time of scan as well.


Faulting application name: SCAN64.EXE, version:, time stamp: 0x4d2e0635  which occured at the same time as the scan ended.


we are going back and forth with our desktop secuirty team on it and it is pretty annoying.  I think the patch is corrupted.  amy insight as to why the CPU would peg out when we dont see this on any other servers with the same setup.

  • Ex_Brit Volunteer Moderator 59,545 posts since
    May 6, 2004
    Currently Being Moderated
    1. Sep 5, 2013 10:49 AM (in response to gow75)
    Re: VSE 8.8 patch 2 issue maybe?

    Moved to the VSE sub-forum for better support.
    Toronto • Canada
    Volunteer Moderator
    I can't help you privately - please post in the Forums
    Use Advanced Forum Search To Find Answers
    Beta Test McAfee Products For PC & MAC
    How To Fix File Associations in Windows
    XP & Office 2003 End-Of-Life - 08 April, 2014
    Anti-Spyware/Malware & Hijacker Tools
  • wwarren McAfee SME 766 posts since
    Nov 3, 2009
    Currently Being Moderated
    2. Sep 5, 2013 12:28 PM (in response to gow75)
    Re: VSE 8.8 patch 2 issue maybe?

    First point to establish and agree on is that High CPU usage of itself is not an issue.

    The ODS will use as much CPU as the operating system is willing to give it; note, the OS is the one that decides this, not VSE.

    If you have a notification system that alerts when high CPU is occurring from an individual process, it needs to ignore our processes when an ODS runs - else you'll just get false positive alerts.


    We'd consider high CPU being problematic if the ODS is configured to run at low or below normal thread priority, and that when the system is being used by higher priority processes that those higher priority processes are not getting the lion share of CPU cycles.


    You mentioned a crash though. That's not associated with high CPU; it's a different symptom, different issue. That should be investigated further.

  • wwarren McAfee SME 766 posts since
    Nov 3, 2009
    Currently Being Moderated
    4. Sep 5, 2013 12:43 PM (in response to gow75)
    Re: VSE 8.8 patch 2 issue maybe?

    Yes, if someone thinks a system will crash because of "too many CPU cycles" they are missing some understanding of how Windows works .


    The system did not crash, but the On Demand Scan process (scan64.exe) did crash.

    The error in Event viewer shows the details of the crash - an access violation.


    If that is a reproducible behavior, we'd very much like to get additional information from you - if you could open a case with Support.

More Like This

  • Retrieving data ...

Bookmarked By (0)


  • Correct Answers - 5 points
  • Helpful Answers - 3 points