A problem caused this program to stop interacting with Windows

I try to run Photoshop.exe, but it doesn't respond. I get this error message. How to fix it? I have no idea where is a problem? I had no problems with it earlier.

ERROR MESSAGE:

Description:
A problem caused this program to stop interacting with Windows.

Problem signature:
Problem Event Name: AppHangB1
Application Name: Photoshop.exe
Application Version: 8.0.0.0
Application Timestamp: 3fce5708
Hang Signature: 1875
Hang Type: 0
OS Version: 6.0.6001.2.1.0.256.1
Locale ID: 1063
Additional Hang Signature 1: 3732c99c21cdca196fbfee3cc7094b85 Additional Hang Signature 2: 848c
Additional Hang Signature 3: 5c7261f725b6a443e8327138a3fe0208 Additional Hang Signature 4: 1875
Additional Hang Signature 5: 3732c99c21cdca196fbfee3cc7094b85 Additional Hang Signature 6: 848c
Additional Hang Signature 7: 5c7261f725b6a443e8327138a3fe0208

Read our privacy statement:
< http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x040 9>

These "hang" messages occur with many programs, and I believe even drivers, not just Photoshop.
Like many things Microsoft they are not well documented and there are no easy solutions. Try searching the Microsoft Knowlessthannothing Base and you will see. Googling gets the same lack of answers.
I presume some running process is blocking a program from accessing the memory it needs to operate but the potential causes for that are endless. First see is you have a system restore point prior to when the problem started and go back there to see if it solves the problem. Unfortunately System Restore is a great idea but something of a crap shoot about whether it will work or if there will be the system restore point you need when you need it.
Right click on the photoshop executable and click on run as administrator (in Vista)--east to try but not likely to work.
You can deactivate, uninstall, reboot and reinstall Photoshop but this often does not solve the problem if it was not caused by corruption of your Photoshop program files, which it probably was not.
Uninstall your current video drivers, reboot and reinstall the latest updated drivers: it is astounding how many problems this cures in windows. Turn of all un-necessary background programs, including antivirus programs (unplug the network cable if you are paranoid) and see if that solves the problem.
Scan for malware.
I presume you have contacted Adobe support: they are not as good as they used to be, who is, but they probably don't have an answer for this one anyway.

try turning off your anti-virus.
"semoi" wrote in message

These "hang" messages occur with many programs, and I believe even drivers, not just Photoshop.
Like many things Microsoft they are not well documented and there are no easy solutions. Try searching the Microsoft Knowlessthannothing Base and you will see. Googling gets the same lack of answers.
I presume some running process is blocking a program from accessing the memory it needs to operate but the potential causes for that are endless. First see is you have a system restore point prior to when the problem started and go back there to see if it solves the problem. Unfortunately System Restore is a great idea but something of a crap shoot about whether it will work or if there will be the system restore point you need when you need it.
Right click on the photoshop executable and click on run as administrator (in Vista)--east to try but not likely to work.
You can deactivate, uninstall, reboot and reinstall Photoshop but this often does not solve the problem if it was not caused by corruption of your Photoshop program files, which it probably was not. Uninstall your current video drivers, reboot and reinstall the latest updated drivers: it is astounding how many problems this cures in windows. Turn of all un-necessary background programs, including antivirus programs (unplug the network cable if you are paranoid) and see if that solves the problem.
Scan for malware.
I presume you have contacted Adobe support: they are not as good as they used to be, who is, but they probably don't have an answer for this one anyway.

I suspect a RAM or hardware problem.