Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

Register Log in
  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Mcaffe VirusScan - Blue Screens... 2

Status
Not open for further replies.
sonnyjim

sonnyjim

IS-IT--Management
Oct 23, 2001
66
0
0
EU
Hi All,

Just a very quick question :

In the past 2 weeks, has anybody running VirusScan or TVD over a network been experiencing Blue Screens in MCSHIELD or MCSCAN?

This has been happening all over the place - our customers , even the PC's here in the office.... But , they all have the latest DATS and I have scoured the Registry for strange entries , have checked the TVD Server also.

Everything appears to be fine - This is happening on versions 4.5.0 and 4.5.1 with the dat file 4194.

This has not happened on any of the machines before - hence my general confusion. The only way to cure it is to remove the application for good. ( obviously not a good cure .

Also , a number of friends in the same business of myself are having the same probs with VirusScan all of a sudden...

odd?

Any Ideas??

"What happens if I press *that* button?"
 
Sort by date Sort by votes
sonnyjim

Noticed this...

Unknown Cause - A fatal exception 0E has occured at 0028:c15681A8 in VXD MCSCAN 32(01) + 00017DB8 , Possibly caused by McAfee DAT files versions 4060 & 4061, update to newer version, win95/win98/98se/(ME)

and this Bug report


and this article

smitee
 
Upvote 0 Downvote
Smitee -

I remember reading that quite a while ago ( around the time that DAT 4160 came out ).

This problem is occuring on DATS 4193 & 4194.

This keeps happening , with the instances increasing in frequency - very , very strange.

I do remember that a virus could do this - Mcafee would detect it ( without showing the user )and then die.
Is there a new malicious code out there?

"What happens if I press *that* button?"
 
Upvote 0 Downvote
A friend loaded the program and ran SDAT4162.exe, intending then to update online. However, he encountered the "illegal operation" error.
 
Upvote 0 Downvote
happened to me from last weds update,
i thot it was just me, and i hate to un and reinstall as
associated programs are fine.

thanks, if any more advice is available please enter in this thread...

:-Q x->
 
Upvote 0 Downvote
update

i waited a week, did new update,rebooted,and now its fine.
thanks to mcafee im guessin.

:-Q x->
 
Upvote 0 Downvote
We dropped ViruScan a year ago because of these quirky problems. Try CA's e-Trust EZ Antivirus (free for 60 days). We registered and have had no problems for a year. It's also much less intrusive than the McAfee product.
 
Upvote 0 Downvote
I work on the PC support for a local authority, we have over 200 users with this problem, it seems to be associated to Windows 95 with MS office, we are having problems with Word, Excel, Powerpoint. The problems started from 4193/4 and are still continuing under 4205. NAI are aware of our situation and are working towards a fix. If you have premium support with NAI I suggest you log a call and help to keep the pressure on NAI to fix this asap
 
Upvote 0 Downvote
I HAVE FINALLY RESOLVED THIS PROBLEM AFTER LOSING DAYS OF SLEEP OVER IT!!!
My entire network has been suffering from all of the above problems and more. We have McAfee for virus protection. I have been on the phone to them at least 5 times in the last 2 weeks. Uninstalls, reinstalls, nothing has worked.
This morning I got a call from Network Associates. They have just put out a Hot Fix for scan engine 4160. It resolves excessive machine slowdowns, BSOD with MCSCAN32 and all of the other problems we have been having. I downloaded the zipfile, installed it and MIRACLE! We are finally up and running as usual.
Thanks heavens. I have lost enough time and energy to this problem. On to the next one...
 
Upvote 0 Downvote
Me too, after about ten weeks of bugging NAI they sent me the hotfix on Friday. I have tested this on several machine with success. The question is, when will the next problem occur??
 
Upvote 0 Downvote
Can you provide a link for this hotfix. I do not see it on their web site.

Thanks in advance.
The Old Man
 
Upvote 0 Downvote
Sorry, I was sent it by backline support. I did not download it!
 
Upvote 0 Downvote
KNOWN ISSUES


1. VirusScan software for Windows 95 and Windows 98
will cause a blue-screen error in these
circumstances:

a. You have installed VirusScan v4.0.1 or v4.0.2
software on your system.

b. You use the SuperDAT package installer to
upgrade the scan engine and related files in
your v4.0.1 or v4.0.2 installation.

c. You install VirusScan v4.0.3 software over
your existing v4.0.1 or v4.0.2 installation.

d. You restart your computer.

This error occurs because of a mismatch between
the VShield VxD files in v4.0.3 and those in
earlier VirusScan versions.

To prevent this error, use the SuperDAT package
installer to upgrade your engine and related
files again, after you install the new v4.0.3
software but BEFORE you restart your
computer.

If you already have the error, however, you can
remedy it by restarting your computer in Safe
Mode, then using the SuperDAT package installer
to upgrade your engine and related files
again. When you restart your computer
normally after that, the file versions will
match and the software will run correctly.

2. The SuperDAT log file is currently limited to a
maximum length of 64K. After that point, the
SuperDAT utility will continue to log events,
but will truncate the file.

3. If you run the SuperDAT package installer to
update and upgrade an existing version of
VirusScan software for Windows 95 and Windows
98 -- v4.0.3, for example -- then you install a
later version of the same software package
-- v4.5.1 for example -- you must run the
SuperDAT package installer again to ensure
that you have the most recent engine files.

4. The SuperDAT package installer does not
currently support the @ symbol used in the
Novell NetWare login script. McAfee does not
create, supply, or support login scripts for
individual environments.

5. The SuperDAT package installer works within your
system's existing security structures. For
Windows NT systems, this usually means that
you must have certain administrative rights
to upgrade the scan engine for your
anti-virus software, because you need those
rights to stop and start system services.
Logging on to the system with the same
identity you used to install your anti-virus
software should give you sufficient rights.

6. The anti-virus scanning engine includes Trojan
horse file detection that allows it to
shut down harmful Trojan horse processes and
remove all traces of the harmful software from
your computer.

To enable support for this function on Windows
NT systems, you must also have two separate
dynamic link library (.DLL) files,
PSAPI.DLL and VDMDBG.DLL, installed in the
\WINNT\System32 folder on your system.

VDMDBG.DLL should already be on your system,
however on some NT 4.0 installations it is
possible that PSAPI.DLL may not exist.
If PSAPI.DLL is not in your \WINNT\System32
folder, you should obtain a copy from Microsoft.

NOTE: The PSAPI.DLL should never be
copied onto a system which already has
PSAPI.DLL installed.
 
Upvote 0 Downvote
KNOWN ISSUES


1. VirusScan software for Windows 95 and Windows 98
will cause a blue-screen error in these
circumstances:

a. You have installed VirusScan v4.0.1 or v4.0.2
software on your system.

b. You use the SuperDAT package installer to
upgrade the scan engine and related files in
your v4.0.1 or v4.0.2 installation.

c. You install VirusScan v4.0.3 software over
your existing v4.0.1 or v4.0.2 installation.

d. You restart your computer.

This error occurs because of a mismatch between
the VShield VxD files in v4.0.3 and those in
earlier VirusScan versions.

To prevent this error, use the SuperDAT package
installer to upgrade your engine and related
files again, after you install the new v4.0.3
software but BEFORE you restart your
computer.

If you already have the error, however, you can
remedy it by restarting your computer in Safe
Mode, then using the SuperDAT package installer
to upgrade your engine and related files
again. When you restart your computer
normally after that, the file versions will
match and the software will run correctly.

2. The SuperDAT log file is currently limited to a
maximum length of 64K. After that point, the
SuperDAT utility will continue to log events,
but will truncate the file.

3. If you run the SuperDAT package installer to
update and upgrade an existing version of
VirusScan software for Windows 95 and Windows
98 -- v4.0.3, for example -- then you install a
later version of the same software package
-- v4.5.1 for example -- you must run the
SuperDAT package installer again to ensure
that you have the most recent engine files.

4. The SuperDAT package installer does not
currently support the @ symbol used in the
Novell NetWare login script. McAfee does not
create, supply, or support login scripts for
individual environments.

5. The SuperDAT package installer works within your
system's existing security structures. For
Windows NT systems, this usually means that
you must have certain administrative rights
to upgrade the scan engine for your
anti-virus software, because you need those
rights to stop and start system services.
Logging on to the system with the same
identity you used to install your anti-virus
software should give you sufficient rights.

6. The anti-virus scanning engine includes Trojan
horse file detection that allows it to
shut down harmful Trojan horse processes and
remove all traces of the harmful software from
your computer.

To enable support for this function on Windows
NT systems, you must also have two separate
dynamic link library (.DLL) files,
PSAPI.DLL and VDMDBG.DLL, installed in the
\WINNT\System32 folder on your system.

VDMDBG.DLL should already be on your system,
however on some NT 4.0 installations it is
possible that PSAPI.DLL may not exist.
If PSAPI.DLL is not in your \WINNT\System32
folder, you should obtain a copy from Microsoft.

NOTE: The PSAPI.DLL should never be
copied onto a system which already has
PSAPI.DLL installed.
 
Upvote 0 Downvote
I work for an MIS department and would really like to find that hotfix thing skippy2 and ndg2 were talking about please tell me how to find. There is around 40 people in my company having this problem.

Thanx for the other advice.
 
Upvote 0 Downvote
Skippy2 Whats the file name of this patch.
What version of Vscan are you running ?
We run version 4.5.0 and 4.5.1, (both 4.1.60 engine version) both versions have experiance slow downs and BSODs

Can you email me a copy of the hotfix ?

Thanks
John
 
Upvote 0 Downvote
Is it just me or has this become more of an issue in the last week.
We are running a mix of win95 and win98 machines on our network with Virus Scan 4.5.1 Scan engine 4.1.60 DAT 4214.
Going to check with NAI about the engine patch.

Thanks for the info
 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

Rosciano
  • Locked
  • Question
Blue screen during the boot.
Replies
1
Views
46
gbaughma
gbaughma
dan2229
  • Locked
  • Question
Blue Screen
Replies
2
Views
18
goombawaho
goombawaho
GCCnewit
  • Locked
  • Question
socket bluetooth scanner
Replies
0
Views
17
GCCnewit
GCCnewit
hikermann
  • Locked
  • Question
Won't boot past blue MS Windows XP screen
Replies
1
Views
16
goombawaho
goombawaho
BJZeak
  • Locked
  • Question
Blue >> Overlay Icon ???
Replies
1
Views
18
BJZeak
BJZeak

Part and Inventory Search

Sponsor

Back
Top