BSOD/reboot when installing Windows Server 2008/2012, Ubuntu Server?

Question

Iron

Hello!
Faced a problem.
Put together a new server.
When installing any OS, it either turns off, or, in the case of Windows 2012, after copying the files, a BSOD appears (I don’t have time to see the error code, it goes into reboot), and the server goes into reboot.
When installing Ubuntu Server, after selecting the language, the server simply shuts down. It also turns off when installing Win Server 2008 R2, after copying the files, again.
When the server is turned on, the speaker beeps briefly 6 times: Keyboard controller initialization error, wiki suggests.
When I turned off the keyboard, I heard how it squeaked and 4 times and 5. (Failure of the system timer and Problems with the processor, respectively).
At the same time, in bios everything is determined perfectly !!! All nodes are visible, all characteristics correspond to the specifications. The settings seem to be correct.
Server MB configuration
: Intel® Server Board S2400GP2
CPU: Intel® Xeon® Processor E5-2407
(10M Cache, 2.20 GHz, 6.40 GT/s Intel® QPI)
RAM: Kingston KVR16R11D4/16 16Gb
HDD: 1TB, 3.5", 7200rpm /min, 64MB, SATA III, Seagate Barracuda 7200.14, ST1000DM003
What I tried to do to solve the problem:
1) Reset BIOS settings, reconfigure
2) Tried to start without HDD
3) Tried to change the RAM slot, but if the first slot is empty, it beeps three times , for a long time, does not see the memory.So it was not possible to fully try
4) I tried different distributions, live images
5) I tried to turn on without keyboard and mouse
Tell me what the problem is most likely with, and if it's in the settings, tell me what to look for!
Thank you!

Answer 1

1. what about the power supply, can the server not have enough oops?
2. Is the latest BIOS version on the motherboard?
3. Try to remove the BIOS battery for 10 minutes, completely turn off the power to the machine, check all the loops and click and, for example, swap the memory strips.
4. Did you run memtest with livsd by car?
5. If this continues, give it to the service, let them diagnose the motherboard with memory and processor. Usually service providers can suggest something sensible.
Is the server generally branded or self-assembly?

Answer 2

Have you tried disabling power management during installation?
Have you looked at the RAM timings?