Windows 2000 Server install and stability issues:

[Migroo]

I've now tried to load Windows 2000 on two machines we have here, to no avail.

The first machine wouldnt get through the installation process, it would bluescreen after the file load when Windows 'detects your hardware'. I tried changing PCI slots and tried different video cards and ethernet cards. The machine was an Athlon 950, Abit KT133 mobo, 256mb crucial ram, 30gb HDD, Pioneer DVD, various video cards (both AGP and PCI) and various ethernet cards tried in different PCI slots.

I gave up on that machine due to lack of progress. That machine had successfully run Win XP Pro for 6 months (before that Win 98 for 18 months) so I thought it was a good machine.

I've just tried installing on a P2-350, Intel motherboard, 128mb ram, 30 gb HDD (a different drive to the above machine), various video cards, Intel Pro 10/100 Server ethernet card etc and it loads the OS (if I'm lucky) and I can get the OS to run but it is unstable, in that it will bluescreen before the night is over (I test by running overnight).. (note this machine ran a host of operating systems fine..)

What can I do? We are running out of options, one of which is to purchase a new P4 server motherboard, new chip, ECC ram etc.. will this be worth it? Personally I can see no guarantee that this new hardware would work either..

Any tips from someone who has done this before?

 

[LiLithTecH]

Sounds more like configuration problems then a hardware issue.
None of the above hardware you mentioned should cause any
problems with the installation.

How are you configuring the install (AD, DHCP, WINS, DC, File Server, etc..)?

In the second instance above, what was the ERROR in the EVENT LOG
pointing to when it BSOD?

 

[Confused]

You could try running Memtest86 and see if there are any errors, as bad RAM could be a cause for it crashing. Also, check your CD, as it may be scratched, which may cause files to copy across wrongly, which, again, may cause errors.

 

[Migroo]

The only functions that this server will be performing are those of a domain controller, some active directory functions (user accounts x 2) and host for 'my documents' for our two users.

Personally I dont think its confuguration related as It normally fails before Win 2k finishes loading AND when I reformat and install Win2k the same error appears (ie before any configuration).

The error is:
*** STOP: 0x000000BE (0xBFFF8418,0x07A2412,0xF741B62C,0x0000000B)
An attempt was made to write to read-only memory.
*** Address BFFF8418 base at BFFD8000, DateStamp 382a167c - ACPI.sys


Thanks so much for your reply

 

[Migroo]

Confused, thanks for the reply.

I doubt its the Ram as its happened in both machines I've tried (different ram, different ram type) but I'll have a look at the CD.

I'm going to give mem-test a try. Which version do I need to test a machine that has no (working) OS installed - the ISO image v3.0 (zip)?

 

[Migroo]

CD looks fine to me. There are a couple of extremely light scratches but theres nothing major. I'd class it as perfect...

 

[Confused]

Memtest will make a bootable floppy disk, so you'll need Pre-Compiled Memtest86 v3.0 installable from Windows and DOS . If you don't have a floppy connected, and want to boot from CD, then download the Memtest86 v3.0 ISO image (zip) and burn it to a CD

I have had problems with scratched CDs with regards to errors when installing an OS, but if you say the CD is perfect, then I don't know what else it might be other than a hardware problem.

I guess you've tried it with the bare essentials, BIOS set to Fail-Safe settings, only 1 stick of memory, 1 hdd, cdrom, and vid card?


Garry

 

[Migroo]

Thanks Garry I'll give Memtest a shot.

Thing is, this particular hardware configuration was working with Win NT server, Win XP Pro etc so nothing is 'broken' as it were. I have tried swapping PCI ports, theres only one stick of RAM in the machine (memtest will remove any doubt) and I've tried two different hard drives. Tried 3 different video cards too - one AGP and the others PCI.

Thanks for your help - I'll get back to you with Memtest results

 

[Migroo]

Memtest appears to be down

 

[Migroo]

I'm having trouble creating a bootable CD for memtest.. I've unzipped the file and created two boot CDs already, using NERO. On one I used no emulation and on the other I used HDD emulation. Is it worth trying Floppy emulation?

The BIOS of the target machine is set to boot from CD first..

 

[LiLithTecH]

I would doubt that is a MEMORY problem also.

As the issue seems to be caused by Power Management,
(ACPI.SYS) have you:

1. UPDATED the BIOS?
2. Tried to MANUALLY SELECT the correct HAL when installing the OS?

A lot of older motherboards have a problem with Win2k's
WMIACPI.SYS (the PNP device driver) and need to be updated.

 

[Migroo]

Thanks, LiLithTech for your response.

1) The Bios has been updated to version P16. There is a P17. Updates in that BIOS are as follows:
- Correct ACPI reporting of ComB when set to IRDA mode
- Added processor updates.

There doesnt seem to be anything significant there. We arent using Com B or anything Infra Red. Were using a CPU that was supported in the first BIOS release!

2) I've tried searching for HAL but I havent got very far.. How would I be able to manually select the correct HAL during installation?

Thanks for your time and patience.

Regards
Chris

 

[LiLithTecH]

To MANUALLY install the Correct HAL

press the F5 key during hardware detection setup
then SELECT

- ACPI Multiprocessor PC
- ACPI Uniprocessor PC
- Advanced Configuration and Power Interface (ACPI) PC*
- MPS Multiprocessor PC
- MPS Uniprocessor PC
- Standard PC
- Standard PC with C-Step i486
- Other


Note:(*) denotes choice for non-Compaq or SGI PC's

 

[redbeard1]

I've had brand new, out of the box, first time used cd's, fail on an install of both win2k and xp pro. Used a different disk for the win2k prob and it then installed. The xp disk, we sent back under warranty, and the new disk worked perfectly.

I've also had cdrom drives cause odd, repeatable errors that I blamed on memory, cpu's and various other stuff and when I switched drives, the os install worked.

 

[Migroo]

Thanks for elaborating LiLithTecH, I'll give that a try.

redbeard1 - I hope thats not a problem or I'll be sending Microsoft a bill for wasted time!!

 

[Migroo]

Right I've just tried to install the OS again, this time with the ACPI setting. I've just got another error - slightly different to last time.

*** STOP: 0x00000050 (0xFFFE3DCC, 0x00000000, 0xBFFAA00F, 0x00000000)
PAGE_FAULT_IN_NON_PAGED_AREA

*** Address BFFAA00F base at BFFA2000, DateStamp 38441c2a - setupdd.sys



The error occured once file install started. The machine was fine during HDD format (pre-file install)

 

[Ulfwald]

Build a DOS boot disk, run Fdisk and build a single partition format it with Fat32. then boot to CD and tell it to leave current file system in tact.

 

[Justen]

Have you tried "Standard PC" With LiLithTecH's instructions? Uniprocessor could work also.

 

[Ape]

I found the is MS site. Although this error I found deals with looking at files on a DVD drive while in Win2K. I noticed that you are installing from a DVD drive. This may not help but could be a start.

Linked for your pleasure

Ape Out.