Novice user error log

Discussion in 'NOD32 version 2 Forum' started by JoeyD, Jan 18, 2004.

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

    JoeyD Registered Member

    Joined:
    Jan 17, 2004
    Posts:
    16
    I switched to NOD32 last week after the latest NAV fiasco. So far I'm very pleased. I found one virus NAV missed because of the update problem so now I will never feel the need look back.

    I need some help with errors in my scanner logs. I'm running Windows XP sp1 with all the updates.

    Here is the log:

    Scan performed at: 1/18/2004 8:36:55 AM
    Scanning Log
    NOD32 version 1.600 (20040116) NT
    Operating memory - is OK
    MBR sector of the 2. physical disk - error reading disk sector
    MBR sector of the 3. physical disk - error reading disk sector

    date: 18.1.2004 time: 08:37:21
    Scanned disks, directories and files: C:; D:
    C:\pagefile.sys - error opening (access denied) [4]
    number of files scanned: 18950
    number of viruses found: 0
    time of termination: 08:41:05 total scanning time: 224 sec (00:03:44)

    Notes:
    [4] File cannot be open. It is being exclusively used by another application or operating system.

    My system seems to be running fine, scan disk and defrag show no errors. The only thing I can think of that might be linked is I used Partition Magic early last Fall to copy my system over to a new hard drive. The process wasn't flawless but in the end all I had to do was reinstall programs and everything seemed to be fine other than this error. Should I be concerned? Or as long as all seems well leave it alone?

    Also maybe I should add I use Outpost Pro ver 2 as my firewall.
     
  2. Phil_S

    Phil_S Registered Member

    Joined:
    Nov 13, 2003
    Posts:
    152
    Location:
    UK
    I don't think they are anything to worry about :)

    The MBR error is usually either because you are running a scan as a limited user without sufficient access rights (in which case running the scan from an account with admin priviledges should fix it), or that NOD is trying to access a disk without a MBR which the OS sees as a fixed disk, e.g. a CD drive or memory stick.

    C:\pagefile.sys is a file exclusively used by Windows. NOD is not allowed access to the file, so cannot check it and is telling you as much. But because the OS has exclusive use of the file, neither can a virus or other malware.
     
  3. Mimo Zus

    Mimo Zus Guest

    I ran into the same *problem* with Nod32 in trial mode. I had removed a
    previous NAV2004 trial before installing Nod32.

    I have a Sony VAIO Z1VA laptop with WinXP Pro sp1 + updates, and I'm running the scans with Administrator privilege.

    In my case I only saw "MBR sector of the 2. physical disk - error reading disk sector". Plus I saw many more (~10) "error opening (access denied) [4]" messages for files in the system $uninstall folder

    As a test I uninstalled Nod32, then installed F-Prot followed by Dr.Web. Both were able to read the MBR:

    For example Dr. Web said:
    ---
    [Scan path] C:\
    Master Boot Record HDD1 - Ok
    Active OS/2 or WinNT Boot Sector HDD1 - Ok
    ---

    If other AV programs can read the MBR why can't Nod32?

    I really like this product and I plan to buy it if I can solve this mystery.

    I sent an email to tech support. I'm waiting to see what they say.

    BTW. I installed/reinstalled Nod32 about three times during this testing. The first time I
    tried to uninstall it WinXP crashed with a blue screen during the uninstall. Yikes!

    Here's the Event:

    Event Type:   Error
    Event Source:   System Error
    Event Category:   (102)
    Event ID:   1003
    Date:      2/8/2004
    Time:      2:47:48 AM
    User:      N/A
    Computer:   My Laptop
    Description:
    Error code 100000ce, parameter1 f2393649, parameter2 00000000, parameter3 f2393649, parameter4 00000000.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: 53 79 73 74 65 6d 20 45 System E
    0008: 72 72 6f 72 20 20 45 72 rror Er
    0010: 72 6f 72 20 63 6f 64 65 ror code
    0018: 20 31 30 30 30 30 30 63 100000c
    0020: 65 20 20 50 61 72 61 6d e Param
    0028: 65 74 65 72 73 20 66 32 eters f2
    0030: 33 39 33 36 34 39 2c 20 393649,
    0038: 30 30 30 30 30 30 30 30 00000000
    0040: 2c 20 66 32 33 39 33 36 , f23936
    0048: 34 39 2c 20 30 30 30 30 49, 0000
    0050: 30 30 30 30 0000
     
Thread Status:
Not open for further replies.