bugcheck 0x100000d1 et cetera .... a fix??
ive been receiving this error during windows normal functioning and i cannot identify whats wrong, can anyone help me?
thanks in advance
the windos minidump and hijackthis logs:
I just got REALLLY tired of the system rebooting for no apparent reason, so
I decided to clean up the Services issue. T
HEELDERGEEK.COM has some
inneresting info on what you DO need versus what you DON'T need when running XP HOME (or PRO) without a home-network...which pertains perhaps
to Most of us, me included.
Forget dump analysis, installing a new graphics board or memory,
or whatever else you've seen. This seems to have worked for me, at least
to the point where things will run fine for HOURS instead of MINUTES. But, no,
I'm not overclocking nor am I gaming, so my approach might fit your
circumstances. BUT..a clean(er) machine is a happy(er) machine, and mine
runs happily with (only) 22 processes; I can probably decrease that by another
five, I betcha.
I can post a 'works with these settings' list here when I get time, but for now
I'll just say that
>>killing the DCOM stuff<< seems to have also killed the bugchecks. (I was actually amazed...) Apparently Windoze has advanced to the point where interactions between it's plethora of parts are not actually understandable.
Getting a (more) stable system by disabling DCOM doesn't mean that DCOM
was the problem but that it, plus something else, had a wierd synergistic BAD
effect on XP, even with SP2 installed. Could've been a memory leak, a conflict
of some kind...or just the bad memory reclamation protocols I've heard are
present in XP. I can only =imagine= what Win7 must be like...yikes.
I hope this helps. Let me know, thanks.
If it works...hey, send cash!! <G>