T7610 stuck in boot loop when trying to install any OS

Question

Hi, I recently got a T7610 workstation, but I can't seem to install any OS onto it. I have tried Windows 10 from CD, Windows 7 from CD, ESXi from USB media, ESXi from CD, and Citrix Xenserver from USB media. In each of these, what happens roughly is: the boot media is detected and the installer begins to load up the installer starts loading files as soon as the installer is done loading files, the workstation reboots and the whole process starts again (sometimes there is a flicker of what the next screen would look like, but usually not) for example, in ESXi the reboot occurs right after the message 'Relocating modules and starting up the kernel' I have tried/ruled out: Run the hardware diagnostic check accessible from the BIOS - no issues Bought a brand new internal HDD and verified that it is connected, detected by the BIOS and LSI Controller - BUT this problem occurs even before I get to the stage of needing the HDD. Ie even if I take out the HDD and run the windows installer, I get into a boot loop long before I actually get to the point in the installation where I need to select the HDD Updated the BIOS to latest version My specs are: 2x xeon e5-2690v2 128gb ddr3 ram nvidia gtx 1060 Ti Please help? I have no idea what to do next!

CharlesIsWorking · Answer

What a beautiful power-house!

Can you run a Linux live cd?

Are your bios settings set to defaults? Are you trying to use UEFI? Windows 10 would like UEFI, but Windows 7 won't sometimes.

Are there any raid configurations on your raid controller? I would get rid of any of those.

grysql · Answer

My T7610 has Bios A16, the latest A17 will not install.

Try this: In the BIOS (F2), set it to Legacy for SATA hard drives, SATA Operation set to AHCI, Secure BOOT should be turned off. I used a Win 10 USB stick and installed the OS, after that everything worked as it should.

BrickRoad · Answer

Aha - I found the problem - turns out it was just one bad stick of RAM. Feel pretty dumb about an error this mundane, but I had assumed the 'health check' in the BIOS would have caught it - I guess not! Thanks to everyone who helped :)

grysql · Answer

Thanks for telling us the solution, good info.

Precision Fixed Workstations

Was this post helpful?