Error allocating memory on update

Discussion in 'ESET NOD32 Antivirus' started by rcash, Dec 7, 2010.

Thread Status:
Not open for further replies.
  1. rcash

    rcash Registered Member

    Joined:
    Dec 5, 2007
    Posts:
    56
    I have several computers that upgraded to 4.2.67 running XP SP3 and 4gb or ram getting an error allocating memory when trying to update the virus signatures. After a reboot the computer will update but will get the error again on the next signature update.

    Is there something that needs to be changed to prevent this?

    Thanks for the help.
     
  2. MattJN

    MattJN Former ESET Support Rep

    Joined:
    Feb 19, 2010
    Posts:
    149
    Hello,

    What version did you upgrade from? Did you push the installation over the top of the existing install? If you did, it is likely that the install is corrupted. If you uninstalled the previous version first, how did you uninstall it?

    Here is a few things to check:

    Open the GUI for NOD32, press F5 to enter advanced setup, locate Tools > log files, and click on it. Change the logging verbosity (bottom) to Diagnostic records, then try updating again. Once you've done that, make sure the main GUI is set to Advanced display mode, then click Tools > log files and look at the events log.

    Check the Task Manager (performance tab) and verify that sufficient memory is available.

    Also, you could follow the instructions in this KB article to clear the update information:

    http://kb.eset.com/esetkb/index?page=content&id=SOLN2134

    The title of the article isn't quite your issue, but it may be useful to you.

    Thanks,
     
  3. rcash

    rcash Registered Member

    Joined:
    Dec 5, 2007
    Posts:
    56
    It was a push over the top of v4.0.474. I will uninstall (from the uninstall link in the start menu), and try a clean install along with the other suggestions.
     
  4. rcash

    rcash Registered Member

    Joined:
    Dec 5, 2007
    Posts:
    56
    Here is the log from the latest update attempt on one of the computers having the issue:

    12/7/2010 6:13:44 PM Update Updater: retval = 0x3101, failures: 20, regretval = 0x6000, add_regretval = 0 NT AUTHORITY\SYSTEM

    12/7/2010 6:13:44 PM Update Updater: compile error 0 NT AUTHORITY\SYSTEM

    12/7/2010 6:12:19 PM Update Updater: Switch DEVEL modules retval = 0x00005007 [NOT NEED] NT AUTHORITY\SYSTEM

    Task manager indicates plenty of memory free > 2gb
     
  5. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    There's no indication of an error in the log. Have you tried running a RAM test, replacing the RAM modules or reducing them to 2 GB? Are you running Win XP in PAE mode?
     
Thread Status:
Not open for further replies.