Windows Server 2003 freezing on boot

[goreblast]

Funny one this; just want to see if you'll think it might be same cause as me. (I'm at work so cannot actually try this until later).

System:

Gigabyte 8VM800M-RZ s478 motherboard
Pentium 4 Prescott 3.0
Two PC2700 512MB RAM (running async at this speed)
Boot drive array RAID 3 on XFX Revo 3-port SATA raid card (3 Samsung 40gb)
Storage RAID 5 array with redundant drive on Promise SX4000 w/ 256 RAM (4 WD 200gb)
Tagan 480W PSU
D-Link Giga LAN card
On-board graphics
Windows Server 2003 Standard 5 Cal all updates
No extra software install - used as a file server only

A week or so ago it wouldnt restart at all - started to boot and wouldnt even display the POST screen, although stayed powered on. Thought it might be a sub standard PSU (Had a 500W Jeantech at the time). I removed the PSU and put in a spare Tagan 480W I had. All seemed well.

Now 50-75% of the time it freezes during the Windows Server 2003 screen for no apparant reason. Both Raid arrays are fully functional. It even freezes during a Safe Mode boot.

It didnt exhibit this behaviour before I install the D-Link card (on board LAN is one 10/100 and I have a gigabit switch with rest of home computers all with onboard 10/100/1000 LAN). Also could it the RAM?

 

[AndyC]

What happens when the dlink is removed, it could be getting into a mess with the networking, try re-enabling the on board network port if this works configure the dlink with a static IP address then disable the on-board.

This is odd because it won't explain the non-boot.

 

[Sp00n]

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

"To View the Safe Mode Boot Log File
To troubleshoot startup issues, view the boot log file, Ntbtlog.txt, and then make a note of the drivers and services that did not load when you started your computer in Safe mode.

This log file is located in the %SystemRoot% folder (by default, this is the Windows folder). The log file lists devices and services that load (and do not load) when you start the computer in Safe mode. You can use a text editor such as Notepad to open and view the log file.

Use the list of drivers and services that did not load at startup to help identify the possible cause of the startup problem.

Note Some startup problems may occur early in the startup process. In this scenario, Windows may not save the boot log file to the hard disk."

Might be an idea if you can get in to safe mode as it'll narrow down some of the hardware which may be causing an error.