Unique.Designs wrote:
A checksum error indicates that the file that left Apple is not the same as when it arrived at your machine. Usually that means the file has been damaged in transit. But it could also indicate a hardware problem with your computer or somewhere on your network.
I had Verizon send me their newest modem to see if it would stop the checksum errors. It did not.
Do you have a firewall/router or an ethernet hub on your local network? I had a bad firewall/router once that was corrupting downloads. I replaced it and the problems went away. However, I also had a lot of problems with web sites where it wouldn't load some of the graphics or even the HTML text would be corrupted.
I have used Disk Utility often lately, as I also have been seeing Firefox, Safari and Photoshop CS either get the spinning wheel of death before a warning message says that the apps are not Responding, which I've usually resolved by Force Quiting the affected app to get to the Finder.
When you get the spinning gumdrop of death, look in the Console application from your Utilities folder and see if there's anything in either the console log or the system log. Particularly, you'd be looking for disk I/O errors. That could indicate bad blocks or a drive controller that's going bad.
Then I run Disk Doctor and defragment with Techtool Pro. But, after a week or so of intensive Photoshop manipulation of hundreds maybe thousands of .jpg files, so they will be the appropriate size for a coin database I am building, the problems come up again.
Since you have TechTool Pro, try testing the RAM and run a surface scan on the hard drive. Or just run all the hardware tests and see if it comes up with anything. You might want to run the RAM tests in a loop if that's possible, since they won't always show a problem the first time through.
I'm wondering if the Force Quiting is causing corruption.
I'm not sure, but I'd guess it's only a problem if the app is writing to the disk at the time you quit it. And even then, the kernel might intervene and make sure the file system is clean.
I'm also wondering if a my Ram, 1) 512 and 2) 256 chips might be causing the problem. Can bad Ram still start up the system but cause an app, that is trying to access the bad sector, to become unResponsive/QUIT?
Absolutely it could be RAM. Especially if it's in a place where the application's data, but not its code is getting corrupted. Bad RAM will cause all kinds of problems: kernel panics, apps that quit unexpectedly, hard drive corruption when corrupted memory structures get written out to disk, etc.
You could moving around, removing, and/or replacing the RAM chips and see if there's any difference.
I'd also look at the CPU upgrade you have. Perhaps it's failing. If it's easy to remove, try that and see what happens.
Finally, how much free hard drive space do you have? You need to keep enough space free for temp files and, especially, the swap files. I try to keep at least 8GB free. I've gotten by with as little as 4GB, but it makes me nervous. Keeping a bit of free space also allows the OS to move files around as it needs to in order to keep fragmentation down.
charlie