Jump to content
HWBOT Community Forums

Leaderboard

Popular Content

Showing content with the highest reputation since 06/24/21 in Posts

  1. Hey everyone, it's time for another freebie! I was going through my hardware recently and came across the KPC Venom container. This is such an iconic and legendary CPU pot but I just don't use it anymore. It's still one of the best all around pots and is especially good for 'fullpot' LN2 or Dry Ice. Rather than let it collect dust or sell it, I'd like to just give it away to someone who will use it and love it the way I did. The container has been lapped and it's in excellent condition. Other than the base sanding, it's in OEM condition with no mods done. I am including a KPC thermal probe and all original hardware except the back plate. Unfortunately the back plate has been used to death and butchered up for other projects, so it wont be included with the freebie. Shipping: I will pay USA shipping, but international people will need to pay the entire shipping bill, and it could be over $50 USD Who's eligible: Everyone in good standing at Hwbot! However, I really do want to see it put to use, so only enter if this is something you would use. How to enter: Just make a post in this thread. Winner selection process: The freebie will be open for about 4 weeks. I have asked @Leeghoofd to conduct the drawing on my behalf from the entries. I will 'close' the event and then turn it over to him to randomly select a winner.
    15 points
  2. Moved Start date to 1st of August , so you have 2 months to play
    6 points
  3. Hola @Joaquin10 , mira amigo que es este mierdero que tienes aqui ??? Te has pasado brincando de Team a Team y cambiando de nombre a cada rato tambien ??? Entonces porque te quejas si tienes problemas con los hwboints ??? Por favor no te quejes mas que ya esto cansa y me tienes enfadado a mi y a los moderators. Parale ya con tanto post de lo mismo y lo mismo , las cosas cambian y hwbot points cambian tambien. Si nesesitas ayuda en traduccion dejame saber y te trato de ayudar ya que google translator no es muy bueno. Entiende que como se distribuyen los puntos cambio ok. Cuidate mucho pero bajale el tono amigo. PM if you need more help. Regards: Angelo ( sorry for my post in Spanish , i have tried to explain to him about the points he lost and why )
    6 points
  4. Another interesting attack vector is BIOS changelogs. Here is a compare between two DFI BIOSes and their changelog. Looks like the last line about bandwidth refers to changes in offset 5D0h - 1618 has been modified to 1518. Which according to previous data should be SYSDCIN delay (6 -> 5). CPU optimal is said to be more FSB friendly. We can see two things - zero byte (in CPU multi ROMSIP lines) is changed from 69 to 21, byte 5 is changed ED -> E4. Looks like 69 is more aggressive than 21. E4 and ED are known to be of same efficiency maybe it's fine tuning with minor changes. Another interesting thing are changes in chipset part of ROMSIP. Some changes are mapped by @digitalbath : Some are still to be figured out. DFI changelist might be handy: https://forums.overclockersclub.com/topic/115082-dfi-nf2-bioses/
    5 points
  5. I'll start here with BIOS modding instruction for beginners. I hope my text is understandable. I am open minded for improvements or error corrections. For the first part, I start here with AWARD BIOS disassembly / change romsips / assembly of BIOS modules. 1.0 assembly - disassambly BIOS modules and change romsips in AWARD BIOS I start modding AWARD BIOS with disassembling and assembling BIOS modules. This is essential to be able to edit the system BIOS module. This method can be used for every AWARD BIOS, not only for NF2 boards. I will explain this method in an example. I will mod here a MSI Delta2 6.0 BIOS. 1.1 Tools we need: awdbedit, hex editor, modbin6 and cbrom32_198. Modbin / cbrom needs a DOS System, so I use a XP System to mod my BIOSes. 1.2 I start with extracting all modules to a seperate folder (here: bin). I use awdbedit to do this: Be aware: Do not edit your BIOS in awdbedit! Now we got our BIOS modules extracted to a seperate folder. The System Module is simple to find (always 128KB) 1.3 disassemby BIOS file Now we need to unload all BIOS modules except the system module. I will use cbrom32 to do this. commands in cbrom: /d -list all modules /modulename release -delete module /modulname extract -extract module /isa modulname - add isa module /modulename filename – add module to BIOS file First, I open two DOS Command boxes. Then i list in the first box all modules from the unmodded BIOS. This will be my lookup table. I copy the unmodded file (here w6570nms.bin) and rename it to "empty_b6a.bin" (name does not matter here). This will be my "empty.bin" BIOS file. I will use the release command in the second box to delete all modules except System BIOS module (most module #0). cbrom32_198 empty_b6a.bin /logo release cbrom32_198 empty_b6a.bin /vga release cbrom32_198 empty_b6a.bin /pci release ---> B enter cbrom32_198 empty_b6a.bin /pci release cbrom32_198 empty_b6a.bin /group1 release cbrom32_198 empty_b6a.bin /group0 release cbrom32_198 empty_b6a.bin /ygroup release cbrom32_198 empty_b6a.bin /epa release cbrom32_198 empty_b6a.bin /acpi release cbrom32_198 empty_b6a.bin /xgroup release Then command cbrom32_198 empty_b6a.bin /d to list my empty.bin file. We see all modules are deleted, only system module is left. I duplicate my empty.bin file. I will need this later. Then I copy all extracted BIOS modules (from point 1.2) into folder. 1.4 edit System module I open the System module 6A61BM4K.BIN (128KB) with my hex editor. 1.4.1 Athlon XP-M name I search for "unknown CPU Type" and change this label to "AMD Athlon XP-M". Never change the size of the system module! 1.4.2 change romsips I search here for hex letters "65D0": All romsips tables begin with 65D0. One table has the size of 100h. This BIOS has 6 Tablles, so the romsips ends after 600h. I mark all tables (600h!) and paste the tables with the romsips I want (here 619XT). Now the system module is modded and I safe the file. 1.5 assembly BIOS file We now need to compress the modified system module. cbrom32_198 empty_b6a.bin /other 5000:0 6A61BM4K.bin (modded sytem module) This command compresses the modified system module into the BIOS file. This makes the BIOS file unusable, but this command duplicates also a copy to a file named "bios.rom". This is the file we need. I delete the unusable empty.bin file and replace it with my copy. I open the bios.rom file and the restored empty.bin copy. We mark and copy complete code in bios.rom (length=13911h!), switch to the restored empty.bin and jump to offset 10000h. This is where the system module beginns. We mark the length of the bios.rom (13911h) after the offset 10000h. Then paste the marked code with modded / compressed code. Fill with FF if the new code is shorter then the old code. Save and exit. cbrom32_198 empty_b6a.bin /d Everything looks fine. Now I will fill the BIOS wit the modules. This time, the order to fill the modules is important! cbrom32_198 empty_b6a.bin /xgroup awardext.rom cbrom32_198 empty_b6a.bin /acpi ACPITBL.BIN cbrom32_198 empty_b6a.bin /epa AwardBmp.bmp cbrom32_198 empty_b6a.bin /ygroup awardeyt.rom cbrom32_198 empty_b6a.bin /group0 _EN_CODE.BIN cbrom32_198 empty_b6a.bin /group1 BGROUP.BIN cbrom32_198 empty_b6a.bin /pci NV2PXES.NIC cbrom32_198 empty_b6a.bin /pci NVRAID.ROM cbrom32_198 empty_b6a.bin /vga CR17NZ.ROM cbrom32_198 empty_b6a.bin /logo Platinum.BMP cbrom32_198 empty_b6a.bin /d compare in case I made a mistake here: 1.6 conclusion: The modified BIOS files looks fine and is ready to use. CBROM did the checksum for us. This method to mod a BIOS file is not the fastest one, but necessary if you want to mod the strings (BIOS items) in the system module (more on this in another chapter). This method works with every BIOS (AN7 for example) 1.7 alternative There is a second and faster way to change romsips: open your BIOS file with modbin modbin creates a temporary ORIGINAL.BIN (128KB) file. This is the system module edit ORIGINAL.BIN, change romsips (1.4) and safe the modified ORIGINAL.BIN file. Safe as... in modbin and quit modbin. modbin will checksum for you end
    5 points
  6. OS is optimized for Rocket Lake mainly. You'll want to use InSpectre for previous Intel gens. For Cascade Lake-X/Coffee Lake-R/Comet Lake-S you will want to use a bios with modified/removed microcode for all benchmarks. For Comet Lake-S specifically, there is a patch that will need to be ran at logon of any user with Task Scheduler for the use of no-ucode bioses, see the XII Apex thread for more details. Maxmem is not set by default. https://drive.google.com/file/d/1TnXW4rUrS7-IzgKLt9peYFChGTJKFmDd/view?usp=sharing Go wild.
    4 points
  7. I actually tested them the other day when binning my PSC on phase:
    4 points
  8. I hope you read part 2 https://overclockers.ru/lab/show/111557/retrokloking-legenda-overklokinga-ian-8pack-parry-voshozhdenie
    4 points
  9. 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
    4 points
  10. 4 points
  11. M10A 2603 BIOS version transplantation for M9A with Resizable bar support by dsanke https://www.mediafire.com/file/5dugae6mqdv0kf5
    4 points
  12. MSI GTX680 Lightning card. 100% working condition, never used on subzero (pulled from daily rig). Additional tests will be made right before shipping to ensure that everything is ok. Guarantee not DOA. 140 euro + shipping (I can ship worldwide, ask for costs). Bank transfer (preffered) or PayPal gift.
    3 points
  13. How did you use the acpi.sys file? It needs to be dropped in Windows>System32>Drivers folder and overwrite the existing acpi.sys file in the drivers folder. The neat thing about this is that XP can be used on Intel SATA ports instead of ASMedia ports. If you are having trouble. Take an existing XP install (like for Z490, Z370, ect) and connect it to a PC via a SATA to USB cable (I've heard this is a must) and drop the acpi.sys file into the drivers folder.
    3 points
  14. How about this one? SODIMM is such a weird format, never could get used to it.
    3 points
  15. HWBOT TEAM CUP THREAD (click title for stages) Due to crazy hardware prizes, no exotic/weird hardware demands No mobile stage Maximum of 2-3 subs per stage ALL STAGES ARE CONFIGURED ROUGHLY, so inputs are welcome. I put the start date at the 15th of August but since we don't expect you to have to wade through Fleabay and such, maybe we can start August 1st ?
    3 points
  16. For most subs only 2, max 3, But I'll add it in the rules per stage, so you know
    3 points
  17. Nick is working on it, he's fully into some new upcoming stuff... Hang in there
    3 points
  18. Hello, I'd like to separate some in-depth research considering sA that started in this thread: https://community.hwbot.org/topic/187148-a7n8x-e-deluxe-as-an-alternative-for-socket-462/ I'd like to discuss some sA and NF2 specific mods to: Make instructions for beginners Investigate other BIOS mods Make some progress if possible I'd like to investigate the work done by gurus like Merlin, tictac and many others, take the best from them and maybe move ahead. It would be very nice to get over 250FSB by tuning system registers and check how it's done. I'll start with some known mods and would like those familiar with ( @Mr.Scott ,@I.nfraR.ed, @digitalbath, @Tzk, @Strunkenbold, @TerraRaptor) to check in and correct if I'm wrong: BPL mod (also NVMM in later versions) - memory init routine from NV. Newer versions are better (up to 3.19?), latest are sometimes incompatible. CPC off (=CR 2T) seems to be modded in BPL. ROMSIP - a set of tables (CPU interface on/off, and for 100/133/166/200 FSB) with CPU and chipset related settings. Influence stability, overclocking, performance. soft-L12 - a mod that acts as BSEL, forcing BIOS to implement FSB200 settings even on FSB133 CPUs. Most mod BIOSes have it, add stability on high bus speeds. modified alpha-timings (can be set using the new NF2 tweaker from Infrared) options ROMs with performance tweaks (3D-fire for example - modified chipset registers?) changed some northbridge registers (S2K control probe limit, XCAARB_RD/WRCOUNT, DQSEN_PULL_B, Auto Refresh Cycle Time, Read-to-Read Command Latency, Pre-charge All Command ) (seen on Asus A7N8X dlx mod BIOS) Please, stay to the topic, don't discuss CPU binning, memory, voltmods and other things. BIOS mods and how they affect the system is the primary goal. Do not discuss cosmetics and general BIOS techniques like opROM update, unlocking menus and so on. I believe we all know how this is done (or it can be discussed in a different topic) so we can focus on advanced stuff. Infrared's Discord channel about Socket A: https://discord.gg/YKHvEt6xct Summary of nf2 registers: https://docs.google.com/spreadsheets/d/1ZDST3XGq0oE7YtQxAME29RtopA8QcePCaHa2NBRHaB8/edit#gid=0
    3 points
  19. I've been going through some of my CPUs. I forgot to note the reported core by BCRC for some of the first entries in the table, so take them with a grain of salt. The lookup table for those cores is not 100% correct anyway. Some of my Thoroughbreds are missing, hopefully I will find where they are Model OPN Batch Core CPUID Rev Unlocked Code Name Site.Major.Minor Multiplier type Possible Marker Athlon XP 1700+ AXDA1700DLT3C AIUGA 0245SPIW Thoroughbred-A 0680 A0 yes 2308 Thoroughbred 1.0.4 Unknown Unknown Athlon XP 1700+ AXDA1700DLT3C AIRGA 0319WPMW Thoroughbred-A 0680 A0 yes 2318 Thoroughbred 1.0.14 Locked MIAGA Athlon XP 1700+ AXDA1700DLT3C RIRGA 0233VPMW Thoroughbred-A 0680 A0 yes 2318 Thoroughbred 1.0.14 Locked MIAGA Athlon XP 1700+ AXDA1700DLT3C JIUHB 0320MPMW Thoroughbred-B 0681 B0 yes 2334 Thoroughbred 1.1.14 Unlocked AIUHB/JIUHB Athlon XP 1700+ AXDA1700DLT3C JIUHB 0323RPMW Thoroughbred-B 0681 B0 yes 2334 Thoroughbred 1.1.14 Unlocked AIUHB/JIUHB Athlon XP 1700+ AXDA1700DUT3C JIUHB 0312XPFW Thoroughbred-B 0681 B0 yes 2334 Thoroughbred 1.1.14 Unlocked AIUHB/JIUHB Athlon XP 1700+ AXDA1700DUT3C JIUCB 0251TPXW Thoroughbred-B 0681 B0 yes 2326 Thoroughbred 1.1.6 Unknown Unknown Athlon XP 1800+ AXDA1800DLT3C JIUHB 0310MPMW Thoroughbred-B 0681 B0 yes 2334 Thoroughbred 1.1.14 Unlocked AIUHB/JIUHB Athlon XP 1800+ AXDA1800DLT3C JIUHB 0333VPMW Thoroughbred-B 0681 B0 yes 2334 Thoroughbred 1.1.14 Unlocked AIUHB/JIUHB Athlon XP 2000+ AXDC2000DUT3C AQZFA 0343UPMW Thorton 06A0 A2 no 2306 {empty} 1.0.2 Locked AQYFA Athlon XP 2000+ AXDC2000DUT3C AQXEA 0324UPMW Thorton 06A0 A2 yes 2316 Thorton 1.0.12 Unlocked Unknown Athlon XP 2000+ AXDA2000DUT3C KIXJB 0415EPMW Thoroughbred-B 0681 B0 no 2333 Thoroughbred 1.1.13 Undetermined JIXIB/AIXJB Athlon XP 2000+ AXDA2000DKV3C JIUHB 0338MPM Thoroughbred-A 0680 A0 yes 2308 Thoroughbred 1.0.4 Unknown Unknown Athlon XP 2100+ AXDA2100DUT3C AIUHB 0302WPDW Thoroughbred-B 0681 B0 yes 2334 Thoroughbred 1.1.14 Unlocked AIUHB/JIUHB Athlon XP 2100+ AXDA2100DUT3C JIUHB 0308VPMW Thoroughbred-B 0681 B0 yes 2334 Thoroughbred 1.1.14 Unlocked AIUHB/JIUHB Athlon XP 2200+ AXDA2200DUV3C AIUCB 0240RPFW Thoroughbred-B 0681 B0 yes 2326 Thoroughbred 1.1.6 Unknown Unknown Athlon XP 2400+ AXDC2400DKV3C AQXFA 0348MPMW Thorton 06A0 A2 no 2306 {empty} 1.0.2 Locked AQYFA Athlon XP 2400+ AXDA2400DKV3C AIXHB 0328SPGW Thoroughbred-B 0681 B0 yes 2334 Thoroughbred 1.1.14 Unlocked AIUHB/JIUHB Athlon XP 2400+ AXDA2400DKV3C AIUGB 0244MPM Thoroughbred-B 0681 B0 yes 2322 1.1.2 Unknown Unknown Athlon XP 2500+ AXDA2500DKV4D AQYFA 0350SPGW Barton 06A0 A2 no 2315 Thorton w/512K 1.0.11 Locked AQYFA What I've seen so far: Reticle site is always 1 - it's either a mistake in the tweaker or these bits started to be meaningful from K8 and up Major mask revision is always the same as the stepping (read from CPUID) and the only core that has 1 instead of 0 is Thoroughbred B (as in "the 2nd revision of T-Bred core") Minor revision is the interesting one BCRC displays Barton if minor revision is 12 and Thorton w/512K when it is 11. Note that the CPU in red is FAKE Thoroughbred-B, in reality it's T-Bred A instead with L3, L5 and L12 bridges manipulated and has fake markings. Up to the "Unlocked" column are values either written on the cpu or detected from other tools. Unlocked column is based on testing. Rest of the columns are from BCRC and the tweaker. I will also check what Palomino reports, but that MSR is invalid on Thunderbird core, so maybe it's the same on Palominos. PS: Maybe we should use some shared google sheet, since you can't really format the tables here.
    3 points
  20. Lots of ways to do this, start here (AB 2.2.4) since you have been trying ABX 2.2.3 This was from UnWinder 680 Lightning On 2.2.4 you may edit Lightning hardware profile files (.\Profiles\VEN_10DE&DEV_1180....cfg) and add the following lines there: [Settings] VDDC_Generic_Detection = 0 VDDC_CHL8318_Detection = 46h VDDC_CHL8318_Type = 1 Those lines disable NVIDIA's capped voltage control module, enable voltage control via direct access to CHL8318 and select offset voltage control mode for it. Note: each card profile must be edited for SLI configs. You can add this to the "OEM" file of many/most versions of AB, I know 411 HWBot works here I think I have one saved LN2 BIOSs FOR THE FIRST 5000 LIGHTNING 680s 80.04.09.00.F7 (non-LN2) 80.04.09.00.F8 (unlocked LN2) AFTER THE FIRST 5000, WE'VE SEEN THESE LN2 BIOSs FROM THE FACTORY: 80.04.28.00.3A (unlocked LN2) 80.04.09.00.3A (unlocked LN2) 80.04.47.00.19 (locked LN2) 80.04.29.00.3A (locked LN2) 80.04.28.00.39 (non-LN2) 80.04.47.00.18 (non-LN2) https://www.overclock.net/threads/official-msi-gtx-680-lightning-owners-club.1280007/ EVC should hook up here ! Have fun 893761724_MSIAfterburner2.2.4.zip MSIAfterburner.oem2 80.04.09.00.F8.rom 80.04.28.00.3A.rom
    3 points
  21. @Antinomy and @I.nfraR.ed shared their thoughts about superlocked cpus and cpu registers (MSR). Maybe we can identify superlocked cpus like this... They also mentioned a tool called Barton CRC (BCRC.exe). So i grabbed a few cpus and here's the result so far. Example screenshot of BCRC output: Here's the result which BCRC reported. The first columns is what i read from the cpu sticker (orange), latter ones are output of BCRC (blue). My conclusion so far is that the minor rev is rather random and the superlock plus the Crystal marker seems to be a more or less random guess. Nr Cpu Rating Stepping week Stepping ED Value CPUID Processor Code Major Minor Type Crystal Marker 11 Athlon XP 2600 AQZFA 0349 TPMW 2306h 06A0h Barton 0 2 locked AQYFA 12 Athlon XP 2600 AQXDA 0318 MPMW 2319h 06A0h Barton 0 15 unlocked unknown 13 Athlon XP 2600 AQXEA 0404 TPMW 2316h 06A0h Barton 0 12 unlocked unknown 15 Athlon XP 2600 AQYHA 0401 UPMW 2315h 06A0h Thorton w/512K 0 11 locked AQYFA 16 Athlon XP 2600 AQXEA 0403 WPMW 2316h 06A0h Barton 0 12 unlocked unknown 17 Athlon XP 2800 AQYHA 0409 SPMW 2315h 06A0h Thorton w/512K 0 11 locked AQYFA
    3 points
  22. When i started looking into romsip modding i found this post by TicTac on pcper forums. See attached screenshot for content. So yes, these are indeed multi specific settings... This made me test my FSB stability at multi 7 or 7.5. If it is stable on these multis, then it'll run on any multi. However he didn't state what these settings are actually controlling. If we can find this out (also for the upper half of the romsips), then we might be able to push the fsb further. We also hit a hard FSB wall at about 263MHz right now, on the german Hardwareluxx Forums we got about 4 or 5 boards which won't pass 32M above 263Mhz, no matter what you do. Vdd, Vcore, Multi doesn't matter, some boards do even freeze when trying to set 264/265 MHz. No clue what causes this, might be some peripheral controller or even the chipset itself acting up. broken link: https://pcper.com/forums/?346001-ROMSIP-Table-Mod-Guide#post3100010
    3 points
  23. Yes. You basically use the PCI registers of the chipset and set the desired settings via ISA or PCI option rom, right before the OS is loaded. There's two ways of doing this: a) you can just hardcode some settings b) you can write some data from modded bios settings to the CMOS register (bios settings are stored here) and load these cmos values from the option rom. This way you can add additional bios settings without hacking the whole bios. We did this on at least 3 or 4 boards (a7n8x-E, a7n8x v2.0, Abit, Epox?) and it works great. the cleanest solution would be to reverse engineer the bios and add those options in a native way. However i've already spend a bunch of hours looking into this on my A7N8X and even comparing different bios versions hasn't got me anywhere. Luckily Asus made 2 bios versions where each introduced a new bios setting, so the changes inside the code are clearly visible. However it looks like the hex strings which are used to define the bios items and the code which is controlled by them are stored right next to each other. So if there's an option added, then some offsets and pointers will break and the bios won't work anymore. My conclusion was that if we ever want to add completely new options into the bios which don't "recycle" unused bios items, then it's a ton of work. That's the point where i gave up... It's probably better to spend more time upon improving and understanding the romsips first.
    3 points
  24. I'd like to add that there's actually two types of nvidia specific code for the ram controller inside the bios, depending on the board and (maybe?) chipset revision. We got NVDAMC and NVMM. NVDAMC is the memory controller firmware up to version 3.19. Nvidia then renamed it to NVMM and introduced version 4.x. Note that these versions are not compatible with each other. So if a board runs on 3.x (examples are Abit NF7, DFI Infinity/LP B, A7N8X), then you can't update to 4.x. Board won't boot. Some newer MSI boards (K7N2?) run on NVMM 4.35 and obviously won't boot on 3.19. I see no reason to use an older version than 3.19. It's the latest available NVDAMC version before NVMM got introduced and runs great in terms of stability and performance. Also note that the NVMM versions (ex: v4.62) extracted from Intel Nforce boards won't work on any socket 462 board. At least that was the conclusion when we tried it in the past. --- If you want to swap the BPL, you can do it with a regular hex editor as it isn't LZH compressed. Thus you don't need modbin to compress it and calculate the checksum.
    3 points
  25. 3 points
  26. Nice find! No wonder E4 didn't work with 1719. As far as I tested, faster sips E4, ED needs lower values like 1618 or 1518. Slower sips like DB needs higher numbers like 1719 or 1821. You can change the last number from 1518 to 1519 and it will work. It's time to make some tests here. I hope I will find the time to do this.
    3 points
  27. OS is optimized for Zen 3 mainly. You'll want to use InSpectre if you use an older Ryzen, and Geekbench 3 version 3.4.3 will score better with previous gens. Maxmem is not set by default. https://drive.google.com/file/d/1TnXW4rUrS7-IzgKLt9peYFChGTJKFmDd/view?usp=sharing Go wild.
    2 points
  28. well its been a minute sorry for the delay. was offered a chance to start finishing up some of my course requirements toward my red hat architect certificate. then bombarded with classwork as well as work. will be resuming my oc adventures within the week. with some slight adjustments. and nothing over the top. i decided to take a crack at 3dmark this morning. its nothing amazing. but it's where my starting point is. https://www.3dmark.com/3dm/64059071 only modded the mpt for max power 360w up from 289 and 375 on the tdc.. also random update. turns out that xfx released 2 different versions of the black edition. which somehow i received the higher binned version. which explains a lot as to why my card never shows up bios check either on techpowerup or even 3dmark. my manufacturer never shows up. hope everyone is doing well and sorry again for the delay =)
    2 points
  29. The wait is almost over.... we are working out the final details Only prerequisite to enter: Corsair memory sticks For Air and Water Cooling setups only (no chillers nor any form of extreme cooling allowed)
    2 points
  30. To start: I believe you will need OS boot mode to be in CSM for the OS itself to work, but for the installation process, I don't remember if it needs CSM or UEFI. When you download anything to bring to your bench OS, such as tools or benchmarks, download from a daily OS to a USB, and then boot from your bench OS to take those things from the USB. Your internet will not be used on your bench OS. To make the OS: Download your ISO. You want Windows 10, 32 bit, version 1809. I've already tested a bunch of versions, anything newer or older is slower, and 64 bit is also slower. You'll want to use an ISO downloader tool like this: https://www.heidoc.net/joomla/technology-science/microsoft/67 From there, make your installation USB. I prefer to use Rufus, found here: https://rufus.ie/ Then, grab the drive you intend to use. 128gb is more than enough. 64gb is honestly still more than enough. 32gb is prob all you need, should be able to be found in SATA SSD form for very cheap. I may try to get it installed onto a 16gb Optane drive sometime. Follow normal install procedures. Once you have that Windows install booting, it will be time to strip the OS. I start this by going to Windows Security and disabling every single thing I possibly can in there. I then go to the normal Windows Settings and turn off everything I can there, as well as removing all the unnecessary programs I find. From within Settings, go to System, About, System Info, Advanced System Settings, Performance. In there, I set Visual Effects to "adjust to best performance" and set my virtual memory to 0mb (pagefile disabled). I suggest you restart to let everything apply, then. After that, press win + r and type in "services.msc". Disable basically everything you can except for the services that screw with how you login (Local Session Manager, User Manager, User Profile Service) and things that screw with your apps (Windows Management Instrumentation, Capability Access Manager, Application Information, and maybe RPC/RPC Endpoint Mapper). Restart again. Press win + r and type in "msconfig.exe". From there, go to services, and disable anything else you can there. Restart again. It may be worthwhile to go to Task Scheduler and delete literally every task you can, though I don't really have much data for the benefit/side effects of that. The base of your OS is done now. It wouldn't be a horrible idea to save a Ghost/Acronis/Macrium Reflect backup to a safe place now. Install your tools: To start, you're going to want Benchmate. You don't just want any version, either. You want 0.10.5. I haven't tried older versions, but anything newer is slower. I couldn't find where I downloaded this, so I'll just put a Google Drive link here: https://drive.google.com/file/d/1ut7j7g5s_XumI6nvachSXC9vDFc4019p/view?usp=sharing If you're trying to keep OS size down, I'd recommend only installing the tools/benches you need from Benchmate. I don't know if this OS is relevant for anything other than SuperPi, so that's the only benchmark I'd install. Also, you're going to want to install CPU-Z later anyways, as the version included in this Benchmate is not the newest and also isn't motherboard-manufacturer-themed. Then, you'll need ZenTimings: https://zentimings.protonrom.com/ I know 1.2.3 works. Not entirely sure if newer works. This would also be a great time to download any other tools you may need, like stuff to change bclk/core ratio/voltages in OS, though you may need to install drivers of some sort for them to work. You definitely want to make a backup of your OS now; it will save you a lot of future headaches. BIOS and related tweaks: First of all, you're going to want the right bios version. I have found newer AGESA versions to be worse for efficiency (worse times on average with same settings, enough for it to actually matter) but only sometimes better for fabric clocks. I personally recommend finding the oldest bios version that doesn't make it impossible to use benchable memory settings. I use A05O1 for the B550 Unify-X, which is the first of two AGESA 1.1.0.0 revision D based bioses for that board. A0502, the second and newer of the two, was slower, despite being the same AGESA version. I personally found an even bigger drop in efficiency when using AGESA 1.2.0.0 or later, although at least one Unify-X user has reported no loss from going newer. Also, Cezanne (the Zen 3 APUs) could be relevant for SuperPi, but I haven't tested them myself or what bios would be best for them. Second of all, you want B-Die. You're going to be running synced. You are going to be running 1t with GDM off if you actually want a decent score. This is more important than running dual rank, but if you can do 2x16gb or 4x8gb with 1t/GDM off, even better. Some subtimings you'll want to set are tRCDWR 8, tRAS 21, tWR 10, tRTP 5, tRDRDSC and tWRWR SC 1, tRDRDSCL and tWRWRSCL 2, tWRRD and tCKE 1. Also, you want PowerDown and any other power saving features off. In rare cases, any of these settings can cause issues, but for every single kit I tested it should work fine. You'll want tRC as low as it can go, which depends on motherboard and primary settings. Generally you can run tRP below tRCDRD and tRCDRD equal or below tCL. tRRD L/S and tWTR L/S has performance scaling as low as you can set them, but different board/imc/mem combinations may have different limits. I personally prefer running tRDWR at 10 and seeing how far I can get tCWL below tCL. tRFC can have performance or stability testing if you set too low, so that would need to be manually tested. There is some debate to if flooring tFAW (as opposed to 16) and flooring your SD/DD timings matter, you'll have to test yourself. Third of all, voltages and other settings. Obviously B-Die benching settings need high volts (>1.8vdimm) and occasionally need vtt below auto. Also, you're going to want to run a static overclock for this competition, ideally hold at or under 5006mhz on one thread for the entire duration of the run. In my case, 5ghz needs about 1.425vcore and is pretty difficult to boot on a normal tower air cooler. I also boot with only 4 cores active and SMT disabled. In terms of other voltages, vsoc is directly related to how high you can run fclk, though too low can be unstable and too high can cause regression. Depending on temps, the max I can run is 1.19 to 1.225, though I have seen multiple users report scaling above 1.25. The 1p8 or pll voltage is supposed to be related to fclk as well, and can be increased to something in the 2.0 to 2.3 range. I have heard reports of going from 2000fclk max to >2066 after tuning this. The derived voltages, vddg and vddp, are also important for stability. I honestly don't know what "optimum" would be for these, as I have found just setting them to 1.15 works for me. Your mileage may vary, I recommend asking daily OCers for advice here. ProcODT, Rtts, and Drive Strengths can all be important for memory stability, especially for dual rank, but I also don't know much about the specifics of what to set those. Ask the daily users for that too. You will have to do a fair amount of trial and error, especially when trying to make high fclk work when you're on the edge of stability. A commonly spread rumor is that fclk instability doesn't affect single-core performance. That is not true. Also, having Whea errors doesn't mean your performance is going to regress. The inverse also applies. It would be a good idea to poke around AMD CBS and PBS and play with obscure settings in there, though I don't know terribly much about what those do. Benching Theory and Practice: For SuperPi specifically, you generally want to have HT/SMT disabled and (unless your best core is the 1st or 2nd core) have at least 3 cores enabled. From Benchmate, set priority realtime, RAMDisk on, LPM on, and set affinity to the last enabled core. You want to run 16k before you run 32m. Ideally run 16k until you get a "good" time and then run 32m. Because of a bug with Benchmate 0.10.5, you'll have to close and reopen SuperPi between each run of 16k. Before you run 32m, you'll want to go into Task Manager and close all unnecessary (such as search, Edge Update, explorer, etc) services as you can. I like to minimize the background Benchmate thing so it isn't on screen, and I prefer to bench in 800x600 and go back to native resolution to take the screenshot. With some practice, you should be able to tell a run with good potential from one that's bad in the first 6 loops or so, however there are no early warnings for if your run is going to randomly slowdown by the halfway point or later. Also, once you have some experience with Pi, you should be able to recognize the difference that small changes (tRAS 29 vs 32) make to your score or if your OS has degraded and needs a reinstall. Overall Goals/Targets: When your OS is setup correctly, your subtimings are dialed in, you should be able to go below 5m44s even with daily settings. Below 5m43s should be viable on daily settings as well, especially if you can do >1900fclk. Below 5m42s is a bit tougher, generally only viable with bench memory settings. This will be tough if both your CPU has a bad fclk wall and your memory struggles to run bench mem settings. I think the minimum to break this wall would be around 3733c12 single rank, given exceptionally tight subtimings and lots of effort. https://hwbot.org/submission/4747440 This is my score as of posting the guide. It's pretty well optimized overall, though I think below 5.41.300 may be possible with these exact settings. Have fun benching!
    2 points
  31. Hi Guys, CPU was sold almost immediately after posting unfortunately, I just went to sleep and haven't had the chance to update until now.
    2 points
  32. Yes , the www.elhvb.com is a must have for all old-timers !!! They host two bios databases , the mobokive and the kuriaki and they also host many manuals for old boards. They sure deserve a donation , for all support that they offer.
    2 points
  33. Also CSM support has to be disabled inorder to run XP on Tachyon.
    2 points
  34. Got LN2 and decided to run some cold mem. BBSE was a bit disappointing but the sticks only just do 2600C8 on air. Full pot & 2.1V: Ran my trusty 1600C7 again and finally got into the 17s. Full pot & 2.36V:
    2 points
  35. This is very nice of you, I don't want to enter, just appreciate what you are doing for the community!
    2 points
  36. ROG CROSSHAIR VIII Series BETA BIOS 3702 UPDATE 1. ComboPIv2_1203_PatchA (Before ver same) 2. Some bug fixes ROG CROSSHAIR VIII HERO BETA BIOS 3702 ROG CROSSHAIR VIII HERO WIFI BETA BIOS 3702 ROG CROSSHAIR VIII FORMULA BETA BIOS 3702 ROG CROSSHAIR VIII IMPACT BETA BIOS 3702 ROG CROSSHAIR VIII DARK HERO BETA BIOS 3702
    2 points
  37. You Impostor! Tell me what sacrifice you want from us to return TAGG back!!! GPU is not ZOTAGG! :D
    2 points
  38. Add per core P state control improves limiting core drop under cold
    2 points
  39. Live Covid session click on picture...
    2 points
  40. No particular interest, I do ultimately want to get my hands on one of each IC (since it's hardly unprecedented for enthusiasts to discover a random IC that's actually useful, see Samsung 1Gb G), but I have a Pi Black 2000 9-9-9 kit of it. It was actually an accident, I didn't even notice they were 1GB sticks until I got them. Freegeek, I assume? That is a good deal, I myself got a lot of 2000-2200 sticks from them a while ago, haven't tested all of the sticks but the 2000 Ripjaws I got in that lot turned out to be excellent. Whether the blacklines are GT depends on the part number, I nabbed a kit of those when I was just getting into DDR3 and was a bit disappointed to find out they were JN. To be fair, I didn't actually pull the spreaders, but they weren't any good. Kingston also depends on the P/N: 2000C9D = 9-9-9 BBSE, 2000C9AD = 9-11-9 BDBG or BFBG, depending on production date. My wishlist was also enormous, but, well, with a lot of time, money, and patience, now the number of kits I have is enormous (a bit too enormous...) Well, shoot, now I have to talk about my favorite subject, insane (near-)vaporware bins. At least, my understanding of some. Near-vaporware (extremely limited): F3-19200CL8D-4GBPIS, 2400C8 Pi. Very good bin, source of some of the best air results I've ever seen (though I believe the particular kit I'm thinking of, which TaPaKaH had at the time, hated cold; air isn't everything), but I've seen kits that were merely "pretty good". Apparently was retail but I don't think there were more than like a dozen kits. F3-19200CL8Q-8GBZHD, 2400C8 Ripjaws Z, same deal as the Pi. Some insane sticks, very limited. As far as I know it was only quad kits, so that doesn't help things. F3-20000CL9D-4GBTDS, 2500 9-11-9 1.65V PSC. Found in an OC3D review. I would guess this exact spec didn't go retail, or if it did, insanely limited. F3-20000CL9D-4GBTDS, 2500 9-11-11 1.65V PSC. The only results I have a link to are from Hiwa, he claimed they were a retail purchase and sold out immediately. If some of those results truly were done with memory on air, that kit of his was golden. Demo/ES SKUs: F3-12800CL5Q-8GBPI, 1600 5-8-5 1.65V PSC. F3-16000CL6D-4GBFX(D?), 2000 6-9-9 1.65V PSC. Look like some sort of Reaper-Flare hybrid. F3-18400CL7D-4GBPID, 2300 7-10-10 1.65V PSC. I know where this kit is but only one stick is still alive. F3-20000CL8D-4GBTDS, 2500 8-12-8 1.65V PSC. Used by Hiwa at a Computex 2010 demo. I believe Andre Yang had a kit as well. Don't have a clear picture on hand. KHX2544C9D3T1FK2/2GX, 2544 9-11-10 1.65V BDBG. PR. F3-20800CL8D-4GBPIS, 2600 8-11-8 1.65V PSC. The "3" and "4" on the PCBs in the picture make me think there were at least two kits... Vaporware (don't have any concrete evidence of these existing, beyond people asking if it exists ) : F3-14400CL6D-4GBFLS, 1800 6-8-6 1.65V PSC. F3-18400CL9D-4GBTDS, 2300 9-9-9-24 1.65V BBSE.
    2 points
  41. With drilled threads in venom he can hold 10900k and 11900k on they maximum or in worst scenario 5-10% from they maximum clock in september when I buy reaktor 3.0 TR I can tell exactly. David do many good things for OC community.
    2 points
  42. 2 points
  43. added many CPU datasheets AMD 486, K5, K6, K6-2, K6-2+, K6-III, K7, K8, K10, K15 Intel 8086, 80286, 80386, 80486, PPRO, PMMX, P2, P3, P4, P4EE VIA C3, C7 Cyrix 6x86, 6x86MX, MII IDT Winchip, Winchip 2, Winchip 3 Rise MP6
    2 points
  44. O.K. CPU multi part byte 2. Looks like byte 2 is always the same in ROMSIP and depends only on multi: After that, bytes 3 and 4 are 00. But there is one notable exception - DFI (and ECS) that use another writing, in fact, two of them. First is a usual ROMSIP entry, second is an entry modified by DFI, let's call it 3A 02 (by bytes 3-4). The third is another DFI entry, I'll call it CA 02. As you can see, in all cases byte 2 remains the same, only bit 7 is set to 1. In 3A 02 byte 1 bit 5 is set to 1, bytes 3 and 4 are 3A 02. In CA 02 byte 1 bits 5 and 3 are set to 1, bytes 3 and 4 are CA 02. Do not, that only these bits in byte 1 are modified. Other bits depend on byte 0 that are use for optimal/aggressive settings. Purpose of these bytes is unkown AFAIK but feel free to test DFIs modded settings.
    2 points
  45. I'll start myself with the ROMsips. I believe that the table consists of two parts - the first part is chipset-related. The second part is CPU-related. The main problem was that I've been trying to match multipliers to CPU part of the table. Then I've remembered this part. And I've understood that FID isn't endoded in ROMSIP. Instead, FID itself is a link to ROMSIP. Let's look at FID table: So, all multipliers are represented by 16 values that are used by SIP (serial initialization protocol, which is quite advanced). And now take a look at the CPU part of ROMSIP: Do you see this? Multis 11-12,5 (and all higher) have same last two bytes, then 5x and 5.5x are different. The first ROMSIP uses different settings for 6x, 6.5x but the second one has same settings as 5x, 5.5x. So these do look like CPU settings. I believe some of them are delays that are programmed during SIP packet. Might be lame, but I didn't see this info before.
    2 points
  • Newsletter

    Want to keep up to date with all our latest news and information?
    Sign Up
×
×
  • Create New...