BSOD as a result of NOD32?

Discussion in 'ESET NOD32 Antivirus' started by crash013, Dec 23, 2007.

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

    crash013 Registered Member

    Joined:
    Apr 17, 2006
    Posts:
    12
    I keep getting BSOD's at random times (sometimes I'm playing a game, watching a movie, or even when it is idle at the desktop when it happens). I looked at the event viewer and I see 2 critical errors:

    Event Type: Error
    Event Source: Service Control Manager
    Event Category: None
    Event ID: 7026
    Date: 23/12/2007
    Time: 5:15:35 PM
    User: N/A
    Computer: GREENMILE
    Description:
    The following boot-start or system-start driver(s) failed to load:
    nod32drv
    NPPTNT2
    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Event Type: Error
    Event Source: Service Control Manager
    Event Category: None
    Event ID: 7000
    Date: 23/12/2007
    Time: 5:15:35 PM
    User: N/A
    Computer: GREENMILE
    Description:
    The AMON service failed to start due to the following error:
    The system cannot find the file specified.
    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
     
  2. crash013

    crash013 Registered Member

    Joined:
    Apr 17, 2006
    Posts:
    12
    By the way, I don't even have NOD32 installed. It hasn't been installed in months, and the BSOD's only started recently.
     
  3. omega5475

    omega5475 Registered Member

    Joined:
    Nov 27, 2007
    Posts:
    34
    I had this problem when I uninstalled NOD32 on my old PC few months ago. What I did was disable the NOD32 driver from loading at startup.

    1. Just go to Device Manager, under Views and choose Show Hidden Devices.
    2. Expand Non Plug and Play drivers and double click nod32drv, disable it from running
    3. Go to Driver tab and change startup type to "disabled".
    4. Do the same for AMON.

    Hopefully it should solve your problem as well.
     
Thread Status:
Not open for further replies.