Re: blue screen error - Symbols can not be loaded...

jgb555

The Event Viewer Report identifies the error. If you get another
incident you need to check this point:
Stop: 0x0000000A (0x00000004, 0x00000002, 0x00000000, 0x804ea20e)
Anything on the line below the line above? You can often see a reference
to the driver causing the error.

Background information on Stop Error message
http://msdn2.microsoft.com/en-us/library/ms793589.aspx

0x0000000A: IRQL_NOT_LESS_OR_EQUAL
Typically due to a bad driver, or faulty or incompatible hardware or
software. Use the General Troubleshooting of STOP Messages checklist
above. Technically, this error condition means that a kernel-mode
process or driver tried to access a memory location to which it did not
have permission, or at a kernel Interrupt ReQuest Level (IRQL) that was
too high. (A kernel-mode process can access only other processes that
have an IRQL lower than, or equal to, its own.)
Source: http://aumha.org/a/stop.htm

You receive a "Stop 0x0000000A" error message in Windows XP
http://support.microsoft.com/kb/314063/

There are a lot of practical suggestions in the Knowledge Base Article
314063

Are there any yellow question marks in Device Manager? Right click on
the My Computer icon on your Desktop and select Properties,
Hardware,Device Manager. If yes what is the Device Error code?

What exactly do you have by way of a Windows XP CD?

What is your computer make and model?

Has the Windows XP SP3 update been installed?

--



Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
jgb555 wrote:
i think the second event log is what you are looking for right?

"PA Bear [MS MVP]" wrote:

See Gerry's reply.

jgb555 wrote:
not sure. i did a find for "stop" and didnt see anything. is there
another
way to look?

"PA Bear [MS MVP]" wrote:

Got a STOP error w/parameters?

jgb555 wrote:
I have been getting blue screen errors about once every 3 weeks.
I was hoping it would magically stop but it hasnt. Before I ship
my notebook to
the manufacturer who was beyond useless, I did a little research
and was able to download the debugging tools and open the .dmp
files. They all say
the same type of stuff which is:
Symbols can not be loaded because symbol path is not initialized.
The Symbol Path can be set by:
using the _NT_SYMBOL_PATH environment variable.
using the -y <symbol_path> argument when starting the debugger.
using .sympath and .sympath+

There's a whole bunch of stuff about symbols like the above and
here is another:
Your debugger is not using the correct symbols


So is this what is causing my blue screen issues or is this
saying i cant
use the debugger to tell me what is causing the issues?


.

Relevant Pages

  • Re: blue screen error - Symbols can not be loaded...
    ... this error condition means that a kernel-mode ... You receive a "Stop 0x0000000A" error message in Windows XP ... Your debugger is not using the correct symbols ...
    (microsoft.public.windowsxp.general)
  • Re: SBS 2003 Internet Connection Wizard failure
    ... Error message when you try to run a wizard in Windows Small Business Server ... Unhandled exceptions are caught by the Visual Studio JIT debugger instead of ...
    (microsoft.public.windows.server.sbs)
  • Re: Icons in system tray disappearing
    ... See if you can find an EXACT error message & then google that message. ... Windows XP Events and Errors ... information --> Complete memory dump. ... You've probably never used the debugger, don't have it and don't want ...
    (microsoft.public.windowsxp.general)
  • RE: Program will not run due to "debugger"
    ... Earlier today, for some unknown reason, an error message popped up saying ... Windows had to close because "Dr. Watson Postmortem Debugger".... ... > installed means that you are running a debugger. ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: blue screen error - Symbols can not be loaded...
    ... I uninstalled the Outlook Business Contact Manager. ... this error condition means that a kernel-mode ... You receive a "Stop 0x0000000A" error message in Windows XP ... Your debugger is not using the correct symbols ...
    (microsoft.public.windowsxp.general)