Question I used AMD program to overclock my ram, now dram LED is on & won’t go off. can this be undone ?

[Iploe]

Around 2 days ago, I was looking through an amd program called amd master and I turned up the speed of my cpu in it with to apply it restarted my pc after that I got no boot screen after the restart and the dram light was on. (Idk why the dram light would be on)

I tried resetting bios using the battery on the motherboard (taking it out for 30 seconds), the dram light was still on, I purchased new ram and put it in yet the light is still on. Idk if the program is doing anything causing it to happen but I get no boot screen and made sure the seating of the ram was good and it is clean.

My specs:
Asus rog strix b550-F (no Wi-Fi)
Ryzen 5 2600 (plans to upgrade)
Patriot Viper Steel 2x8gb 3200mhz(old kit)
Silicon power value gaming 2x16gb 3200mhz(new kit)
Radeon rx 6900xt oc edition
1000w power supply 80+ gold fully modular
western digital 500gb ssd
Seagate 1t hard drive


Edit: have tried new bios restring method sadly didn’t do anything, have reseated ram, cleaned out the slots, tested for faulty ram, bought new ram, tried with 1 stick, tried with both sticks, sadly none of this has changed anything

 

[Darkbreeze]

BIOS Hard Reset procedure

Power off the unit, switch the PSU off and unplug the PSU cord from either the wall or the power supply.

Remove the motherboard CMOS battery for about three to five minutes. In some cases it may be necessary to remove the graphics card to access the CMOS battery.

During that five minutes while the CMOS battery is out of the motherboard, press the power button on the case, continuously, for 15-30 seconds, in order to deplete any residual charge that might be present in the CMOS circuit. After the five minutes is up, reinstall the CMOS battery making sure to insert it with the correct side up just as it came out.

If you had to remove the graphics card you can now reinstall it, but remember to reconnect your power cables if there were any attached to it as well as your display cable.

Now, plug the power supply cable back in, switch the PSU back on and power up the system. It should display the POST screen and the options to enter CMOS/BIOS setup. Enter the bios setup program and reconfigure the boot settings for either the Windows boot manager or for legacy systems, the drive your OS is installed on if necessary.

Save settings and exit. If the system will POST and boot then you can move forward from there including going back into the bios and configuring any other custom settings you may need to configure such as Memory XMP, A-XMP or D.O.C.P profile settings, custom fan profile settings or other specific settings you may have previously had configured that were wiped out by resetting the CMOS.

In some cases it may be necessary when you go into the BIOS after a reset, to load the Optimal default or Default values and then save settings, to actually get the BIOS to fully reset and force recreation of the hardware tables.

 

[Iploe]

BIOS Hard Reset procedure

Power off the unit, switch the PSU off and unplug the PSU cord from either the wall or the power supply.

Remove the motherboard CMOS battery for about three to five minutes. In some cases it may be necessary to remove the graphics card to access the CMOS battery.

During that five minutes while the CMOS battery is out of the motherboard, press the power button on the case, continuously, for 15-30 seconds, in order to deplete any residual charge that might be present in the CMOS circuit. After the five minutes is up, reinstall the CMOS battery making sure to insert it with the correct side up just as it came out.

If you had to remove the graphics card you can now reinstall it, but remember to reconnect your power cables if there were any attached to it as well as your display cable.

Now, plug the power supply cable back in, switch the PSU back on and power up the system. It should display the POST screen and the options to enter CMOS/BIOS setup. Enter the bios setup program and reconfigure the boot settings for either the Windows boot manager or for legacy systems, the drive your OS is installed on if necessary.

Save settings and exit. If the system will POST and boot then you can move forward from there including going back into the bios and configuring any other custom settings you may need to configure such as Memory XMP, A-XMP or D.O.C.P profile settings, custom fan profile settings or other specific settings you may have previously had configured that were wiped out by resetting the CMOS.

In some cases it may be necessary when you go into the BIOS after a reset, to load the Optimal default or Default values and then save settings, to actually get the BIOS to fully reset and force recreation of the hardware tables.

Thank you for this information but sadly the situation hasn’t changed after trying this

 

[Darkbreeze]

What is the exact model of your "1000w power supply"?

Which exact slots are the memory installed in?

You might also try this.

Remove the graphics card, completely, from the motherboard. Then do a hard reset again of the BIOS. Then power on the system without the graphics card installed. There will of course not be any display. After about a minute or so, power off. Reinstall the graphics card and power back on to see if you now have a display at all. If that fails to work you might do the same procedure, and yes, I realize it's somewhat of a PITA, but this time remove the CPU, then power on, then off, then reinstall the CPU and power on.

The reason for both efforts is that in some cases the removal of specific hardware paired with an attempt to boot will force a reconfiguration of the hardware tables and bring everything back into play. It doesn't always work, but it's always worth a shot when all else has failed.

Also, if you have any non-essential USB devices plugged into the machine, remove them during the processes. Sometimes a glitchy USB device will cause the system to exhibit a variety of different types of issues.

 

[Zerk2012]

Thank you for this information but sadly the situation hasn’t changed after trying this

That shouldn't save settings to BIOS. Try to boot in safe mode.

 

[Unolocogringo]

That shouldn't save settings to BIOS. Try to boot in safe mode.

Ryzen Master does save settings to bios if you apply them.
It then reboots the system with the new bios settings and/or loads itself at boot.
Only use it for monitoring not changing bios/overclock settings.

 

[Darkbreeze]

That shouldn't save settings to BIOS. Try to boot in safe mode.

What are you even talking about? Of course a hard reset forces a refresh of the hardware tables. Usually on the same page with you, but no idea what you are trying to say here.

It LITERALLY doesn't matter whether Ryzen master does or does not save settings to the BIOS, IF you do a full reset of the BIOS, it should not matter what Ryzen master has set and certainly not after a full refresh of the BIOS settings, otherwise what would be the point of HAVING them?

Besides which, if you can't even get past (Or even SEE) the POST/ boot screen, it's pretty clear that Ryzen master can't be repeatedly responsible for the lack of ability to even get an onscreen display.

And, it's literally IMPOSSIBLE to boot to safe mode if you have nothing on the display from power on forward. How is it you think you can boot to safe mode if there is no display, at all?

 

[Blackink]

I NEVER rely on software to overclock my computers. Well....I did that once and learned my lesson.

That lesson was to NEVER use software to try and overclock your system and once it fails, do a full, clean install of the operating system.

 

[Darkbreeze]

I mean, that ALMOST goes without saying. But I'm glad I didn't have to be the one to say it, like I usually am. I agree 100% but that honestly has little relevance AFTER the fact.

 

[Darkbreeze]

Jesus dude. Do us all a favor and at least READ the thread before posting. Because, had you DONE that, you'd know, we've already been down that road and the right way, not the halfway.

 

[Zerk2012]

What are you even talking about? Of course a hard reset forces a refresh of the hardware tables. Usually on the same page with you, but no idea what you are trying to say here.

It LITERALLY doesn't matter whether Ryzen master does or does not save settings to the BIOS, IF you do a full reset of the BIOS, it should not matter what Ryzen master has set and certainly not after a full refresh of the BIOS settings, otherwise what would be the point of HAVING them?

Besides which, if you can't even get past (Or even SEE) the POST/ boot screen, it's pretty clear that Ryzen master can't be repeatedly responsible for the lack of ability to even get an onscreen display.

And, it's literally IMPOSSIBLE to boot to safe mode if you have nothing on the display from power on forward. How is it you think you can boot to safe mode if there is no display, at all?

Never used it from what the web says it has different settings to do different things some will even check for stability before the changes take affect.

Resetting the CMOS should of fixed it but seem not to. Might be a good time to update the BIOS since the board should have a flash button.

If he even ever responds back.

 

[Blackink]

I mean, that ALMOST goes without saying. But I'm glad I didn't have to be the one to say it, like I usually am. I agree 100% but that honestly has little relevance AFTER the fact.

I only mention it so if others are searching for fixes to the OP's problem, maybe they will take the advice and NOT overclock your computer using software.

And even if they do use the software and they have problems, like the OP did, maybe the full OS install will fix his problem.

I ran into the same problem with Asus software many years ago. Though I'd use it to overclock my system......yup, as soon as I did and after the first restart-Blue screen of death.

I think I tried everything including what the OP did to fix the problem but nothing worked.
I ended up doing a full re-installation of my OS.

 

[Blackink]

Jesus dude. Do us all a favor and at least READ the thread before posting. Because, had you DONE that, you'd know, we've already been down that road and the right way, not the halfway.

Huh?!?

 

[USAFRet]

Huh?!?

Not you...a post that is now deleted.
Was totally clueless.

 

[Darkbreeze]

Yeah, you should just do a cleanup on the thread and delete my post that was in reference to that clueless post, and any other posts related to it after the fact.

 

[Karadjgne]

There's essentially 2 bios on a motherboard. There's the hard-coded bios, that's the part that requires a physically downloaded vendor upgrade, which has All the factory settings. Then there's CMOS, which is user changed settings plus others which override factory settings with its memorized settings.

When you push the button, CMOS applies any settings from it's memory and that bios starts the post process, and eventually leads to OS startup. The issue with CMOS is that it's memorized settings and users only see specific settings, not every setting. So software OC can and does change multiple hidden settings. A CMOS reset only changes what's out of range, so many of those hidden settings do not get reverted back to stock as they are considered acceptable. Vcore is a prime example, if a software OC changed vcore from 1.325v to 1.400v, a cmos reset may not revert that back as the cpu is good at 1.4v.

That requires a full bios reset and a hard boot, as a soft boot calls up cmos settings and reapplies it's memorized settings. This is why manual bios manipulated OC is superior to software OC, the only changes are ones done by the user, so are easily reverted, software OC changes things you never knew existed and as soon as the software loads, continually tries the change those settings for the next cmos boot.

 

[drea.drechsler]

I NEVER rely on software to overclock my computers. Well....I did that once and learned my lesson.

That lesson was to NEVER use software to try and overclock your system and once it fails, do a full, clean install of the operating system.

Normally, I'd agree with you. But this is Ryzenmaster, made by AMD expressly for this purpose, and it has been quite reliable through all generations of Ryzen CPU's and AM4 motherboards. And further, resetting CMOS is about as hard of a system-level reset as can be done to return motherboard and CPU to full-default settings for booting up.

I think there's something else going on. They're trying to get to the bottom of it...hopefully they will for OP's sake.

 

[Blackink]

Normally, I'd agree with you. But this is Ryzenmaster, made by AMD expressly for this purpose, and it has been quite reliable through all generations of Ryzen CPU's and AM4 motherboards. And further, resetting CMOS is about as hard of a system-level reset as can be done to return motherboard and CPU to full-default settings for booting up.

I think there's something else going on. They're trying to get to the bottom of it...hopefully they will for OP's sake.

I saw the Asus Mobo and thought the OP had used Asus' OC software.

 

[Karadjgne]

And further, resetting CMOS is about as hard of a system-level reset as can be done to return motherboard and CPU to full-default settings for booting up.

That's just the point. There's multiple hidden settings, ones a user cannot access in most bios. The bios for the bottom of the line motherboards is the same bios as for the top of the line, the difference being the levels of user accessibility vs hidden settings. Many of those settings are not on/off switches with a single choice for default, they are ranges. For example, vcore default might be a range from 1.28v-1.44v default, so if you reset cmos from a vcore of 1.43v and expect it to go to 1.32v, very often it doesn't because the attached number is inside default range.

The problem with software OC is that there are so many simultaneous changes that a lot of hidden settings get changed as a result and resetting CMOS doesn't always change them back. Cmos is the soft coded changes that get applied from user or software saves, BIOS is the hard coded originals on the other half of the same chipset.

The only way to work around cmos is to first erase it so that it cannot apply anything, then reset Bios defaults, then boot to safe mode to stop any autostart or windows task programming and then remove the software from startup/registry completely.

This is Asus, Amd, Msi, Intel, you name it, they do not want users getting rid of their software. Getting away from Armory Crate is a freakin nightmare, it's got no kill button and half a dozen ways to activate it, or make it seem that it needs to be activated. Ryzen Master isn't much different with too many things left on Auto.

The worst part about Ryzen Master is its settings are windows task level, so if you do the Auto OC, it gets written to registry as such, you clean the bios, the cmos, delete the software, and as soon as you do a regular boot, the Ryzen Master settings bypass the UEA, get applied from registry and get re-stored as such into cmos as you shutdown. Now you have no idea why your settings are changed, why you see OC values, because there's nothing you can see to make any changes because the software doesn't exist.

 

[drea.drechsler]

....

The worst part about Ryzen Master is its settings are windows task level, so if you do the Auto OC, it gets written to registry as such, you clean the bios, the cmos, delete the software, and as soon as you do a regular boot, the Ryzen Master settings bypass the UEA, get applied from registry and get re-stored as such into cmos as you shutdown. Now you have no idea why your settings are changed, why you see OC values, because there's nothing you can see to make any changes because the software doesn't exist.

Hmmm...so you're suggesting Ryzenmaster applies overclock settings at every bootup? First I've heard of that, and definitely not my experience when I did use it. But it's been a while...and I've also not used it in conjunction with Radeon Settings, which does overclock GPU at every startup (unless it experiences a crash of somesort).

I definitely agree about the motherboard mfr' utilities...asus' in particular since I went through the nightmare multiple times killing it's services that download and re-install the spam/scamware via BIOS code.

Still, this doesn't seem to be what OP's problem is...at least as I read it in the first post. It seems to me he can't even get through POST so Windows never has a chance to load anything.

What you say about resetting CMOS is interesting...but very confusing. I'm not sure I understand what you're saying, exactly. Resetting CMOS shorts out the battery (voltage) from a volatile storage area for all settings (or should, sometimes also pulling the battery for a while helps I don't know why, possibly because it can take a while to bleed off the charge and holding the pins shorted that long is tiring to do reliably). When the voltage is removed and charge bleeds off the settings have no alternative but to return to a zero-state condition, a natural default setting. This is true even for the plethora of settings a user can't touch in BIOS but Ryzenmaster might. So...I'm confused. Are you saying there is a non-volatile storage area for settings that do not get a reset? like, perhaps, the BIOS chip itself? then you're saying Ryzenmaster alters BIOS code in-situ? That would be novel.

 

[Karadjgne]

Hmmm...so you're suggesting Ryzenmaster applies overclock settings at every bootup?

Yep, I made that mistake. Forgot to undo the RM OC before removing the program.

No, what I'm saying is that RM stores it's settings in the registry, windows task level, so even clearing the cmos does nothing because as soon as you boot up a regular boot, the pc passes post the first time and starts to load the OS, the RM settings get applied, which if they are bad then kills the OS loading by causing errors. Which are now in cmos again. And pc won't now boot. Viscios cycle.

Clearing cmos, then entering bios and resetting to factory defaults gives the pc a last known good boot point, breaking the cycle, then safe mode to remove the registry entries or other software autostarts as a loading issue.

 

[kerberos_20]

to reset CMOS on your mainboard, you need to reset it through clear cmos jumper (or screw driver), not with battery, that battery just holds date and time and bios passwords, it is not used for storing bios settings

https://imgur.com/ifBxFuk

View: https://imgur.com/ifBxFuk

 

[Darkbreeze]

to reset CMOS on your mainboard, you need to reset it through clear cmos jumper (or screw driver), not with battery, that battery just holds date and time and bios passwords, it is not used for storing bios settings

https://imgur.com/ifBxFuk

View: https://imgur.com/ifBxFuk

We've had this conversation before, and I'm not going down that rabbit hole again, but suffice to say that we have to agree to disagree on this factoid. The mere fact that for EVERY motherboard I've ever worked with, ALL of the settings have in every case been reset to the default values anytime I've removed the CMOS battery refutes the idea that it only holds relevance for the date, time and passwords, regardless of the board model. So, while you are certainly entitled to your opinion on this, it's not shared by most of us.

 

[drea.drechsler]

to reset CMOS on your mainboard, you need to reset it through clear cmos jumper (or screw driver), not with battery, that battery just holds date and time and bios passwords, it is not used for storing bios settings

https://imgur.com/ifBxFuk

View: https://imgur.com/ifBxFuk

Well, then every AM3 and AM4 motherboard I've owned seems to be faulty because when I remove the battery it resets all BIOS settings to defaults exactly as though I had reset CMOS, or ticked the "reset to optimized defaults" setting in BIOS screen. I honestly can't remember how my socket 7 motherboard behaved but I do recall the settings of interest in that era (CPU voltage and frequency, ATA, parallel and serial port IRQ and address settings mainly) were made by jumpers.

I honestly do not care about RTC or actions that reset it since the system clock is set and maintained by Windows so I don't pay attention to it.

It has been curious to me and unexpected that with AM4 removing the battery turned out to be useful for clearing faulty memory settings in particular to allow an apparently bricked system to restart. I never needed that for any of the AM3+ boards I've worked with. Perhaps something with DDR4 memory or Ryzen MMU's is sensitive to the RTC in a way that needs the battery pulled to reset it.

 

[kerberos_20]

mine mainboard doesnt trigger nvram reset when pulling out battery, just date/time gets reseted, while clr cmos jumper triggers only nvram reset while date/time remains unchanged

well, easy to solve this, just refer to your mainboard manual on how to reset your cmos