New
#1
BSOD because of NOD
hey i uninstall my NOD 32 4.x because of BSOD dump memory problem but i want to use nod.
is there anyway to fix this ?
hey i uninstall my NOD 32 4.x because of BSOD dump memory problem but i want to use nod.
is there anyway to fix this ?
Did you use the proper bittage, x86 or x64?
Were you running another antivirus product at the same time?
Did you have a previously installed version of ESET NOD32 Antivirus?
These are the minimum requirements to make sure Eset is installed, and runs properly.
See:
How to Download and Install ESET NOD32 Antivirus (4.x) - ESET Knowledgebase
x86
only NOD 32 internet security
So you have the right bittage for your machine.
Did you have NOD 32 internet security running at the same time?
What is the full name of the NOD 32 4.x you are trying to install?
It may have "internet security" already integrated, the two programs are clashing, and you need eset's uninstaller to remove the one you already have installed.
ESS 32 bit 4.2.58.3 this version i am using & i am using only this.
maybe here is my problem
http://www.backupassist.com/blog/sup...32-anti-virus/
Last edited by j0hnny; 09 Jan 2012 at 06:15.
If you have BackupAssist on your machine, It is a good possibility that is your problem.
Your version is also a little old, new version is 5.0 .
I would suggest that you do the follow up actions mentioned in the comments section listed below the article you linked to.
To help you make sure, you could go to Crashes and Debugging - Windows 7 Forums, and submit a report.
Run the https://www.sevenforums.com/crashes-d...tructions.html which includes the Debugger mentioned in the article, and our BSOD Team can take a look at it for you.
Give a brief synopsis of your problem to help the team understand what you feel is happening, and your suspicions about BackupAssist. You could even refer them back to here or to the link.
The team may suggest that you follow the Wilderssecurity thread.
Hi Anak
last night i installed ESET SMART SECURITY 5 & i think bsod problem solved..was using old version of nod32 maybe here is the problem
Anyway thanks for your reply +REP
Your welcome!
When a reputable company starts to hear of problems with their software it usually doesn't take long for them to check it out, and provide an update to their product to fix it.
If you get by in the next few days with no recurring BSOD's I'd say its fixed.
If you get any more, post in https://www.sevenforums.com/crashes-debugging/, after running the instructions.