From: "P. J. Alling"
It sounds like it has a high priority task that's not completing.
Usually this doesn't quite crash the GUI but does lock it up.  Back when
I was doing SDK development it happened all the time, but then I could
usually deduce which task had gone haywire, since I usually created the
problem.  In this case it could be anything from a rogue dll that cannot
completely load and doesn't fail gracefully to a hardware problem such
as a problematic sector on a hard drive.   You don't mention if you're
using SATA or PATA drives, ribbon cables can go bad over time and lead
to very hard to diagnose problems if the error is intermittent.  I don't
have enough long term experience with SATA cables to know if they could
cause the same problem.  You can also have similar problems if any
expansion cards aren't completely seated or there are cracked leads to
the cards on the buss.

That describes it pretty well, the GUI doesn't crash but it does lock up.

I've tried just walking away from it to see if maybe it will eventually
unlock, but so far no joy. I've left it over-night & it's still frozen
the next day.

It still has PATA CD-ROM & DVD drives, but the new HDD is SATA. Cables
should all be good, I had a look at them when I was replacing the memory.

But "rogue dll" makes me wonder if I need to look for a new mouse
driver. The one thing that I'm sure is common to every occurrence is I
go to move the mouse pointer & find it's frozen.

Thanks for the ideas.

--
PDML Pentax-Discuss Mail List
PDML@pdml.net
http://pdml.net/mailman/listinfo/pdml_pdml.net
to UNSUBSCRIBE from the PDML, please visit the link directly above and follow 
the directions.

Reply via email to