Thank you so much for all you have done for us! I have a RX5700 XT that I thought I had murdered in a freak accident and thanks to you, it's back up and running! I watched several of your videos and learned so much! I was easily able to determine that it was a blown fuse. I purchased a solder/hot air station and had at it with tremendous success! My technique needs improvement but I'm pretty proud of what I accomplished on my first endeavor! Thank you, thank you, thank you!
When you first started recording and I saw the Corsair LPX ram installed, I thought you were crazy. LPX ram is, for my money, the best, most compatible, stable (at stock XMP) ram on the market. Then you pulled out the Oloy, and I was like, "Nope. That makes sense." I now just use LPX ram in everything, matching the speed to the application, and I've never had a problem over the roughly dozen computers I've built in the last 3 years or so. NO, RGB doesn't need to be there on RAM. It doesn't make it faster.
I've got a 32GB kit of Corsair 3200MHz LPX RAM that is not compatible with my RoG Strix B450-F mobo at stock XMP profile. I have to manually set a lower speed to get it to work. 2666MHz is the fastest stable speed it can handle.
There's nothing particularly special about LPX over say a kit of crucial ballistics or something for example it's more about the quality of the chips on the modules oloy are probably sk hynix (as a guess) chips and actually shouldn't be too bad I mean I've had like patriot kits not work so ..... Brand don't mean a thing really as for compatibility it's really down to the motherboard manufacturers as much as the ram, u should try like lga 1366,2011 for annoying ram compatibility ddr4 is generally much less problematic so I'm not so sure about your overall hardcore faith on LPX. Corsair just get it about a lot and it's common easy to get well priced ram which is why you generally see it often doesn't automatically make it the best ram 😂
"this video is (...) about investigating the problem to learn more about it" - I hope it's not just me who does this all the time. I even kept a dying hard drive in my system for months to learn more about the process. it got very painful in the last weeks. (complete system freezes of up to 45 minutes, and it was a data-only drive. once it died, the system even refused to boot until I disconnected it.)
Thanks alot.... You are doing fantastic job ... Im from ruler area of pakistan have'nt so much resources like u but watching your vids now i could play good with first gen window systems(mostly came in scraps). Thanks again
Interesting to note.. newbies etc 'Chunwell introduced its OLOy brand in 2018. A company spokesperson told us that all of OLOy’s products are made in Taiwan, where Chunwell also manufactures modules for other brands.' Another great vid and stay safe ! 👀👍
I had a bad time for a while with my rig, It would have random strange hangs when the system would fail to respond with no information or diagnostics. Finally lost the random hangs with some of the sata drives in the system unplugged UREKA!! I monkeyed around with cables/ports/etc for waaaayyyy too long only to find out that the problem was the fancy sata cables I bought specifically for the build (can't remember the brand) with one end with a factory 90 to keep from stressing the connector at the hard drive. Bad connectivity for the sata controller was doing wonderful things in Windows.
I work on vintage computers (I've been at this a VERY long time). I can't believe I've been doing "The rain dance" and not recognizing that all I did was put a band-aid on it. Thanks for showing me I should be fixing the problem, not just finding the work around.
Well, sometimes there isn't a "real" fix, and the rain dance is all you've got. I think the moral of the story is that you should seek a more permanent solution if you can find one. But sometimes - and I imagine especially with vintage equipment - a rain dance might be the only solution you've got.
My God this is a life saver! I got a B450 Steel Legend a few days back cuz my B450 Tomahawk broke and i got the new board checked at the shop i got it from with my CPU EXCEPT for the RAM. So i get home assemble it and it would do this exact same thing i.e restart cycle forever. Im gonna take this board to the shop i got it from today and get the BIOS updated. Came across your channel recently definitely getting a sub and fuck Asrock for this stupid rain dance mess. Cheers
Bios 4.20 is more than 2 years newer than the 1.00 initial release bios the customer had on it up until now, no brainer. Also, there is no 30x ram multi in this board's bios, so upon setting XMP it selects the closest lower multi and compensates the missing amount with BCLK increase. I can see at the end that it shows "2864MHz" as CPU freq so it achieved XMP with 2933 multi and 102.3 BCLK. This is why it was set at that on 1.00 bios too from 100.0 BCLK.
I think having just the BIOS file on your USB stick is precautionary more than anything, because flashing can easily brick your board. It's just trying to minimize what could go wrong for something as sensitive as flashing a BIOS.
Adam, I just wanna share small story of me fixing my RAM not working issue. I had a 2x4GB ddr3 setup, but windows was saying "Total Physical Memory: 8GB" "Available Physical Memory: 4GB". I had messed about with the BIOS, reseated the RAM several times, tried other RAMS, check the bios (BIOS was saying 4GB), did mem checks with mdshed.exe, unplugged things that weren't needed, power cycled and drained - reset the cmos and all that, and i just couldn't figure out why windows could see that 8GB was installed, but the BIOS and windows were only seeing 4GB. Anyway I was thinking "it's gotta be a BIOS setting or something"...still, just to be sure i got a soft bristle paintbrush out, some 99% IPA with an eye dropper, and took Everything apart and cleaned all of the connection to the cpu, the cpu pins, it's socket, the ram sticks, ram slots, and even the bloody power connections. To my surprise, that fixed it. Available Physical Memory is now at 6GB. Coulda been because i reseated everything and fixed a loose connection i was unaware of...but while cleaning i did see dust build-up on one of the ram slots and i think it was probably the cleaning. just because everything else looked clean, and i didn't notice anything to be loose.
I'm currently running down an issue with a certain NVMe drive brand and certain motherboard combo. Finding others with the same issue posting online. Not bios related. Possible drive firmware related or motherboard itself related. Able to duplicate same failure with multiple same brand NVMe drives but otherwise works fine with every other brand NVMe drive I've tested.
I’m new to your channel. I’m very disappointed you didn’t break the ribbon cable on the ram, the customer will be disappointed too 😅😂🤣 NorthridgeFix send me here
Random speculation: The modules don't have a valid JEDEC profile in their SPD and need the XMP in order to work. And the pitfall with any "auto" setting in the BIOS is that you'd think it means something like "enable if present" or "enable if needed" or even "use some clever algorithm to figure it out". However, for a lot of motherboard manufacturers, it often means "use whatever settings causes the least amount of trouble for our support department". Which usually equates to "disabled". Could be what happened here. Someone thought: "XMP is (usually) for overclocking, and that can cause problems, so let's disable it by default (with the auto setting)." Once you manually set the speed, or actually enabled a specific XMP profile, the modules worked. It could be that that's all the update fixed and the BIOS now just actually looks at the XMP if it can't find a working JEDEC profile in the SPD. Just guessing though.
@@Rusty_Gold85 You have a point, although if I were the manufacturer's lawyer, I'd argue something like: "If a RAM module doesn't have a JEDEC profile, it violates the official specification, and thus isn't supported. It's like putting diesel in a petrol car. You wouldn't blame the manufacturer for that, would you?" IMHO, if this really was the issue, they'd both be at fault for not adhering to the robustness principle (basically: strictly keep to the standards yourself, but be lenient when others don't). RAM *should* always have a working, safe JEDEC profile. And mainboards *should* have a way to deal with it if it doesn't.
I've had this same exact issue on my last build, and wouldn't you know it was an asrock motherboard lol. They really need to add a disable xmp completely option.
At least there is update fixing the issue, alto you can't even boot to bios to apply the fix. I have friend who had to buy older CPU to apply the update because it turns out the CPU he bought for the build isn't supported out of the box. Sometimes you have to verify the compatibility for build you making.
The problem is that the Bios version he was using does not have a 3000Mhz option. When the Bios tried to initiate it didn't recognized the Memory XMP as valid and refuses to boot. Usually when that happens the Bios just loads the default DDR speed (DDR4 are usually 2133~2400) or the lowest speed available but it seems that this Bios version was also missing that feature. Updating the Bios added the missing 3000Mhz Memory speed allowing it to work normally. Well his board was on the first released Bios and they are the ones that usually have the most amount of problems. I had a similar problem when I was trying to OC a DDR3 Memory. It had 2 XMP profiles. The first one was a normal 1600Mhz but the second was a not so common 1666Mhz that my motherboard didn't support. When I tried to set it to the 1666Mhz profile the motherboard just ignored it and load the 1600Mhz one.
the memory is way newer than that mb and the mb didn't support it is my guess until you updated the bios ofc. before i buy a mb I make sure and look at all the memory that it will support
heh, not sure if you caught it (i had to go back and look) but it was on BIOS v1.0 before you flashed it 😂 (with at least 2 BIOS updates between that and 4.20 that improved RAM compatibility)
I want to point out that slots 2-4 are not generally the dual channel config with 2 stick. It depends on manufacturers. My asus z170 states clearly in the manual that dual channel with 2 sticks is slots 1 and 3. Same era boards from gigabyte and msi do use slots 2 and 4 but like i said it's not a general rule. The ram compatibility issue is not something new. It can happen with every board out there but most of the times is solvable with bios update. I remember purchasing patrior viper memory instead of corsair just because corsair had some incompatibility issues with my board and 3000 mhz corsair modules other buyers pointed out.
Oh my, this gives me flashbacks to my old Gigabyte board, t'was a Z97 one. It worked most of the time but randomly every few months it would just start throwing RAM for some unknown reason. I had 4x8GB sticks in it, and I'd have to remove all but one, do a handful of BIOS resets, then it'd finally come back (claiming DualBIOS had to be invoked) and I'd be able to slot my RAM back in like nothing ever happened despite XMP settings and such not having changed. Weirdly enough I gave the board to a friend of mine and moved to an Asus board (which was rock solid until I moved to Ryzen), he slotted a 4690k into it and the board never complained. Not even once. But it was just so odd I had to do the rain dance ritual every few months with that old board. (CPU and RAM weren't bad either, the CPU I used on that board is still being used to this day in a friend's PC and that thing's still working great, and the RAM went into the Asus board and again continued to work great for years.)
Old Asrock and even newer Asus boards are real sticky about the QVL list. Like, my old Crosshair IV did not at all like HyperX Fury Ram. That's a reputable Kit, but it was too new to be on the QVL list and it just would not post with it in there until I bumped the baseclock. It was intensely frustrating.
Same problem a few months back with asus 470- f wouldn't post with fury hyperx 3000 ram. One bios update later..job done. No guidance..just worked through that exact routine to gain the answer.
My 1st AMD board was an ASRock Taichi X470 Ultimate. Beautiful board but I found it to be unstable as hell and wouldn't run my 3200MHz G.Skill Ram at 3200 - best I could get was about 2933. This was on the latest firmware at the time. I ended up buying an Asus X570 board as the ASRock board has a bizarre issue when enabling Hyper-V and using a NVME boot drive - I got guaranteed hard lock ups after the 2nd reboot after enabling Hyper-V. Didn't happen with SATA SSD, only NVME. I need Hyper-V, so I had no choice but to get another board. Suffice to say, ASRock will not be high on my list of vendors to use again in the future.
I went back to intel because of a rain dance situation. I had a 3950X and 3070 and every time bios would reset I'd have to take my build apart to set pcie back to 3.0 which was a beast because I have a ITX sandwich style case. SM580 to be exact.
Is the CMOS battery good? The bios date before the update was 02/02/2021. After the bios update it is now 10/31/2019. Unless the date reset with the cmos battery out and that part was edited out between the bios flashing.
some people are just lazy lol, however my tower is literally on a table and in sight all the time. plus basically glass everywhere you can see any dirt buildup, I clean it at least twice a week lmao , then a full system teardown and deep clean probably twice a year, (maybe just once a year now since takes so long to get everything apart and back how I want it with a custom loop)
ASUS B450M-A unable to find BIOS file. formatted my USB to FAT32, double checked its being picked up in BIOS, done all the normal diagnostics such as resets and redownload, different format ETC, there is no instant flash option. when in flash mode, nothing related is picked up?
Hi pal, can I send in my laptop to you to fix? When the charger is connected it makes a ticking sound, but doesn’t turn on. The ticking sound only comes when the charger is connected. Will obviously pay thanks.
I'm not taking on mail-in repairs at the moment I'm afraid! Try a different charger on it if you can - if another charger doesn't fix it, I'm guessing short on DC input based on the ticking noise.
I've been watching your subscriber count grow since the 42K, should have started earlier really. Nevertheless, it has been an interesting, if not enjoyable, addition to your content and is fast approaching a well deserved 100K. The question is WILL THERE BE CAKE?
I have owned asrock b350, b450 and now x570 pro4 boards and have never been able to run my memory sticks at their max rated speeds. I had tridentz, rip Jaws v, corsair lpx. 3200 ran at 2933, 3600 runs stable at 3200. I tried xmp settings and ryzen dram Calc settings.
I had an MSI motherboard refuse to update bios until I deleted everything else off the flash drive. I tried. I'm comfortable updating a bios with any old flash drive, but this was a first for me! It was a b450 gaming pro carbon wifi. Similarly, I updated it for xmp issues!
Interesting - maybe there's some old exceptions like this that cultivated the "you must use a blank drive" mentality. A lot of superstition is based on old habits that were legit at the time.
Possibly. There are instances where older BIOSes can work better than the latest version. But it's hit or miss if the mobo will let you downgrade a BIOS, so you might end up having to remove the BIOS chip and reprogramming it. Entirely possible, but a bit outside the scope of this example. If the BIOS update hadn't fixed this, I'd probably have recommended the customer return the RAM and get a different kit, or failing that, sold/traded it with someone. If you're up against a brick wall with compatibility, best solution is to just change the incompatible component. Thankfully this example wasn't so serious.
@@Adamant_IT I've had to deal with this kind of issue in the past, but never been able to fully fix it (and in fact my current computer has this problem). Downgrading the BIOS has been always scary since manufacturers scream to never do that, so never gave that a try. Thanks for the insight, and, while at it, thanks for all the info you put out, been learning a great deal.
How truly weird, that the XMP Profile changes the BCLK to 102.4 MHz. You can see at the very end, after the XMP Profile was loaded, the CPU is now running at 2.864 GHz instead of 2.8.
After I purchased a crucial nvme ssd for my pc I got a no post after installing it sure enough a bios update resolved the compatibility issue and it works now. no raindance required btw. It’s an ASrock board 🤷♂️
I've encountered this issue many times, one solution I could share is by re-seating the processor, since this addresses the connection between the CPU and the RAM slot, before updating BIOS SW.
doesn't removing the CMOS and letting the capacitors drain accomplish the same thing though? i don't see how reseating the cpu would change anything - assuming that it's not damaged, it's got a clean connection to the socket, and done right.
@@Layarion Reseating the CPU (which, these days, houses your memory controllers as well) is to make sure you've got it in the socket correctly and that the pads/pins are clean. If you've got a system that keeps 'losing' RAM sticks, and they 'come back' after replacing thermal paste, or removing your cooler to swap sticks around, try reseating the CPU. It's amazing what one or two dodgy connections can do regarding missing RAM. (Had a twin-CPU workstation running triple-channel DDR3 that I had issues with. Reseating the CPUs after spending months 'rain dancing' the problem with swapping sticks around to get all 12GB of RAM to show up instead of 4, 6, or 8, well, it solved the problem long enough for the system to die of old age when the VRM's exploded. Ran with 6 sticks of 2GB each.)
@15:20 Not buying obscure RAM would have prevented the "rain dance" in the first place. :) @17:17 Yeah, as long as it is in the root directory and the files system is FAT32.
Brilliant video, So i have a question.. My system i updated the ram to 32Gb, the system worked fine and booted into windows, I then got occasional blue screens. Can an outdated bios cause blue screens? or is the blue screen just a windows error thing? After this I updated Bios first (quite out of date) and that actually made me sweat as I had no post after the update restarted but after removing the cmos battery for a few mins I did get a post. So that was strange, but then at the same time I decided to re install windows again. So far it seems to be good again, but I actually have no idea what may have fixed it.
BIOS update may well have fixed it. They often have tweaks to how memory is handled. I've also seen obscure gremlins in windows cause it. I had one in my home PC for months, changed out every component in the system, re-installed every driver - and then finally out of desperation, did a clean windows install and that did the job. Great that it's fixed, bummer that I never discovered the cause.
aaaah the pro 4's, i also have had many weird issues with these boards , had to do a build for a friend last month with a B450 Pro4 , and i always buy the same memory kit thats I know works and boosts perfectly on XMP with 2nd & 3th gen ryzen, now i had no post ... , tried another kit that wasn't on the list , posted and worked perfectly. i have started to step away from asrock for budget builds , i rather use the cheap gigabyte motherboards from now on
Mainly consistency. I could save time by using the reset jumper, but battery-out never fails me. It's worth noting that while I talk about people being superstitious over files on a flash drive, BIOS resetting with the battery is one of my superstitions. Both ways work though. Do what works for you!
@@Adamant_IT Fair! I appreciate the transparency, haha. I think on Windows 8/10, even "safe eject" for USB drives is quite unnecessary. I've never had issues improperly ejecting, but when I improperly eject and then plug into a Win7 PC, it's unable to read it. However, please note that while I've done enough testing to see a pattern with Win8/10 not caring, and Win7 being troublesome, I haven't done nearly enough testing to make any firm conclusions. After facing trouble with unsafely ejected drives on Windows 7, I have started to always safely eject again anyway. Just in case.
Yeah, I say it because I've been told I was wrong in the past, even with literal video evidence at hand. People get really superstitious about these things. Ultimately, they can do whatever works for them, but I speak from my personal experiences.
Exactly how I would have diagnosed this. I always do a BIOS update when doing a new build anyway. I would have been suspicious of an unknown brand of memory in the first place. Like your style young man, but try not to be quite so cavalier with the power downs and pulling ram and graphics cards ... (for the benefit of the newbies out there.)
I fix everything at home and I like your videos. But how you can survive without air compressor like Senco? When you get it you can't live without it anymore. You can't compare it to the air bottles so lets not mention it at all :)
Only for the sake of nice matching modules. I think Intel boards can run Flex mode, which gives dual channel even with mixed modules, but I've never tested it. So yes, probably could've been done. Most gaming rigs don't need more than 16GB, so not super important here.
@@Adamant_IT As long as each channel is configured the same way I've never had issues getting dual channel when some modules are mismatched. Most recently I set up an older AMD system with 5GB DDR2 (2x2GB and 2x512MB) and it ran fine in dual channel mode.
I've used ASRock's internet update in the past and it worked a treat - however, it's always worth looking up the updates page to check for update warnings, notes, etc, and by the time you've done that, you may as well download the file yourself while you're there.
3060 Ti to an i5 8400...? :P take it that's for that thing where you only use 4K so the CPU has less of a load on it than at the lower resolutions due to having fewer fps to render...?
I also have same issue.... I bought 2nd hand RAM which has single rank 4gb. Tried it on hp z200, no dice. Returned to seller, seller said it's working, the replacement ram is still single rank. No dice. Put that RAM on h61 motherboard, it ran.
I had the same issue when I got more RAM for my older laptop. I solved it by swapping with a friend who had dual-rank 4GB but could use the single-rank modules.
I had this problem when i bought my 6th gen intel with h110 motherboard. Bought a local brand zion 8gb module but wasnt working on it; but tried the ram in a friends house and it worked. So i took his 8 gb adata and it worked in my pc.