I.nfraR.ed

Wait, 2033 is much faster than 2100? Is that the slow down some people talk about? I guess you don't want to disclose your timings, but if you run latest beta of ZenTimings, could you spot some differences in non user-configurable timings? I don't have 5000 series to check myself. Is it strap related? For example, is it the same if you use the lower strap and clock the bclk up or is it just some internal strap that makes things waaay slacker?

Possibly yes, I don't recommend it. It was a suicide and I was aware of potential loss of hardware. Especially on non-ceramic Athlons. Just for reference - I don't have it noted, but if I have to assume, knowing how they scale on cold, probably 2600-2700 valid with ~2V.

I benched it before it was cool :p

The "official" 1.2.1 is available on the site and has Vermeer support fixed.

New beta with Vermeer support somewhat fixed. You might have some readings missing though. Don't have a CPU to properly debug. ZenTimings v1.2.1.65 beta2 https://drive.google.com/file/d/1dC12pYM2qyY8D9aoEd192NtAeVh7m9uJ/view?usp=sharing

New v1.2.0 is up on the official site: ZenTimings I have verified it to work on my system, but there aren't much reports from users, so if there's some serious issue will have to hotfix it. There are now 2 versions of the app, but they both include the major and important fixes, since they share the same common code. The difference is in the UI. People were asking about dark theme, which is not really possible with the old Windows Forms the app was based on. Or at least not in a satisfactory way. Not all controls can be styled or at least not easily. So, the UI was completely rewritten to use Windows Presentation Foundation framework, which allows easier theming. This comes at a cost though. In order to support the themes, I had to up the minimum required version of .NET framework from 4.0 to 4.5, which means no XP support (not that most people need it). It's also a little more memory consuming, but I have tried to minimize RAM usage as much as possible. Due to that change, I have decided to still support the legacy version (it's basically the same old UI, but with updated core functions, so nothing is missing, except dark mode). I will still support it in the future, unless some breaking change is needed in the common module. It's a major release, thus the version is now 1.2.0. You can read the changelog on the site. I don't have a Zen3 system, but there's some preliminary support for Vermeer and Genesis (based more on assumptions). Will definitely need user input once it gets available in stores. It would be quite some time until I get one. I would need a new motherboard for that, unless Crosshair VI Hero actually gets some beta/unofficial bios. v1.1.0 hit more than 5400 downloads! Thank you all. Not that it benefits me in any way, but it's encouraging at least. Last, but not least, I will make sure to find time and finally update the OP with some info. CPUs tested: 1800X, 1600AF, 3000G, 240GE, 3900X on Crosshair VI Hero running latest bios 7803. Note: This is a direct copy from the overclock.net forums post.

On the back of the board, top corner, closest to I/O side.

Using Sempron 150 vs 145 is cheating ? Great job! Is that with a changed dll?

Nothing new, unfortunately. Have to quit my job if I want to support all the apps in a timely manner Which I might do, since I can't stand it anymore. I wanted to release the next ZenTimings version before switching to ZenStates again.

I have created a Discord channel/server/whatever: https://discord.gg/8cfR3UZ If you have problems with it, let me know.

Testers are always welcome. Maybe I should create a Discord channel or something like that.

ZenTimings v1.1.0 is "officially" released. Probably ton of bugs, but will try to address them in the next versions, especially when more debug reports are available. The simple site (a copy of ZenStates with changed main color :D) is also live: https://zentimings.protonrom.com/ For debug reports, please use the tool in Tools -> Debug and attach the generated text file or copy the text directly.

Yes, that's possible and would like to add CLI. The linux have CLI and GUI. Currently very busy with ZenTimings, but after that I will get back to ZenStates with the new thing I've discovered recently.

Beta version of ZenStates with advanced Memory Controller config included. Should work on all Zen2-based CPUs and Renoir (Desktop АМ4). Readings are not realtime, but just a snapshot on app open. Don't have plans to add realtime reading, maybe a simple separate monitor app with just voltages, clocks and power. Still haven't found how to read BCLK, ACPI always reports 100. Download from GoogleDrive: https://drive.google.com/file/d/1YfHep9mX2POJhRrdEM_0WQklMDd0amZb/view?usp=sharing. 10/08/2020: Re-uploaded with a fix for first read after reboot.

New version of ZenTimings, with more items, Renoir and future CPUs support. https://github.com/irusanov/ZenTimings/releases Still working on the new ZenStates version. A new Linux version based on GTK3 coming too.

According to my spreadsheet, it should be Athlon XP 2000+ AXDC2000DUT3C AQZFA 0343UPMW Thorton

Not bad, although not sure how this translates to a DDR3 board.

None of them is really a pot :D. The one over the memory is just the coldplate of Dominator water block with a styrofoam container attached with putty. The block on top is a solid glass souvenir to add some weight, because there's no mounting.

Yes, it does. A guy from the discord channel tested it some time ago. There seems to be a difference in the chipset registers and values that work on the award boards don't work on the AMI.

I have gained maybe 1MHz if anything at all going from air to chiller on the NB. For validation only, might help with stability when running 32M, but I haven't tried that. In my experience it doesn't scale well with cold. As for the other question - no, never had such a bad board. All my nforce2 400 ultra boards did at least 250MHz with mods. Maybe some bad capacitors?

Keep in mind that Asus have the polarity markings for capacitors the reverse of e.g. Abit and DFI. So in fact you need to rotate the capacitor. You might know it, but just in case you've overlooked. The filled half of the circle is the positive side. Doh, is it DHL? I've had similar, when all of my contact info is replaced with something like "GDPR!!!!", so the local office can't even call me, because my mobile number is missing. Luckily I had a tracking and called the office for assistance, otherwise it would be returned back to the sender. Yeah, I've tried that long time ago and apart from being slower it did not gave me a higher FSB. I've always wanted to try 1618 or 1510 for all multipliers and see what will happen.

I'm not sure it does anything after the DRAM is initialized. 790FX boards have it as a setting i the bios. In K8 bioses it's called "DRAM Drivers Weak Mode". Normal is the recommended setting. Some quotes from documents:

I've tried this and some other combinations, but it always leads to a freeze. I don't know if there are other prerequisites.

Massive!

APIC off is a little more stable at high FSB and voltages for me, especially with high CPU voltage. I'm running APIC off and SSD connected to the integrated SATA on my NF7 with the images I've posted on your forum. Haven't noticed a negative effect by turning APIC off, but SATA SSD might make a difference, haven't tested. I'm currently testing the modded NF7 bios (NF7_[ED]_A6, I believe) from @digitalbath and it seems faster than mine, but it also requires a bump in VDD (chipset voltage), but I'm down to 38 27.xxx. So it seems ED is one of the fastest overall, allowing a good FSB as well. With my tweaked ROMSIP values it now runs on the lower VDD, but it would also be a little slower. These are the current ROMSIP values I'm using for 260MHz and tight BH-5 timings. It's a little bit slower, but not much, while allowing the run to complete. No 32M at 260MHz yet, though. PS: I don't see a dramatic difference in aida numbers, except Write speeds. But even with similar aida numbers one ROMSIP can be much faster that another one. We're probably hitting some nForce2 throughput, that's why aida shows similar numbers with many of the ROMSIP tables. Pi 32M tells a different story, though.