Jump to content
HWBOT Community Forums

I.nfraR.ed

Members
  • Posts

    2464
  • Joined

  • Last visited

  • Days Won

    36

Everything posted by I.nfraR.ed

  1. These are my s.939 FX, never found a cheap FX-60 when I was adding to my collection and now it is too late, I guess. Should have bought long time ago and maybe more 55s and 57s. ADAFX53DEP5AS CAAXC 0433MPMW Clawhammer ADAFX55DEI5AS CAA2C 0509FPMW Clawhammer ADAFX55DEI5AS CAA2C 0512RPMW Clawhammer ADAFX55DAA5BN CABCE 0516MPM San Diego E4 ADAFX55DAA5BN CABCE 0516WPMW San Diego E4 ADAFX57DAA5BN CABNE 0530APMW San Diego E4 ADAFX57DAA5BN CABNE 0530APMW San Diego E4 The FX55 Clawhammer I tested ( CAA2C 0512RPMW) validated 4050 according to my notes, but it seems I have never uploaded it. Not that the batches would be very helpful, these days you get whatever you can find.
  2. Here are several reasons - he has a 4K, he wants to use it - to piss off @unityofsaints (bonus points - there is BM on the screenshot) - everything in 'Murica is big - because why not Jokes aside, sometimes I bench on my main monitor (2K), just because it is more convenient, especially if it is the current 24/7 system and I'm benching on the chiller. And main reason - because I am lazy.
  3. Is your monitor for ants? :p You can always right-click on the image, then open in new tab and zoom in.
  4. NB PLL voltage (NB/PCI-e/PLL Voltage Control on Gigabyte) helps.
  5. Here you can find links to many bios versions, link to 1202 is still working: https://docs.google.com/spreadsheets/d/19gqxeeAdUmkwgE0EvH4MlJ7meeDbEHYP-FHYW-PMyOk/edit#gid=522016589
  6. @chispy Here you go, uploaded everything I have for that card, including the GPUTweak: https://drive.google.com/drive/folders/1zjNjpkBbChOASw7luWiiXTS9yA2JH08_?usp=sharing PS: Some of the files are probably for the PowerColor card I had back then, but I think it was just a reference with a different cooler.
  7. Maybe it's a bios problem, I can select 1900 from the oc menu on the Gene and it works.
  8. What does it help for? It's still 2:1 MCLK:UCLK
  9. The whole bot is using my personal page customization, it would be hard for anyone else to top that
  10. I tried hard for 5150, but no luck. Might try again tomorrow.
  11. Thanks. Voltage scaling above 5GHz is very bad.
  12. I guess so, it seems to be a new die and has maximum of 2 cores, where Raven Ridge complex contains 4 cores and if yours is RavenRidge then it should have 2 cores disabled, but the full die. https://www.facebook.com/NkdHardware/posts/pfbid02QT9BaH9a8xA6YXvGbKpnjGZk1tDQVVHFsdY2A6WXqXLdj3o8fruVVPKu9ZEqff6dl
  13. I thought they are the same and there's no visual way to distinguish the crystals, so delidding would be pointless?
  14. I wonder if there's a real Picasso 3000G out there, you wouldn't know as the CPUID is always the one of Picasso and tools identify it based on the cpuid - family, model and revision. The rest, like the fab process, is displayed based on this information. For 3000G it is a manual "override" as the cpuid masks it as a Picasso. It's shady practice from AMD side anyway. I've recently read it got a refresh of the box package. From what I know Dali is Raven Ridge 2, or a Raven Ridge refresh, basically a new stepping, I think. The same problem might exists for some of the rest of the APUs in your list.
  15. No, this error is from the vc++ redistributable. AMD OCL is slower than the one linked by @Zombie568, so if you want to get the maximum out of the bench you have to change. I use this version (Intel OCL 2.1): https://nextlimitsupport.atlassian.net/wiki/download/attachments/22683316/opencl_runtime_18.1_x64_setup.msi This pack is also useful Visual C++ Redistributable Runtimes All-in-One: https://www.techpowerup.com/download/visual-c-redistributable-runtime-package-all-in-one/
  16. No, same for me. Attached mine, but it was in the "modded" folder, so I might have done something to it which I don't remember. 89fxau52.f7e
  17. M and Q (C3 and C2 steppings) revisions of K10 cpus are not in separate categories, while there's a difference in clock potential. On the other hand, 1600 and 1600AF are in separate categories. So both options are sensible. In "our" case with the 3000G there's no difference in specs, they are basically the same core, "Dali" being a newer stepping B1 and carrying a cpuid of "Picasso". It's messed up. But on the other hand, if there's any difference in performance, I believe it is insignificant. It's still a RavenRidge "revision". Since there's a "Dali" category already, perhaps the easiest one is to create an additional 3000G "RavenRidge" one. If I had to decide, I'd remove "Dali" and use just one category, but I can see the other option similarly valid. PS: 1600 and 1600AF makes more sense as there's a significant difference between Zen and Zen+, while there isn't between those 2 3000G. It would have been the same if "Dali" was indeed "Picasso" as the cpuid dictates. I don't know if AMD did it on purpose, but it's misleading. Do you know if, e.g. GPU clocks are different or anything else?
  18. These are complete mess. I can't really find a 100% reliable information for the CPUIDs of the different variants. Sources seem to be contradictory. https://github.com/InstLatx64/InstLatx64/blob/master/AuthenticAMD/AuthenticAMD0820F01_K17_Dali_CPUID.txt The InstLatx64 dumps seem to have CPUID 820F01 (model 20h) as "Dali", 810F81 (model 18h) as "Picasso", 810F10 (model 11h) as "GreatHornedOwl", so basically the same as Picasso, but first revision (0), which is also the cpuid of "RavenRidge". CPU World lists an additional CPUID for "Picasso" - the same 810F10. 3000G added as "Dali" doesn't really match the other "Dali" models, e.g. 3020e: https://valid.x86.fr/qsv6dz 3200G, for example, has the same cpuid as 3000G: https://hwbot.org/submission/5339568_naganannan_y_cruncher___pi_1b_ryzen_3_3200g_2min_23sec_517ms and is still displayed as Picasso by cpuz. I think "Dali" is used for mobile APUs only (FP5 socket). Wikichip lists 3000G as an exception in the "Dali" subfamily https://en.wikichip.org/wiki/amd/cores/dali PS: I guess it is accepted as an exception as an incorrect CPUID. One could think it is the the same as 3200G and 3400G, but with less cores. It is in fact "the same" as the RavenRidge counterpart. I've changed the detection in my software to reflect what cpuz displays. IMO there should be only one 3000G category, thus "Dali" designation removed as both variants are Zen-based. I'm not 100% sure though, so maybe contact someone more knowleadgeble and who has access to NDA documents, perhaps Martin from hwinfo or Franck from cpuz? Two different categories also make some sense as they have different CPUIDs, but in reality the APUs are not different performance wise, if I'm not wrong. @unityofsaints's APU is basically a shamelessly rebranded 240GE.
  19. XOC mode of cpuz enabled.
  20. Back to some 32M on Zen4. Should be able to improve it further. 5m 36.210s
  21. Ah, so not exactly "normie" sticks
  22. Have you tried unsafe math optimization? Should be able to run it with that OpenCL version.
  23. I've seen this 2-3 times and I think it is related to unstable system and/or some files get locked/corrupted due to a bsod. Usually a subsequent restart fixes it for me. If not, then a clean BM install should help.
×
×
  • Create New...