Windows "stops responding" after screensaver

[Guest]

A friend's XP Home computer has a recurrent problem - and has had it for some
time. This PC is an AMD 1800+ with 512 MB DDR, 40 GB HDD, and Matrox G450
"dual-head" 128 MB AGP video.
The problem:
After the computer goes to screensaver (for any period of time), when he
tries to shut it down, the log off /shutdown screen does not appear for a
very long time, upwards of about three to five minutes. Then, finally, the
log off /shutdown window appears and it is possible to shutdown or log off.
Everything functions "as advertised"... But EVERY time the screensaver is
"activated", this problem recurrs.

I've looked at the running processes (only 23 processes listed in the task
manager - none of which seem to be using any processor time, other than
"system idle" which shows 98-99% processor time).
I've scanned for viruses (with Norton AV, then ZoneAlarm AV, then with Panda
Software online scanner), and for spyware (using these same products PLUS
Spybot Search and Destroy) and show nothing "infecting" this PC.
I've uninstalled all 3rd party apps that I consider to be "non-essential"
(he needs his Peachtree Accounting, Adobe 7 reader - or at least some version
of Adobe Reader, plus ZoneAlarm Security Suite AV and firewall) and,
regardless, still see the same problem.
This problem SEEMS to have manifested itself when he began using MSN
Messenger - or so he believes....
I've even tried uninstalling the anti-virus and firewall (ZoneAlarm Security
Suite - a "clean" uninstall, according to their instructions) and still have
the same issue.
I'm about to tear my hair out (what's left of it...)...
Does anyone have a clue as to what else I could try?

 

[Guest]

A friend's XP Home computer has a recurrent problem - and has had it for some
time. This PC is an AMD 1800+ with 512 MB DDR, 40 GB HDD, and Matrox G450
"dual-head" 128 MB AGP video.
The problem:
After the computer goes to screensaver (for any period of time), when he
tries to shut it down, the log off /shutdown screen does not appear for a
very long time, upwards of about three to five minutes. Then, finally, the
log off /shutdown window appears and it is possible to shutdown or log off.
Everything functions "as advertised"... But EVERY time the screensaver is
"activated", this problem recurrs.

I've looked at the running processes (only 23 processes listed in the task
manager - none of which seem to be using any processor time, other than
"system idle" which shows 98-99% processor time).
I've scanned for viruses (with Norton AV, then ZoneAlarm AV, then with Panda
Software online scanner), and for spyware (using these same products PLUS
Spybot Search and Destroy) and show nothing "infecting" this PC.
I've uninstalled all 3rd party apps that I consider to be "non-essential"
(he needs his Peachtree Accounting, Adobe 7 reader - or at least some version
of Adobe Reader, plus ZoneAlarm Security Suite AV and firewall) and,
regardless, still see the same problem.
This problem SEEMS to have manifested itself when he began using MSN
Messenger - or so he believes....
I've even tried uninstalling the anti-virus and firewall (ZoneAlarm Security
Suite - a "clean" uninstall, according to their instructions) and still have
the same issue.
I'm about to tear my hair out (what's left of it...)...
Does anyone have a clue as to what else I could try?

 

[Guest]

A friend's XP Home computer has a recurrent problem - and has had it for some
time. This PC is an AMD 1800+ with 512 MB DDR, 40 GB HDD, and Matrox G450
"dual-head" 128 MB AGP video.
The problem:
After the computer goes to screensaver (for any period of time), when he
tries to shut it down, the log off /shutdown screen does not appear for a
very long time, upwards of about three to five minutes. Then, finally, the
log off /shutdown window appears and it is possible to shutdown or log off.
Everything functions "as advertised"... But EVERY time the screensaver is
"activated", this problem recurrs.

I've looked at the running processes (only 23 processes listed in the task
manager - none of which seem to be using any processor time, other than
"system idle" which shows 98-99% processor time).
I've scanned for viruses (with Norton AV, then ZoneAlarm AV, then with Panda
Software online scanner), and for spyware (using these same products PLUS
Spybot Search and Destroy) and show nothing "infecting" this PC.
I've uninstalled all 3rd party apps that I consider to be "non-essential"
(he needs his Peachtree Accounting, Adobe 7 reader - or at least some version
of Adobe Reader, plus ZoneAlarm Security Suite AV and firewall) and,
regardless, still see the same problem.
This problem SEEMS to have manifested itself when he began using MSN
Messenger - or so he believes....
I've even tried uninstalling the anti-virus and firewall (ZoneAlarm Security
Suite - a "clean" uninstall, according to their instructions) and still have
the same issue.
I'm about to tear my hair out (what's left of it...)...
Does anyone have a clue as to what else I could try?

Quit using a screensaver,,,,,Duh

 

[Guest]

try a different scrensaver?

 

[Guest]

I used to have a Matrox video card with problems similar to yours. Buried
down in the bundled controller software for the video card was a section that
dealt with screensavers and other programs that "took over" the video (such
as a air/train sim). It had to do with Direct X releasing the drivers back
to the operating systems. I'm sorry I can't be more specific, but it was a
while ago.

 

[Guest]

Well, gee - thanx a whole helluva lot "Biggy Bob", your absolutely "stellar"
response was worth all that was paid for it.
Nada ....
The issue at hand here has more to do with "power management" than a simple
screensaver option... which was probably not fully explored or explained in
this posting. No screensaver options could have dealt with this issue....
The owner neglected to inform me that the motherboard had been recently
replaced with a newer model - and even though he had the ability to load the
drivers for this motherboard, there were "listings" for devices that no
longer existed in the device manager. Including some ACPI devices that did
not pertain to the new motherboard version.
After the ACPI components in the device manager were removed and the PC
rebooted, the issue was resolved when Windows XP re-installed the ACPI
components properly and proper power management was restored...
But gee... thanx so much for your technical expertise, Bob.
duh....