0x0000008E STOP MESSAGE - More Info

  • Thread starter Thread starter Ian Mageau
  • Start date Start date
I

Ian Mageau

Here's something new.

As per my previous posts I cannot boot up into Safe Mode
or Safe Mode with Networking.

Just now I found I CAN boot into Safe Mode with Command
Prompt. This may be usefull... I was able to run
regedt32. However I then thought of running MMC for
further log information and I got the usual 0x0000008E
STOP MESSAGE.

I tried again Safe Mode and Safe Mode with Networking.
And either clicking Yes or No to Use or not use System
Restore and it crashes.

My hypothesis? Corrupted/Broken/Something with the
explorer.exe. Since this is the major component loaded at
startup in normal mode and the only major missing
component from Safe Mode with Command Prompt.

And if I'm not mistaken that's the process which manages
paging file... which could be greatly affected by a
memory upgrade.

Ok so this is all speculation. Can someone help me out? ;)

Also I'm wondering if I can run SFV from Safe Mode with
Command Promt? Maybe? If so what tags should I append to
the command line?

Thanks everyone in advance for all your help!

Regards,

Ian Mageau
 
This behavior can occur if one of the following conditions is true:
a.. One or more of the random access memory (RAM) modules that are
installed on your computer are faulty.
b.. The RAM configuration is incompatible with Windows XP.

--
 
I tried that already. All 4 modules one by one.

No change whatsoever.

Someone outside this group suggested possibly the DIMM
slots got damaged, which is possible... However I doubt it
since the system goes through POST just fine AND I'm able
to run micro-distributions of Linux with no problem. Only
Windows gives problems.

Right now my main concern is getting the system booted and
networked (File system and network access) so I can move
all the files. At which point I can fdisk and format the
drive. I'll try reinstalling Windows again then.

Thanks for your reply,

Ian Mageau
 
Hmm. Ian, this is becoming quite the twister, isn't it? I thought I'd
throw this your way...just in case; (regrettably, I'm not CERTAIN of the
function of this action.)

There's a tiny two-position jumper on the mobo somewhere that, when switched
over, resets the CMOS parameters. I believe that's what it's for. I
mention this because, when I dropped into my local store recently, the
fellow had just inserted a second stick of RAM into a client's board...and
it wasn't booting properly. He pulled this little jumper off and popped it
onto the other set of pins...then popped it right back again. Poof! The
board happily accepted the pair of sticks. And he acknowledged that they
were not identical.

Personally, I was a bit suspicious of the chicken bones and the komodo
dragon skull he had hanging over the work table...but hey! If it works,
right?

Back to you.
Ron
 
Ok... Thanks for the suggestion. However at this point
I'm pretty doubtfull of any hardware problems.

I just successfully installed Windows 2000 Pro on the
existing partition without making any changes. Runs like
a charm. Now I'm happy, I will backup the entire drive.
Then fdisk and try a clean install of Windows XP Pro
again.

From what I've learnt in the past few days... I think
Windows XP just didn't like me upgrading my RAM hehe. I'm
guessing it messed up its virtual memory alocations and
its pagefile. As to why it wasn't installing I'm not
sure. But the Windows XP installer is pretty weak I have
to say. In all its facets it's basically a stripped down,
locked down version of the Windows 2000 installer. I'm
hoping once I repartition the drive I will be able to
install and should hopefully not have any more problems.

I'll let you know how it turns out.

Regards,

Ian Mageau
 
Back
Top