Wilders Security Forums  

Go Back   Wilders Security Forums > Official ESET Support Forum > ESET Home Users Products Forum > ESET NOD32 Antivirus
User Name
Password
Register FAQ Members List Calendar Search Today's Posts Mark Forums Read

 
 
Thread Tools Search this Thread
  #1  
Old December 23rd, 2007, 05:39 PM
crash013 crash013 is offline
Infrequent Poster
 
Join Date: Apr 2006
Posts: 12
Default BSOD as a result of NOD32?

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  
Old December 23rd, 2007, 05:53 PM
crash013 crash013 is offline
Infrequent Poster
 
Join Date: Apr 2006
Posts: 12
Default Re: BSOD as a result of NOD32?

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  
Old December 23rd, 2007, 06:10 PM
omega5475 omega5475 is offline
Infrequent Poster
 
Join Date: Nov 2007
Posts: 34
Default Re: BSOD as a result of NOD32?

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.
 

Wilders Security Forums > Official ESET Support Forum > ESET Home Users Products Forum > ESET NOD32 Antivirus « Previous Thread | Next Thread »

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Settings
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT -4. The time now is 03:16 AM.


Powered by vBulletin® Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.
Copyright ©2002 - 2013, Wilders Security Forums