BSOD Error help...tia

[Guest]

Archived from groups: microsoft.public.windowsxp.general (More info?)

while running adaware on my pc it restarted and i got this error message
from the BSOD

***STOP 0x0000008e (0xc0000005,0x8056e2a2,0xb4c81ba4,0x00000000)
i got this error once and it changed the next time to
***STOP 0X0000008e (0xc0000005,0x8056e2a2,0Xf3242ba4,0x00000000)
and then changed to
***STOP 0X0000008e (0xc0000005,0x8056e2a2,0Xf3300ba4,0x00000000)

ive just added new ram but im sure that that is not the problem because I
ran loads of tests on it and even tried different ram but to no avail, i
also added a new gfx card to replace the onboard one and this still didnt
help
I've googled this error to no avail i was really looking for help on this
one because its not just when i run adaware it does it at other random
times. Please any help would be much apprciated

cheers Stone Monkey

 

[Guest]

Archived from groups: microsoft.public.windowsxp.general (More info?)

http://support.microsoft.com/search/default.aspx?catalog=LCID%3D1033&ast=1%2C2%2C3&spid=1173&mode=a&cat=false&kt=ALL&title=false&mdt=&pwt=False&comm=1&query=+0X0000008e&srch=sup&x=15&y=14&range=21-40

--
Mary Sauer MSFT MVP
http://office.microsoft.com/
http://msauer.mvps.org/
news://msnews.microsoft.com
"Stone Monkey" <tenny2k@NOSPAMERSrtennant.fsnet.co.uk> wrote in message
news:Xns9685E1C7F759Atenny2kNOSPAMERSrten@84.92.1.10...
> while running adaware on my pc it restarted and i got this error message
> from the BSOD
>
> ***STOP 0x0000008e (0xc0000005,0x8056e2a2,0xb4c81ba4,0x00000000)
> i got this error once and it changed the next time to
> ***STOP 0X0000008e (0xc0000005,0x8056e2a2,0Xf3242ba4,0x00000000)
> and then changed to
> ***STOP 0X0000008e (0xc0000005,0x8056e2a2,0Xf3300ba4,0x00000000)
>
> ive just added new ram but im sure that that is not the problem because I
> ran loads of tests on it and even tried different ram but to no avail, i
> also added a new gfx card to replace the onboard one and this still didnt
> help
> I've googled this error to no avail i was really looking for help on this
> one because its not just when i run adaware it does it at other random
> times. Please any help would be much apprciated
>
> cheers Stone Monkey

 

[Guest]

Archived from groups: microsoft.public.windowsxp.general (More info?)

From my research it seems that this could be caused by a driver issue. I
would suggest updating your video driver to the latest WHQL certified version
available at the manufacturer's web site.

Then, I'd recommend that you update your motherboard drivers, and then
update the BIOS on your motherboard.

Then, let us know if that fixes the problem. If not, we can continue
troubleshooting it fromt here.

"Stone Monkey" wrote:

> while running adaware on my pc it restarted and i got this error message
> from the BSOD
>
> ***STOP 0x0000008e (0xc0000005,0x8056e2a2,0xb4c81ba4,0x00000000)
> i got this error once and it changed the next time to
> ***STOP 0X0000008e (0xc0000005,0x8056e2a2,0Xf3242ba4,0x00000000)
> and then changed to
> ***STOP 0X0000008e (0xc0000005,0x8056e2a2,0Xf3300ba4,0x00000000)
>
> ive just added new ram but im sure that that is not the problem because I
> ran loads of tests on it and even tried different ram but to no avail, i
> also added a new gfx card to replace the onboard one and this still didnt
> help
> I've googled this error to no avail i was really looking for help on this
> one because its not just when i run adaware it does it at other random
> times. Please any help would be much apprciated
>
> cheers Stone Monkey
>

 

[Guest]

Archived from groups: microsoft.public.windowsxp.general (More info?)

"Mary Sauer" <gsauer@mycolumbus.rr.com> wrote in
news:esZ8TobfFHA.1048@tk2msftngp13.phx.gbl:

> http://support.microsoft.com/search/default.aspx?catalog=LCID%3D1033&as

thanks but the 0x0000008e error can be cause by so many things that it
really doesnt help narrow things down, thanks anyway

 

[Rock]

Archived from groups: microsoft.public.windowsxp.general (More info?)

Stone Monkey wrote:

> while running adaware on my pc it restarted and i got this error message
> from the BSOD
>
> ***STOP 0x0000008e (0xc0000005,0x8056e2a2,0xb4c81ba4,0x00000000)
> i got this error once and it changed the next time to
> ***STOP 0X0000008e (0xc0000005,0x8056e2a2,0Xf3242ba4,0x00000000)
> and then changed to
> ***STOP 0X0000008e (0xc0000005,0x8056e2a2,0Xf3300ba4,0x00000000)
>
> ive just added new ram but im sure that that is not the problem because I
> ran loads of tests on it and even tried different ram but to no avail, i
> also added a new gfx card to replace the onboard one and this still didnt
> help
> I've googled this error to no avail i was really looking for help on this
> one because its not just when i run adaware it does it at other random
> times. Please any help would be much apprciated
>
> cheers Stone Monkey

http://aumha.org/win5/kbestop.htm
0x0000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED

--
Rock
MS MVP Windows - Shell/User

 

[Guest]

Archived from groups: microsoft.public.windowsxp.general (More info?)

To determine what driver is causing the problem I need you to enable driver
verifier.
Steps:
1) Windows Key + R
2) Type in 'verifier' and hit enter
3) Make sure 'Create Standard Setting' is selected and hit next
4) Click on 'Select all drivers installed on this computer' and hit Finish
5) Reboot

There is a possibility that your computer will crash on reboot. If this
occurs hit F8 when rebooting just before the windows logo screen and select
the safe mode boot option. Follow the same steps above but on step 4 choose
'Select driver names from a list'; hit next; check the box next to any
driver where the provider is not Microsoft; hit Finish; reboot.

This will slow the performance of you computer a little while enabled but
will hopefully catch the driver causing corruption. Next time you crash
the blue screen will hopefully say something like
"DRIVER_VERIFIER_DETECTED_VIOLATION". If this occurs please send the
corresponding minidump (by default it is at c:\windows\Minidump ) my way.
If you have any questions or I didn't explain something well enough don't
hesitate to e-mail me (remove "online") back. Good Luck,


Joshua Smith
OpenGL Test Lab
Microsoft
-----

Get Secure! www.microsoft.com/security

This posting is provided "AS IS" with no warranties, and confers no rights


"usasma" <usasma@discussions.microsoft.com> wrote in message
news:14541F77-2CBB-4422-8122-98FA24E1D02B@microsoft.com...
> From my research it seems that this could be caused by a driver issue. I
> would suggest updating your video driver to the latest WHQL certified
> version
> available at the manufacturer's web site.
>
> Then, I'd recommend that you update your motherboard drivers, and then
> update the BIOS on your motherboard.
>
> Then, let us know if that fixes the problem. If not, we can continue
> troubleshooting it fromt here.
>
> "Stone Monkey" wrote:
>
>> while running adaware on my pc it restarted and i got this error message
>> from the BSOD
>>
>> ***STOP 0x0000008e (0xc0000005,0x8056e2a2,0xb4c81ba4,0x00000000)
>> i got this error once and it changed the next time to
>> ***STOP 0X0000008e (0xc0000005,0x8056e2a2,0Xf3242ba4,0x00000000)
>> and then changed to
>> ***STOP 0X0000008e (0xc0000005,0x8056e2a2,0Xf3300ba4,0x00000000)
>>
>> ive just added new ram but im sure that that is not the problem because I
>> ran loads of tests on it and even tried different ram but to no avail, i
>> also added a new gfx card to replace the onboard one and this still didnt
>> help
>> I've googled this error to no avail i was really looking for help on this
>> one because its not just when i run adaware it does it at other random
>> times. Please any help would be much apprciated
>>
>> cheers Stone Monkey
>>

 

[Guest]

Archived from groups: microsoft.public.windowsxp.general (More info?)

Stone Monkey wrote:
>
> while running adaware on my pc it restarted and i got this error message
> from the BSOD
>
> ***STOP 0x0000008e (0xc0000005,0x8056e2a2,0xb4c81ba4,0x00000000)
> i got this error once and it changed the next time to
> ***STOP 0X0000008e (0xc0000005,0x8056e2a2,0Xf3242ba4,0x00000000)
> and then changed to
> ***STOP 0X0000008e (0xc0000005,0x8056e2a2,0Xf3300ba4,0x00000000)
>
> ive just added new ram but im sure that that is not the problem because I

Your PC doesnt like the new ram you installed. Pretty simple. It's the
last thing you did before you started seeing the niggle.



--
http://www.bootdisk.com/

 

[Guest]

Archived from groups: microsoft.public.windowsxp.general (More info?)

Plato <|@|.|> wrote in news:42c58063$0$90592$bb4e3ad8@newscene.com:

> Stone Monkey wrote:
>>
>> while running adaware on my pc it restarted and i got this error
>> message from the BSOD
>>
>> ***STOP 0x0000008e (0xc0000005,0x8056e2a2,0xb4c81ba4,0x00000000)
>> i got this error once and it changed the next time to
>> ***STOP 0X0000008e (0xc0000005,0x8056e2a2,0Xf3242ba4,0x00000000)
>> and then changed to
>> ***STOP 0X0000008e (0xc0000005,0x8056e2a2,0Xf3300ba4,0x00000000)
>>
>> ive just added new ram but im sure that that is not the problem
>> because I
>
> Your PC doesnt like the new ram you installed. Pretty simple. It's the
> last thing you did before you started seeing the niggle.
>
>
>

yes but i've tried other sticks of ram and even tried it without the new
ram

 

[Malke]

Archived from groups: microsoft.public.windowsxp.general (More info?)

Stone Monkey wrote:

> Plato <|@|.|> wrote in news:42c58063$0$90592$bb4e3ad8@newscene.com:
>
>> Stone Monkey wrote:
>>>
>>> while running adaware on my pc it restarted and i got this error
>>> message from the BSOD
>>>
>>> ***STOP 0x0000008e (0xc0000005,0x8056e2a2,0xb4c81ba4,0x00000000)
>>> i got this error once and it changed the next time to
>>> ***STOP 0X0000008e (0xc0000005,0x8056e2a2,0Xf3242ba4,0x00000000)
>>> and then changed to
>>> ***STOP 0X0000008e (0xc0000005,0x8056e2a2,0Xf3300ba4,0x00000000)
>>>
>>> ive just added new ram but im sure that that is not the problem
>>> because I
>>
>> Your PC doesnt like the new ram you installed. Pretty simple. It's
>> the last thing you did before you started seeing the niggle.
>>
>>
>>
>
> yes but i've tried other sticks of ram and even tried it without the
> new ram

Then the problem lies with the motherboard. Perhaps you damaged the RAM
slots whilst you were putting in the new sticks. Perhaps the m/b has
coincidentally started to fail.

Malke
--
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic!"
MS-MVP Windows - Shell/User