NOD32 incompatiblity with Hyper Threading?

Discussion in 'NOD32 version 2 Forum' started by Eliot, Mar 26, 2004.

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

    Eliot Registered Member

    Joined:
    Aug 8, 2003
    Posts:
    854
    Location:
    Arkansas, USA
    I am gettting a slew of BSOD's and have removed each application that runs in background except for NOD32. I am still getting the BSOD. Is there something that I am missing in the search here for a problem related to this?
     
  2. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    Hello,

    please try turning IMON off by clicking the Stop button and rebooting the machine to see if the problem goes away. If so, please drop an email to support@nod32.com (with a short description of the problem) and we will provide you with a fix.
     
  3. Eliot

    Eliot Registered Member

    Joined:
    Aug 8, 2003
    Posts:
    854
    Location:
    Arkansas, USA
    Thanks Marcos. Will do. :)
     
  4. Adam

    Adam Guest

    I have had a similar problem - the onset of BSOD after a NOD32 install. Was there any resolution to this issue?
     
  5. Paul Wilders

    Paul Wilders Administrator

    Joined:
    Jul 1, 2001
    Posts:
    12,472
    Location:
    The Netherlands
    In combo with Hyper Threading? If so, follow the advice as provided by Marcos mentioned above. If not: please open a new thread on this forum in regard to your issue.

    regards.

    paul
     
  6. Adam

    Adam Guest

    I'm not able to say if Hyperthreading is causal, or, in fact, if NOD32 is either. I was getting BSOD, intermittently (every other day) since I installed NOD32. I even reinstalled a clean WinXP SP1a with my core apps + NOD32 to see if it made a difference - it did not. My setup:

    P4EE 3.2 OC'd to 3.6 (Prime95 stable for > 24 hours tests 1,2,3; Memtest stable > 24 hours) with HT enabled
    P4C800E-Dlx, BIOS 1016
    1G Corsair TwinX4000Pro 2.5,4,3,7,8 64T/15.6us Turbo, PAT
    WinXP Pro SP1a and all updates
    Latest INF drivers
    TDS-3 latest version, memory resident protection
    Process Guard 2.0 (latest version)
    Kaspersky AV 4.5.x - Monitoring was disabled when NOD32 was installed, used for On-demand only
    First-Defense ISR (latest version)
    Steganos Security Suite (latest version)

    It's worthwhile noting that, with the exception of NOD32, I ran the rest of the system w/o a BSOD EVER for months. They started, coincidentally (o_O) after NOD32 install a few days ago of a newly purchased version, and persisted AFTER a clean reinstall of everything from a clean WinXP SP1a base.

    The BSOD's typically do NOT point out a driver. They happen most often after a fresh reboot just as the welcome screen appears (I'm in a workgroup). One happened while I was switching between users.

    For the moment, I've de-installed NOD32 and have KAV running full steam so I can see if I eliminate BSOD. I will know in a few days.

    I'd much rather use NOD for realtime monitoring and use KAV as on-demand only ... buto_O??
     
  7. adamsfbay

    adamsfbay Registered Member

    Joined:
    Apr 4, 2004
    Posts:
    5
    I just want everyone to know that Eset support got RIGHT back in touch with me and are helping me with this problem.

    I'm back using NOD32 for realtime, and KAV is, again, on-demand backup only.

    So far so good.

    -Adam
     
  8. Unregistered

    Unregistered Guest


    So... what seems to be the cause of the problem?

    Take care... Quinn
     
  9. Harold77

    Harold77 Registered Member

    Joined:
    Jan 15, 2003
    Posts:
    54
    I've been using NOD32 for over a year with my Intel 3.06 ghz system with HT enabled and haven't had that sort of problem at all.

    Maybe you need to exlclude some of your security apps .exe with the NOD32 exclude function.:)
     
  10. Unregistered

    Unregistered Guest

    The new IMON they sent me from Eset resolved the problem completely without any other changes to my system.

    -Adam
     
Thread Status:
Not open for further replies.