Boot failure with Win2K3 Server standard edition

[CougTek]

Is ntbtlog the equivalent of bootlog for WinXP? It's been a while since I debugged using the boot log.

Anyway, the computer will always bluecreen in standard mode. It boots fine in safe mode. User can't tell me what he did to screw the installation. I have the iso CD for Win2K3 Advanced Server and for Small Business Server, but not the one for the standard edition, so Windows repair is out of question.

The system is an old Compaq Proliant ML-370. It is a dual P3 933MHz with 2.5GB RAM and a 3-drives RAID 5 array. Yes, it's a Frankenstein box, but Im not the one who suggested they build it that way.

The ntbtlog stops after the following line :

Loaded driver \systemroot\System32\Drivers\Fastfat.sys

I have no idea what fastfat.sys is a driver for.

They POS server has to be up and running by tomorrow morning, eastern time (or for Monday morning in Australia).

 

[Mercutio]

I can get you a proper ISO if you wait about 8 hours for me to put it someplace.
Do you need a standard or volume license?

 

[Bozo]

A quote from IT Pro"
At this point, I was becoming aggravated. I knew that I had seen the error message before, but I couldn't recall exactly where. I determined that the next step was to check out the hardware and make sure that all the cables were attached to the drives. They were. To be on the safe side, I swapped in a new drive cable, but doing so changed nothing. In desperation, I started checking all the hardware components in the system. To my chagrin, I heard a "click" when I pushed down on the second DIMM in the system. Like Archimedes, I was about to shout "Eureka" at my discovery but instead uttered a more Homer Simpson-like "Doh!" I had located the problem, but in doing so recalled that bad memory can cause the OS to generate the corrupt FastFAT.sys error message."

Memory problem?

Or: http://support.microsoft.com/kb/289205
Install the latest service pack

Bozo :joker:

 

[sechs]

FYI, FastFAT is the FAT filesystem driver.

Also realise that the problem is sometimes with the driver that was supposed to load after the last one that you see.

 

[CougTek]

It was the standard license, but the customer decided to try to re-install Windows 2K3 himself. I told him it could me the memory too, but he's no hardware guy so he won't check this. The problem is now on his hands and not mine.

Thanks for your help.