Stop message during upgrade from 98se to 2000

  • Thread starter Thread starter Don P
  • Start date Start date
D

Don P

My initial attempt to upgrade to windows 2000 pro was
unsuccessful due to lack of ram. I added 128mb and was
able to avoid the initial error I was getting. Now I am
receiving the following:

*** STOP: 0x000000C2
(0x00000099,0xE12361E8,0x00000000,0x00000000)
BAD_POOL_CALLER

This is on a blue screen

It happens when I try to boot from the Windows 2000 Pro
CD.

If I try to boot from the hard drive which was running
windows 98se until I began the upgrade, I get an error
stating that I have a corrupt or missing ntoskrnl.exe.

Anyone's superior knowledge on this would be greatly
appreciated.

Thank You

Confused
 
Thanks Ted for the reference.
I still don't understand the fix. Is this a hardware
problem or a driver issue? I've since removed all cards
except the video for the monitor. Still get the same
error. I even started over and used a win98se boot disk
to fdisk and format. Now I have nothing on my drive. No
big lose though, I had my files bu. Now I just want to
get an OS on the thing. Would this problem be resolved
with putting win98se on instead of win2kpro? To be
honest I have never done any debugging before. Your help
needed. Thanks
 
Additional Note:
I tried using a downloaded boot disk (4 floppies) from
bootdisk.com. Using these instead of the full cd version
of win2kpro caused a STOP 0x0000007F
(UNEXPECTED_KERNEL_MODE_TRAP). I have no idea why I
would get a different error. I read over the
http://support.microsoft.com/default.aspx?scid=kb;EN-
US;137539. If this is a hardware/memory problem, why
would I not get the same error when setup is with a cd.
Could all of this be due to a motherboard problem. But
it was not having problems with win98se.

Don P
 
I see you have found the following link:

http://support.microsoft.com/default.aspx?scid=kb;en-us;137539

You mentioned having added a RAM module (MEM upgrade). I suggest you use
modules which are identical & from the sme batch to prevent
problems...Win2000 can be fussy at times...Mismatched memory modules can
cause this problem too! Your problem could likely be resolved after using
matched modules...

I also suggest that you update the BIOS before installing Win2000 on the
system...BUT only after contacting the Motherboard Manufacturer...By the way
I hope you're NOT OVER CLOCKING! If you are, don't (at least NOT while
installing the OS)!

Ted
 
Back
Top