• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Little build questions

Page 3 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
Try one stick at a time first. Start with slot 1. If that doesn't work, work your way across. The list is of sticks Asrock have test and guarantee to work, not necessarily the only ones that will work.
 
I would double-check your PSU connections, and make sure that your modular cables are oriented correctly (the PSU end versus the mobo or drive end). I know that you had some questions about this with the 24-pin ATX cable.
 
The RAM slots aren't clear - there are 4, the manual only describes them as two pairs, slot 1 and 3 one pair, slot 2 and 4 the other (and they aren't numbered 1-4).
 
The RAM slots aren't clear - there are 4, the manual only describes them as two pairs, slot 1 and 3 one pair, slot 2 and 4 the other (and they aren't numbered 1-4).

They are sequentially numbered, reading from left to right (normal orientation is with the manufacturer name/mobo model text right side up as opposed to upside down or sideways). So Slot #1 is the first one on the left, and slot 4 is the one at the end.
 
I'll look at that... but again... one stick works despite the manual showing them as pairs of slots 1/3 and 2/4? And the ram issue could prevent any video signal?
 
Well. I took out 3 stick of RAM leaving only the one closest to the heatsink, which I think is slot 4, still a code 55.

Then I took that out and put a different stick in slot one. For the first time a new code - stayed on 63 a while then plugged the monitor in (still no signal), looked back and it was d7.
 
63 isn't good - chip error - but it cleared.

d7 seems ok - keyboard and mouse not recognized, which is fine they aren't plugged in. So now the issue is no monitor signal and then I do isolation on the RAM.
 
Some progress - video is now working to boot to a BIOS screen - press F2 or delete for setup, or F11 for boot menu.

But with a keyboard plugged in - no keys have any effect.
 
Good news, the keyboard started working. Now I can go all around the BIOS seup menu and find I have more questions.

It seems to recognize the hard drive - but since I'd normally format the hard drive from Windows, but have a USB to install Windows to that hard drive, we have a chicken and egg problem.

I have to assume the USB knows how to deal with this and can try that.

Then that leads to - what else do I need to setup? What about 'BIOS updates'? Does this MB have any built-in wi-fi and if so how to set it up, if not do I need to move the ethernet cable from the old PC to this one for connectivity (figuring out how to connect ti hardwired is a whole other issue - I have a second cable but need to get a switch device I guess).

If I find one of the RAM sticks is bad... bleh, guess I'd have to see about buying another of the same type, hear mixing them isn't good.
 
I added a second stick of RAM to slot 3 (since it says 1 and 3 are a pair). It went back to error 55 no RAM.

Then I removed the second stick, and put it in slot 1 instead of the one I knew worked - and it booted fine. So either slot 3 is bad or not the right place for a second stick.
 
It's exciting it's ready to install Windows 10 - but until I get the RAM issue figured out I'm going to wait. If I install it now, I think it might bind the key to this MB serial number, and if the MB has a defect and has to be replaced it's a hassle to get Windows changed to a new MB. I guess I should get it connected to the internet also.
 
Last edited:
If you want an OS for trouble-shooting purposes, just use Linux (Mint is a popular distro), off of a USB stick. (Or you could install it too.)

That way you can test the mobo, without using up a Windows' license.
 
Back
Top