Memory error and crash since October 22 update
I have a win xp pro sp2 system, 1 gig mem and ZA suite licensed.
I've been experiencing crashing of my win xp system since the Oct. 22 update. I get the following or something similar
"Instruction 0x7c910a0a reference memory at 0xffffffffd. The memory could not be read". I can't take a screen capture b/c the system is very unstable and I can't launch any other program. Vsmon crashes and when I shut down ZA suite, everything crashes. When I shut down, I get errors with zlclient (?), vsmon and xpcom have errors in shutting down. It may not even shut down forcing me to power off and on to reboot.
I've rebooted into safe mode to delete the .tmp, .rld and .rmp (?) files from /windows/internet logs/ as per forum message and rebooted. Still have the same crashing.
How do I roll back from the Oct. 22 update?
Operating System:Windows XP Pro
Product Name:ZoneAlarm Internet Security Suite
Re: Memory error and crash since October 22 update
Because of the situation, your are better to uninstall the ZA in the safe mode. But do it this way:
Click on Start -> Programs -> Zone Labs
- RIGHT-click on Uninstall ZoneAlarm, then select Properties
- Under Target you will see the following line (the actual drive may
be different on your system):
"C:\Program Files\Zone Labs\ZoneAlarm\zauninst.exe"
Change it to:
"C:\Program Files\Zone Labs\ZoneAlarm\zauninst.exe" /clean
(add a space and then the /clean)
-Return to the Uninstall ZoneAlarm in the Zone Labs of the All Programs
- Click OK to run the uninstaller, and OK any security alerts that
- say "Yes when being prompted for the removal of all files.
- maually remove these folders:
WINDOWS\ Internet Logs
Program Files\Zone Labs
The installers from the previous to the present releases are found at the ZAISS Release History.
The memory issue is not a physical RAM issues, but the inability of the application to read or use the files held in the memory. This could be a windows operating system issue or some security software conflict or even remmants from previous applications causing issues. It could be several other things.
Try the previous release and see if that helps.