Technobabble problem

[Andy Flowers]

Apologies for another question (problems with XP shutdown continuing)

Further to previous threads (and many apologies to all those kind people
out there trying to cure my PC shutdown problems)

To recap, my PC has been shutting down since I bought it, repair bloke
changed fans etc, didn't fix it, now won't answer phones. Running
Windows XP

After useful help from usenet have disabled automatic restart and now
get the following message on a blue screen

"A problem has been detected and windows has been shut down to prevent
damage to your computer

STOP ox0000008E (oxC00000005, oxBF865476, oxF43EBBCC, ox00000000)

win32k.sys - Address BF865476 base at BF800000, Datestamp 3f73195d

Beginning dump of physical memory

Physical memory dump complete"


If anyone has any advice, your guidance will be much appreciated.

Cheers

 

[Rick \Nutcase\ Rogers]

Hi Andy,

Faulty/mismatched/incompatible ram is nearly always the cause of this error.
Suggest you see about getting them replaced. If you have multiple sticks,
try removing one to see if it cures the problem.

--
Best of Luck,

Rick Rogers aka "Nutcase" MS-MVP - Win9x
Windows isn't rocket science! That's my other hobby!

Associate Expert - WinXP - Expert Zone

 

[Malke]

Apologies for another question (problems with XP shutdown continuing)

Further to previous threads (and many apologies to all those kind
people out there trying to cure my PC shutdown problems)

To recap, my PC has been shutting down since I bought it, repair bloke
changed fans etc, didn't fix it, now won't answer phones. Running
Windows XP

After useful help from usenet have disabled automatic restart and now
get the following message on a blue screen

"A problem has been detected and windows has been shut down to prevent
damage to your computer

STOP ox0000008E (oxC00000005, oxBF865476, oxF43EBBCC, ox00000000)

win32k.sys - Address BF865476 base at BF800000, Datestamp 3f73195d

Beginning dump of physical memory

Physical memory dump complete"

Hi, Andy. Still slogging away at it, eh? You are amazingly cheerful.
Anyway, do a RAM test. On another computer, download the Windows
precompiled version of Memtest86 (http://www.memtest86.com/). Use it to
make a bootable floppy and boot the sick computer with it. Be prepared
to let the machine run for a few hours (unless you immediately see RAM
errors!). Let's hear back from you after you've done that test.

Cheers back at you,

Malke

 

[Andy Flowers]

Hi, Andy. Still slogging away at it, eh? You are amazingly cheerful.
Anyway, do a RAM test. On another computer, download the Windows
precompiled version of Memtest86 (http://www.memtest86.com/). Use it to
make a bootable floppy and boot the sick computer with it. Be prepared
to let the machine run for a few hours (unless you immediately see RAM
errors!). Let's hear back from you after you've done that test.

Cheers back at you,

Malke

Many thanks for getting back to me

From yours, and a couple of other replies (not the abusive ones) it does
indeed appear that I have a RAM problem.

I hope the thread has been useful to others with similar problems (and
fingers crossed its sorted out mine).

Once again, many thanks, and thanks to everyone who have taken the time
to post constructive and helpful comments.

As to the others - well that's Usenet for you!

Cheers