Whenever I close the lid of my laptop, the computer crashes:
I can hear the hard disk spin down and I get a blue-screen-of-death, saying,
This problem has occurred on TWO DIFFERENT Dell notebooks, both running Windows 2000 SP4, and with THREE DIFFERENT versions of ZoneAlarm Security Suite.
It seems to be related to "srescan", since disabling this driver eliminates the problem.
(I see that others on this forum had BSOD problems with "srescan" early this year, but nobody seems to be complaining about the current version.)
Details are given below.
I've been working on this problem with ZA Tech Support on and off since August 21st, and they cannot seem to explain or fix it.
Unless anyone here knows a solution, I propose to permanently disable srescan (via "My Computer/Properties/Hardware/Device Manager/View: Show Hidden Devices/Non-Plug and Play Drivers/srescan/Disable", which seems to survive even a clean un-install and re-install of ZASuite!).
Then I will at least have an up-to-date firewall and virus scanner.
Before I do this, however, I have the following two questions:
1) Exactly what does "srescan" do (i.e., what do I lose by disabling it)?2) Will disabling "srescan" cause problems (other than eliminating its intended function)?
Any relevant information or advice would be greatly appreciated.
Details of the Two Laptops, Debugging Attempts, and "srescan" Versions:
A) The system that has received the most diagnosis is a Dell Latitude C600 Notebook, Intel Pentium III processor (x86 Family 6 Model 8 Stepping 10), built circa July 2001 (DS/N TW-09C748-12800-16J-3942), with 261,600 KBytes of RAM installed, running Microsoft Windows 2000 5.00.2195, Service Pack 4 (with all of the latest Critical Updates from Microsoft).
The BIOS version is A09.
B) The other system that exhibits the identical problem is a Dell Latitude D505 Notebook, Intel Celeron M processor 1200MHz, built circa April 2004 (DS/N CN-0H2049-48643-41T-1738), with 260,312 KBytes of RAM installed, running Microsoft Windows 2000 5.00.2195, Service Pack 4 (also with all of the latest Critical Updates from Microsoft).
The BIOS on this system is A03.
(This system also differs in that its hard disk crashed roughly a year ago, and I had to re-install Windows 2000, etc., on a new drive.
Therefore, this system is not so cluttered with extraneous software and registry entries as the older C600.)
On both of the above systems the BSOD-on-lid-closure problem began when I upgraded ZASuite from version 6.5.737.000 to version 7.0 (in one case, to version 7.0.337.000, and the other, to version 7.0.408.000 -- the latest available).
The problem is eliminated by a manual un-install of 7.0 and return to the ORIGINAL version 6.5.737.000.
The problem recurs, however, as soon as I do an Anti-spyware Update on version 6.5.737.000, which also installs the newest version (220.127.116.11) of the Anti-spyware engine.
However, the problem does NOT occur (so far, at least) on an IBM laptop dating from 2001 (call it Machine C), running the same OS along and ZoneAlarm Pro version 6.5.722.000, even though this ZAPro has also updated to Anti-spyware engine version 18.104.22.168 on this machine.
On Machine A, I followed the detailed instructions of tech support to manually un-install ZASuite 7.0 and do a clean re-install -- didn't help -- and (using "msconfig.exe", copied from a Windows XP machine) to turn off all non-Microsoft services except "TrueVector Internet Monitor" and all startup items except "Zlclient.exe" -- also didn't help.
Under "Power Options Properties/Advanced", we also turned off "Enable hibernate support" and "Prompt for password when computer goes off standby".
("When I close the lid of my portable computer" has always been set to perform the action, "None", on all three laptops.)
I even tried un-installing and re-installing the latest device driver for "System Devices/APCI Lid", also to no avail.
The only things that DID eliminate the BSOD were to disable "srescan" in the Device Manager, as described above, or to revert to version 6.5.737.000 WITHOUT updating the Anti-spyware signatures.
Tech support finally requested a memory dump and promoted my problem to the "Escallations Dept.", where it now languishes, apparently indefinitely.
For what it's worth, the PRESENT version numbers and digital-signature timestamps of "srescan" on these three machines are as follows:
ZA Progrm Version
(Why the .sys and .dll versions are different on Machine A, I don't know.
As noted above, I did perform a manual (presumably complete) uninstall of the previous installation, as instructed by tech support, before re-installing the current version.)
Operating System:Windows 2000 Pro
Product Name:ZoneAlarm Internet Security Suite