Real Geek Forums > Archives > Operating Systems > Windows XP > Windows XP Hardware > 0x0000008E STOP MESSAGE - More Info

0x0000008E STOP MESSAGE - More Info

Posted: 07-13-2003, 06:04 PM
Ian Mageau
Guest
Posts: n/a
 
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
>-----Original Message-----
>My computer was running ok. But I did have an extra 1GB
>of DDR RAM on the shelf. So I figured I'd install it.
>
>After I did, I booted up and everything went through
POST
>no problem. It loaded Windows XP no problem. And I got
>the welcome screen. I chose my user as normal and
entered
>my password. Then I got 0x0000008E STOP MESSAGE.
>
>I rebooted, and instead this time when I logged in I got
>an error saying "A problem is preventing windows from
>accurately checking the license for this computer.". And
>no option to correct it. Reboot again and let chkdsk go
>through. Now we're back to the STOP message.
>
>I hopped on the MS knowledgebase through another PC and
>found out that error means either 1) Faulty RAM module
or
>2) RAM Configuration incompatible with Windows XP.
>
>I said OK... I tried switching the 2 modules in diff
dimm
>slots. I tried going down to 1x 512MB module. Tested
both
>modules. And since I was getting no results I deviced to
>go back to my original RAM configuration. SAME problem.
>Again same, switch modules, try one by one routing. To
no
>avail.
>
>So I gave up. But I still need some of the information
on
>that disk and I can't get it using this windows
>installation.
>
>So here I am trying to install Windows XP. I've tried
>booting up, selecting repair existing, booting up, new
>install (same path) and new install (new path). And
every
>time... no matter how many times I repeat those steps I
>always end up getting "Setup has made changes to your
>drive, please reboot". And sometimes Setup tries to be
>original and throws in a PFN_LIST_CORRUPT Stop Message.
>Which according to what I could find is a Win2000 error,
>not WinXP.
>
>Any ideas???
>
>Please help. I'm at a loss here...
>.
>

0x0000008E STOP MESSAGE - More Info


Responses to "0x0000008E STOP MESSAGE - More Info"

PaulM
Guest
Posts: n/a
 
Re: 0x0000008E STOP MESSAGE - More Info
Posted: 07-13-2003, 06:16 PM
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.

--
-----
Paul
-----
www.paulsxp.com
www.paulsxp.com/forums

"Ian Mageau" <PsychNet2000@hotmail.com> wrote in message
news:03af01c34969$3b3c7f00$a001280a@phx.gbl...
> 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
>
> >-----Original Message-----
> >My computer was running ok. But I did have an extra 1GB
> >of DDR RAM on the shelf. So I figured I'd install it.
> >
> >After I did, I booted up and everything went through
> POST
> >no problem. It loaded Windows XP no problem. And I got
> >the welcome screen. I chose my user as normal and
> entered
> >my password. Then I got 0x0000008E STOP MESSAGE.
> >
> >I rebooted, and instead this time when I logged in I got
> >an error saying "A problem is preventing windows from
> >accurately checking the license for this computer.". And
> >no option to correct it. Reboot again and let chkdsk go
> >through. Now we're back to the STOP message.
> >
> >I hopped on the MS knowledgebase through another PC and
> >found out that error means either 1) Faulty RAM module
> or
> >2) RAM Configuration incompatible with Windows XP.
> >
> >I said OK... I tried switching the 2 modules in diff
> dimm
> >slots. I tried going down to 1x 512MB module. Tested
> both
> >modules. And since I was getting no results I deviced to
> >go back to my original RAM configuration. SAME problem.
> >Again same, switch modules, try one by one routing. To
> no
> >avail.
> >
> >So I gave up. But I still need some of the information
> on
> >that disk and I can't get it using this windows
> >installation.
> >
> >So here I am trying to install Windows XP. I've tried
> >booting up, selecting repair existing, booting up, new
> >install (same path) and new install (new path). And
> every
> >time... no matter how many times I repeat those steps I
> >always end up getting "Setup has made changes to your
> >drive, please reboot". And sometimes Setup tries to be
> >original and throws in a PFN_LIST_CORRUPT Stop Message.
> >Which according to what I could find is a Win2000 error,
> >not WinXP.
> >
> >Any ideas???
> >
> >Please help. I'm at a loss here...
> >.
> >

Ian Mageau
Guest
Posts: n/a
 
Re: 0x0000008E STOP MESSAGE - More Info
Posted: 07-14-2003, 10:20 AM
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
>-----Original Message-----
>"Ian Mageau" <PsychNet2000@hotmail.com> wrote:
>
>>Thanks Paul.
>>
>>I also read Microsoft KBID 315335. No need to quote it
>>for me.
>>
>>As per my previous posts, I ensured that the RAM modules
>>are NOT faulty. IF and only IF the RAM configuration is
>>incompatible with Windows XP then I have no clue why
>>ANYONE would want windows XP. 2x512MB or 2x256MB is NOT
>>an uncommon RAM configuration.
>>
>>Thanks for coming out!
>>
>
>It seems that you have more than one RAM module installed.
>
>It could be that the two RAM modules are not compatible
with each
>other.
>
>This can happen if, for example, the modules are from
different
>manufacturers, or even from the same manufacturer but
different
>production lots. In these situations there can be
internal
>differences in the physical layout and/or the material
composition of
>the RAM modules, and these differences can affect the
strength and
>timing of the signals returned from the RAM. Windows is
sensitive to
>this and can react adversely to them.
>
>The "acid test" for identifying this type of problem is
to run the
>computer with only a single RAM module installed. If
the computer
>operates error-free (albiet somewhat slower) with each of
the modules
>installed by itself, but there are problems when the
modules are
>installed together then this is pretty conclusive
evidence of
>incompatible modules. The only "cure" is to replace one
or more
>modules so that all are absolutely identical - same
manufacturer and
>same production lot.
>
>Good luck
>
>
>Ron Martell Duncan B.C. Canada
>--
>Microsoft MVP
>On-Line Help Computer Service
>http://onlinehelp.bc.ca
>
>"The reason computer chips are so small is computers
don't eat much."
>.
>
Ron
Guest
Posts: n/a
 
Re: 0x0000008E STOP MESSAGE - More Info
Posted: 07-14-2003, 12:40 PM
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


Ian Mageau
Guest
Posts: n/a
 
Re: 0x0000008E STOP MESSAGE - More Info
Posted: 07-15-2003, 02:23 AM
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

>-----Original Message-----
>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
>
>
>.
>
 
LinkBack Thread Tools Display Modes
 

« Previous Thread | Next Thread »

Thread Tools
Display Modes
Linear Mode Linear Mode

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On
Forum Jump


Similar Threads
Thread Thread Starter Forum Replies Last Post
Error Message When Sending Message In Windows Mail Norm Windows Vista 4 03-22-2006 11:56 PM
SP2 RC1 causes stop condition 0x0000008E. Joe Coplen Windows XP Beta 1 04-01-2004 09:46 PM
0x0000008E STOP MESSAGE Cari \(MS-MVP\) Windows XP Hardware 6 07-15-2003 05:16 PM
RPD protocol info Chuong Windows XP Work Remotely 0 07-12-2003 05:03 AM
E-Mail message saying I have 1 new message under my Logon ID in XP Ramesh \(XP Power User\) Windows XP Network & Web 0 07-02-2003 03:14 PM