Re: JIT Debugging needs to be installed

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

On Feb 4, 10:47 am, Denise <Den...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

If you can think of anything else, I'm ready to listen, and I appreciate the
help you've given me so far . . . thanks :)

You may be able to get more info from the Event viewer Denise.
HOW TO: View and Manage Event Logs in Event Viewer in Windows XP
http://support.microsoft.com/default.aspx?scid=kb;EN-US;308427
Or,
Start > Run, copy & paste > eventvwr.msc /s & press Enter.
Scroll down to the last time your computer crashed and it should tell
you what device/driver caused the problem?

Also, minidumps.
Control Panel --> System --> Advanced --> Startup and Recovery -->
Settings ---> Write debugging
information --> Complete memory dump
Minidumps are located in c/windows/minidumps
How to solve Windows system crashes in minutes
http://www.networkworld.com/news/2005/041105-windows-crash.html
http://www.microsoft.com/whdc/devtools/debugging/default.mspx
http://forums.majorgeeks.com/showthread.php?t=35246
This primer will show you how to solve problems quickly. Using a tool
that costs nothing, you can solve approximately 50% of Windows server
and workstation crashes in a few minutes. The tool is WinDbg, the free
Windows debugger.
You've probably never used the debugger, don't have it and don't want
it. After all, it's a developer's tool, not an administrator's, right?
Yes, but what you need to know is remarkably easy to learn, and even a
rudimentary familiarity with the debugger could enhance your skills
and your resume.
Still hesitant? Think about this: After rebooting a crashed machine,
we've brought up the debugger, opened a memory dump file, given the
debugger a single command, and learned not only that the cause was a
driver, but also the driver's name - all in less than a minute.
Granted, the debugger was installed and configured, we knew what
commands to use and what to look for.

Another thought.
If you want to be 100% sure it's a HP problem, uninstall it.

.

Relevant Pages

  • Re: JIT Debugging needs to be installed
    ... Also, in the System Event Viewer, at 5:32:58 PM today, I received a Warning. ... Windows does not recognize the service's error code. ... You've probably never used the debugger, don't have it and don't want ...
    (microsoft.public.windowsxp.perform_maintain)
  • Re: JIT Debugging needs to be installed
    ... View and Manage Event Logs in Event Viewer in Windows XP ... How to solve Windows system crashes in minutes ... You've probably never used the debugger, don't have it and don't want ...
    (microsoft.public.windowsxp.perform_maintain)
  • Re: Unknown device error... please help!
    ... > You can access Event Viewer by selecting Start, Administrative Tools, ... View and Manage Event Logs in Event Viewer in Windows XP ... > A tip for posting copies of Error Reports! ... >>I am getting an unknown device driver error that causes sytem crashes, ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: tcl windows crash
    ... the strange thing is that there is nothing in the event viewer and I do ... not get a windows application error message. ... > tclsh in the debugger environment. ...
    (comp.lang.tcl)
  • Re: BIOS - COULD THERE A PROBLEM WITH MY PCS BIOS?
    ... You can access Event Viewer by selecting Start, Control Panel, ... View and Manage Event Logs in Event Viewer in Windows XP ... with a Master - DMA off, Slave DMA on, Secondary IDE channel with a ... I have hibernation turned off on both drives ...
    (microsoft.public.windowsxp.basics)