Sounds like it could be related to faulty memory modules, an overheating processor or some other hardware problem.
DaveTN has posted a few times regarding these kinds of issues and has suggestions for how to diagnose them. They involve running with just one memory module at a time and observing the system for an amount of time it would normally take for the freeze to occur, then swapping the module with the other one.
Also, downloading a CPU temperature monitoring program such as SpeedFan (http://www.almico.com/speedfan.php) may yield some clues.
Folks, I've read other similar posts and haven't gotten any relief yet. After Touchsmart software gets launched, I can play the music app fine, but if I touch the photo app, the machine freezes and nothing will unfreeze it. alt f4 won't work. c-a-del wont respond. c-a-esc doesn't respond.
I'm running the latest service pack of vista home premium with all patches installed. I've uninstalled all touchsmart apps and reinstalled them one at a time. I've update every driver on the machine to the latest level. I've run advanced system care to check sw issues. I've run hardware checks from the f9 menu. I've stopped Virus scanning. I've stopped Malware scanning. I spent 2 hours online with HP support.
I don't know what else to try.
less frequently, IE8 will freeze mid process and the only way out is to reboot. In fact, this is my 4th attempt at posting this due to freezes. since noon, I've restarted 6 times.
Any suggestions?
Thank you. I'll look for his post.
I ran a couple tools to test the ram but I'll do the removal test.
"GeekTieGuy said:
Sounds like it could be related to faulty memory modules, an overheating processor or some other hardware problem. "
______________________________________________________
Interestingly, I removed a memory stick and the machine worked perfectly for 12 hours. I then swapped the memory with the one I had removed first, and it ran perfectly another 12 hours. I put both in, instant app freezes...
I'm now wondering whether the upper memory slot has a problem or whether there is some 64bit memory addressing conflict that is causing this...
The workaround for now is to run on 2gb instead of 4gb.
RSS

