Hi Josh,
Well, debugging is only useful if you understand the code the program is
written in, and are capable of isolating and rewriting the error (debugging
doesn't fix a problem, it points out where in the program code the problem
may lie - the program writer has to fix it). This requires access to the
sourcecode for the program and the ability to recompile it. Otherwise, don't
try debugging. I would hazard a guess that you have or had some programming
software that was capable of debugging code you were working on, and this is
why you get prompted. You should not initiate the debugging sequence, as
that will tie up the system as it attempts to access and and interpret the
instruction set. It is this sequence, and the subsequent inability to access
it that is causing the system to crash.
--
Best of Luck,
Rick Rogers, aka "Nutcase" - Microsoft MVP
Associate Expert - WindowsXP Expert Zone
Windows help -
www.rickrogers.org