BSOD Help!

3 seperate BSOD message. I hope someone can tell me what to look for. The
last 2 did not specify any file name.

Stop: 0x0000008E (0x00000005, 0x954B1987, 0x9D63FBE0, 0x00000000)

Win32k.sys - address 954B1987 Base at 95400000, Date Stamp 46d4d163

----------------------------------------------------------------------------------------

Stop: 0x0000008E (0xC0000005, 0x81CE892E, 0x9A007A14, 0x00000000)

----------------------------------------------------------------------------------------

Stop: 0x0000008E (0xC0000005, 0x81D3FE59, 0xA64CB95C, 0x00000000)
--
Tbrox

"tbrox" <> wrote in message
news:62BE98E4-82FC-439A-88B2-...
> 3 seperate BSOD message. I hope someone can tell me what to look for. The
> last 2 did not specify any file name.
>
> Stop: 0x0000008E (0x00000005, 0x954B1987, 0x9D63FBE0, 0x00000000)
>
> Win32k.sys - address 954B1987 Base at 95400000, Date Stamp 46d4d163
>
> --------------------------------------------------------------------------
--------------
>
> Stop: 0x0000008E (0xC0000005, 0x81CE892E, 0x9A007A14, 0x00000000)
>
> --------------------------------------------------------------------------
--------------
>
> Stop: 0x0000008E (0xC0000005, 0x81D3FE59, 0xA64CB95C, 0x00000000)
> --
> Tbrox


can you boot to safe mode?

If you try to boot to safe mode...but get the same types of errors...
run a RAM test

Yes I can boot into safe mode however I can never tell how long it will take
to get the BSOD. I did run memtest86 and at 26% I had over 150 errors.

This is a new computer running 4GB Kingston PC8500. I was thinking RAM but
I'm not sure If I have all the MB ram settings correct and if the RAM for
sure is the problem.
--
Tbrox


"philo" wrote:

>
> "tbrox" <> wrote in message
> news:62BE98E4-82FC-439A-88B2-...
> > 3 seperate BSOD message. I hope someone can tell me what to look for. The
> > last 2 did not specify any file name.
> >
> > Stop: 0x0000008E (0x00000005, 0x954B1987, 0x9D63FBE0, 0x00000000)
> >
> > Win32k.sys - address 954B1987 Base at 95400000, Date Stamp 46d4d163
> >
> > --------------------------------------------------------------------------
> --------------
> >
> > Stop: 0x0000008E (0xC0000005, 0x81CE892E, 0x9A007A14, 0x00000000)
> >
> > --------------------------------------------------------------------------
> --------------
> >
> > Stop: 0x0000008E (0xC0000005, 0x81D3FE59, 0xA64CB95C, 0x00000000)
> > --
> > Tbrox
>
>
> can you boot to safe mode?
>
> If you try to boot to safe mode...but get the same types of errors...
> run a RAM test
>
>
>

"tbrox" <> wrote in message
newsC220F06-7178-453A-96BD-...
> Yes I can boot into safe mode however I can never tell how long it will
take
> to get the BSOD. I did run memtest86 and at 26% I had over 150 errors.
>
> This is a new computer running 4GB Kingston PC8500. I was thinking RAM
but
> I'm not sure If I have all the MB ram settings correct and if the RAM for
> sure is the problem.
>


Then you *defiantly* have a RAM problem.

memtest should be able to run for hours without so much as a single error!!!

Check your mobo manual carefully and check the settings in the bios.

If you are not sure...then *underclock* the RAM.

As a matter of fact...set the ram to some minimal setting and run memtest
again.


If there are any errors at all the RAM is probably defective...so you should
check it stick by stick.

If the errors stop entirely, you may clock the ram up higher...
but if it has errors when running at it's specified rating...then the RAM is
prob. defective


BTW: When running memtest...once even *one* error is found...no sense in
letting it run any further

tbrox wrote:
> 3 seperate BSOD message. I hope someone can tell me what to look for. The
> last 2 did not specify any file name.
>
> Stop: 0x0000008E (0x00000005, 0x954B1987, 0x9D63FBE0, 0x00000000)
>
> Win32k.sys - address 954B1987 Base at 95400000, Date Stamp 46d4d163
>
> ----------------------------------------------------------------------------------------
>
> Stop: 0x0000008E (0xC0000005, 0x81CE892E, 0x9A007A14, 0x00000000)
>
> ----------------------------------------------------------------------------------------
>
> Stop: 0x0000008E (0xC0000005, 0x81D3FE59, 0xA64CB95C, 0x00000000)

Your memory is faulty.

Alun Harford

Thanks, I will focus in on my RAM
--
Tbrox


"Alun Harford" wrote:

> tbrox wrote:
> > 3 seperate BSOD message. I hope someone can tell me what to look for. The
> > last 2 did not specify any file name.
> >
> > Stop: 0x0000008E (0x00000005, 0x954B1987, 0x9D63FBE0, 0x00000000)
> >
> > Win32k.sys - address 954B1987 Base at 95400000, Date Stamp 46d4d163
> >
> > ----------------------------------------------------------------------------------------
> >
> > Stop: 0x0000008E (0xC0000005, 0x81CE892E, 0x9A007A14, 0x00000000)
> >
> > ----------------------------------------------------------------------------------------
> >
> > Stop: 0x0000008E (0xC0000005, 0x81D3FE59, 0xA64CB95C, 0x00000000)
>
> Your memory is faulty.
>
> Alun Harford
>

Thanks, I will focus in on my RAM
--
Tbrox


"philo" wrote:

>
> "tbrox" <> wrote in message
> newsC220F06-7178-453A-96BD-...
> > Yes I can boot into safe mode however I can never tell how long it will
> take
> > to get the BSOD. I did run memtest86 and at 26% I had over 150 errors.
> >
> > This is a new computer running 4GB Kingston PC8500. I was thinking RAM
> but
> > I'm not sure If I have all the MB ram settings correct and if the RAM for
> > sure is the problem.
> >
>
>
> Then you *defiantly* have a RAM problem.
>
> memtest should be able to run for hours without so much as a single error!!!
>
> Check your mobo manual carefully and check the settings in the bios.
>
> If you are not sure...then *underclock* the RAM.
>
> As a matter of fact...set the ram to some minimal setting and run memtest
> again.
>
>
> If there are any errors at all the RAM is probably defective...so you should
> check it stick by stick.
>
> If the errors stop entirely, you may clock the ram up higher...
> but if it has errors when running at it's specified rating...then the RAM is
> prob. defective
>
>
> BTW: When running memtest...once even *one* error is found...no sense in
> letting it run any further
>
>
>

I don't know who've made your computer but at DELL they have hardware
diagnostics downloads. They are model specific but cover a wide range of
models.

The way I did it was as follows.

I have another partition, went there and ran it from XP to check Vista
because I was suspicious of crashes. needless to say it was all b*s. The RAM
was perfectly fine. Eventually I found out it was all my fault. A lot of
people who come here with problems like yours forget to mention that did
something drastic to their Vistas (pretty much as I did before I learned
Vista ways).

I think you may try to defragment--it is helpful, you can also leave your
machine overnight with Internet connection open. You may be surprised to
find a healthy Vista next day, although it might take more than one night
because there are so many such idiots like you and I out there.


"tbrox" <> wrote in message
news:2C890696-E5A9-4C1B-9C3F-...
> Thanks, I will focus in on my RAM
> --
> Tbrox
>
>
> "Alun Harford" wrote:
>
>> tbrox wrote:
>> > 3 seperate BSOD message. I hope someone can tell me what to look for.
>> > The
>> > last 2 did not specify any file name.
>> >
>> > Stop: 0x0000008E (0x00000005, 0x954B1987, 0x9D63FBE0, 0x00000000)
>> >
>> > Win32k.sys - address 954B1987 Base at 95400000, Date Stamp 46d4d163
>> >
>> > ----------------------------------------------------------------------------------------
>> >
>> > Stop: 0x0000008E (0xC0000005, 0x81CE892E, 0x9A007A14, 0x00000000)
>> >
>> > ----------------------------------------------------------------------------------------
>> >
>> > Stop: 0x0000008E (0xC0000005, 0x81D3FE59, 0xA64CB95C, 0x00000000)
>>
>> Your memory is faulty.
>>
>> Alun Harford
>>

"AlexB" <> wrote in message news:...
> I don't know who've made your computer but at DELL they have hardware
> diagnostics downloads. They are model specific but cover a wide range of
> models.
>
> The way I did it was as follows.
>
> I have another partition, went there and ran it from XP to check Vista
> because I was suspicious of crashes. needless to say it was all b*s. The RAM
> was perfectly fine. Eventually I found out it was all my fault. A lot of
> people who come here with problems like yours forget to mention that did
> something drastic to their Vistas (pretty much as I did before I learned
> Vista ways).

> I think you may try to defragment--it is helpful,

> you can also leave your
> machine overnight with Internet connection open. You may be surprised to
> find a healthy Vista next day, although it might take more than one night
> because there are so many such idiots like you and I out there.

WTF? Have you been overdosing on stupid pills?


-Michael

What are stupid pills?

You, mentally retarded, what is your counter proposal? Could you explain
what is wrong with what I suggested? How would you approach this problem
with your monumental Ubuntu experience?

You have absolutely nothing to say, just splash short phrases of insult
revealing your personality totally naked. Just run your racket and be happy.

"MICHAEL" <> wrote in message
news:O0n$...
> "AlexB" <> wrote in message
> news:...
>> I don't know who've made your computer but at DELL they have hardware
>> diagnostics downloads. They are model specific but cover a wide range of
>> models.
>>
>> The way I did it was as follows.
>>
>> I have another partition, went there and ran it from XP to check Vista
>> because I was suspicious of crashes. needless to say it was all b*s. The
>> RAM was perfectly fine. Eventually I found out it was all my fault. A lot
>> of people who come here with problems like yours forget to mention that
>> did something drastic to their Vistas (pretty much as I did before I
>> learned Vista ways).
>
>> I think you may try to defragment--it is helpful,
>
>> you can also leave your machine overnight with Internet connection open.
>> You may be surprised to find a healthy Vista next day, although it might
>> take more than one night because there are so many such idiots like you
>> and I out there.
>
> WTF? Have you been overdosing on stupid pills?
>
>
> -Michael
>