Stop 0x8E mssg

I keep getting this message for some reason. I thought that it might be a problem with the bios so i reset the cmos batt, and nothing happened (with the message, bios got reset meaning it is not a problem with the bios) I have formatted this computer about 2 times to no prevail... still the dreded blue screen of death. my fears about this are slowly coming true... it has to be a either an os problem (hopefully) or the dreaded hardware problem (not cool)... btw, i clean installed windows xp pro both times... another thing, i recently put a new psu in recently(i calculated the voltage myself twice, and the store that i bought it from calculated it also, so it should not be a problem with the voltage)

anyone have any ideas?

There are so many possible problems i just said heck with it and threw it under windows XP (since that may be the reason, hopefully)

ps. i have had an increadibly busy schedule with collage *sigh*, so i might not get back right away... but i will be checking when i can.

Thanks,
Jason

 

but there is nothing on my computer but the operating system... and i cannot even access the OS. not in safe mode or anything... everything in the load windows menu ends up the same way... Stop 0x8E

 

Hi

Take a look at this page had some tips you could try, Please post back if it helped
link
Good luck

 

wow... according to this, it says that it might be a problem with the ram... you know, i think that i will have to mess with that stuff and see if it is... thanks

i think this may of helped,
Jason

 

well, now i am not getting the 8E message anymore, im only getting a 0x50 message now

 

what did you do the make the error massage change?

 

ok... it turned out that i was looking around and made the computer think there was 2 memory chips instead of the one that it has... i fixed it, and now i am not getting that message anymore, YAY... but now i am getting the 0x8E message again, joy...lol


Jason

 

Perhaps running Standard Recovery would be an option for you.
See this Post

Hope you get things up and running
Beamuse

 

http://support.microsoft.com/?kbid=315335

i have linked it to the RAM, but the sad thing is, i have tried 2 different chips, same size and everything, but it still does not want to work... does this mean that it is a problem with the mobo?

i do not have the money to go out and buy a new computer (college budget)

 

You could try running the Windows Memory Diagnostic Program

The diagnostic includes a comprehensive set of memory tests. If you are experiencing problems while running Windows, you can use the diagnostic to determine whether the problems are caused by failing hardware, such as RAM or the memory system of your motherboard.

Hope this helps
Beamuse

 

Hi
Have you tried one memory stick at a time, may be only one is faulty?

 

A stop 8e is caused by a Drwatson-ish event inside a kernel driver. I would not think that its being caused by bad ram, without throwing a host of other fun codes as well. I'll bet you have a bum driver. The dump will allow us to pinpoint which one done it.

Can you run the dump through the dump tool and post results?
http://www.windowsbbs.com/showthread.php?t=33471

 

i would if i could get on my computer... as it is, it seems to stop at MUP.sys when loading

Jason

 

even in safe mode?? What did you do, you must have some mismatched files.

3 options
1) pull the drive, and run "savedump -c thepagefile memory.dmp "
2) do a 'big copy' restore of the system32 and drivers directory.
3) parallel install, tweak boot.ini for debug, boot up under debugger, collect !analyze -v output and paste it here.

 

Actually... some have come to think that it was a problem with the ram, not the drive....

To date... I have gotten these two stop messages

0x0000008E
0x00000050

These seem to go hand in hand... both problems with the ram at least I think it is. See Info

Also, there seems to be a problem with mup.sys (possible driver info) since the safe mode boot screen seems to change into the blue screen of death upon hitting this file.

You did give a good idea. (I think this was what you were suggesting at least)
It would be a great idea to test the HD on another computer to see if it is the cause... but, you see, that is quite impossible. The only other computer that I have, coincidentally typing this very response on right now, just so happens to be my laptop... bad times, bad times indeed.

Well, I do not mean any sarcasm or criticism in this post, even though it may sound like it... this computer thing just makes me want to do something like this guy (very funny, but a download... if you don’t trust me, I understand )

Thanks a lot,
Jason

 

Oh ya, the link is from ebaumsworld.com
(Don’t want to infringe on any copyright laws today... that is not on my calendar until Thursday )

 

Create a set of boot floppies
How to obtain Windows XP Setup boot disks
XP setup boot disks

Then follow the directions using the floppies and recovery console
How to Use Recovery Console - (making sure to print out the directions before you start)
Recovery Console

Or you can use your recovery cds and do a recovery that will save your files but replace the OS.

These methods happen before windows boots so hopefully one will work.

Beamuse

 

its difficult to make an authoritative leap from the safe mode output to a specific driver at fault. The only good data is a dump for 8es. At this point i see no evidence to support it being a ram problem, otherwise it wouldnt be in so consistant a spot. Its certainly a possiblity, but the odds are quite low right now.

Heres what i recommend. Do a parallel install to a different partition or c:\windows2 so you can get into the machine. Bring that parellel install up to the same service pack/hotfix level as the other install, then copy all the SYS files from \windows2\system32\drivers over. That should get you into a 'i can boot into safe mode' state.