-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 It would appear that on Jul 6, Fritz Whittington did say: > > I'm not at all sure what happened to the text I typed in to respond to this, > but here's another try: > > While it perhaps is corrupted software or configuration, erratic behavior like > this is often associated with flakey memory or an overheated CPU. Check that > your CPU fan is running, and swap out your memory with some other machine. Wouldn't it be better to try memtest86 before physically swapping out the memory? I mean if the OP happens to have another machine with compatible memory and is comfortable with a hands on approach to hardware then swapping out the memory may be a good idea. Especially if memtest finds an error. It is, after all possible (according to what I've read) for a problem in some part of the pc outside of the actual memory to cause it to flunk the memtest. But if the PC passes memtest then it shouldn't be necessary. And the OP might not have any compatible memory to swap in... - -- | --- ___ | <0> <-> Joe (theWordy) Philbrook | ^ J(tWdy)P | ~\___/~ <<jtwdyp@xxxxxxxx>> ############################################################## # You can find my public gpg key at http://pgpkeys.mit.edu/ # ############################################################## -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFA7AMHRZ/61mwhY94RAn6XAKCOl/oL5nYScz/FdZqSvIrEhTpB2QCbBPxu 3U3pLisgak8uozoO9RTDWZc= =yee+ -----END PGP SIGNATURE-----
