Many thanks all, much appreciate your helpful advice.
Alias & others:
My delay in upgrading to SP3 is mainly because I had a bad experience when
doing so on my previous PC. Could well have been down to me, but
nevertheless I'm at present reluctant to take the risk again. If I could
find some foolproof way of doing a 100% restore in the event of serious
problems again, then that would be a different matter. But that's another
whole subject ;-)
Don:
My TASKMGR.EXE is identical to yours.
I've never looked at the topic of 'Windows compatibility' before. Not sure
how it's relevant, but then my knowhow on this is negligible. Is
Acgenral.dll only executed when an old and potentially incompatible
program is being run? If so, does that mean I must first identify what app
*causes* the crash? Which so far I haven't done. Or even established that
it is an 'application', rather than say hardware (e.g RAM, drivers etc) or
some obscure low level element of XP Pro, a service, process, whatever -
I'm out of my technical depth here. In any case, the error is *about*
Acgenral, not about any 'app' that Acgenral might be working on!
Paul:
Really generous of you to respond in such detail, thanks a bunch!
I can't be sure but I think I was indeed opening (or at least
re-activating) an application directly before the lock-up.
I studied that 8 year old MS KB article, but not sure I get anything from
it. My Acgenral.dll is 'created Feb 28th 2006', size 1,852,416 bytes. The
version listed in that article is obviously different, being 4 years
older.
I haven't tested RAM and so must do that soon if nothing more obvious
emerges. Likewise, cable connections, although that seems very unlikely;
occasional accidental knocks etc on the (floor-standing) PC case have
never generated this problem.
I did a CHKDSK C: /f recently. No bad sectors reported. (BTW, I had to go
to Event Viewer to find the log; isn't there a switch setting to
supplement or replace \f that reports everything conveniently as well as
fixing any repairable problems?)
I haven't done one on my second (identical) HD, I:, which I use mainly for
backup. Will do shortly.
I use Avira AntiVir, resident to guard and nightly to scan my OS HD, C:. I
have MW and occasionally run that too. I don't *think* this is a malware
issue.
I'm not into Linux!
Tecknomage:
This OEM (Mesh) PC came with a recovery CD, not a 'WinXP Pro SP2 Setup
CD', so if/when I *do* get to update to SP3, I'll adopt your neat
suggested method, thank you.
Great stuff about PE. I do have it (and ProcMon), although I'm no expert
on its efficient use, so it's really good news to find expertise about it
here. (BTW, I posted an identical message in the SysInternals forum
yesterday, but so far no replies.)
Focusing on PE, I set its options to those you recommended. (With one
exception - I've kept the familiar 'CPU' column, as that's about the only
one I understand! And it does give me something with which to compare in
XP TM.) I've saved the 'column set'. And added PE to Startup.
BTW, I note the Help says the PE tray icon should be green. Mine is black.
You can see it in this screenshot, which has the main purpose of showing
all here the fairly large number of programs/services I have running, and
to get your OK on the way I've setup PE's main display.
http://dl.dropbox.com/u/4019461/PE-1.jpg
But I'm not sure how to proceed in using PE for the issue under
discussion. For a start, I just ran PE while composing this reply. Not
after any obvious problems like those I described. although quite a few
applications running and XP TM > Performance > PF Usage showing 1.25 GB.
(Note that it's been a day or two since I rebooted.) I used Find with
'acgenral' as target. These were the results displayed. Apart from
reminding me how inter-related and complex all this is (and how many
instances of svchost.exe are currently being run), I'm afraid it means
nothing to me!
Process Type Handle or DLL
rundll32.exe 444 DLL C:\WINDOWS\AppPatch\AcGenral.DLL
services.exe 800 DLL C:\WINDOWS\AppPatch\AcGenral.DLL
Isass.exe 812 DLL C:\WINDOWS\AppPatch\AcGenral.DLL
svchost.exe 1100 DLL C:\WINDOWS\AppPatch\AcGenral.DLL
svchost.exe 1148 DLL C:\WINDOWS\AppPatch\AcGenral.DLL
svchost.exe 1268 DLL C:\WINDOWS\AppPatch\AcGenral.DLL
svchost.exe 1352 DLL C:\WINDOWS\AppPatch\AcGenral.DLL
svchost.exe 1428 DLL C:\WINDOWS\AppPatch\AcGenral.DLL
spoolsv.exe 1528 DLL C:\WINDOWS\AppPatch\AcGenral.DLL
svchost.exe 1732 DLL C:\WINDOWS\AppPatch\AcGenral.DLL
explorer.exe 1980 DLL C:\WINDOWS\AppPatch\AcGenral.DLL
netdde.exe 2156 DLL C:\WINDOWS\AppPatch\AcGenral.DLL
svchost.exe 3732 DLL C:\WINDOWS\AppPatch\AcGenral.DLL
svchost.exe 3752 DLL C:\WINDOWS\AppPatch\AcGenral.DLL
alg.exe 3840 DLL C:\WINDOWS\AppPatch\AcGenral.DLL
I note your advice about what to do when the error occurs again, but as
everything else was frozen I don't see how we can expect PE to run?
I don't have Adobe Premier, but it's interesting that I have been getting
crashes while running the latest version of my own video editor, Magix
MovieEdit Pro 17 Plus. However, I'm pretty sure that on the last occasion
the freeze occurred, MEP wasn't running.
BTW, my son just moved to San Diego to take up a job with QualComm. Looks
a great city!
Joe:
As mentioned above I do have Malwarebytes and run it occasionally to
supplement my nightly scans with Avira AntiVir (free).
Jim:
Indeed, that struck me too. What do you make of it?