986MB of Temp Files

Discussion in 'NOD32 version 2 Forum' started by Webby, Jan 2, 2006.

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

    Webby Registered Member

    Joined:
    Jan 1, 2006
    Posts:
    93
    Hi all,

    I do believe that some part of NOD32 produces a "copy file" of websites or "temp files" of information you have downloaded.... am I correct?

    As I said in my first ever post, I have joined a Distributed Crawling Project to help build a Search Engine and have managed to crawl up to 1,800,000 URL's in 24hours.

    Question is I've had a memory failure warning twice and a virtual shut down of my PC on 2 occasions and I'm not sure why I have 2GB of RAM and bucket loads of hardrive space.

    Using CCLeaner after a session's I removed 986MB & 700MB? of temp files. Has this hugh amount come from NOD32 I wonder?

    Can I switch this temp file thing off?

    Any ideas
    Cheers Webby
     
  2. Webby

    Webby Registered Member

    Joined:
    Jan 1, 2006
    Posts:
    93
    Mind if I "Bump" this one, I'm still wondering where all those temp files came from. Has anybnody any ideas?

    Cheers Webby
     
  3. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,375
    Hi Webby,
    do you remember what were the names of the files in the temp folder?
     
  4. Webby

    Webby Registered Member

    Joined:
    Jan 1, 2006
    Posts:
    93
    Hi Marcos,

    Errr! no there was nothing to actually say it came from *** program. I have disabled NOD32 from any the scanning when I run this Distributed Crawling Project so I don't see the amount of files I used to.

    I'm going to activate the scanning again and see what files are produced... this may take a hour or to so let's see what comes up.... May not be NOD32 at all, I don't no.

    Back later
    Cheers Webby
     
  5. CtlAltDelete

    CtlAltDelete Registered Member

    Joined:
    Dec 18, 2005
    Posts:
    64
    This issue has been posted several times already. There was never a definitive answer the first time....the thread just died.

    I too have several NOD temp files that are in Windows:\temp

    I have just learned to go in there and delete them once per month. And yes, it's NOD doing it. I can remove NOD and they stop producing.......reinstall NOD and they start appearing again. They are not aborted scans, etc....whatever was brought up in the first thread.
     
  6. peewee

    peewee Guest

    link please -thanks.
     
  7. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,375
    These temp files should be created only when NOD32 is scanning an archive, but should be deleted after the scan has completed. Please try to investigate when the problem occurs. Are you using MS Exchange by chance?
     
  8. CtlAltDelete

    CtlAltDelete Registered Member

    Joined:
    Dec 18, 2005
    Posts:
    64
    Nope, not using exchange. Win XP and Outlook. Do a search here, you'll find the old thread. Nothing unusual about the other folks either.....just tons of NOD temp files being left....no answer ever given.
     
  9. peewee

    peewee Registered Member

    Joined:
    Jan 31, 2006
    Posts:
    30
    So no linky like that ay o_O
     
  10. Webby

    Webby Registered Member

    Joined:
    Jan 1, 2006
    Posts:
    93
    Hi all,

    Sorry I'm at work... must make this quick

    My router crashed the other night and my mates coming round to have a look later, I hope to add to this thread tonight or tomorrow.

    Cheers Webby
     
  11. Webby

    Webby Registered Member

    Joined:
    Jan 1, 2006
    Posts:
    93
    Hi all,

    Sorry that took so long.... I am now the owner of a new router :D

    Ok below is the log from Crap Cleaner and as you can see the files are not named after a program which makes me wonder where they come from. I had IMON switched off while I did the Distributed Crawling of some 800,000 urls. Now I know AMON is still scanning and this makes wonder is the files have now come from NOD32? AS you can see 673MB o_O

    If you see further down again all the files look very simular.

    Cheers Webby

    -----------------------------
    ANALYSIS COMPLETE - (163,497 secs)
    ------------------------------------------------------------------------------------------
    673,8MB to be removed. (Approximate size)
    ------------------------------------------------------------------------------------------

    Details of files to be deleted (Note: No files have been deleted yet)
    ------------------------------------------------------------------------------------------
    IE Temporary Internet Files (2 files) 134 bytes
    C:\Documents and Settings\Dario\Local Settings\History\History.IE5\desktop.ini 113 bytes
    C:\Documents and Settings\Dario\Local Settings\History\History.IE5\MSHist012006013020060206\index.dat 32,00KB
    C:\Documents and Settings\Dario\Local Settings\History\History.IE5\MSHist012006020620060207\index.dat 32,00KB
    C:\WINDOWS\TEMP\Perflib_Perfdata_208.dat 16,00KB
    C:\WINDOWS\TEMP\Perflib_Perfdata_3fc.dat 16,00KB
    C:\WINDOWS\TEMP\Perflib_Perfdata_730.dat 16,00KB
    C:\WINDOWS\TEMP\Perflib_Perfdata_7dc.dat 16,00KB
    C:\WINDOWS\TEMP\Perflib_Perfdata_7e0.dat 16,00KB
    C:\WINDOWS\TEMP\Perflib_Perfdata_7e8.dat 16,00KB
    C:\WINDOWS\TEMP\Perflib_Perfdata_7fc.dat 16,00KB
    C:\WINDOWS\TEMP\Perflib_Perfdata_a8.dat 16,00KB
    C:\WINDOWS\TEMP\Perflib_Perfdata_b0.dat 16,00KB
    C:\WINDOWS\TEMP\Perflib_Perfdata_bb4.dat 16,00KB
    C:\WINDOWS\TEMP\Perflib_Perfdata_c4.dat 16,00KB
    C:\WINDOWS\TEMP\Perflib_Perfdata_e4c.dat 16,00KB
    C:\DOCUME~1\Dario\LOCALS~1\Temp\Adobelm_Cleanup.0001 58,56KB
    C:\DOCUME~1\Dario\LOCALS~1\Temp\ASPNETSetup.log 8,22KB
    C:\DOCUME~1\Dario\LOCALS~1\Temp\CFG12.tmp 123 bytes
    C:\DOCUME~1\Dario\LOCALS~1\Temp\CFG41D.tmp 123 bytes
    C:\DOCUME~1\Dario\LOCALS~1\Temp\CFG420.tmp 123 bytes
    C:\DOCUME~1\Dario\LOCALS~1\Temp\ColorProfile.log 18,37KB
    C:\DOCUME~1\Dario\LOCALS~1\Temp\control.xml 717 bytes
    C:\DOCUME~1\Dario\LOCALS~1\Temp\dd_netfx20MSI1A05.txt 2,20MB
    C:\DOCUME~1\Dario\LOCALS~1\Temp\dd_netfx20UI1A05.txt 16,24KB
    C:\DOCUME~1\Dario\LOCALS~1\Temp\dotNetFx.log 2,35KB
    C:\DOCUME~1\Dario\LOCALS~1\Temp\FCCADD4F.TMP 21 bytes
    C:\DOCUME~1\Dario\LOCALS~1\Temp\ff_temp\xpcom.ns\bin\components\jar50.dll 59,10KB
    C:\DOCUME~1\Dario\LOCALS~1\Temp\ff_temp\xpcom.ns\bin\components\xpinstal.dll 0,16MB
    C:\DOCUME~1\Dario\LOCALS~1\Temp\ff_temp\xpcom.ns\bin\js3250.dll 0,39MB
    C:\DOCUME~1\Dario\LOCALS~1\Temp\ff_temp\xpcom.ns\bin\nspr4.dll 0,15MB
    C:\DOCUME~1\Dario\LOCALS~1\Temp\ff_temp\xpcom.ns\bin\plc4.dll 28,10KB
    C:\DOCUME~1\Dario\LOCALS~1\Temp\ff_temp\xpcom.ns\bin\plds4.dll 24,10KB
    C:\DOCUME~1\Dario\LOCALS~1\Temp\ff_temp\xpcom.ns\bin\xpcom_compat.dll 66,60KB
    C:\DOCUME~1\Dario\LOCALS~1\Temp\ff_temp\xpcom.ns\bin\xpcom_core.dll 0,38MB
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IH1.tmp 393 bytes
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IH10.tmp 100,25KB
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IH1004.tmp 538 bytes
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IH1006.tmp 80 bytes
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IH1007.tmp 708 bytes
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IH1009.tmp 13,12KB
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IH100A.tmp 3,78KB
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IH100D.tmp 99,80KB
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IH100E.tmp 100,00KB
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IH1012.tmp 100,53KB
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IH1013.tmp 14,28KB
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IH1014.tmp 89,19KB
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IH1016.tmp 5,33KB
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IH1019.tmp 98,70KB
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IH101B.tmp 98,69KB
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IH101C.tmp 99,00KB
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IH101D.tmp 220 bytes
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IH102.tmp 100,00KB
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IH1026.tmp 28,36KB
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IH1027.tmp 101,54KB
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IH1029.tmp 248 bytes
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IH102D.tmp 16,00KB
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IH102E.tmp 14,32KB
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IH103.tmp 97,85KB
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IH1030.tmp 1 bytes
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IH1036.tmp 20,78KB
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IH1039.tmp 204 bytes

    ----------------------------------------------
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IHD331.tmp 98,75KB
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IHD338.tmp 98,67KB
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IHD33E.tmp 238 bytes
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IHD340.tmp 2 bytes
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IHD345.tmp 0 bytes
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IHD357.tmp 97,82KB
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IHD35F.tmp 100,00KB
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IHD363.tmp 35,63KB
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IHD370.tmp 3,92KB
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IHD372.tmp 13,08KB
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IHD37A.tmp 477 bytes
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IHD37D.tmp 0 bytes
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IHD37F.tmp 0 bytes
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IHD387.tmp 13,30KB
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IHD38E.tmp 16,82KB
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IHD390.tmp 100,26KB
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IHD397.tmp 0 bytes
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IHD39E.tmp 101,60KB
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IHD3B.tmp 291 bytes
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IHD3BA.tmp 31,03KB
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IHD3CC.tmp 0 bytes
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IHD3D4.tmp 238 bytes
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IHD3D8.tmp 101,59KB
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IHD3E2.tmp 0 bytes
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IHD3E6.tmp 101,45KB
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IHD3E7.tmp 0 bytes
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IHD3F5.tmp 725 bytes
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IHD40.tmp 97,94KB
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IHD413.tmp 100,15KB
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IHD425.tmp 477 bytes
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IHD428.tmp 0 bytes
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IHD434.tmp 0 bytes
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IHD436.tmp 2 bytes
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IHD43F.tmp 97,74KB
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IHD442.tmp 0 bytes
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IHD46B.tmp 0 bytes
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IHD476.tmp 98,38KB
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IHD478.tmp 98,54KB
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IHD481.tmp 0 bytes
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IHD48C.tmp 2,41KB
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IHD48D.tmp 0 bytes
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IHD48E.tmp 287 bytes
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IHD4B6.tmp 12,87KB
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IHD4BC.tmp 0 bytes
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IHD4BF.tmp 409 bytes
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IHD4CD.tmp 477 bytes
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IHD4CF.tmp 782 bytes
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IHD4D1.tmp 0 bytes
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IHD4F0.tmp 314 bytes
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IHD4F1.tmp 0 bytes
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IHD4FD.tmp 101,24KB
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IHD4FE.tmp 0 bytes
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IHD50E.tmp 385 bytes
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IHD511.tmp 100,15KB
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IHD515.tmp 101,60KB
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IHD51A.tmp 0 bytes
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IHD51F.tmp 98,44KB
    C:\DOCUME~1\Dario\LOCALS~1\Temp\IHD528.tmp 25 bytes
     
  12. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,375
    Temporary files that come from NOD32 commence with "NOD".
     
  13. Webby

    Webby Registered Member

    Joined:
    Jan 1, 2006
    Posts:
    93
    Hi all,

    Please check this post and come back again: https://www.wilderssecurity.com/showthread.php?t=158289

    After so long with MJ-12 excluded from the IMON scan I fired it up once again.

    Within an hour I had 140MB Temp files and PF Usage in the Task Manager rising by 1MB per second.

    MJ-12 is on my D Drive only and the temp files are showing up on C/ as in the other posts I made above.

    The files are only created when NOD32 has access to MJ-12
     
  14. Blackspear

    Blackspear Global Moderator

    Joined:
    Dec 2, 2002
    Posts:
    15,115
    Location:
    Gold Coast, Queensland, Australia
    That software must create a lot of activity as AMON will be checking every opening and closing file, hence the creation of temps files.

    Cheers :D
     
  15. Webby

    Webby Registered Member

    Joined:
    Jan 1, 2006
    Posts:
    93
    Ok, thanks for that Blackspear.

    Looks like my virus hunting is out as I still have to exclude the MJ-12 from the IMON scan. Its only then that the temp files are not made and PF Usage is normal o_O

    Cheers Webby
     
Thread Status:
Not open for further replies.