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?

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?

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?
>
>

The date and time was 12/2/2008 3:02 PM, and on a whim, jgb555 pounded
out on the keyboard:

> 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?
>>

That info is usually in the Blue Screen when it happens.

--
Terry R.

***Reply Note***
Anti-spam measures are included in my email address.
Delete NOSPAM from the email address after clicking Reply.

Disable automatic restart on system failure. This should help by
allowing time to write down the STOP code properly. Right click on
the My Computer icon on the Desktop and select Properties, Advanced,
Start-Up and Recovery, System Failure and uncheck box before
Automatically Restart.

Entries also appear in the System log of Event Viewer.

You can access Event Viewer by selecting Start, Control Panel,
Administrative Tools, and Event Viewer. When researching the meaning
of the error, information regarding Event ID, Source and Description
are important.

HOW TO: View and Manage Event Logs in Event Viewer in Windows XP
http://support.microsoft.com/kb/308427/en-us

A tip for posting copies of Error Reports! Run Event Viewer and double
click on the error you want to copy. In the window, which appears is a
button resembling two pages. Click the button and close Event
Viewer.Now start your message (email) and do a paste into the body of
the message. Make sure this is the first paste after exiting from
Event Viewer.


--



Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~

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?

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?

i got a screen shot of the "error signature" that shows up after restart. is
that helpful?

"Gerry" wrote:

> Disable automatic restart on system failure. This should help by
> allowing time to write down the STOP code properly. Right click on
> the My Computer icon on the Desktop and select Properties, Advanced,
> Start-Up and Recovery, System Failure and uncheck box before
> Automatically Restart.
>
> Entries also appear in the System log of Event Viewer.
>
> You can access Event Viewer by selecting Start, Control Panel,
> Administrative Tools, and Event Viewer. When researching the meaning
> of the error, information regarding Event ID, Source and Description
> are important.
>
> HOW TO: View and Manage Event Logs in Event Viewer in Windows XP
> http://support.microsoft.com/kb/308427/en-us
>
> A tip for posting copies of Error Reports! Run Event Viewer and double
> click on the error you want to copy. In the window, which appears is a
> button resembling two pages. Click the button and close Event
> Viewer.Now start your message (email) and do a paste into the body of
> the message. Make sure this is the first paste after exiting from
> Event Viewer.
>
>
> --
>
>
>
> Hope this helps.
>
> Gerry
> ~~~~
> FCA
> Stourport, England
> Enquire, plan and execute
> ~~~~~~~~~~~~~~~~~~~
>
> 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?
>
>
>

in the system event log at the time of shut down i see 2 errors. the first
is this:

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7023
Date: 12/2/2008
Time: 4:35:10 PM
User: N/A
Computer: JAREDTRAVELMATE
Description:
The Business Contact Manager SQL Server Startup Service service terminated
with the following error:
The specified service does not exist as an installed service.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.



the second is this:

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 12/2/2008
Time: 4:36:00 PM
User: N/A
Computer: JAREDTRAVELMATE
Description:
Error code 1000000a, parameter1 00000004, parameter2 0000001c, parameter3
00000001, parameter4 80502386.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 31 30 30 30 30 30 30 1000000
0020: 61 20 20 50 61 72 61 6d a Param
0028: 65 74 65 72 73 20 30 30 eters 00
0030: 30 30 30 30 30 34 2c 20 000004,
0038: 30 30 30 30 30 30 31 63 0000001c
0040: 2c 20 30 30 30 30 30 30 , 000000
0048: 30 31 2c 20 38 30 35 30 01, 8050
0050: 32 33 38 36 2386

does this help?

"Gerry" wrote:

> Disable automatic restart on system failure. This should help by
> allowing time to write down the STOP code properly. Right click on
> the My Computer icon on the Desktop and select Properties, Advanced,
> Start-Up and Recovery, System Failure and uncheck box before
> Automatically Restart.
>
> Entries also appear in the System log of Event Viewer.
>
> You can access Event Viewer by selecting Start, Control Panel,
> Administrative Tools, and Event Viewer. When researching the meaning
> of the error, information regarding Event ID, Source and Description
> are important.
>
> HOW TO: View and Manage Event Logs in Event Viewer in Windows XP
> http://support.microsoft.com/kb/308427/en-us
>
> A tip for posting copies of Error Reports! Run Event Viewer and double
> click on the error you want to copy. In the window, which appears is a
> button resembling two pages. Click the button and close Event
> Viewer.Now start your message (email) and do a paste into the body of
> the message. Make sure this is the first paste after exiting from
> Event Viewer.
>
>
> --
>
>
>
> Hope this helps.
>
> Gerry
> ~~~~
> FCA
> Stourport, England
> Enquire, plan and execute
> ~~~~~~~~~~~~~~~~~~~
>
> 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?
>
>
>

<QP>
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.)
</QP>
Source & more: http://aumha.org/a/stop.htm

>>>>> I have been getting blue screen errors about once every 3 weeks.

Could be due to something as simple as overheating. See
http://www.bleepingcomputer.com/tuto...torial118.html

jgb555 wrote:
> in the system event log at the time of shut down i see 2 errors. the
> first
> is this:
>
> Event Type: Error
> Event Source: Service Control Manager
> Event Category: None
> Event ID: 7023
> Date: 12/2/2008
> Time: 4:35:10 PM
> User: N/A
> Computer: JAREDTRAVELMATE
> Description:
> The Business Contact Manager SQL Server Startup Service service terminated
> with the following error:
> The specified service does not exist as an installed service.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
>
>
> the second is this:
>
> Event Type: Error
> Event Source: System Error
> Event Category: (102)
> Event ID: 1003
> Date: 12/2/2008
> Time: 4:36:00 PM
> User: N/A
> Computer: JAREDTRAVELMATE
> Description:
> Error code 1000000a, parameter1 00000004, parameter2 0000001c, parameter3
> 00000001, parameter4 80502386.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: 53 79 73 74 65 6d 20 45 System E
> 0008: 72 72 6f 72 20 20 45 72 rror Er
> 0010: 72 6f 72 20 63 6f 64 65 ror code
> 0018: 20 31 30 30 30 30 30 30 1000000
> 0020: 61 20 20 50 61 72 61 6d a Param
> 0028: 65 74 65 72 73 20 30 30 eters 00
> 0030: 30 30 30 30 30 34 2c 20 000004,
> 0038: 30 30 30 30 30 30 31 63 0000001c
> 0040: 2c 20 30 30 30 30 30 30 , 000000
> 0048: 30 31 2c 20 38 30 35 30 01, 8050
> 0050: 32 33 38 36 2386
>
> does this help?
>
> "Gerry" wrote:
>
>> Disable automatic restart on system failure. This should help by
>> allowing time to write down the STOP code properly. Right click on
>> the My Computer icon on the Desktop and select Properties, Advanced,
>> Start-Up and Recovery, System Failure and uncheck box before
>> Automatically Restart.
>>
>> Entries also appear in the System log of Event Viewer.
>>
>> You can access Event Viewer by selecting Start, Control Panel,
>> Administrative Tools, and Event Viewer. When researching the meaning
>> of the error, information regarding Event ID, Source and Description
>> are important.
>>
>> HOW TO: View and Manage Event Logs in Event Viewer in Windows XP
>> http://support.microsoft.com/kb/308427/en-us
>>
>> A tip for posting copies of Error Reports! Run Event Viewer and double
>> click on the error you want to copy. In the window, which appears is a
>> button resembling two pages. Click the button and close Event
>> Viewer.Now start your message (email) and do a paste into the body of
>> the message. Make sure this is the first paste after exiting from
>> Event Viewer.
>>
>> 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?

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?
>
>