J
Juan Wei
Paul has written on 7/1/2013 2:46 AM:
Thanks, Paul, but I guess I'll just wait them out."Not responding" can easily occur, if you're stuck in a kernel call.
There would be no indication on the %CPU display, if that happens.
And AV programs are the sort of things, that screw around with *everything*.
Which is why removing them, is a start.
You can set up a kernel debugger, connect the PC via serial cable to
a second PC, and debug the machine that way. I've never done it,
and I doubt I'd be successful getting it to run in any case. It's
that ugly. I have a pretty poor record, getting debuggers to run.
The one in Visual Studio wasn't bad (that's an application level
debugger). At least I managed to single-step that one. At least
some of the free debuggers out there, they don't have good
docs for naive users like myself (GDB comes to mind).
The idea would be, if you got stuck in a kernel call for long enough,
you could go to the second PC, and see if the kernel debugger is
responding or not.