Thanks Jord, pretty sure anybody posting to this thread aware of all the tools. Being overclockers and enthusiasts and all. Lots of programs to monitor Ryzen temps actually since they all have been brought up to date on the architecture. Most popular is HwInfo64 whose developer has been very active in the Ryzen/AMD community to pick out bugs and develop solutions around them. I use SIV to monitor all my voltages, temps and powers. Use it to control my AIO and GPU fans too.

The Ryzen Master utility has little use for me but I downloaded it from your link and probably will investigate just to see what it is and does. Thanks for the link.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

Since overclocking the Ryzen and installing Lunatics I have seen a jump in my RAC for HOTH of over 4000RAC a day.

Cant complain about that.

I will keep an eye on it but so far so good.

---

"I know I am insignificant...Just look how many stars their are...!"

Before I introduced the new 1070's to Numbskull, so was totally dependent on the CPU change from FX to Ryzen, the daily RAC increased by 12K/day.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

Before I introduced the new 1070's to Numbskull, so was totally dependent on the CPU change from FX to Ryzen, the daily RAC increased by 12K/day.

Its amazing that a simple processor change can have such a drastic influence. Goes to show the improvements in processing capabilities of current gen CPU's.

Can you imagine what NASA would of been capable of back in the 60's if they had of had this king of processing power. We would be on Mars by now.... ;)

---

"I know I am insignificant...Just look how many stars their are...!"

I notice a difference in APR between Pipsqueek and Keith-Windows7. Even though both systems are configured almost identically, Pipsqueek usually does more work even with a 200 Mhz core clock deficit compared to Keith-Windows7 which is my daily driver and has all the programs I normally use. Pipsqueek is just a cruncher with very minimal additional programs loaded. There is noticeable difference in responsiveness between the two systems. The amount of extra overhead with background services running on Keith-Windows7 does impact its APR compared to Pipsqueek.

. . Hi Keith,

. . Have you heard anything more about the BIOS updates for ASUS MoBos? Is it safe to buy one yet without having to do an after market BIOS upgrade? Or for that matter anything from M$ about a patch for the thread steering issue?

. . I should be monitoring it myself but I get distracted :)

. . June is getting close and I want to make it happen .... the old Pentium D is showing it's age. :( {I am getting more frequent lockups} :(

. . Oh, BTW do you remember in which thread there was that recent discussion about recovering ghosted WUs? I have created a few :(. Never upgrade a crunching app in the same timeframe as updating Linux and the subsequent need to re-install video drivers. Somehow the cuda 80 libraries went walkabout and it trashed the whole cache (only 100 tasks). :(

Stephen

??

. . Hi Keith,

. . Have you heard anything more about the BIOS updates for ASUS MoBos? Is it safe to buy one yet without having to do an after market BIOS upgrade? Or for that matter anything from M$ about a patch for the thread steering issue?

. . I should be monitoring it myself but I get distracted :)

. . June is getting close and I want to make it happen .... the old Pentium D is showing it's age. :( {I am getting more frequent lockups} :(

. . Oh, BTW do you remember in which thread there was that recent discussion about recovering ghosted WUs? I have created a few :(. Never upgrade a crunching app in the same timeframe as updating Linux and the subsequent need to re-install video drivers. Somehow the cuda 80 libraries went walkabout and it trashed the whole cache (only 100 tasks). :(

Stephen

??

Hi Stephen, any ASUS motherboard in the retail supply chain should by now have the most recent stable BIOS. It will still have to do a BIOS upgrade later this month when AMD releases the 1.0.0.5 or .6 AGESA firmware. That will improve the memory compatibility greatly supposedly. The BIOS update is very simple really. Just revert back to F5 BIOS defaults before flashing the latest BIOS through the EZ Update feature in the BIOS Tools section. Whatever you do, DON'T EVER update the BIOS within Windows. You just place the new BIOS in a FAT32 formatted USB stick and plug it in to the motherboard and use the tool facility to flash the BIOS. EASY PEASY. I've done it through 0505,0511,0515 and 0604 for my Prime X370 motherboard with no issues at all.

There is no thread steering issue with M$. That was an early "red herring" that was caused by an outdated and not updated utility that misdiagnosed Ryzen's NUMA architecture. There is no thread scheduling issue with any OS. There is a new Ryzen Balanced Power Plan that is included with the latest AMD motherboard drivers that gets around Windows silly Balanced Power Plan which parks all cores except for one. I just use the High Performance power plan since my machines are crunching full time anyway and there is no need to downclock them except for turning the systems off. The new Ryzen power plan allows the same downclocking and downvolting for lower power states just like the stock Windows Balanced plan. Most of the popular utilities have been updated to understand and interpret Ryzen correctly by now. There is no compatibility problem with Rzyen.

The ghost recovery process is well documented in the Panic Mode 105 thread which is now closed. Basically, just make sure you have room in your allotment for the recovered tasks, set NNT to get there and when you have some tasks to report, interrupt the regular 305 second scheduling server connection just as it happens and appears in the Event log and toggle allow network activity off with a quick mouse click. Then shut down BOINC fully and wait a minute or so and restart BOINC, re-enable task allowing and network activity and the previous server connection that was interrupted completes and gets 20 of your ghosted tasks. Repeat the process as many times as necessary to clear the ghosts.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

Well after a couple of days running the processor at 3.6Ghz and doing the final tweaks thanks to the advice of various members in particular Keith Myers, I have now bumped up the processor to 3.7Ghz.

We will see what happens and I will continue to play with the machine to see what we can get out of it.

---

"I know I am insignificant...Just look how many stars their are...!"

. . Hi Keith,

. . That is all good news to me. My timeframe is mid to late June so hopefully by then they may be mobos with that latest update already in them and my Windows 10 should install fully Ok. I only expect to run stock clocks/RAM speed (though if there is a price drop I may upgrade to slightly faster RAM like 2666). I just have to decide on a suitable case/PSU and I am off.

. . That recovery method seems much simpler than the one I have been using, if I can just get the timing right to make it work. Have you used it yet ?

. . Well I will give it a go and see if I can get them ghosties out of the system and my wingmen's q's.

. . Thanks

Stephen

:)

Well after a couple of days running the processor at 3.6Ghz and doing the final tweaks thanks to the advice of various members in particular Keith Myers, I have now bumped up the processor to 3.7Ghz.

We will see what happens and I will continue to play with the machine to see what we can get out of it.

Hi LooneyTunes, I quickly looked at your valids and everything looks good. I did see one thing that is a possible area for improvement. You are using the SSE3 CPU app that you either selected on purpose or let the Lunatics installer choose by default. You might be able to nudge a bit more performance out the 1700X by choosing the AVX app in the Lunatics installer. On the BLC CPU tasks, I find the AVX CPU app about 50% faster than the SSE3 app. Not so large an improvement in the Arecibo CPU tasks. I guess the difference being how the tasks are coded internally or something that responds especially well to the CPU's AVX instruction set or path through the registers. With the ongoing reduction in Arecibo datasets and eventual ending, it might make sense to optimize for BLC tasks since that will be predominately what the project is going to send us in the future.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

. . That recovery method seems much simpler than the one I have been using, if I can just get the timing right to make it work. Have you used it yet ?

. . Well I will give it a go and see if I can get them ghosties out of the system and my wingmen's q's.

. . Thanks

Stephen

:)

Yes, I have been using it exclusively quite a lot lately. I have been making ghosts every time I use Laurent/Petri CPU2GPU script for moving CPU tasks to GPU on outage Tuesday's. I am trying to troubleshoot why this is happening with Laurent. It is not that hard to execute the procedure. Just have the Event log open with the Projects tab selected and watch for the next scheduler connection countdown to zero. When it gets down to 10 seconds to go, select the Activity menu in the Manager and hover your cursor over the "Suspend Network Activity" option. Then as soon as you see "SETI@home | Sending scheduler request: To report completed tasks." print in the log, tap your left mouse button quickly and you should see "Suspending network activity - user request" print in the log. Then just shut down BOINC and wait a minute or so before starting it back up. Upon BOINC restart, Allow tasks again and allow network activity and you should get your first slug of 20 ghosted tasks resent to your computer.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

Well after a couple of days running the processor at 3.6Ghz and doing the final tweaks thanks to the advice of various members in particular Keith Myers, I have now bumped up the processor to 3.7Ghz.

We will see what happens and I will continue to play with the machine to see what we can get out of it.

Well it always depends on whether you "won the silicon lottery" if your particular chip responds well to overclocking. Since the 1700X is supposed to automatically boost at least two cores to 3.8 Ghz when it decides the power budget will allow it, I decided to try and see if I could get my 1700X at least to 3.8 Ghz on all cores all the time. Since I have the ASUS Prime X370 Pro motherboard I don't have a B-Clock generator and can only use the CPU multiplier to get an overclock for the CPU. I found I could easily get all cores to 3.8 Ghz with just the 38X multiplier with everything on Auto in the BIOS. I since have tried to get a little more out of it but have been unsuccessful in getting 3.9 Ghz stable with my normal SETI loading. I have found that I can get 3.85 Ghz stable with just a 0.01875 V offset added to stock CPU voltage with everything else on Auto. My chip seems to have a overclock wall right at 3.85 Ghz, you have to start adding a silly amount of voltage to get any higher overclock stable and that comes with increased cooling requirements which leads to higher temps and fan noise. I decided it isn't worth it. And I have no interest in trying to achieve the highest overclock for benchmarking that other people focus on. I just want to run my equipment.

I have also been able to achieve a significant improvement in performance simply because I can get my memory to work at 3200 Mhz with CL14 latency. That helps the CPU perform faster and helps it crunch faster too.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

Well after a couple of days running the processor at 3.6Ghz and doing the final tweaks thanks to the advice of various members in particular Keith Myers, I have now bumped up the processor to 3.7Ghz.

We will see what happens and I will continue to play with the machine to see what we can get out of it.

Hi LooneyTunes, I quickly looked at your valids and everything looks good. I did see one thing that is a possible area for improvement. You are using the SSE3 CPU app that you either selected on purpose or let the Lunatics installer choose by default. You might be able to nudge a bit more performance out the 1700X by choosing the AVX app in the Lunatics installer. On the BLC CPU tasks, I find the AVX CPU app about 50% faster than the SSE3 app. Not so large an improvement in the Arecibo CPU tasks. I guess the difference being how the tasks are coded internally or something that responds especially well to the CPU's AVX instruction set or path through the registers. With the ongoing reduction in Arecibo datasets and eventual ending, it might make sense to optimize for BLC tasks since that will be predominately what the project is going to send us in the future.

I have changed the Lunatics Installer over to use AVX for CPU as suggested. Lets see how that goes.

---

"I know I am insignificant...Just look how many stars their are...!"

Did some more playing around with the BIOS.

Currently have the processor running at 3.75Ghz. Tried 3.80 but was getting random reboots. Mind you, it is still using standard voltages on the CPU so some playing with that may help.

I have also managed to get the HyperX Ram to run at 2666 stable with stock settings. I found a good article at http://www.overclockers.com/kingston-hyperx-fury-ddr4-2400mhz-32gb-memory-kit-review/ which gave me some clues as to the rams potential.

Thats all I can play with today as I am off to start renovating the bathroom at the investment property.... YaY....

---

"I know I am insignificant...Just look how many stars their are...!"

Did some more playing around with the BIOS.

Currently have the processor running at 3.75Ghz. Tried 3.80 but was getting random reboots. Mind you, it is still using standard voltages on the CPU so some playing with that may help.

I have also managed to get the HyperX Ram to run at 2666 stable with stock settings. I found a good article at http://www.overclockers.com/kingston-hyperx-fury-ddr4-2400mhz-32gb-memory-kit-review/ which gave me some clues as to the rams potential.

Thats all I can play with today as I am off to start renovating the bathroom at the investment property.... YaY....

I had to use some additional CPU voltage +offset to get 3.8 Ghz stable at full load. I added +18 mV to the stock 1.35V VID for the 38X multiplier. Under load, the CPU VDD droops down to as low as 1.306V but more typically 1.312V. That is with LLC on Auto. That automatically boosted VDDSoC voltage from stock 0.883V to 1.10V for the SoC IMC controller. I also found out that the Prime DOESN'T set VTTDDR properly from 1.35V DIMMS. It leaves that voltage at stock 0.600V for 1.2V DIMMS. I had to manually input the 1/2 VDimm voltage of VTTDDR to 0.675V for my 1.35V DIMMS. That got me stable at either 3.8 or 3.85 Ghz.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

Did some more playing around with the BIOS.

Currently have the processor running at 3.75Ghz. Tried 3.80 but was getting random reboots. Mind you, it is still using standard voltages on the CPU so some playing with that may help.

I have also managed to get the HyperX Ram to run at 2666 stable with stock settings. I found a good article at http://www.overclockers.com/kingston-hyperx-fury-ddr4-2400mhz-32gb-memory-kit-review/ which gave me some clues as to the rams potential.

Thats all I can play with today as I am off to start renovating the bathroom at the investment property.... YaY....

If you haven't done so, so far, download the latest HwInfo64 utility HwInfo64 for its ability to display the true operating voltages going onto the CPU and SoC. Look for the voltage values labelled with SVI2. Those voltages are coming directly off the VRM's that supply the CPU and SoC and are already displaying the delivered true voltages after voltage droop. A lot more accurate than what is set in the BIOS settings for voltages or the voltages displayed by the onboard motherboard SIO chip. The voltages from the SIO chip are what is displayed by outdated programs that haven't been updated for Ryzen.

After looking at the "real" voltages from the SVI2 registers, you begin to realize that the voltages actually being used by Ryzen are really quite sensible. That fact makes the reported "alarming" voltages first written about in reviews on the initial platform release pretty ridiculous now.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)