BSOD Help!

[tbrox]

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

 

[philo]

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)

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]

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.

 

[philo]

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

 

[Alun Harford]

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

Your memory is faulty.

Alun Harford

 

[tbrox]

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

Your memory is faulty.

Alun Harford

 

[tbrox]

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

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

 

[AlexB]

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.

 

[MICHAEL]

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

 

[AlexB]

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]

What are stupid pills?

An excuse for your ignorance/imbecility.

Perhaps, you could be a participant in the clinical trials for
the anti-stupid pill.
http://www.heraldtribune.com/apps/pbcs.dll/article?AID=/20060810/COLUMNIST23/608100713

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?

The OP has already received a good answer... it was not your post.

You have absolutely nothing to say, just splash short phrases of insult
revealing your personality totally naked.

Stop drooling.

Just run your racket and be happy.

Just try to keep your ignorance to yourself.

Thanks.


-Michael

 

[tbrox]

I build my own computers and have been for 20 years and I know all about
defrag and other cleanup and maintenence things to do. I also know that BSOD
are normally caused by a hardware problem or driver problem. I also know
about Dell computers and dell diagnostics.

I just finished a pretty extensive RAM test of all 4 of my 1GB modules and I
tested them in all 4 of my memory slots. I found one module that constantly
failed at the same spot. I now have that module out of my computer and I
will know within 36 hours if my blue screen problems are all gone.

I don't fault AlexB for trying to help however I don't think AlexB really
understands what kinds of things cause the BSOD. I did fix one BSOD by
performing a clean install with all updated drivers on a Dell laptop once.
However most of the time I fix them by replacing hardware or updating
drivers. I would prefer it if everone would play nice on these message
boards.

 

[philo]

Thanks, I will focus in on my RAM

OK...
looks like you got it figured out now.

BTW: I've been on Usenet for a number of years.
I always advise simply ignoring inappropriate remarks..
but of course, never follow my own advice most of the time <G>

 

[AlexB]

Thank you very much, Thorox. It is a nice ending. I am happy you did. I also
take such things into my notebook. It is like expanding my own experience
without going thru such calamities.

I just wanted to relay my PERSONAL experience and I thought you could take
it or throw it away. It was up to you. I am glad you have experience with
hardware testing although many people don't.

I am just curious what diagnostics did you use for your testing? Dell's or
third party? If it is DELL's the first thing this GUI says is to close all
programs, etc on the disk. If you have only one disk what are you going to
do?

I am just curious how people handle such problems especially with laptops
where you most likely do not have a spare OS to boot from?

Many thanks.

 

[tbrox]

On most dell computers during bootup there is a prompt in the upper right
hand corner of your screen to press F12. The next menu offers some
diagnostic option.

 

[thetruthhurts]

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

The reason that the MVPs are silent on this thread is that they've
never seen a BSOD on Vista.

 

[philo]

The reason that the MVPs are silent on this thread is that they've
never seen a BSOD on Vista.

ROTFLMAO !!@!!


BTW: I never have once gotten a blue screen once I switched to a monochrome
monitor <G>

 

[tbrox]

I'm sure thetruthhurs sarcasim is designed to make us laugh.

For those who might be reading and are looking for an answer I think I may
have found it.

I used memtest86+ memory tester and found 1 of my four Kingston 1066
(PC8500) memory modules constantly failed. Since I'm running 4 sticks in dual
mode I remove the bad module and one good module. I reset all the memory
settings in my BIOS back to auto. I still got BSOD only this time the stop
codes were differnt. The first time I got the following.

Stop: 0x0000000a
The second time I got:
Stop: 0x00000050 with a drive named ecache.sys
and once again I got the 0x0000000a error.

Research continued to point to a memory problem. This last go around I
changed my memory DRAM frequency to 800 Mhz instead of Auto or 1066. For the
first time ever I have gone over 24 hours without a blue screen.

Here is some additional information. My memory settings after removing the
faulty module come from the Asus P5E motherboard. It has the latest Intel x38
express chipset on it. The people on the Asus message board are telling me
to downgrade my BIOS to the release version. I have not done that yet but I
think I will try because I want to be able to run my RAM at the specified
speed of 1066. After all that is what I paid for.

Just in case thetruthhurs was not kidding I hope thetruthhurts never gets a
bad memory module because I would not want to wish the BSOD on anyone.

Here is to hoping mine stay away.

 

[Alun Harford]

The reason that the MVPs are silent on this thread is that they've
never seen a BSOD on Vista.

I get the feeling Microsoft need to make a Windows version of the badram
patch, and enough automatic configuration that users don't see it.

After all, they're the ones who get the blame when people run their OS
on defective hardware.

Alun Harford
(Who has never seen a BSOD on Vista)

 

[philo]

I'm sure thetruthhurs sarcasim is designed to make us laugh.

For those who might be reading and are looking for an answer I think I may
have found it.

I used memtest86+ memory tester and found 1 of my four Kingston 1066
(PC8500) memory modules constantly failed. Since I'm running 4 sticks in dual
mode I remove the bad module and one good module. I reset all the memory
settings in my BIOS back to auto. I still got BSOD only this time the stop
codes were differnt. The first time I got the following.

Stop: 0x0000000a
The second time I got:
Stop: 0x00000050 with a drive named ecache.sys
and once again I got the 0x0000000a error.

Research continued to point to a memory problem. This last go around I
changed my memory DRAM frequency to 800 Mhz instead of Auto or 1066. For the
first time ever I have gone over 24 hours without a blue screen.

Here is some additional information. My memory settings after removing the
faulty module come from the Asus P5E motherboard. It has the latest Intel x38
express chipset on it. The people on the Asus message board are telling me
to downgrade my BIOS to the release version. I have not done that yet but I
think I will try because I want to be able to run my RAM at the specified
speed of 1066. After all that is what I paid for.

Just in case thetruthhurs was not kidding I hope thetruthhurts never gets a
bad memory module because I would not want to wish the BSOD on anyone.

Here is to hoping mine stay away.

<snip>

Looks like you are pretty well along the path to having the problem solved.

If the bios rollback does not get you going...you should contact the RAM
mfg...
I'd want to use the RAM at it's rated speed too...