Discussion in 'ESET NOD32 Antivirus' started by Wi11iam, Jul 6, 2008.
ADD another to the bunch
vista x64 bsod
I'd sure like to hear something public on this thread from ESET personnel regarding a solution for this issue.
I received the same Stop Error (BugCheck 1E - Probably caused by : ntkrnlmp.exe), several times when logging in, on a Vista Ultimate 64-bit system with 4GB of RAM, after installing NOD32 v3.0.667 and updating NVIDIA display drivers to v175.19.
I have since rolled back the NVIDIA display drivers to v175.16 (re-downloaded from the NVIDIA driver archive) and have also since updated NOD32 to v3.0.669 and have not had an issue since (about 15 days since rolling back the NVIDIA drivers).
I looked at your dump file and you do appear to be running the NVIDIA display drivers v175.19 (nvlddmkm.sys - Fri May 16 18:17:25 2008 ).
As there may be a conflict between NOD32 and the Forceware 175.19 drivers I would suggest you uninstall the 175.19 drivers and install the 175.16 drivers or the 169.25 drivers. Both drivers are available from the driver archive on the NVIDIA download page.
Then see if the problem resolves.
I also found the 175.19 drivers hung the system during a reboot or when installing a Windows update.
It would be interesting to see if other users with the same problem have also updated the NVIDIA display drivers.
I believe the 175.19 drivers have been recalled for some cards or reissued.
I'm running with nVidia v. 175.75 from Laptopvideotogo. I wonder if that is causing the vista x64 sp1 Eset AV BSOD problems I'm having with .667 and up? Kind of like the way my games look and run with this version of the driver though.
Going to try Forceware v. 177.66 and see if that solves the problems.
In fact, prior to updating NOD32 to version .667 and getting the BSODs, I also updated my NVIDIA drivers (Lenovo package for my T61p) ... perhaps there is really an interrelationship between the two.
All the machines here with 64Bit OSes do have nvidia cards in them.
Worth taking a look at, thanks for the advice!
Put, Installation 169.25,175.16,163.75-Does not help(With version 667, looked, earlier)version 669 -175.19 -Now costs)), at me, changes are not present, seldom happens BSOD
rebooted,After reboot i received a BSOD,оr when I include a computer, a desktop, there are 1-5 seconds, and BSOD, happens at me seldom
Excuse, I use the automatic translator
Speed of uploading of 2-3 Mb/s, and is more
full memory dump 360MB
Are you asking what drivers to use? If so, try the 175.16 drivers.
So far, I have not had a problem with the 175.16 drivers but if you do have any issue with them then try the 169.25 drivers.
The "Release Highlights" are listed on the download page of each driver.
For anyone using ATI drivers there may also be a conflict between the latest Catalyst drivers (8.6) and NOD32 at startup.
I came across the following thread this morning:
The similarities being that the OP is running a 64-bit OS (Windows 200 with 4GB or more RAM, same BSOD (BugCheck 1E - Probably caused by : ntkrnlmp.exe) occurring at login.
Looking at the minidump file in the first post shows he appears to be running ATI Catalyst driver 8.6 (atikmdag.sys Mon May 12 12:10:44 200.
If you follow the thread it appears that using Catalyst 8.5 drivers with the latest versions of NOD32 has no issue while the Catalyst 8.6 drivers may produce a similar BSOD at login.
i tried with 3 different drivers, using the most recent now. all gave bluescreens.
i dont think its video drivers fault. although a conflict between eset and video is possible.
i do believe it is the eset kernal mode drivers.
also, i only bsod on startup, as eset is loading. after that system runs fine, until the next boot.
anyone know the ftp where older versions os eset can be downloaded from? .662 was last stable i think (not sure though)
right now i'm running without antivirus.
I bet some people that have this issue think the BSOD is related to hardware.
This will cause unnecessary upgrades to components that they might think is causing the issue
As I mentioned I would above, I installed Forceware 177.66 and EAV .669 and haven't seen any BSODs yet. About 8 hours or so now and a couple of reboots so starting to get hopeful this will continue on in this vein.
Only problem is the gaming performance of the v. 177.66 driver is noticeably not as good as the v. 175.75 I was using before. Guess I'll have to try some more Forceware versions to find something that doesn't BSOD with EAV but gives me the gaming performance I want.
Interesting... Am just in the process of building a new machine for the wife.
Vista-64; NOD32 and ATI 4870 with their "hotfix" version of the 8.6 Catalyst driver.
Machine was stable; all patches and applications installed.
Loaded NOD32 with userid / password. NOD was performing it's upgrade when suddenly, screen went black, fan jumped to full speed and the machine was dead.
Hit RESET; at startup Vista seemed to do some sort of registry scan. NOD32 came up without userid / password filled in. Supplied those and had no problems.
One thing that has occurred to me with respect to display drivers is that it probably is important to completely uninstall them before installing a new version. Just maybe incomplete uninstalls are contributing to the BSOD problem some of us are/were having.
So . . . next I'm going to uninstall my current display driver from within safe mode and run a free program called "Driver Sweeper" that is designed to remove leftover remnants of display drivers and also clean the registry with CC Cleaner, and then reboot and try installing Lenovo's recently released nVidia driver for my machine, which is actually is Forceware v. 175.97, and see how it does with my games and with EAV v. 669.
I "found" a little driver program that removes drivers, it really is good.
And only $9.99.
It does not randomly go through your sustem looking for any drivers.
You choose the makers name of the drivers and type,
nvidia control panel.
You must follow the simple instructions, it is very easy to use and every trace of the particular set of drivers you want to remove will be removed.
VERY highly recommended.
I have no connection at all with the program, except as a customer.
That's exactly what "Driver Sweeper" does, except it's free. You select "nvidia display" and that's all it cleans up. No need to pay $9.99 to anyone.
driver sweeper: http://downloads.guru3d.com/download.php?det=1655
tried that too.
also happening on my dell precision laptop which uses a quadro card, different driver set altogether.
i dont think its the video driver.
i think the best fix was mentioned by a previous poster, install .650 from http://www.techpowerup.com/downloads/Utilities/Antivirus/
and wait for eset to fix it with a new version.
You're right about that. I wasted 2 days running memtest and prime95 trying to find some fault with the hardware. Not to mention the time spent rolling my system back to a previous image, uninstalling other software, disabling one driver after another... the list goes on.
The thing that gets me is I have an open case number for this problem and I can't get anyone from ESET to take a look at the memory dumps that I have saved. They keep asking for my event logs and I keep telling them that I don't have them any more to which they respond by asking for my event logs... around and round we go.
I hope that they get this sorted soon.
I have openned an incident with ATI; of course, they want me to supply a core dump. If onbly I could cause the BSOD to occur agaib (although last time it wasn;t so much a BSOD; rather a BLACK screen and a hung PC).
One comment from ATI was:
Of course, they are kind of missing the point here... It's NOT endless; its only sporadic with the first one coming AFTER installing NOD32.
If only they would update their internal documentaion on what to ask customers to do..
GlobalFlag of 400 HEX means Enable Pool Tagging which is ALWAYS in place on Vista.
No BOOT.INI; one needs to use either BCDEDIT OR MsConfig to reduce usable memory.
And of course, Vista HAS no Complete Memory Dump option.
It does but you have to reg hack it to get the drop down option, see my previous post on the first page of this thread
2 Options reg hack or remove 2GB to get the drop down option.
Just reporting that I haven't had any more BSODs since uninstalling my previsous nVidia driver and "clean" installing Forceware 175.80 and EAV 3.0.669 and it's been a couple of days and several reboots now.
I was going to also try the official Lenovo driver (Forceware 175.97), however, this LTV2G driver has started working pretty well for me so I think I'm going to stick with it for a while.
I do think that BSODs are being caused, IN MANY CASES, by some interaction of ESET and the display driver, or possibly by a corrupt installation of the display driver. For those who are continuing to have problems, I suggest trying some "clean" installs of different versions of the display driver from Laptopvideo2go with EAV .669.
It worked (so far) for me.
There appears to be a conflict with nvidia’s latest display drivers,175.19 as my problems started after upgrading. Once installed the problems persist with all nvidia display drivers no matter how thoroughly you uninstall the new drivers. I think It has led many to believe their hardware is failing on the nvidia forums. I had to go back to 2.7
Here’s a memory.dmp http://home.comcast.net/~krakken2/MEMORY.zip
All I can say is uninstalling and cleaning from within Safe mode and then reinstalling a different nV driver seems to have worked for me so far.
I just hope I don't have to eat my words later on.
From the dump file you received a VIDEO_TDR_FAILURE involving the nvlddmkm.sys (Timestamp of nvlddmkm.sys is Fri May 16 18:17:25 2008 ).
Are you saying this problem occurred with various NVIDIA display drivers and the problem resolved after installing NOD32 v2.7?
Pretty much yes, I was chugging along fine with the 169.25’s and nod32 3. something and decided to upgrade to 175.19’s and crash boom bang. Rolled back to the 169.25’s and it still crashed, sometimes it would boot all the way and as long as I didn’t restart it would run ok, so it was something loading at startup.
I’ve tried 4 nvidia drivers all the way back to 163.75’s and it still BS’s at startup. I can do a diagnostic startup without nod32 then after it’s booted manually run nod without a problem, or run 2.7. As it stands now I cannot run 3.0 on this machine without a BSOD at startup. Oh and I did try a clean install of 3.0. Right now I’m running fine with v2.7 and nvidia’s 175.16 drivers and I’m not installing v3.0 again until I see a new version that says “bug fixed” so I don’t think there’s anything else I can do to help. If I'm wrong let me know.
Separate names with a comma.