jgb555

I actually did this once before and wasnt sure when to stop it. It kept
running and i stopped it after about 15 mins. It didnt show any errors. How
long do i let it run for?

"jgb555" wrote:

> 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

i found this in the latest dump file. Mean anything?

MODULE_NAME: mfehidk

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 485162bc

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx"
referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP:
nt+74950
8054b950 ab stos dword ptr es:[edi]

TRAP_FRAME: 9bb66bbc -- (.trap 0xffffffff9bb66bbc)
ErrCode = 00000002
eax=0000001c ebx=00000000 ecx=00000000 edx=e46615c8 esi=e46615d0 edi=00000000
eip=8054b950 esp=9bb66c30 ebp=9bb66c88 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nt+0x74950:
8054b950 ab stos dword ptr es:[edi]
es:0023:00000000=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

BUGCHECK_STR: 0x8E

LAST_CONTROL_TRANSFER: from 9b578cc2 to 8054b950


also see this:

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

"Gerry" wrote:

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

Rey Santos

In the link I gave, instead of using Sample 1 use Sample 2

Start > All Programs > Accessories > Command Prompt

In command prompt after typing cd c:\program files\debugging tools for windows

Then at the prompt C:\Program Files\Debugging Tools for Window, type windbg
-y srv*c:\symbols*http://msdl.microsoft.com/download/symbols -i
c:\windows\i386 -z c:\windows\minidump\Your Minidump file.dmp

You should be connected to the internet.
--
Rey


"

Gerry

jgb555

What version of McAfee do you have installed? When does the subscription
expire?

What version, if any, of Daemon Tools do you have installed?


--



Hope this helps.

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



jgb555 wrote:
> i found this in the latest dump file. Mean anything?
>
> MODULE_NAME: mfehidk
>
> FAULTING_MODULE: 804d7000 nt
>
> DEBUG_FLR_IMAGE_TIMESTAMP: 485162bc
>
> EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx"
> referenced memory at "0x%08lx". The memory could not be "%s".
>
> FAULTING_IP:
> nt+74950
> 8054b950 ab stos dword ptr es:[edi]
>
> TRAP_FRAME: 9bb66bbc -- (.trap 0xffffffff9bb66bbc)
> ErrCode = 00000002
> eax=0000001c ebx=00000000 ecx=00000000 edx=e46615c8 esi=e46615d0
> edi=00000000 eip=8054b950 esp=9bb66c30 ebp=9bb66c88 iopl=0 nv
> up ei pl zr na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030
> gs=0000 efl=00010246 nt+0x74950:
> 8054b950 ab stos dword ptr es:[edi]
> es:0023:00000000=????????
> Resetting default scope
>
> CUSTOMER_CRASH_COUNT: 1
>
> DEFAULT_BUCKET_ID: WRONG_SYMBOLS
>
> BUGCHECK_STR: 0x8E
>
> LAST_CONTROL_TRANSFER: from 9b578cc2 to 8054b950
>
>
> also see this:
>
> ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
>
> "Gerry" wrote:
>
>> 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?