jgb555

Thanks. I read the General Troubleshooting of STOP Messages and that seems
like a daunting task. I am not a very techincal skilled person with this
stuff. Is it possible to see what is causing the access of the memory
location that causes the STOP in the events viewer? Does this mean anything.
These warnings seem to occur a lot in the viewer

Event Type: Warning
Event Source: b57w2k
Event Category: None
Event ID: 4
Date: 12/2/2008
Time: 4:34:59 PM
User: N/A
Computer: JAREDTRAVELMATE
Description:
Broadcom NetLink (TM) Gigabit Ethernet: The network link is down. Check to
make sure the network cable is properly connected.
Data:
0000: 00 00 00 00 02 00 56 00 ......V.
0008: 00 00 00 00 04 00 05 80 .......€
0010: 00 00 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........

I am not connected to any network so does this mean anything?

"PA Bear [MS MVP]" wrote:

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

PA Bear [MS MVP]

> I am not connected to any network so does this mean anything?

No.

jgb555 wrote:
> Thanks. I read the General Troubleshooting of STOP Messages and that
> seems
> like a daunting task. I am not a very techincal skilled person with this
> stuff. Is it possible to see what is causing the access of the memory
> location that causes the STOP in the events viewer? Does this mean
> anything. These warnings seem to occur a lot in the viewer
>
> Event Type: Warning
> Event Source: b57w2k
> Event Category: None
> Event ID: 4
> Date: 12/2/2008
> Time: 4:34:59 PM
> User: N/A
> Computer: JAREDTRAVELMATE
> Description:
> Broadcom NetLink (TM) Gigabit Ethernet: The network link is down. Check
> to
> make sure the network cable is properly connected.
> Data:
> 0000: 00 00 00 00 02 00 56 00 ......V.
> 0008: 00 00 00 00 04 00 05 80 .......€
> 0010: 00 00 00 00 00 00 00 00 ........
> 0018: 00 00 00 00 00 00 00 00 ........
> 0020: 00 00 00 00 00 00 00 00 ........
>
> I am not connected to any network so does this mean anything?
>
> "PA Bear [MS MVP]" wrote:
>
>> <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?

Rey Santos

Event ID: 7023 EVENT_SERVICE_EXIT_FAILED
http://www.microsoft.com/technet/sup...ager&LCID=1033

See this if it ap[plies:
Visio2000: Error Message: "An Error 1060 - The Specified Service Does Not
Exist as an Installed Service..." When You Perform an AutoDiscovery and Layout
http://support.microsoft.com/kb/286014

Event ID: 1003 ER_KRNLCRASH_LOG
http://www.microsoft.com/technet/sup...rror&LCID=1033

Bug Check 0xA: IRQL_NOT_LESS_OR_EQUAL
http://msdn.microsoft.com/en-us/library/ms793589.aspx

You have dump files:
How to read the small memory dump files that Windows creates for debugging
http://support.microsoft.com/kb/315263

I prefer the graphical version of the debugger instead of the command line
version, type the following command instead:
windbg -y srv*c:\symbols*http://msdl.microsoft.com/download/symbols -i
c:\windows\i386 -z c:\windows\minidump\Your Minidump file.dmp

Replace the last entry with your minidump file (MiniMMDDYY-01.dmp)

Windebug will open the Command window results/log

Click the blue "!analyze -v"

Look for the "Probably caused by: ", "MODULE_NAME:" and "IMAGE_NAME:"
headings. This is the program that caused the error. Sometimes when it's a
device driver it means that that device is causing the BSOD and by disabling
it or updating the driver your system will run stable. If you don't know what
device that name relates to then Google it.


--
Rey


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

Gerry

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?

Gerry

jgb555

Does the Stop Error occur during or after the computer boots?


--



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?

jgb555

I uninstalled the Outlook Business Contact Manager. Not sure if it will do
anything but it kept throwing an error and i dont use it. To answer your
questions, no issues in device manager, sp3 is installed, and I have an acer
travelmate 6292.

As far as xp cd's, I had to be sent restore cd's from acer 2 months ago or
so because this laptop kept having issues and they wanted me to do a factory
restore. So I have what they sent. It fixed the issues I was having and all
has been pretty good execpt for these blue screen errors.

Thanks.

"Gerry" wrote:

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

jgb555

Rey,
Can you please clarify what you mean by
type the following command instead:
windbg -y srv*c:\symbols*http://msdl.microsoft.com/download/symbols -i
c:\windows\i386 -z c:\windows\minidump\Your Minidump file.dmp

type it where? start run? if so it didnt work. do i need to specify the
path for windbg?

"Rey Santos" wrote:

> Event ID: 7023 EVENT_SERVICE_EXIT_FAILED
> http://www.microsoft.com/technet/sup...ager&LCID=1033
>
> See this if it ap[plies:
> Visio2000: Error Message: "An Error 1060 - The Specified Service Does Not
> Exist as an Installed Service..." When You Perform an AutoDiscovery and Layout
> http://support.microsoft.com/kb/286014
>
> Event ID: 1003 ER_KRNLCRASH_LOG
> http://www.microsoft.com/technet/sup...rror&LCID=1033
>
> Bug Check 0xA: IRQL_NOT_LESS_OR_EQUAL
> http://msdn.microsoft.com/en-us/library/ms793589.aspx
>
> You have dump files:
> How to read the small memory dump files that Windows creates for debugging
> http://support.microsoft.com/kb/315263
>
> I prefer the graphical version of the debugger instead of the command line
> version, type the following command instead:
> windbg -y srv*c:\symbols*http://msdl.microsoft.com/download/symbols -i
> c:\windows\i386 -z c:\windows\minidump\Your Minidump file.dmp
>
> Replace the last entry with your minidump file (MiniMMDDYY-01.dmp)
>
> Windebug will open the Command window results/log
>
> Click the blue "!analyze -v"
>
> Look for the "Probably caused by: ", "MODULE_NAME:" and "IMAGE_NAME:"
> headings. This is the program that caused the error. Sometimes when it's a
> device driver it means that that device is causing the BSOD and by disabling
> it or updating the driver your system will run stable. If you don't know what
> device that name relates to then Google it.
>
>
> --
> Rey
>
>
> "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?
> >
> >

jgb555

Geez, so much for the waiting and hoping it wouldnt happen again. It just
did. I had disabled tha automatic restart and got this error code on the
blue screen prior to shut down:

STOP: 0x0000008E (0xC0000005, 0x8054B950, 0x9BB66BBC, 0x00000000)

I got this as the error code after restart and this link which says its a
RAM issue?

BCCode : 1000008e BCP1 : C0000005 BCP2 : 8054B950 BCP3 : 9BB66BBC
BCP4 : 00000000 OSVer : 5_1_2600 SP : 3_0 Product : 256_1

http://wer.microsoft.com/responses/R...f-f3c4d31c2b33


"Gerry" wrote:

> jgb555
>
> Does the Stop Error occur during or after the computer boots?
>
>
> --
>
>
>
> 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?
>
>
>

Gerry

jgb555

These types of error can always be down to bad memory. Download and run
the test.

Do you have one or two memory modules? Page 58 of the User's Guide deals
with memory.

If you have bad memory you may have a warranty claim.

BTW this is not the same error as the earlier one but this is not
unusual.

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

0x0000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED
A kernel mode program generated an exception which the error handler
didn't catch. These are nearly always hardware compatibility issues
(which sometimes means a driver issue or a need for a BIOS upgrade).
Source: http://aumha.org/a/stop.htm


--



Hope this helps.

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



jgb555 wrote:
> Geez, so much for the waiting and hoping it wouldnt happen again. It
> just did. I had disabled tha automatic restart and got this error
> code on the blue screen prior to shut down:
>
> STOP: 0x0000008E (0xC0000005, 0x8054B950, 0x9BB66BBC, 0x00000000)
>
> I got this as the error code after restart and this link which says
> its a RAM issue?
>
> BCCode : 1000008e BCP1 : C0000005 BCP2 : 8054B950 BCP3 :
> 9BB66BBC BCP4 : 00000000 OSVer : 5_1_2600 SP : 3_0
> Product : 256_1
>
> http://wer.microsoft.com/responses/R...f-f3c4d31c2b33
>
>
> "Gerry" wrote:
>
>> jgb555
>>
>> Does the Stop Error occur during or after the computer boots?
>>
>>
>> --
>>
>>
>>
>> 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?

PA Bear [MS MVP]

See http://aumha.org/a/stop.htm

jgb555 wrote:
> Geez, so much for the waiting and hoping it wouldnt happen again. It just
> did. I had disabled tha automatic restart and got this error code on the
> blue screen prior to shut down:
>
> STOP: 0x0000008E (0xC0000005, 0x8054B950, 0x9BB66BBC, 0x00000000)
>
> I got this as the error code after restart and this link which says its a
> RAM issue?
>
> BCCode : 1000008e BCP1 : C0000005 BCP2 : 8054B950 BCP3 :
> 9BB66BBC BCP4 : 00000000 OSVer : 5_1_2600 SP : 3_0 Product :
> 256_1
>
> http://wer.microsoft.com/responses/R...f-f3c4d31c2b33
>
>
> "Gerry" wrote:
>
>> jgb555
>>
>> Does the Stop Error occur during or after the computer boots?
>>
>>
>> --
>>
>>
>>
>> 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?