Jump to content
NotebookTalk

All Activity

This stream auto-updates

  1. Past hour
  2. Does the 1394 ID update mean that it supports 64GB of memory? Or should I just run the "update bat" like a regular BIOS update?
  3. Brother @tps3443 dodged a scammer bullet yesterday. Glad you were not a victim, Brother T. https://www.overclock.net/posts/29585246/ The scumbag posted the same scam on a Swedish web site. https://www.blocket.se/recommerce/forsale/item/22104267?ci=4
  4. Does anyone know anything about updating the Secure Boot Certificates? My X170KM-G (Origin PC EON17-X) running Windows 11 does not "want" to update, not even by using commands in an elevated Powershell: reg add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Secureboot /v AvailableUpdates /t REG_DWORD /d 0x5944 /f powershell -command Start-ScheduledTask -TaskName "\Microsoft\Windows\PI\Secure-Boot-Update" and restarting twice, as recommended. This is what Windows Security shows me, but Origin PC's page no longer has anything about the EON17-X 2021 version of the X170KM-G --- they have a newer model with the same EON17-X name, but it is a completely different machine from 2023.
  5. - Lowest latency I managed: - Highest bandwidth I obtained (almost saturating the theoretical maximum of 102.4GB/s at 6400MT/s). Stable only up to ~75ºC:
  6. Today
  7. Ok, I really don't have high hopes for the clock values as I got them by dividing the 4 bytes of hex by 32768. As it turns out you have to substract 16384 and then multiply by 2... on each 2 byte chunk of the 4 byte clock value ! See here : https://rog-forum.asus.com/t5/rog-gaming-notebooks/laptop-pascal-vbios-unlocks-quot-wip-quot/td-p/658321 I'll make a version only with power editing that way you can test that out (as it should work fingers crossed), while I fix the clock editing. Here is this [POWER ONLY] version 1.0 : Release v1.0 | [POWER ONLY] Nvidia-vBIOS-Clock-Power-Tweaker · JadeRover/Nvidia-vBIOS-Clock-Power-Tweaker
  8. I'll be testing p3200, p4200 made by your program & the gp106m lol
  9. In games, based on the limited data I've recorded, the modules operate at 55-65°C. In 1 hour of OCCT testing with CPU + Memory, the temperature stabilizes at ~84°C (the module in contact with the thermal pad of the memory's thermal enclosure) and ~79°C on the other module with a 1.5mm thick copper/graphene heatsink. Before using this heatsink, this module stabilized at 89°C in the same 1-hour OCCT test. I'm considering buying 3mm thick heatsinks and removing the thermal enclosure from the memory. The temperatures will likely be lower. I also don't have a water cooler, but I use an IETS GT600 which should make a significant difference. If stability problems occur when your memory reaches 85°C, try decreasing the tREFI and/or increasing the tRFC. For M-die, the tRFC should naturally be higher than in A-die.
  10. How are temps on your dual rank kits? I use the single rank A-die and M-die modules (2x16GB or 2x24GB). I had them tuned pretty decently but ran into heat related memory stability issues when the modules would get up to 85C in combined loads. I do not have the water cooling addon so its probably limited by the air cooling capability. M-die can go up to 8000MT with VDD2 adjusted to 1.2v although I never really used it as I run in Hybrid graphics mode which still has glitches over 7200MT depending on the memory kit used.
  11. 1394GUID shoule be something like SN or UUID for your onboard 1394 device, iirc e.g. just like mac address for ethernet card
  12. Im afraid i dont have more detailed info to provide, just uploaded the files "as is". according to BufferMod this bios support 16GB DDR3 SODIMM module.
  13. I'm confused because the term "1394 ID" is unfamiliar to me.
  14. New scores: https://www.3dmark.com/spy/63490027 https://www.3dmark.com/sn/13862641
  15. I have two sets of memory, both 2x32GB dual-rank, so it's quite different (and demanding) compared to your kit. If your memory is Hynix A-die, you can probably lower the tRFC significantly (384-448). Try making it the same as tRFC2. tRAS also, you can probably reduce it quite a bit (42-54). You should be able to achieve 7200MT/s by increasing the VDD to 1300/1325. If you can't, it may be necessary to loosen the tRCD/tRP slightly to 44. For everything else, it's difficult for me to comment... I went back to using the original memory, Adata 5600MT/s CL46, because its adjustment limit is almost identical to the other set I have (Fury Impact 5600MT/s CL40), both are Hynix A-die. With Fury I can get some slightly tighter subtimings, but without a relevant difference in performance. Perhaps 200 to 300 more points in the CPU score on TS. Without access to manually adjusting SA and VDD2, I can't go any further... My tuning is: RATIO 192 tCL 36 tRCD/tRP 39 tRAS 54 tCWL 34 (32 with Fury) tFAW 16 tREFI 24576 tRFC 400 tRRD 0 tRTP 20 tWR 72 tWTR 0 tRFCpb 320 tRFC2 400 tRFC4 0 tRRD_L 8 tRRD_S 4 tWTR_L 24 tCCD_L 14 (12 with Fury) tCCD_L_WR 64 (56 with Fury) tWTR_S 7 NMode 2 VDD 1300 VDDQ 1250 VPP 1800
  16. No, I don't have it. I'm currently checking the sales website. I haven't flashed the BIOS yet.
  17. Also very important, version 1.0 of my program might be saving the wrong clock values !! I will be making some actual vbios tests on my p3000 in my m6700 this week end. In the meantine no one should try to flash a custom vbios made from my program.
  18. Hello, this is P106m card vbios ? Manual looking at the clock table, it has only one core value of 1290Mhz and all the others are null (FF). For the memory clock it is 1500Mhz (in afterburner clock dual rank mode). Also the power table is a desktop type with 3 values (not supported by my program). Those I read from your vbios are all at 100w. I can make you a custom vbios to try if you want. I made one quickly, boost to 1910Mhz (I changed all the instances of 1290Mhz to 1910Mhz) and mem up to 2000 Mhz you can give it a try, the checksum was fixed as well. You will probably hit a vrel limit and be around the 1850Mhz mark p106m_vbios_checked.rom
  19. Do you have 16GB DIMMs? If the BIOS works and the RAM too then I'll flash
  20. The update procedure should be in the Readme file. It's best to check it before proceeding. I also plan to check the Readme file before flashing.
  21. No I don't run, I wait for others to test it.
  22. Hello. Has the BIOS on your P570WM been updated? It should work without problems using Rufus. Since the Readme is a .doc file, I don't have the corresponding application, so I'll try running it once I find a compatible application and check its contents.
  23. Got the grip, cage light and mic setup and it's really good. I might get the second grip for video work, and I need to get the required lenses for my setup now. I will be getting the full set of Neewer lenses to attach to the rig. I will get a pic this morning and pop up in a bit.
  24. Thank you very much!
  25. @JadeRover gp106 card doesn't seem to work https://drive.google.com/file/d/1MO-UXQ-GLcrlnBZCJ3sgqiiOXfxzizmG/view?usp=sharing
  26. Yes win11 works. I haven't tested it yet, put covering pwr pin might be the fix. Hoping to test it in a week or two
  1. Load more activity
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Terms of Use