Jump to content

Motherboard/GPU Bricked?

Hi everyone,

 

I'm a new PC builder, and so recently most of the parts had been delivered and I started working on it. These are the parts I used:

 

CPU: Ryzen 5 3600

Motherboard: Asrock B450M PRO4 Micro-ATX

Memory: G.Skill Ripjaws V 16 GB (2x8) DDR4-3600

Storage: Crucial P1 1TB M.2 NVME SSD

GPU: MSI GeForce GTX 1660 SUPER VENTUS XS OC

Power Supply: EVGA BQ 600W 80+ Bronze Certified Semi-Modular

 

I started building once I got all the parts, except for the NVME because it arrived reaaaally late and I just wanted to start building.

So, I built it. It was fine at first- it could go into BIOS. I noticed that the ram was running really slow (like 2133 instead of 3600, if my memory serves me right) and so switched to the XMP profile.

Then I saved the changes and exited. But since I had no OS on my computer yet it I guess shut down/restarted and just brought me back to BIOS. It was at this point I thought that I should do a BIOS update because I heard that my motherboard and CPU weren't compatible without one. However, I came to the realization yesterday thanks to one of my friends that I actually didn't need to do one because the motherboard was compatible for the CPU out-the-box.

 

It literally said on the box "3000 Ready", and somehow I didn't see it; however, I didn't know this two days ago when I actually built it. And so then I got the latest BIOS of my motherboard onto a flash drive and plugged it in to the front USB ports. However, it didn't detect the drive no matter which port I put it in, so what I did after was shut the computer down, took out the flash drive and put it in again (This time in the USB 3.0 port, if it matters), and then powered the computer on again. This is where the problem occurs: when I turned on the computer, the monitor turned black and green and shortly afterwards I see "no display detected" on my screen (I was using a DisplayPort, GPU to Monitor.) It never said it was going through the BIOS update- maybe it actually was in the background but who knows.

 

Over these past 2 days, I've been trying everything I could scrounge on the Internet to try and fix it, but nothing worked:

  • I've powered down and unplugged countless times already.
  • Removed the CMOS battery for a few minutes, 4 hours, and overnight, placing it back in and testing it.
  • I've powered it on without the CMOS battery.
  • Shorting the CLRCMOS pin (I didn't have a jumper cap so I used a screwdriver- no clue if it actually worked) with the CMOS battery in and out for 15 seconds.
  • Re-seated the ram, and having one stick at a time
  • Tried turning it on using different display cables, like DisplayPort with GPU in and DVI cable with GPU in and out.

I should mention that yesterday morning when I first powered on the computer, using my DVI cable as the display cable, it gave me a screen that was flashing RGB in the background and a blue box in the middle (see below.)

 

screen.jpg.3a0547a3ccaaad4aadb013faf5b10a6a.jpg

 

However, after that I have not been able to see this screen. Posting this here is my last effort of trying to find a solution before I go through with RMA'ing either my motherboard or my GPU. Even though, I don't even know which I should be sending back. So far I've come to two possible reasons for why something got bricked:

  • Changing the ram to its XMP profile: I'm not entirely sure if this is the reason because after I changed it to the XMP profile, I saved and exited. Since I didn't have any storage devices yet- so no OS- it just I guess went back to BIOS again, and it was all fine. But I have no clue, and details matter.
  • When I tried flashing the latest BIOS: This is the reason that I'm pretty sure that got my motherboard or GPU got bricked.

 

I've already did forms for both the GPU and motherboard. I had one done for the GPU first because I thought that it was the problem, but I came to realize that it also might have been the motherboard, so then I did one for it yesterday. I'm still under warranty, just around 20 days left of it.

 

Any help you guys can give me is appreciated!

 

Link to comment
Share on other sites

Link to post
Share on other sites

if i understand correctly, jayzstwocents just did a video about something similar

just reapply xmp

Link to comment
Share on other sites

Link to post
Share on other sites

6 minutes ago, chen57 said:

if i understand correctly, jayzstwocents just did a video about something similar

just reapply xmp

Yeah but wasn't that CPU related for him? It was an issue with the 9900KS not being fed enough voltage on the default settings. That wouldn't apply here.

Link to comment
Share on other sites

Link to post
Share on other sites

10 minutes ago, chen57 said:

if i understand correctly, jayzstwocents just did a video about something similar

just reapply xmp

Hey, thanks for your reply. Sorry lol but I don't really know what that means. Do you mean something like just setting the ram to the XMP profile again? I can't really do anything because no matter how many times I try I can't get past the "no display".

Link to comment
Share on other sites

Link to post
Share on other sites

5 minutes ago, chen57 said:

true but did you try it ?

Yeah Jay could at least get into his bios, it was loading the OS that was giving him problems. So I don't think that related here.

 

I've never heard of applying an XMP profile bricking anything. Sure it may not boot, but then you could just return it to default settings. That's not what's happened here. My best guess is you made a mistake somewhere when trying to update the bios. If a computer loses power or something like that when it's writing to the bios, the motherboard is bricked. And since you can't even get into bios that seems more likely here.

Link to comment
Share on other sites

Link to post
Share on other sites

2 minutes ago, TheBahrbarian said:

Yeah Jay could at least get into his bios, it was loading the OS that was giving him problems. So I don't think that related here.

 

I've never heard of applying an XMP profile bricking anything. Sure it may not boot, but then you could just return it to default settings. That's not what's happened here. My best guess is you made a mistake somewhere when trying to update the bios. If a computer loses power or something like that when it's writing to the bios, the motherboard is bricked. And since you can't even get into bios that seems more likely here.

I see. The computer never lost power, or at least I didn't notice that it did. I don't know if there are anymore solutions for this- should I just RMA the mobo?

Link to comment
Share on other sites

Link to post
Share on other sites

1 minute ago, bubbliorno said:

I see. The computer never lost power, or at least I didn't notice that it did. I don't know if there are anymore solutions for this- should I just RMA the mobo?

I mean I can't be sure exactly how you went about updating the bios, so not sure what could've gone wrong. My best guess from your description above is that maybe when you plugged it in one of the first times it was actually updating or something and you didn't realize it, then you power cycled the computer. Honestly no clue, but it sounds like a bios issue to me. I'd contact Asrock support and see what they can do for you, just explain that the board won't work and you're not sure why. If they offer an RMA take it.

Link to comment
Share on other sites

Link to post
Share on other sites

12 minutes ago, TheBahrbarian said:

I mean I can't be sure exactly how you went about updating the bios, so not sure what could've gone wrong. My best guess from your description above is that maybe when you plugged it in one of the first times it was actually updating or something and you didn't realize it, then you power cycled the computer. Honestly no clue, but it sounds like a bios issue to me. I'd contact Asrock support and see what they can do for you, just explain that the board won't work and you're not sure why. If they offer an RMA take it.

Alrighty, thank you!

Link to comment
Share on other sites

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×