New build, new issues

Undy

Undy

Undy

Associate
Joined
13 Jan 2023
Posts
6
Location
UK
Not a first time builder here, but on my first build from scratch in a very long time and I've got two issues I'm currently fighting with.

I've got a Gigabyte B660 DS3H AX mobo and 2x8GB Vulcan Z T-Force 3200MHz RAM. On first power on after building, with the memory in the A2 and B2 slots, I got a flashing DRAM LED and no display output. After a bit of playing around I've determined that I can start up to bios if I have either stick of RAM in the B2 slot only, but if I put either of them into the A2 slot I get the DRAM error (I didn't try to much with the A1/B1 slots but it seemed A1 was dead too). Fairly sure this is something I'll need to get on to Overclockers support about to get an RMA on the mobo, unless anyone has any other ideas?

I pulled across a couple of SSDs from my old rig, one of which has the Win 10 install, and having decided to limp on with one stick of RAM, I managed to get into the bios and enable legacy boot mode, but when I attempt to boot from the SSD with the OS install I just get the flashing cursor in the top left of the screen and nothing else. If I use a Win 10 boot USB I can use the command prompt through that to explore the file system on the SSD and I can see all the Windows folders and files etc, but I can't seem to boot from the drive at all. Does anyone have any suggestions on how to fix that one?

Appreciate any help anyone can offer on either point as this is really sucking the fun out of building a new rig now.
 
mickyflinn said:
Which cpu is it ?

Check the cpu socket for bent pins and an overtightened cpu cooler can cause dram errors.
Click to expand...
It's a i5-12400 - no sign of bent pins in the socket. I tried backing off the CPU cooler screws but made no difference to the DRAM error - still works with either stick in the B2 slot but dies when anything is put in A2.

defoerate said:
I think that Win10 has drivers set up for the old machine so it's normal to be unable to boot. Better off doing a clean install then grabbing the files you need off that drive.

Also try update the BIOS to tackle the RAM problem. I had a quick look the latest version is F21.

I think this is your motherboard support section
www.gigabyte.com

B660 DS3H AX DDR4 (rev. 1.0/1.1) Support | Motherboard - GIGABYTE Global

Lasting Quality from GIGABYTE.GIGABYTE Ultra Durable™ motherboards bring together a unique blend of features and technologies that offer users the absolute ...
www.gigabyte.com www.gigabyte.com
Click to expand...
That makes sense about the clean install - Both my SSDs have data which I don't really have a way to move off them at the moment as I don't have another working rig to load them up on. Is it possible to create a partition on a disc that already contains data and install the OS on the new partition without wiping the data that's there?

My bios is on version F2. I formatted a USB stick to FAT32 and extracted the latest version files to it, but the USB doesn't show up in Q-Flash (I can see it in the boot order though). The FAT partitions of the SSDs are there, but not the USB.
 
mickyflinn said:
Click to expand...
Yeah I've been trying to follow that guide but the UI in my version of Q-Flash is different. I got as far as selecting the .F21 file, clicked run, the system rebooted back into Q-Flash but says "Can't Read File". The only option was to OK out of the dialogue box, and now the USB doesn't show in the drop down for drives to flash from again. I have no idea why it sometimes shows and sometimes doesn't.
 
Last edited:
I tried a different angle. Used a Linux boot disk to get in and back up the files from one of my SSDs then did a clean Win 11 install (which was an odyssey in itself), then used @BIOS to update to version F21. The bios update was successful, but anything in my A2 RAM slot still leads to the DRAM error and prevents the PC from starting up. Is there anything else likely to be causing the issue or is it fairly certainly a defective motherboard? Just want to be sure I've checked everything before returning the board to Overclockers for them to tell me there's nothing wrong with it!
 
defoerate said:
It doesn't sound good. Try Enable Memory Fast Boot Mode and set XMP disabled.

Memory Boot Mode-> Fast Boot (pg 14)

Extreme Memory Profile (X.M.P.) -> Disabled (pg 13).
Click to expand...
I've tried every combination of XMP and fast boot enabled / disabled but no dice. Can't see how it's anything other than a defective mobo. I've sent a message to Overclockers so I'll see what they say on Monday. Wee bit frustrating but I've worked in manufacturing long enough to know these things happen.
 
You must log in or register to reply here.
Back
Top Bottom