Question Ryzen Master What a Disaster

[Rinzler]

Mistakenly installed this on my Win 7 PC running a Ryzen 7 2700 (non X)

After installation (which yielded no stop/warning message indicating it was not compatible) it began to launch and immediately blue screened, upon restart windows crashed and rebooted. After some fiddling I managed to remove ryzen Master and windows then began to boot up normally.

However my cpu jumps from 15X multiplier, all the way up to around 37. Voltage is very erratic bouncing wildly from 0.7 to 1.4

I updated and flashed the bios (gigabyte 450M board)

No effect, should I simply RMA the CPU?

Anything else to try?

 

[Markfw]

Sorry i hurt your feelings, you seem hell bent on simply assigning blame and have not added anything of any value. Again why post at all?

The VERY first word I posted in this thread is MISTAKENLY...is it not?

I made a mistake, I conceded that off the bat. And I also conceeded there is documentation stating compatibility.

However the average user new to Ryzen or not up on all things Hardware may not be aware and there needs to be a safeguard in place that costs AMD literally nothing.

Anyway all of that is not the focus. Please do not post unless you have a positive contribution.

See post 24, that came to mind, but I have tried to make a positive contribution. Emphasizing to READ THE MANUAL. You still have placed blame on AMD and thats wrong. When you admit you were wrong blaming them, and read the manual, then the contribution will be positive.

 

[Steltek]

For once, I'm going to try to be the voice of reason here. Mark this event, for this is probably the first time this century that I've attempted this!

I doubt the CPU is damaged and probably won't be unless you keep using it in this state.

Do you have either a valid system backup or access to a spare drive or SSD to use for a temporary installation?

If so, what I would do is to first reset the CMOS to defaults using the CMOS reset jumper or reset CMOS button (whichever your motherboard has). Then, I'd then create a Win10 flash drive installer and use it to temporarily install Win10 (make sure to leave the system unplugged from network access so you don't have to deal with updates or a Microsoft account).

Once it is up and running, install ONLY the most recent AMD chipset drivers. Reboot, then install Ryzen Master under Windows 10. Start Ryzen Master, make sure it works, then properly exit out of it.

Reboot the system. Then, uninstall the Ryzen Master software, followed by a shutdown. Reset the CMOS again using the jumpers or RESET CMOS button, and restart.

Hopefully, if this works, it will remove whatever traces of the install that is affecting your machine. If it doesn't and the system still exhibits problems, you are now running under a supported configuration. You could then email AMD support and ask if they can provide you with a way to manually uninstall whatever Ryzen Master did to your motherboard BIOS and hopefully they can help you.

If the problems go away, on the other hand, restore your backup. If you don't have a backup, do a clean Win7 install if you insist on continuing to use it. You would also have the option to attempt to try to upgrade your prior non-functional Win7 installation to Windows 10 by booting from a flash drive media installation. If you try to do this, though, I'd load that drive as a second drive and manually search out all AMD files and delete all AMD references from the registry using Regedit before attempting the upgrade.

Now, the voice of reason is leaving the building!

 

[Thunder 57]

Caveat Emptor

Also in your first post where you did admit you made a mistake, you ask about doing an RMA rather than asking/trying to run it on a supported OS.

 

[Rinzler]

See post 24, that came to mind, but I have tried to make a positive contribution. Emphasizing to READ THE MANUAL. You still have placed blame on AMD and thats wrong. When you admit you were wrong blaming them, and read the manual, then the contribution will be positive.

I wish reading the manual after the fact could reverse the issue, sadly not.

 

[Rinzler]

For once, I'm going to try to be the voice of reason here. Mark this event, for this is probably the first time this century that I've attempted this!

I doubt the CPU is damaged and probably won't be unless you keep using it in this state.

Do you have either a valid system backup or access to a spare drive or SSD to use for a temporary installation?

If so, what I would do is to first reset the CMOS to defaults using the CMOS reset jumper or reset CMOS button (whichever your motherboard has). Then, I'd then create a Win10 flash drive installer and use it to temporarily install Win10 (make sure to leave the system unplugged from network access so you don't have to deal with updates or a Microsoft account).

Once it is up and running, install ONLY the most recent AMD chipset drivers. Reboot, then install Ryzen Master under Windows 10. Start Ryzen Master, make sure it works, then properly exit out of it.

Reboot the system. Then, uninstall the Ryzen Master software, followed by a shutdown. Reset the CMOS again using the jumpers or RESET CMOS button, and restart.

Hopefully, if this works, it will remove whatever traces of the install that is affecting your machine. If it doesn't and the system still exhibits problems, you are now running under a supported configuration. You could then email AMD support and ask if they can provide you with a way to manually uninstall whatever Ryzen Master did to your motherboard BIOS and hopefully they can help you.

If the problems go away, on the other hand, restore your backup. If you don't have a backup, do a clean Win7 install if you insist on continuing to use it. You would also have the option to attempt to try to upgrade your prior non-functional Win7 installation to Windows 10 by booting from a flash drive media installation. If you try to do this, though, I'd load that drive as a second drive and manually search out all AMD files and delete all AMD references from the registry using Regedit before attempting the upgrade.

Now, the voice of reason is leaving the building!

Thank-you very much. I was thinking of doing something very similar to this.

Cheers,

 

[Thunder 57]

I wish reading the manual after the fact could reverse the issue, sadly not.

Experience is a hard teacher because she gives the test first, the lesson afterwards. – Vern Law

Ar least you learned something from this mistake though.

 

[Rinzler]

Caveat Emptor

Also in your first post where you did admit you made a mistake, you ask about doing an RMA rather than asking/trying to run it on a supported OS.

That's true, is asking about possibly doing an RMA a bad thing? I also asked for your suggestions.

As I mentioned I did know at that point my system was not compatible.

 

[Thunder 57]

That's true, is asking about possibly doing an RMA a bad thing? I also asked for your suggestions.

As I mentioned I did know at that point my system was not compatible.

Asking if an RMA is in order before trying suggestions is a bit premature. Hopefully you've got everything worked out now.

 

[Steltek]

Asking if an RMA is in order before trying suggestions is a bit premature. Hopefully you've got everything worked out now.

RMA on the CPU would not help you, as it is the motherboard that is causing the problem at this point. I'd only RMA the motherboard if the process I described above doesn't resolve the problem AND if AMD support can't help you with some way to manually remove whatever Ryzen Master did to the board.

If you RMA the board, you may get a used board of dubious quality back. Or, even worse, they stick a CPU in it, see that it boots up, and just send it back to you as being non-defective (or as "fixed"). The folks that work in the motherboard RMA departments of the major manufacturers often aren't the sharpest sticks in the forrest....

Eventually, a motherboard RMA might end up being the only thing you can do. But you are a long way away from needing to do that at this point.

 

[Rinzler]

RMA on the CPU would not help you, as it is the motherboard that is causing the problem at this point. I'd only RMA the motherboard if the process I described above doesn't resolve the problem AND if AMD support can't help you with some way to manually remove whatever Ryzen Master did to the board.

If you RMA the board, you may get a used board of dubious quality back. Or, even worse, they stick a CPU in it, see that it boots up, and just send it back to you as being non-defective (or as "fixed"). The folks that work in the motherboard RMA departments of the major manufacturers often aren't the sharpest sticks in the forrest....

Absolutely agree. Since my original post my focus has gone to the motherboard (or more specifically the bios)

If I had a spare factory EPROM I would desolder mine from the board and install it.

To add one more thing, I switched off the CPU boost function in the bios. This has calmed things down a lot.

Voltage is much more steady as well as frequency. Performance under load is totally stable but has dropped 8-10%

 

[Avalon]

Sorry i hurt your feelings, you seem hell bent on simply assigning blame and have not added anything of any value. Again why post at all?

The VERY first word I posted in this thread is MISTAKENLY...is it not?

I made a mistake, I conceded that off the bat. And I also conceeded there is documentation stating compatibility.

However the average user new to Ryzen or not up on all things Hardware may not be aware and there needs to be a safeguard in place that costs AMD literally nothing.

Anyway all of that is not the focus. Please do not post unless you have a positive contribution.

As mentioned by others previously, Ryzen Master is NOT for average users. Thus, your entire post is invalid.

 

[Steltek]

Absolutely agree. Since my original post my focus has gone to the motherboard (or more specifically the bios)

If I had a spare factory EPROM I would desolder mine from the board and install it.

Why? You have a path forward to try to resolve your problem, but you keep reaching for totally out of the box (and unnecessary, at this point) solutions like this to avoid doing it. If what we are suggesting here works, you will be left with a perfectly fine motherboard in normal condition. And if there is a problem, AMD support should be able to help you with it.

If you are worried about the Windows 10 upgrade, don't. It is still free, and it doesn't cost you anything except the time to do it. The simple fact of the matter is that it is the easiest Microsoft OS to install to date, and you WILL eventually have to upgrade unless you plan to never upgrade your software or purchasing another motherboard. And, in case you were not aware, installing Win10 does not preclude you from going back to Windows 7. You don't even have to activate Win10 if you don't want to, just use a temp install to try to fix this mess.

Finally, another thing. AMD processors don't work like Intel processors do. Voltage spikes occur as a consequence of their design -- the processor quickly boosts up a core to accomplish something then idles down that core as soon as possible. The 3000 series processors are even more advanced in doing this, so much so that upon release no software other than Ryzen Master could deal with them without giving false readings. As a result, it is entirely possible the fluctuations you are worrying about are normal activity that you just didn't have reason to notice before.

 

[DrMrLordX]

Thank you, it may not be fully uninstalled.

Likely so. Read below.

Thank-you very much. I was thinking of doing something very similar to this.

I want to add that reseting CMOS is not enough. Steps to take:

1). Install Win10
2). Install Ryzen Master
3). Make sure Ryzen Master has all settings at default
4). Uninstall Ryzen Master
5). Make sure CMOS is at default settings.
6). Flash/Reflash latest UEFI to motherboard
7). If desired, uninstall Win10 and go back to using Win7 (though I do not recommend using an unsupported OS; Win7 is EoL for consumer use).

Alternatively, just boot a Linux install and see if you get undesirable boost behavior from it. Win7's scheduler is probably not going to handle Ryzen correctly at all. And you probably don't have access to the Ryzen power plans either, which you really should want/need.

 

[LOUISSSSS]

Why do you guys care so much who I blame? If you are able to help then do so. If not and your only goal is to thread crap then why post at all?

You are engaging in the same thing you accuse me of. Whatever you may think what's done is done.

However my assertion that AMD didn't do near enough in regards to safeguarding it's users still stands.

this is why people don't help you. If you say sorry to AMD for blaming them i can get u some help. i know how to fix this

 

[Rinzler]

Why? You have a path forward to try to resolve your problem, but you keep reaching for totally out of the box (and unnecessary, at this point) solutions like this to avoid doing it. If what we are suggesting here works, you will be left with a perfectly fine motherboard in normal condition. And if there is a problem, AMD support should be able to help you with it.

If you are worried about the Windows 10 upgrade, don't. It is still free, and it doesn't cost you anything except the time to do it. The simple fact of the matter is that it is the easiest Microsoft OS to install to date, and you WILL eventually have to upgrade unless you plan to never upgrade your software or purchasing another motherboard. And, in case you were not aware, installing Win10 does not preclude you from going back to Windows 7. You don't even have to activate Win10 if you don't want to, just use a temp install to try to fix this mess.

Finally, another thing. AMD processors don't work like Intel processors do. Voltage spikes occur as a consequence of their design -- the processor quickly boosts up a core to accomplish something then idles down that core as soon as possible. The 3000 series processors are even more advanced in doing this, so much so that upon release no software other than Ryzen Master could deal with them without giving false readings. As a result, it is entirely possible the fluctuations you are worrying about are normal activity that you just didn't have reason to notice before.

Good info thanks,

 

[Rinzler]

Likely so. Read below.



I want to add that reseting CMOS is not enough. Steps to take:

1). Install Win10
2). Install Ryzen Master
3). Make sure Ryzen Master has all settings at default
4). Uninstall Ryzen Master
5). Make sure CMOS is at default settings.
6). Flash/Reflash latest UEFI to motherboard
7). If desired, uninstall Win10 and go back to using Win7 (though I do not recommend using an unsupported OS; Win7 is EoL for consumer use).

Alternatively, just boot a Linux install and see if you get undesirable boost behavior from it. Win7's scheduler is probably not going to handle Ryzen correctly at all. And you probably don't have access to the Ryzen power plans either, which you really should want/need.

Thanks, will be doing this on the weekend.

 

[chrisjames61]

Unfortunately after some research it appears the problem goes much much deeper, came across this post in another forum

"
I used ryzen master. 1 format later... It orbitally nuked everything, i couldn't even reach bios. that was the 1st night i owned 3600. All in all, i actually managed to reach a healthy state again, after countless cmos resets, restarts and a few mantears.

I am happy to report that ryzen master has no place in my Windows, like ever again. Bios tweaking is enough. If u fuck up, it just will return to a prior known state, with ryzen master, you will probably need to nuke your bios along with yourself."


Still not sure how to attack the situation, but it appears RM writes some information to the bios which is very difficult to get rid of. AMD should be ashamed.

Did you read what Mark said? It isn't compatible with Windows 7. How can you say "AMD should be ashamed" when the error is on you? Do you always blame others for your mistakes and then come to a forum and deflect the blame?

 

[chrisjames61]

Oh I'm sure AMD states in some documentation somewhere it's only Win 10 compatible, the question is how many users are actually going to read through a user guide beforehand. Allowing it to install on a Win 7 system without so much as a warning and then causing the PC to be inoperable is really inexcusable for AMD IMO. Im far from the only person that thinks so.

Anyway I will be installing Win10 on a old spare drive and then installing RM to see what happens.

Why would you think software developed for Ryzen and the AM4 platform would be compatible with Windows 7 when you know that Windows 7 isn't even compatible with the hardware you installed it on? That is like trying to put diesel fuel in a car with a gasoline motor and trying to blame Ford or Toyota.........

 

[chrisjames61]

Yes I need glasses. Did it ever cross your mind this didn't show for me? I never saw this message at any point.

Thanks for the valuable input sir.

Try looking next time. Or double check before you come on a forum and rant. You expect people to agree with you?

 

[chrisjames61]

Why do you guys care so much who I blame? If you are able to help then do so. If not and your only goal is to thread crap then why post at all?

You are engaging in the same thing you accuse me of. Whatever you may think what's done is done.

However my assertion that AMD didn't do near enough in regards to safeguarding it's users still stands.

You always need to be spoon fed? You actually use a computer? Mods: sorry for all the posts but this egregious lack of personal responsibility really is troubling.

 

[Iron Woode]

Why do you guys care so much who I blame? If you are able to help then do so. If not and your only goal is to thread crap then why post at all?

You are engaging in the same thing you accuse me of. Whatever you may think what's done is done.

However my assertion that AMD didn't do near enough in regards to safeguarding it's users still stands.

here is some help: do a repair install of win 7 and be done with it.

or install win10 fresh.

 

[DAPUNISHER]

Due to the thread title, I now have the almost 20 year old Star Wars Rap stuck in my head. Thanks, I guess?

Ryzen Master, What a disaster
It's Skywalker we're after
Yes, but if he could be turned to the dark side
He'd make a powerful ally
Another dark Jedi
He will join us or die!

It brings another ancient meme to mind -

The F is for freaking.

And to address the spurious aspersions being cast toward AMD:
“A common mistake that people make when trying to design something completely foolproof is to underestimate the ingenuity of complete fools.” ― Douglas Adams

 

[DrMrLordX]

here is some help: do a repair install of win 7 and be done with it.

or install win10 fresh.

That won't do the trick. Ryzen Master really can change settings in the UEFI on a semi-permanent basis. Since it failed so spectacularly, it's hard to tell exactly what it changed. There's a very specific way to extirpate those changes from the UEFI.

Installing Ryzen Master on an unsupported OS is a really, really bad idea.

 

[JoeRambo]

Due to the thread title, I now have the almost 20 year old Star Wars Rap stuck in my head. Thanks, I guess?

Ryzen Master, What a disaster
It's Skywalker we're after
Yes, but if he could be turned to the dark side
He'd make a powerful ally
Another dark Jedi
He will join us or die!

Best post ever LOL, I love that song, so damn catchy even 20 years after.

P.S. and Ryzen Master is a disaster even in supported configuration, i'd use it to check memory timings only, I has lightyear ahead of it.

 

[lightmanek]

I use RyzenMaster every day to switch betwen my OC profiles.
X399 + TR1920 and W10Pro.
No issues, but I grew up on hardware OC and I2C programming to achieve normally locked FSB clocks or hard modding CPU's, GPU's and motherboards, so what I do know ...