Jump to content

agent_x007

Member
  • Posts

    1,078
  • Joined

  • Last visited

Awards

This user doesn't have any awards

Recent Profile Visitors

2,273 profile views
  1. Did you picked "high performance power plan" before testing ? (^may be the cause of dropping NB Frequency)
  2. tRC is timing that should be visible in BIOS (or AIDA64), set it's value to what those two timings (tRP and tRAS) combined to. With your current settings, that would be 18 + 38 = 56. It probably won't make much difference though... as Intel CPUs don't use it much. No worries if it's not in BIOS, just move on to next thing. Also, if you want more information about your memory (like what chips were used), you can try running "thaiphoon burner" program, it provides more information about what they are (it's not 100% right all the time but it's good enough). The last weird thing that strikes me is IO-Ls at 14... Try setting 25 and see what happens. Fair warning : Tweaking this can result in failed boot, and clearing CMOS may be required to make PC boot again.
  3. Drop tFAW to 20 and tRC to value = tRP + tRAS. After this, check bandwidth again.
  4. It looks like badly configured CSM/EFI boot mode, or Secure Boot failure. Have you tried "Load Default" and setting RAM parameters manually ? Are you on latest BIOS ? What's your SOC voltage ?
  5. 1) Your NB Frequency is really low, also try using latest version of AIDA64. 2) He is using Quad Channel, and his score is also pretty low for Quad 3200MHz... 3) Can you provide a screen shot from ASRock's Timing Configuration (v4.0.4) program ? 4) Are you sure CPU isn't throttling from too high temperature ?
  6. PCI-e not working on Win98 is not accurate
  7. Any special 10-year anniversary of WAN show with Linus and Luke (October 9 2012 - October 12 2022) ?
  8. NV patch for DP ? https://www.nvidia.com/en-us/drivers/nv-uefi-update-x64/
  9. Nvidia DP patch was installed ? https://www.nvidia.com/en-us/drivers/nv-uefi-update-x64/
  10. Did you selected "40Hz" as refresh rate of games you are playing ?
  11. @DildorTheDecent @Jumper118@iHardware Shelden Been away for awhile, but I found myself new platform to test Cooling : Eisbaer AIO (modified : 360x45mm + 3x Delta fan) FX-8150 @ 4,94GHz + 16GB @ 2079MHz CL9 1,67V (4x4GB) + Crosshair V Fomula (1703 w/NVMe mod) FX-8150 @ 4,94GHz + 16GB @ 2079MHz CL9 1,67V (4x4GB) + Crosshair V Fomula (1703 w/NVMe mod) FX-8150 @ 4,94GHz + 16GB @ 2079MHz CL9 1,67V (4x4GB) + Crosshair V Fomula (1703 w/NVMe mod) FX-8150 @ 4,94GHz + 16GB @ 2079MHz CL9 1,67V (4x4GB) + Crosshair V Fomula (1703 w/NVMe mod) ^Side note : 420W from the wall (I'm using Corsair AX860)
  12. 1,86GHz tells me it's Core 2 Duo E6300. You should have searched for at least Core 2 Duo E6600/E6700 (2,4GHz/2,67GHz or over +30% CPU perf. at stock vs. what you have). But if current one is fine for your use - good for you. PS. DO NOT confuse Pentium Dual-Core E6600/E6700 with Core 2 Duo E6600/E6700. The former ones will give you problems in your board, while the latter ones will not.
  13. That's what you get for running 2019 benchmark on 2007 hardware (Dual Core on top of that, and probably at 1/3 full speed - if what diagnostic programs are showing is true). PS. I wouldn't bother with anything past R10 or R11.5. IntelBurnTest is also faster to check stability (2 passes at Standard setting are fine for quick check).
  14. You can throw high perf. power plan to see if that changes anything... But first disable C1E/SpeedStep in BIOS.
  15. Just to point out : This MB doesn't support this CPU. EDIT : Disable C1E/SpeedStep in BIOS if you can (it's clearly broken as CPU doesn't go higher in clock speed when loaded with benchmark).
×