Video Screencast Help
Search Video Help Close Back
to help
Not able to make it to Vision this year? Get a sampling in the Best of Vision on Demand group.

DWHWIZRD.EXE Error at memory location 0x65efdbb6

Updated: 21 May 2010 | 6 comments
apache 2's picture
apache 2
0 0 Votes
Login to vote
We were running SAV 10.1.5.5000 and upgraded to 10.1.5.5010 to get rid of the dwhwizrd.exe error but it has returned with a different memory location. Anyone have a clue as to the solution?
Thank you in advance..
Discussion Filed Under:
,

Comments

TLV's picture
23
Jul
2007
0 Votes 0
Login to vote
TLV

Same problem on this end too.  Problem went away for a few weeks now it is back.  Thinking of moving to 10.1.6 on new server.  All XP systems with Windows 2003 standard servers.
 
Thoughts??
LANTech's picture
23
Jul
2007
0 Votes 0
Login to vote
LANTech

We are currently using version 10.1.6.6010. Just this morning I
received this error on startup:

Application popup: DWHWIZRD.EXE - Application Error :
The instruction at "0x65efdcb6" referenced memory at "0x65efdcb6".
The memory could not be "read".

I will say that this error doesn't happen often, but it still happens even with the latest version.

TLV's picture
23
Jul
2007
0 Votes 0
Login to vote
TLV

Just got off the phone with Symantec Tech Support.  They suggested uninstalling the client and pushing a new install from the server.  My concern is that this is so intermittent that is will pop up again later !
fjorq's picture
23
Jul
2007
0 Votes 0
Login to vote
fjorq

The DWHWIZRD.exe error is associated with corrupted definitions on the system.  You can follow this procedure to clean the definitions structure on an affected system:
If you are seeing several systems with this error, it could be that the server definitions are corrupted and since they are being sent to the clients, the clients would also have corrupted defs...
 
==============================
Download the latest i32.exe file to the desktop from the security response web site

http://securityresponse.symantec.com/avcenter/down...

1. Stop the Symantec AntiVirus service

2. Stop the Symantec Antivirus Definition Watcher service

3. On the client, open Windows Explorer and browse to the following location:

Windows = C:\Documents and Settings\All Users\Application Data\Symantec\Symantec AntiVirus Corporate Edition\7.5

4. Browse to the I2_LDVP.VDB folder and delete the .VDB subfolders

5. Browse to the 'VirusDefs' folder and delete all numbered folders. Delete all (if any) folders with a .TMP extension.

Windows: C:\Program Files\Common Files\Symantec Shared\VirusDefs

6. Run i32.exe from the desktop. This creates new numbered folders in the VirusDefs folder.

7. Edit the 'definfo.dat' file in the VirusDefs folder so that the value for CurDefs and LastDefs is the same as the new numbered folder.

example:

[DefDates]

CurDefs=20061222.009

LastDefs=20061222.009

8. Edit the 'usage.dat' file so that the value between the hard brackets"[ ]" is the same as the new numbered folder.

example:

[20061222.009]

DEFWATCH_10=1

NAVCORP_70=1

9. Start the Symantec AntiVirus Definition Watcher Service.

10. Start the Symantec AntiVirus Service

Verify that the virus definition date has updated in the local user interface. It may take a few minutes.

TLV's picture
24
Jul
2007
0 Votes 0
Login to vote
TLV

Thank you for the information, I am going to give it a try on one of my users systems.  Will post results.
 
Thanks again for the detailed procedure.
SMP KANsas's picture
24
Jul
2007
0 Votes 0
Login to vote
SMP KANsas

Dear TLV:  You posted a couple of mesages on the Symantec Forum and I didn't see how your results went.
Could you either reply or post another message.  I didn't want to run the fix that FJorg suggested until I heard back from you.  Thanks SMP KANsas
 

Message Edited by SMP KANsas on 07-24-200711:34 AM

Technical Support

Symantec.com

Store

Community Stats

Total Content Items
Members
270,010