Jump to content
HWBOT Community Forums

I.nfraR.ed

Members
  • Posts

    2391
  • Joined

  • Last visited

  • Days Won

    26

Everything posted by I.nfraR.ed

  1. These "possible crystal marker" and "possible parent crystal" are just educated guesses based on other parameters. The multiplier type is also probably guessed based on some parameters (major.minor rev, but maybe something else too). That minor revision is kind of strange, I would have guessed higher minor revision would mean a newer cpu, but based on your table - that is not the case. I've added a message box to the tweaker on app open that displays the info I currently have implemented. There's not much info about the topic, but K8 KBDG (BIOS and Kernel Developer's Guide for AMD AthlonTM 64 and AMD OpteronTM Processors) has the MSR register in question documented There's one more value, which is "Reticle Site" and I've included it in the info. Curious to see what different cpus show. Btw, reading and writing MSRs is quite easy. You can use the MSR Editor and MSR Walker in CrystalCPUID tool. PS: I'm thinking of writing a small tool that automatically dumps CPUID registers, MSRs and all the info like cpuid, name, family, model, revision, etc. This way, the comparisons would be easier and faster. Edit: Replaced the app with new build. I was reading wrong part of the register, but it should be ok now. nForce2XT_Debug_20210703.zip
  2. Yes, this has so much potential. I was fighting with the board for several hours and managed to complete just 2 runs :D Had a better one with better timings, but with a bugged troll's lair.
  3. Yes, I've seen the same, but better structured changelogs, here: https://www.lejabeach.com/DFI/BIOS/dfiultrabbios.html I've compared them in the past, but not so extensively. There's a mention about "improved" 3D Mark 2001SE performance, but I don't know if the changes are in the romsip tables or somewhere else. Maybe it's worth checking performance of the bioses "as-is" on a real Ultra B first, with same manual settings on diffrerent benchmarks, but that's a lot of work. 2004/01/31 2. Increase 3DMark2001 SE performance (compare to 12/31) AFAIK that 15 10 doesn't work and it had been changed in most (all?) modbioses. Apparently Oskar Wu changed it too. I believe what you've shown on the right side should be close to optimal for all boards with all multipliers (the multiplier tables part). NF3 and NF4 bioses also use "E4", although I don't know how relevant it is.
  4. Yes, even stock 7800GS+ scored 100fps at CL and CPU @ 2500. 107+ fps with CPU @ 2750. You can try 7.11 and 8.4/8.5 drivers with the 1950X. Nothing would come close to 3850's Nature performance though. I guess you use specific test order and setlod?
  5. Yes, tried different bioses and different values in the tweaker. I may install your modbios with the predefined romsip tables to check, but so far nothing helps.I can boot 260, but no stability, 255 is on the edge and usually experience a sudden force close while running a test (mostly on the "high" ones). 253 was ok. AGP bus up to 105MHz and voltage up to 1.8V didn't make a difference. Kind of want to try a KT880 board to see if it will be the same. I have a Delta-FSR somewhere in the closet.
  6. Thanks. It seems HD3850 isn't very suitable for socket A. It's either a driver issue or it's a severe bottleneck by the platform. VGA overclock doesn't do much, mostly noticeable in Nature and that's what saves the day compared to e.g. a lower-tier nvidia card. CPU overclock doesn't help much either, I have similar scores on air-cooled CPU. I don't know why the "low" tests are so bad, especially car. FSB clock is the way to go and although this board can run 1M at close to 270MHz, it's really unstable above 250MHz with 3850. I also had to use the integrated SATA, since the VGA blocks both IDE ports and can't install the IDE-SATA adaptor. I guess one of my issues might be the modern PSU I'm using, had huge issues with CPU overclock. It is tested for 2.9 on ambient (3050 1M on chiller), but I couldn't even POST at 2.9. Had to clock it in windows. Also higher voltage was making it worse. I may try with 7800GS+, it will probably do better in other tests, not sure how it would compete in Nature. Ah, one more note - latest gpuz from the official site BSODs with gpuz-v2.sys or something like that.
  7. You need VC++ 2005 SP1 redistributable package in order to run the patch. It didn't help with hiccups in car test when the mech is shooting. I've tested many drivers and have no solution yet.
  8. I'm lucky my HD3850 still works, although it appeared dead at first. Thanks for the patch.
  9. The popular believe is that it's basically a Win10 with a new shell and icons, so I wouldn't expect any difference in performance at this stage.
  10. It should be similar to F7e, which has some (broken) support for Vishera and I think you want older bioses for K10 anyway.
  11. Yes, however I have the same question about 3rd stage - are there no limits really or they were left out for some reason?
  12. I know it's a language barrier, but don't know how to help you and what the problem is.
  13. Good question. IMO, any customization needs to be controlled with the appropriate interface for that. I guess that feature will be back at some point, but not the free form css input. If a "theme" customization is needed, then some sort of a theme editor has to be implemented.
  14. Haha, so I now know what he tried to do, either by mistake, or intentionally exploiting css injection vulnerabilities In fact I wanted to test it and report if something is wrong, but never actually got to it. Custom CSS without sanitizing it can be dangerous. PS: I think it is possible to steal someones account using that kind of XSS attack, but haven't drilled much in the topic. So..a good call, I would say.
  15. You're only interested in the "Manual OC" section at this point. Run the app, check the "En" checkbox if it is not, then select desired core index from the dropdown that currently says "All Cores", then select desired multiplier and click Apply. This should set the multiplier on selected core and you can verify it in cpuz with a right click on the frequency. It should show the desired core running at the selected multiplier. All other cores in the same CCD will drop automatically to some lower frequency. I could not make wazza work, even on XP with the classic tweaks. // Edit, I've missed the 32bit libraries in the zip, so here's a new archive with everything included. ZenStates_2.0.0_debug_20210520.zip
  16. Yes, seems to be gone, but I can't really tell if something is still applied, since the site uses the custom styles from my profile Some of the styles are a little off, due to some upgrades during the years though. The logo I had is gone. PS: Actually the custom css is still applied, the background on my profile page uses black/grey shade rather than the default blue of the rest of the pages.
  17. I don't really understand what you're trying to say
  18. Attached is a latest build. The functionality is quite limited, but I don't have time to actually finish it. Manual OC should work though. ZenStates_2.0.0_debug_20210507.zip
  19. I don't have a new Asus motherboard, but I think it can't. You can use Shamino's "OC TOOL" from the link posted in this thread, it can control cores individually: You can also use ZenStates, but I'm at work right now and have no access to my PC at home. Will attach a latest build in the evening. Keep in mind there's some relation between core frequencies and your other cores will drop to lower frequency when you set 5GHz to a single core, but that's ok for a single-threaded benchmark. As for the devices, it's always a good idea to disable everything that is not needed, such as LAN, WiFi, Audio, etc. It is not required, though.
  20. I had the same error on s.775 and could not figure out why. Changed the strap and it went away. Go figure...
  21. PBO settings don't matter when in manual overclock mode. Turn SMT off, but leave all cores enabled. Disable all unneeded devices in bios Boot and load windows at whatever all-core multiplier and voltage you can or feel comfortable with., e.g. 4.5GHz, 1.25V. For voltage, there are 2 "manual" modes, one is the full manual where the boards overrides it and you can only change from BIOS or special tools like TurboV. The other manual mode is AMD Overclocking, which can be changed from ryzen master as well. When in windows, you need to find which of your 6 cores can do 5GHz and at what voltage one by one. You may have bad sample and not all cores could do 5GHz. Increase voltage to 1.45V for example and set core #1 (second core) to 5GHz, if it doesn't crash, run superpi with affinity set to that core. If it passes, then you know core #1 is capable of 5GHz. Clock core #1 back to 4.5 and increase core #2 to 5GHz, perform the same test. Do the same for all 6 cores. If the system crashes/freezes at some point, then reboot and continue where you left. You can then test your best cores for minimum voltage as well or if none of the cores can do 5GHz at 1.45V, maybe try 1.5V. That's the general idea, to find a strong core which can do 5GHz. You don't need all the cores at that frequency, just one of them and set the superpi affinity (from Benchmate context menu) to that core, so it will only run at that thread. My CPU can run 5GHz on all cores, but cores #1 and #3 are better than the others.
×
×
  • Create New...