B00kWyrm
Posts: 992 +39
Win XP Home SP3 on a Gateway 4525gx Laptop, w/ 2gb RAM.
Every time I close windows, I get this popup that I must click the button "end Now" before I can actually shut down.
Any ideas how to get rid of this error, or how to track down the specific process that is causing it?
What I have done...
Completely uninstall Wireless and reinstall... several times.
Completely uninstall Proset and delete... Problem persists.
Completely uninstall drivers for Wireless... (redetected upon restart, so.,..)
Completely delete the preciously automatically installed drivers... Problem persists.
No Traces in Event Viewer or Minidumps to help.
I have noticed in another thread that Norton can sometimes cause this issue, but I have never had Norton on my system.
The issue began when I did a hard drive replacement, with a rebuild of my system from the Gateway restore disk, followed by a complete update to SP3. It was not present prior to the disk upgrade / replacement. Also, I did the 8-steps complete, with clean report, just to be safe.
Any ideas as to how to trace which exact process is causing this, and thus moving toward solving this annoyance?
Thanks in advance.
Every time I close windows, I get this popup that I must click the button "end Now" before I can actually shut down.
Any ideas how to get rid of this error, or how to track down the specific process that is causing it?
What I have done...
Completely uninstall Wireless and reinstall... several times.
Completely uninstall Proset and delete... Problem persists.
Completely uninstall drivers for Wireless... (redetected upon restart, so.,..)
Completely delete the preciously automatically installed drivers... Problem persists.
No Traces in Event Viewer or Minidumps to help.
I have noticed in another thread that Norton can sometimes cause this issue, but I have never had Norton on my system.
The issue began when I did a hard drive replacement, with a rebuild of my system from the Gateway restore disk, followed by a complete update to SP3. It was not present prior to the disk upgrade / replacement. Also, I did the 8-steps complete, with clean report, just to be safe.
Any ideas as to how to trace which exact process is causing this, and thus moving toward solving this annoyance?
Thanks in advance.