Playing with RAM only way to boot !

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   I encounter the exact same problem.
I can't boot anymore.
It worked well for 4 months, i didn't changed anything (except maybe the bios update, i can't remember, i had nearly 20 days uptime) and it refuses to boot.

DrDebug sometimes shows a lot of numbers. Sometimes it doesn't show anything...

I just sent an email to Asrock.

I wondered if it came from another component. I tried another power supply, another gpu but still the same behaviour. I can't test another cpu/mobo/ram unfortunately.

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
lord Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 23 Apr 2018 Status: Offline Points: 1	Post Options Post Reply Quote lord Report Post Thanks(0) Quote Reply Topic: Playing with RAM only way to boot ! Posted: 23 Apr 2018 at 10:44pm
	I encounter the exact same problem. I can't boot anymore. It worked well for 4 months, i didn't changed anything (except maybe the bios update, i can't remember, i had nearly 20 days uptime) and it refuses to boot. DrDebug sometimes shows a lot of numbers. Sometimes it doesn't show anything... I just sent an email to Asrock. I wondered if it came from another component. I tried another power supply, another gpu but still the same behaviour. I can't test another cpu/mobo/ram unfortunately.

BC_ATM Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 14 Apr 2018 Status: Offline Points: 6	Post Options Post Reply Quote BC_ATM Report Post Thanks(0) Quote Reply Posted: 15 Apr 2018 at 1:04am
	I unplugged my only device, the samsung hard drive and nothing changed I also removed the graphics card and tested, same. I could of by now booted it past this by pulling out the RAM a number of times but now it's not even going that far after the BIOS update ^^

kerberos_20 Members Profile Send Private Message Find Members Posts Add to Buddy List Senior Member Joined: 06 Dec 2017 Location: czech republic Status: Offline Points: 3687	Post Options Post Reply Quote kerberos_20 Report Post Thanks(0) Quote Reply Posted: 14 Apr 2018 at 11:56pm
	C0 is BDS execution (Boot Device Selection) try to unplug all of your SATA/m.2 devices , then clear CMOS and see if this helps then keep pluging one sata/m.2 device at a time, to see where it fails
	userbenchmark

BC_ATM Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 14 Apr 2018 Status: Offline Points: 6	Post Options Post Reply Quote BC_ATM Report Post Thanks(0) Quote Reply Posted: 14 Apr 2018 at 10:11pm
	X399 TAICHI sTR4 1950X Threadripper Corsair 750w Geforce GT 710 Samsung 250gb SSD G.SKILL 16GB KIT DDR4 3200MHz CL14 Flare X for AMD Windows 7 Hi people, I finished my first build and straight away had issues booting :( The board would light up blue but nothing further. I played around with the RAM and magically it booted. Now, everytime I shut down and try to boot it's a major issue getting it going Pulling the RAM out of slot 8 is the only trick to get it booted, sometimes the fans just spin, debug runs and it powers off but most times it will boot up after a few attempts. This doesn't happen with any of the other slots and works with any 1 of the 4 RAM sticks. I see this problem is common with no definitive solution. I ended up updating my BIOS to 2.0 and now it won't even boot up - fans spin and debug stops at C0 and then powers off. It is likely that during the BIOS flash that if the computer tried to reboot, it couldn't and failed? I'm sure I put the RAM in the wrong way at the start, could this have caused any damage? Any ideas? Thanks