Re: blue screen error - Symbols can not be loaded...
- From: jgb555 <jgb555@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 2 Dec 2008 17:08:01 -0800
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?
- Follow-Ups:
- References:
- blue screen error - Symbols can not be loaded...
- From: jgb555
- Re: blue screen error - Symbols can not be loaded...
- From: PA Bear [MS MVP]
- Re: blue screen error - Symbols can not be loaded...
- From: jgb555
- Re: blue screen error - Symbols can not be loaded...
- From: PA Bear [MS MVP]
- blue screen error - Symbols can not be loaded...
- Prev by Date: XP based PC disconnecting LAN from the internet
- Next by Date: Re: Running sfc /scannow - Advice Please
- Previous by thread: Re: blue screen error - Symbols can not be loaded...
- Next by thread: Re: blue screen error - Symbols can not be loaded...
- Index(es):
Relevant Pages
|
